I disagree. In companies with an embedded software team, no. But in companies where software isn't a focus of what the company does, there are plenty of bits of arduino code shipped on millions of devices. For example, my Beko branded fridge (they sell 3 million fridges per year). And my unbranded motion-sensitive security light.
Arduino had more impact at making people aware that tinkering with controllers might be fun (or profitable) than the actual amount of tinkering with Arduinos (or clones) suggests. Aiming for that "not the core job description" subset of professionals seems like a very good match.
As a professional embedded systems engineer, I'm not the "ideal Arduino customer." But having the arduino ecosystem available means that I can build a one-off for a client in a matter of minutes when it would otherwise take days or weeks. That means I become the "embedded mercenary" that they like and want to hire again :-)