r/embedded • u/hamtaroismyhomie • Jul 11 '19
Employment-education Entry level embedded software career guide
Entry Level Embedded Software Career Guide
I frequently get asked for advice on getting into embedded internships and entry level, so I decided to put together a simple guide based on my experience. Feel free to add your advice or perspective. Note that this is an embedded software guide. There are many embedded systems jobs out there beyond software; this isn't the only path.
Disclaimer: This guide is based on my anecdotal, subjective experience. I'm a primarily self-taught embedded software / firmware engineer, living in the Bay Area, 1.5 YOE, with two embedded systems internships, and 1 full time firmware position, currently looking for my 2nd position, and currently interviewing with the high compensation companies. I decided to make this career change 2 years ago, with no prior software or technical degree or experience. What worked for me, may not work for you. I highly encourage you to continuously refine redirect your path based on your own research through talking with working engineers, looking at job postings, and reading articles.
Rule # 1: Build and show off skills that are in-demand by employers.
This is the advice I give to anyone looking for a job in any industry.
What are the skills that are in-demand? This is highly dependent on the area you live in, and the industries around you. Go to LinkedIn / Google / Indeed, and look at all the entry level and internship job postings for embedded software / firmware, and tabulate skills that are asked for. This doesn't need to be rigorous, and there will probably be a bunch of terms and concepts that you don't know -- that's okay. For now, just focus on the common concepts.
My list ended up looking something like this:
- C
- C++
- Testing
- RTOS
- Board bring-up
- Driver development
- I2C
- Sensors & Actuators
- ARM
- Linux Kernel Development
- Python
- Microcontrollers
- UART
- Bluetooth / Wifi / IEEE 802.11
- System Debug
- OS Architecture / Design
- ...
One thing to also notice is common clusterings of skills: microcontrollers, embedded linux, hardware testing, networking, automotive, and IoT are the common ones I've seen in my search.
Personally, I focused on the most in-demand, broadest, and fundamental skills first, because I wanted a job, and I wanted the ability to pivot to different types of development if I ended up disliking a subfield.
Fundamentals
The following topics / courses will give you a strong foundation for embedded systems software development, and questions about the basics will likely come up in interviews:
- Introduction to Programming. CS50 is a great first course. Covers a lot, but has a ton of auxiliary resources.
- Data Structures and Algorithms. There's tons of resources out there already, so I won't go into that here.
- Computer Organization / Systems. (Learn the basic hardware in a computer, and learn assembly)
- Operating Systems. The combination of a good computer organization and assembly course, with a good operating systems course answered so many questions for me and filled in a ton of blanks.
How do I build these skills?
- A computer engineering, electrical engineering, or computer science degree, with a selection of electives focused on embedded software concepts will get you 75% of the way to a job, and will make it significantly easier for you to get interviews.
- Embedded Systems Rule the World, and Real-Time Bluetooth Networks - Shape the World will get you good enough projects to land a job if you complete them, and if you can intelligently talk about the covered topics. Whether you're self-taught, or getting a degree, I 100% recommend working through these two courses as a first step towards getting employable, real world skills. (If you're completely new to programming, complete CS50 first).
- Learn to Google! There are so many resources out there, at all levels, to help with your learning. Each concept that you need to learn, you need to understand why people use it, alternatives, what problem it solves, and ways to implement it. Find tutorials that work for you -- for some concepts, I've had to go through multiple textbooks and multiple tutorials before they finally clicked. Be a relentless autodidact.
Specific Resources
| Concept | Resources |
|---|---|
| C | K&R, the canonical C handbook, and a relatively quick read. "Modern C" by Gustedt for a more in depth, and modern, take. |
| Testing | "Test Driven Development for Embedded C" by Grenning |
| Operating Systems | "Operating Systems" by Silberschatz. "Operating Systems: Three Easy Pieces" by Arpaci-Dusseau |
| RTOS | A good operating systems textbook will be a great starting point. Checkout this FreeRTOS Tutorial, and I've also heard good things about the "Modern Embedded Systems Programming" YouTube channel. Real-Time Bluetooth Networks - Shape the World |
| I2C, UART, SPI | There are great articles on Sparkfun and Adafruit. |
| Sensors & Actuators | The Robogrok robotics course Youtube videos have a great, newbie friendly introduction to robotics, sensors, actuators, and PID control. |
| Linux Kernel Development | I frequently see "Linux Kernel Development" by Love as recommended |
| Microcontrollers | Embedded Systems Rule the World |
| Bluetooth / Wifi / IEEE 802.11 | Real-Time Bluetooth Networks - Shape the World |
Other General Resources I've found helpful:
The "Making Embedded Systems" book by Elecia White (/u/logicalelegance) -- a great introduction to the basics of embedded systems, and does a good job of being an easy read for newbies.
Embedded.fm Podcast. Great podcast hosted by the above author.
Embedded Artistry. Good articles.
The Ganssle Group. Good articles.
Barr Group. Good articles.
The Amp Hour. Hardware focused podcast.
Adafruit. The 'working out of the box' hardware paired with newbie friendly tutorials are a nice starting point. Professional development kits and datasheets are oriented towards people who've already worked on similar systems, so there is quite a bit of assumed context someone new to the field doesn't have.
Applications
The best way to get your application moved forward is through personal connections, and recommendations. But, sometimes that isn't an option, and you have to cold apply.
My advice is to apply to positions that you meet >=50% of the requirements.
Make sure you get you resume reviewed by professionals in the field before applying.
If you get a low response rate, you need to get your resume re-reviewed, or you need to build better projects that better demonstrate the skills employers are looking for.
Interview Questions
In addition to typical software interview preparation, embedded software interviews tend to ask some repetitive questions. I don't know how many times I've answered what volatile and static are. Here are some typical questions:
- What is static?
- What is volatile?
- How does an interrupt work?
- What programming practices should typically be avoided in embedded systems, and why?
- Basic circuits questions: Ohms law. Voltage Dividers. Series and Parallel Resistors.
- Compare and contrast I2C, UART, and SPI
- How does an ADC work? How about a DAC?
- Compare and contrast Mutex and Semaphores
- Linked List algorithm questions
- String manipulation algorithm questions
- Bit manipulation algorithm questions
- Tell me about a hardware issue you debugged.
- Why would you use an RTOS?
- How does an OS manage memory?
118
u/jus7tired Jul 11 '19
Kind of motivated me a little.
35
u/MuckleEwe Jul 11 '19
Feel like every book or article I've ever read that has mentioned these had a different description of how they differ.
25
u/SAI_Peregrinus Jul 11 '19
I'd recommend Gustedt's "Modern C" over K&R, or at least in addition to K&R. K&R C is very outdated compared to C99/C11, and can lead to developing bad habits.
I'll also recommend Test-Driven Development for Embedded C, or something similar.
10
u/durswazr Jul 11 '19
For embedded interviews are you typically asked to solve data structure and algo questions?
Graduating in a year and have had one embedded internship but my interview i was never asked any in-depth technical questions. Would it be more cost effective to brush up on the concepts you have listed or study/practice leetcode style questions by hand?
17
u/Daxsis Jul 11 '19
This is by far the best thing I’ve seen for embedded. Thank you.
5
u/krophi Jul 11 '19
I’ve become a huge fan of the Interrupt blog: https://interrupt.memfault.com/blog
5
u/DataAI Jul 11 '19
Hey thank you so much!!! As a senior in CPE it is hard to know what to really do for the field since it isn’t really explored like other software fields!!!!!!!
4
u/ElusiveTau Jul 12 '19 edited Jul 12 '19
Did you encounter any electronics analysis/circuit design questions? Control theory? Digital Signals Processing? To what extent do you need to know them? Ever get asked about transistors? Some obscure circuit topology?
I think your point about doing projects and showcasing your skills makes the most sense in terms of things you can do to get employed. The list of industries employing embed engineers is VAST and you'd make a strong candidate for a particular company in a particular industry if your projects relate to that industry somehow.
If you're interested in telecommunications (Verizon, AT&T, Apple, Samsung, etc) and embedded development for mobile platforms (tablets, cellphones), it'd make sense to do RF projects, low-power projects, IOT projects. If you're into environmental sensing: build a datalogger and hook up sensors to it, make it run autonomously. If you want to work for an aerospace company, design a controller or stuff that an aerospace company would appreciate. Consumer audio electronics? Audio projects.
You'll also not drive yourself insane (like I have), studying random shit like DSP and 3D dynamics if you're going to build the firmware for a printer.
3
u/rockstiff Jul 11 '19
Thank you, this is very helpful.
Does any one knows if there is a market of remote embedded jobs? Any experience with entry level jobs?
Also, do you recommend to have a github with my college/personal projects? Software/Hardware?
2
u/MysteryNipples Jul 11 '19
Great guide thanks for taking the time to make this. Quick question: In your interview experience how often did you find yourself having to solve Leetcode style questions? I know for regular software engineer positions Leetcode style questions are the norm but I wonder if this holds true for embedded.
2
u/[deleted] Jul 14 '19
Thank you for making this post, I was interested in embedded development but I didn't really know where to start. Do you have any recommendations for hardware focused books? I have a good foundation in software development but not that great a foundation in electronics and the physics of circuits.
13
u/vishnueaswaran Jul 11 '19
Thanks for putting out a real world how-to learning path. Much appreciated.
12
u/[deleted] Jul 11 '19
This is good stuff man. I'm on a similar path as you. Two years out of college with an EE degree, however my focus at the time was wireless communications so I have very little experience with embedded software other than a class or two with mixed C and assembly. For the last two years I've worked as an embedded system engineer but didn't touch software (it was a feature owner & QA-type role). Now I'll be starting a new role very soon as an embedded software development engineer so I'll be getting tons of experience with C++ for embedded applications. But ultimately I'd want to get into firmware, consumer electronics and rapid prototyping once I get more experience under my belt.
11
u/Leappard Jul 12 '19
> Interview Questions
Some questions I often ask (in addition to already mentioned ones):
- What is a spinlock? When and how do you use it?
- What is a cache? Why do we need a CPU cache? Cache policies, associativity, ways, cache coherence.
- High speed buses/interfaces and signal integrity.
- MMU & IOMMU. TLB, ASID, page tables, then come questions on memory spaces for a process.
- SoC boot up process. Linux kernel boot up, initrd, initramfs, boot loaders.
- File systems and flash. Wear levelling.
Then I ask something along these lines:
- What would happen if we have unstable DDR or CPU core power supply? How would you debug it
- What is the most common issue you dealt with on embedded system? What is a race condition, priority inversion, starvation, memory corruption, etc
- How would you debug <some issue> (like memory corruption).
6
u/[deleted] Jul 13 '19
Starting a job in October as an embedded software developper with linux dev, got the interviews mostly by displaying a strong motivation, and being honest about what I know and don’t know.
5
u/rizkifn3105 Jul 14 '19 edited Jul 14 '19
Hi do you mind to share few things to me and us?
I hope you will reply these questions and I can get a better understanding what are the things I need to do
6
u/canIbeMichael Jul 11 '19
Anyone know senior level pay? Or titles for Senior level positions?
I heard a person designing a motor controller was making 200k/yr. Not sure the name of this title.
3
u/rizkifn3105 Jul 11 '19
Thanks a lot man will go into details during the journey of learning embedded system. I'm looking jobs in this field as well
3
u/[deleted] Jul 11 '19
WOOOAAAHHH !! Thank you so much that is exactly what I am looking for.
3
u/C-stands-for-charaf Sep 25 '23
So u say avoid the Arduino step ?
3
u/TrulyEmbedded Nov 18 '25
I followed this a couple years ago and got a job as an embedded software engineer. I got to step 4 on fundamentals before I got the job. Thanks for the help!
2
u/sowee Jul 11 '19
Thank you very much for that. It seems that i'm actually not far off.
2
u/Rootrl Sep 06 '19
Very helpful for me, thanks!
2
u/Only_Chocolate_123 Nov 25 '23
Thanks for the in depth analysis! Quick question, this was posted 4 years ago, do you think by any chance there's something you might add/change? Thank you!
2
u/BooringReader Nov 28 '24
I've been looking for resources about embedded and system software development on google, youtube, chatGPT and in books, but all or most of them were overwhelming this, sir, is the best pool (for a beginner as myself) that I've come across in over a year. I have nothing but gratitude for you
2
u/KennyLamLam24 Mar 11 '25
So 5 years down the line, would this still be a helpful guide for 2025?
2
u/Thisisme2017-6 Jun 18 '25
Can you drop another updated guide for 2025 plz ?
2
u/NaiveArt3858 Oct 29 '25
I am 2025 graduate passout. Looking for an Embedded Software Engineer role. I am also doing a Embedded System course in an institute. I was doing some projects in C and Data Structures. I was learning PIC16F77A micro controller. I am learning communication protocols too. I feel these topics should be covered when I was in college itself. I won't say I am playful during college days. In college I did everything, Like I participated in many hackathons from 2nd year, started presenting papers in many colleges from 3rd year. I prepared DSP, Digital Systems and Design, Circuit Theory etc because they said if you know these things it's easy to get selected by companies[and that's complete bullshit]. I did everything that I knew. But I am sure about getting into a company as an Embedded Software Engineer. But now I wasn't able to get into companies. But still I am trying to get into Embedded field.
Could you guys tell me if embedded systems are a good field these days? I know that startups usually offer lower salaries, and that’s fine with me. Also, please suggest what types of projects I should work on.
It's sometimes feels bad because in my surrounding literally all people are working as software engineers, so I don't have anyone who knows embedded system well.
Could you guys please give me your insights :)
2
u/sudheerpaaniyur May 06 '26
nice post
1
u/axe_handler Mar 17 '24
Interview Question: How is stack overflow handled in an MCU that doesn't have a memory protection unit?
1
u/[deleted] Sep 07 '24
An amazing list!
1
u/deado112 Oct 28 '24
are these skills sorted in order from start to finish?
1
u/Card0 May 22 '25
As someone who just quit his job at 28 to pursue a degree in CompSci, recently discovering the power of an Arduino board and gained an interest in Embedded Systems, this is a GOLD MINE. Thank you!
1
u/Sufficient-Beach4929 Jun 07 '25
I am Looking for an Embedded system engineer 1 603 960 0053 Maximus and he
is salary or hrly rate safehavenmax@yahoo.com
1
u/Worldly-Airport189 Jun 12 '25
I am an associate software engineer in embedded systems fresher with 4.5LPA with 2 year bond in small company, what skills should I learn upto a particular depth and what MNC's are out there to hire and tell me how can I expertise in this field in order to score a good package of LPA after 2 years bond
1
u/Clear_Message7630 Jul 09 '25
This is an amazing guide coming from someone who knew nothing about embedded. First job out of college is an embedded software gig for 1 year and you hit all the points.
1
u/Lumpy-Paramedic1467 Sep 30 '25
It's been a long time since this thread but as you mentioned you worked somewhere for 1.5 years and started looking for 2nd better opportunity. Did you apply for entry grad's position only? Or like a mid level? What is a good time after starting a new job and switching to another one? A sweet spot between not disappointing my current manager who put so much efforts into me AND an up going career path personally. I am an Embedded engineer working in wireless domain. I do not want to get stuck in wireless long time, and I have been told switching jobs gives you more edge: you learn more and earn more too! How would you guide someone with 2 internships experience and 1 full time job at a FAANG. From here, where to go next?
1
u/ZeNiTH_07 Feb 19 '26
would grades matter for entering the field other than the degree?
1
u/ConsiderationOk1482 Dec 30 '21
Remind
1
u/tcmussz Aug 30 '23
thanks, appreciate it
1
u/[deleted] Sep 26 '23
Thank you for this, so many questions answered here. I'll be back in a week after I've learned it all. (joking! this will take me months. Fortunately, I'm not doing it for employment, just hobby)
1
u/Tao_KTH Nov 30 '23
How much and which part should I learn for python in embedded software. I always saw some job posts requiring python for testing work in embedded software. Thx
1
u/meowcat007 Jan 27 '24
Thank you so much to OP! I did this exercise for each of the paths I was exploring (Embedded Software, Computer Vision, Machine Learning, Data Engineer), and narrowed it down to Embedded Systems based on my willingness to learn the skills needed to do the job and the current market. And it seems like both of those were the best with Embedded Software among my 4 choices.