6 ms·
Slightly off-topic, but: Sadly, and for reasons I don't entirely understand, embedded software developers tend to get paid far below similarly-senior desktop, m
by ryandrake 2y ago
Slightly off-topic, but: Sadly, and for reasons I don't entirely understand, embedded software developers tend to get paid far below similarly-senior desktop, mobile, or web developers. I wouldn't recommend a career switch unless you're really interested in the space and willing to accept the compensation difference.
- coumbaya 2y agoYup, switched from embedded (on high-speed trains), to modern backend, x4 my salary. Unfortunate since embedded was super interesting.
- synergy20 2y agowhat do you mean by 'modern backend'? backend is pretty legacy except for the SSR node.js movements these days as far as I can tell, maybe some Go-lang microservices too.
- coumbaya 2y agoMaybe in my head 'modern' is the wrong word, I just meant web backend on modern stack (yes, in go), or at least backend for recent startups with everything in the cloud etc. While I don't really agree with using a shiton of cloud services (especially coming from embedded without even dynamic allocations), it does make for interesting problems related to distributed messaging and things like that.
- mmmlinux 2y agoAny tips on moving from embedded?
- coumbaya 2y agoNot sure I'm the best to give tips because I just had many great opportunities at work, moved from C/C++ embedded to Go embedded (same company) and then Go web backend at another. I wouldn't do anything different, because money is great, but tbh it's less interesting than C on an 8086 or embedded Go with audio/video, lua interpreter, GPS pathing and stuff like that.
- phkahler 2y ago>> Yup, switched from embedded (on high-speed trains), to modern backend, x4 my salary. These comments leave me confused. My Michigan based understanding would have you both poorly paid for embedded work and obscenely paid for backend work. I know some folks in CA make 200K and up, I'm just not sure how common that is. And anyone doing embedded should be at least 100K, so I don't see an easy x4.
- coumbaya 2y agoAh, the explanation is quite simple and I should've included it, sorry. I'm working in France, so I was at more or less 25k in embedded (not poor by french standard for my age, and had a lot of extra perks (like free train) compared to other companies, but not great either. I doubled when I started working for a french startup, and doubled again when I started working for an US-based startup.
- phkahler 2y agoOh you changed countries in there too! That explains it ;-)
- Nico_Log 2y agoOff-topic but, could you share a transition plan with me? I am a pure embedded sw. guy (3 YOE) and have already started to learn DB management and higher-level languages (Java and C#). How was your transition?
- deleted 2y ago[deleted]
- adamnemecek 2y agoProfit margins are low when you ship physical stuff.
- Jtsummers 2y agoThat depends on your market. In the aviation field margins can be pretty high for certain components, but the money is in the longtail (repairs and replacements), not in the initial sales. This leads to bidding low and skimping on budgets in the initial development portion. Once the system is deployed, they'll make plenty of money but there's less that needs to be done to sustain it on the software side.
- thadt 2y agoVisibility. Places that tend to build the kind of hardware that needs custom firmware are so preoccupied with the application space and hardware that the embedded software is almost an afterthought. You finally get the electronics, packaging, and other parts together and then just pass it off to the wizard to infuse it with some spells before it is ready to ship. Pulling together working hardware, packaging, and logistics is non-trivial, often involves multiple people, many moving pieces, extended chunks of time, and heroic efforts to resolve the inevitable problems. When the hardware comes together, it is only after a valiant team effort and at some cost. Everyone knows how hard it was. By comparison, firmware is invisible, usually written by fewer (or one) people, and usually carries lower risk. If your firmware has a bug two weeks before shipping, it's a recompile and we're back on track. If your hardware has a bug two weeks before shipping, it might be the end of the organization. With hardware, it's the physical 'thing' that is the product. With applications, it's the software itself that is the valuable thing.
- Jtsummers 2y agoIt's the companies we work for (worked, in my case). They tend to be hardware companies, and software is not what they see as a critical, or even top ten, concern. It's not "real" engineering (not that most software engineering is real engineering, but in embedded, safety-critical systems it is, or at least should be). Programmers are pegged at a salary somewhere between technicians and lower level engineers. It's gotten better over the years, but there are still huge misunderstandings and misvaluations of the different work. Obviously a hardware system needs hardware engineers, but nearly every hardware system these days involves software systems that do the actual work of coordination, communication, and control. It can't be treated as an afterthought but it often is.
- kevin_thibedeau 2y agoHardware companies have 10x the overhead of a software house. You can't have $200K+ prima donnas calling all the shots when you need a whole cadre of additional labor to handle development, compliance, production, test, packaging, and distribution processes.
- zem 2y agothis is a weird tangent; you don't need to be a prima donna or call the shots for your work to be fairly valued at $200k
- Jtsummers 2y ago> You can't have $200K+ prima donnas calling all the shots Prima donnas? What a twit. I wrote nothing about having software "calling the shots" (I assume that's who you mean as "prima donnas"), but when software is essential to your system, you should have that team at the table in your planning and budgeting efforts. If not, you'll get poor quality because it's low priority. And you'll get poor quality if you reliably underpay people, the good ones leave.
- phkahler 2y ago>> but when software is essential to your system, you should have that team at the table in your planning and budgeting efforts. I like to tell them that software should be on the BoM even though the marginal cost in $0.00. Having it noted as a component helps get people on board with proper versioning, and also raises visibility for something otherwise unseen.
- tester756 2y agoSame in semiconductors. Almost all of my ex-colleagues went to web dev/fin tech :(
- n_ary 2y ago> I don't entirely understand, embedded software developers tend to get paid far below similarly-senior desktop, mobile, or web developers I disagree. At my workplace(regulated industry), Embedded software engineers are paid 2x-5x of other engineering groups. Infact, some of our embedded engineers have so much leverage that they have negotiated 3-4 day work-weeks. Second highest paid group are DevOps(though they don't actually do much for us, as there is separate IT department). And our generic software engineers for web and custom-devices also make decent salary. What you mention could be a US centric thing. Just to make some sense, our embedded software engineers not only write good code, they also maintain their own CI/CD, extensive test coverage, harsh code reviews, very well maintained codebase(unlike on other places I have worked where arcane header files are thrown around and used, no questions asked), automated deployment and update system, A/B testing, rollback and other interesting things typically practiced by higher level(web/desktop/mobile etc.) engineers. I have also worked at a big name AG where they make specialized hardware, the engineers there also made very decent pay but quality of software and development practices were more like script kiddies copy pasting things and calling it a day if the emulator showed correct operation.
- spacemadness 2y agoThis is why I left embedded unfortunately. The other commenter speaking of specializations as key to a more lucrative career is spot on though. I would have loved to have specialized in a subarea involving DSP but didn’t see much of an opening without even more school. And even then the open positions are few and required a lot of digging, and of course prior experience. Watching my colleagues with much easier software gigs get paid more and not be forced to fly to China on a moments notice made me realize I need to switch focus. I did really enjoy some projects I had the opportunity to work on and have no regrets. But I do miss looking at schematics as part debugging.