Description:
I’m in IT support right now and I’ve got a chance to lean either into more systems work where I am or start pushing toward embedded firmware roles. I keep seeing job posts that ask for C, microcontrollers, RTOS, and hardware debugging, and I’m not sure which side of my current experience actually transfers. How do I decide which path gives me a realistic shot at landing an embedded firmware job, and what should I focus on first if I only have time to build one direction?
2 Answers
Pick firmware. IT support maps cleaner than it looks. Field bugs, serial consoles, logs, weird boot issues - that stuff transfers. Spend 3 months on C, STM32 or ESP32, FreeRTOS, and a logic analyzer. Build one blinking LED, one UART menu, one sensor readout.
iT support can point you at firmware faster than more systems work if you’re hungry for the grind - job posts are scaring you a bit, but your real transfer is debuggging weird edge cases and staying calm when stuff’s busted. Pick C plus one microcontroller board first, then hit UART, GPIO, and basic hardware tools- that combo gets you real signal fast.
Join the conversation and help others by sharing your insights.
Log in to your account or create a new one — it only takes a minute and gives you the ability to post answers, vote, and build your expert profile.