Embedded Systems Engineer
You write the software that runs on a chip with no screen, no operating system and 64KB of memory.
Degree usually expected Hard. Constraints are absolute and debugging often needs an oscilloscope.
Can I actually do this?
We have marked this one as not no-degree-friendly, and want to be straight about why: postings commonly ask for electronics or computer engineering, and unlike many such requirements this one is frequently real — you are working with hardware, timing and physical signals, not just code. It is not impossible without a degree, and hobbyist hardware experience genuinely counts here more than in most fields. But it is a longer road, and we would rather say so.
Who it suits. People who like knowing exactly what every byte is doing.
Runway. Years, and electronics knowledge is part of the job rather than a bonus.
Coming from an electronics or trades background rather than software? That is a real advantage here, and one of the few fields where it is. Desktop Application Developer Backend Developer
Also advertised as
The route
Four stations, in order. Each one is a thing you finish before the next matters.
-
Station one
Learn it free
Only the best few, deliberately. Every one of these is free to use — the pill on each card says exactly what is and isn't free.
The Embedded Rust Book
Free to learn · no certificate
A complete free introduction to bare-metal programming — registers, interrupts, no operating system. Rust rather than C, but the concepts are the concepts.
Verified 2026-07-28
ESP-IDF — getting started
Free to learn · no certificate
A real toolchain for a chip you can buy for a few pounds. Free documentation; the hardware is the cost, and it is small.
Verified 2026-07-28
MQTT specification
Free to learn · no certificate
How constrained devices talk to the world. An open OASIS standard, free to read.
Verified 2026-07-28
-
Station two
Attest strategically
Nothing worth buying. This field hires on hardware you have made work. A board on your desk running your firmware is the credential, and the entry cost is the price of a development board rather than an exam.
Nothing here is worth paying for
No credential needed
Nothing worth buying. This field hires on hardware you have made work. A board on your desk running your firmware is the credential, and the entry cost is the price of a development board rather than an exam.
Checked 2026-07-28
-
Station three
Prove it
A certificate says you passed a test. These say you can do the job.
A device that does something physical
Reads a sensor, drives a motor, lights up on a condition. Video of it working plus the source.
A bug you found with instrumentation
Show a timing or memory problem you traced with a logic analyser, oscilloscope or debugger. This is what separates embedded from application work.
Something running on a tight budget
Fit a real function into constrained memory and say what you gave up.
-
Station four
Get hired
Search these exact titles
Who hires for this. Hardware manufacturers, automotive, medical devices, industrial control, aerospace and consumer electronics.
Interviews here often involve real hardware or a datasheet, which rewards hands-on building over study. That is our reading of the field, not a verified hiring statistic.
On salaryWe don't publish salary estimates. Numbers copied between blogs drift from reality, and a wrong number costs you real negotiating power. When we have a verified public source, it goes here with its date.
Where this route continues
- IoT Developer — the connected-device specialism
- Robotics Software Engineer — the same skills aimed at motion
- IoT Developer — sideways move
- Robotics Software Engineer — sideways move
This page last verified 2026-07-28 · How we verify
The Embedded Rust Book, ESP-IDF getting started and the MQTT specification page fetched and READ 2026-07-28.