What is the job of an Embedded Systems Engineer?
The job of an embedded systems engineer consists of designing and programming the small computer that sits inside a device and makes it work: a household appliance, a car, a piece of medical equipment, an energy meter, a toy or an industrial machine. That computer, made up of a microcontroller, sensors and a program, usually does a single function and has to do it reliably, with little memory, little energy and sometimes within fractions of a second.
A typical day mixes desk and lab. Code is written and reviewed, almost always in C or C++, tested on a real electronic board, and instruments such as the oscilloscope are connected to see which signals come out and to look for the reason something fails. There are also meetings with the person who designs the circuit, the one who manufactures the product and the one who tests it. A large part of the time goes into finding errors that only show up now and then.
Typical tasks
- Defining with the team what the device must do and what memory, energy and speed it has available.
- Writing the program that reads sensors, controls motors, screens or communications, and reacts to what happens.
- Choosing the microcontroller and the right components together with the person who designs the circuit.
- Testing the program on the board and checking the signals with measuring instruments.
- Finding and fixing errors, whether in the program, the wiring or the timing.
- Setting up automated tests and documenting how the system works.
- Updating the program of products already in use and solving faults that customers report.
Subjects and content usually covered
- Programming in C and C++, data structures and algorithms.
- Analog and digital electronics, and circuit analysis.
- Computer architecture and microcontrollers.
- Real-time operating systems and scheduling of tasks that must be completed on time.
- Communication protocols between devices, such as those used by sensors, networks and wireless connections.
- Signals and systems, and the basics of automatic control.
- Software testing, version control and security of connected devices.
Usual duration and type of training
The most common route is a university degree in a related engineering field, such as electronics, electrical engineering, mechatronics, computer science or computer engineering, which usually takes 4 to 6 years depending on the country and the university. After that, the specifics of the field are learned through personal projects, internships and short courses lasting a few weeks to a few months. Graduate programs and specialization courses of 1 to 2 years also exist. The length and the names of the qualifications vary from one country to another.
How you get there and what is usually required to practice
It is not a degree with that name everywhere: it is a job reached from a related engineering field. The most common background is electronics, mechatronics, computer science or electrical engineering, with the missing pieces filled in through projects, internships or a first position as a junior firmware programmer or test technician.
In general no professional license is required to practice, although in some countries an engineering degree has to be registered with a professional board or council. Medical, automotive and aviation products are subject to strict safety standards, and companies usually train their staff in them. The first job is usually the hardest to get, and a portfolio of personal projects helps show what a person can do.
Skills that help
- Programming carefully in languages close to the hardware, paying attention to memory and execution time.
- Reading circuit diagrams and component data sheets.
- Using instruments such as a multimeter, an oscilloscope and a logic analyzer to see what is happening in the circuit.
- Debugging in an orderly way: forming a hypothesis, testing it and ruling it out until the cause turns up.
- Documenting the work so that other people can maintain it.
- Communicating with the people who design circuits, manufacture and test, who use different terms.
Career paths and job opportunities
- Consumer electronics and appliance companies.
- Car and auto parts manufacturers.
- Medical device and laboratory equipment companies.
- Automation, machinery and robotics industry.
- Telecommunications companies and makers of smart meters and connected devices.
- Small companies that develop their own products, and research centers.
What you are not always told
- Many errors appear intermittently and finding them can take days; patience for debugging is a central part of the work.
- The work has strict limits on memory, power use and cost, so the elegant solution often does not fit and another one has to be found.
- A fault in a device that has already been manufactured is hard and expensive to correct, so a lot of time goes into testing and reviewing.
- Close to a product's delivery date, deadlines can tighten and working days can get longer.
- Part of the day is spent in front of a board and a tangle of cables, and part in front of documents and meetings, more than many people imagine.
How the field is changing
More and more devices connect to networks, which makes it necessary to take care of security and to be able to update the program remotely once the product is in use. Microcontrollers are gaining capacity, and in some cases they run small machine learning models inside the device itself. Simulation tools, automated tests and programming assistants change the way of working, although checking on the real hardware is still necessary. Requirements for standards and certification of connected products are also growing.
Want to know if this is the right career for you?
Take the free vocational test with 5 scientific methods — CHASIDE, Holland, Big Five, MMMG and VAK — to get your personalized profile. You can also explore all university careers or learn about the scientific methodology.