Ask HN: Tips for transitioning from web development to embedded/firmware?

I started my career 15+ years ago doing native development (C, C++, etc.), but the last decade I've been doing fullstack web applications. I'd like to transition closer to my roots with a job doing primarily C, C++ or Rust. The natural place seems to be in embedded development or firmware work. How feasible is the transition this late in the game? Any advice?

I'd say just do it. You have been in the industry for 15+ years and you surely know how to network/do interviews. I feel that you are just hesitating or wait for some confirmations. I wrote similar posts so that's my guess, but please criticize me if I'm wrong. My point is, whoever has actually done the transition, their experience may not really help you a lot. They might have a cousin who actually refers them to the company; They might have worked 10 years of embedded projects as a hobby; They might be lucky because 5 years ago there were a huge opening somewhere. I heard of a metaphor about elevators -- Several people ride an elevator to floor 100, and a reporter asked them how they get there -- one of them said he did 1,000 push-ups, another said he read 2 books, and a third said he bumped his head against the elevator's walls. Those experience might be very well relevant, or not. But above all, copying others' experience, in THIS market, probably doesn't work. Now that you are 6 years senior than me regarding SWE experience, I think you already know what to do -- just do it.
There are two issues: 1) transitioning your skills, and 2) persuading someone to hire/pay you for your new skills. Transitioning your skills is possible. But embedded is a different world and a different mindset. You a lot less RAM and a smaller CPU. You may have hard deadlines - the right answer can be wrong if it's too late. You may have multiple threads that have to share data and not corrupt it, no matter what order events occur in. In the worst case, you may not have logging available at all, and you may not have a debugger. (I think the worst I ever had to do was attach a logic analyzer to the address bus, triggered by a specific address, and then use it to look at past memory addresses in order to figure out what path of execution had got me to the point of the crash.) So, yeah. It's a different world. Learnable, but different. Getting someone to believe you can do it enough that they're willing to pay you: I don't have great advice there. I spent almost my whole career in embedded. It seems to me that it's easier to get from there into, say, desktop programming, than it is to go the other way. Your best bet might be to emphasize your native development background, and count on there being a shortage of embedded people.
If you have no logging and no debugger .. you should run away. Fuck debugging something complex by blinking a led. This is a waste of your time. I'm sure you can make Claude help you with this .. but still..logs are important. So is a good debugger and software support for it. It saves so much time in the end.
You can get started learning with any of the amazingly cheap and powerful ESP32, Raspberry Pi, Raspberry Pi Pico, and Arduino stuff out there, along with dirt cheap TANG FPGAs, etc. Get some projects under your belt in your free time. Start with the canonical blinking of an LED, and step it up from there.
I've done both over my career (as well as some other stuff.) While they are very different, if you know C, it's not hard to transition. Getting a job in the embedded space though is obviously a lot harder than web. There are simply fewer jobs to be had. Doing some personal projects in the space may reawaken your C skills, and help demonstrate competence. Good luck!
  1. rkagerer

    Way too much caution in this thread. I've done all kinds of programming including embedded and full stack (from before the latter was even a colloquialized term).

    I absolutely love the degree of control you can get at the microcontroller level. One of my proudest projects had IRQ handlers written in assembly where I counted instruction cycles in order to guarantee worst-case latencies and well-defined impact to realtime activities in the main loop. There were also some lower-priority tasks going on that were cooperatively multitasked.

    Some time later I wrote a JavaScript library that mimicked some of those cooperative multitasking concepts to queue background image downloads and other generic "ITasks" in a manner that maximally utilized available connections (which were extremely limited by servers back then) and allowed on-the-fly reordering. The frontend used it to always ensure whatever image the user was most interested in (i.e. tiny previews, and large version of the result presently hovered over or that we anticipate will be hovered next) came up as close to instantaneous as we could get, and the rest of the large images lazy-loaded in an intelligent order. The result was an experience that felt so much faster than how most other websites operated back then (and ironically even now as bloat has really slowed a lot of sites down), and users loved it.

    So the concepts you learn at one end of the spectrum can definitely benefit you at the other.

    I have much less fun n […]

  2. rleigh

    I transitioned from C++ native development at the age of 39, 7 years ago now. Haven't ever looked back; embedded development is a lot of fun and I'm constantly doing new stuff, be it exploring a new peripheral and making it work just so, or integrating lots of different activities into an RTOS and making sure the timings are still spot on. Yesterday was implementing a radix tree. Or doing mechanical design and test fixtures. There's a lot of variety, and the hands-on application of software, electronic and mechanical aspects to make working systems is very satisfying.

    Not having an electronics background or an embedded background, there was certainly a steep learning curve. Lots of stuff to learn and master. But anyone who already knows C and C++, and who is prepared to knuckle down and get stuck in, will do fine.

  3. ferguess_k

    I'd say just do it. You have been in the industry for 15+ years and you surely know how to network/do interviews. I feel that you are just hesitating or wait for some confirmations. I wrote similar posts so that's my guess, but please criticize me if I'm wrong.

    My point is, whoever has actually done the transition, their experience may not really help you a lot. They might have a cousin who actually refers them to the company; They might have worked 10 years of embedded projects as a hobby; They might be lucky because 5 years ago there were a huge opening somewhere. I heard of a metaphor about elevators -- Several people ride an elevator to floor 100, and a reporter asked them how they get there -- one of them said he did 1,000 push-ups, another said he read 2 books, and a third said he bumped his head against the elevator's walls.

    Those experience might be very well relevant, or not. But above all, copying others' experience, in THIS market, probably doesn't work. Now that you are 6 years senior than me regarding SWE experience, I think you already know what to do -- just do it.

  4. tptacek

    I started my career in C/C++ and have done a fair amount of embedded work. In terms of actually doing stuff, there has never in the history of the world been a better time to do low-level and embedded systems work. The right advice here: find a project, scrounge the parts, and have an agent do basic bring-up work for you. If your last serious C work was 15 years ago, I think you'll be astonished how quickly you can progress to the "rewarding" part of any project.

    If your question is instead how you make a career transition to embedded/firmware work, that's much trickier. The obvious concern is AI's impact on the job market, but I'm chiming in to observe that this isn't the biggest problem with a web->embedded transition. Good jobs doing embedded stuff, at least for people who don't already have a pedigree doing that work, has for as long as I can remember been a bottleneck for people wanting to do this stuff. There's simply a lot more high-level work to be done than low-level work.

    I can see bright spots potentially ahead; I'm not a big Jevon's Paradox person but one kind of clearly Jevon-y area is hardware, because we've zorched one of the biggest impediments to getting new projects off the ground. But it hasn't happened yet, and might not.

More from this day

2026-11-22