Embedded Software Engineer

An embedded software engineer writes the code that runs inside physical products rather than on a PC or phone — things like medical devices, car control units, industrial machinery, smart meters, drones, satellites and consumer electronics. The work sits close to the hardware: you're programming microcontrollers (small single-chip computers) to read sensors, drive motors, talk to other chips and do it all reliably within tight limits on memory, processing power and battery life. You typically work inside a product development team alongside electronics and mechanical engineers, testers and sometimes regulatory or safety specialists.

Starting salary: £28k–£38k
Live graduate jobs: 12 open now
Main way in: Graduate schemes at engineering, defence, aerospace, automotive…
They usually ask for: A degree in electronic engineering, electrical and electronic…

Approximate graduate salary

Typically somewhere around £28,000–£38,000 to start, but this varies a lot. Smaller manufacturers and firms outside the South East tend to sit at the lower end; large defence, semiconductor, automotive and aerospace employers, and roles in Cambridge, Bristol and London, tend to sit higher. Treat any figure as a rough guide and check individual adverts.

What you'd actually do

Writing and debugging C or C++ that runs on a microcontroller or small embedded Linux board - often code that reads a sensor, controls a motor or actuator, or moves data between chips over interfaces like SPI, I2C, UART or CAN bus.
Sitting at a bench with the actual hardware: flashing new firmware onto a board, stepping through code with a debugger, and watching signals on an oscilloscope or logic analyser to work out whether a bug is in your code or in the electronics.
Reading datasheets and reference manuals - long technical documents for chips and sensors that tell you which registers to set and what the timing constraints are. New engineers are often surprised how much of the week this takes.
Writing test code and running things on the bench or in a test rig, including unit tests that run on a PC and hardware-in-the-loop tests where your firmware runs against simulated inputs.

Show 3 more

Talking to hardware engineers about schematics and board bring-up (getting a brand-new circuit board to boot and show signs of life for the first time), and raising issues when a design makes the software harder than it needs to be.
Working through code reviews, version control (Git) and issue trackers, and in regulated sectors writing or updating requirements and traceability documents that link each requirement to the code and tests that satisfy it.
Optimising: cutting memory use, reducing power draw, or making an interrupt routine fast enough to meet a timing deadline.

How graduates get in

Graduate schemes at engineering, defence, aerospace, automotive and electronics companies - common, and often structured with rotations across firmware, hardware and test. These usually recruit in the autumn for the following summer.
Direct entry to a junior or graduate embedded/firmware engineer vacancy at a small or mid-sized company. This is very common in this field: a large share of embedded work happens at SMEs and product design consultancies that hire ad hoc rather than on a scheme, so job boards and speculative applications matter more here than in, say, banking.
A year-in-industry placement or summer internship during your degree, which often converts into a graduate offer. This is probably the single strongest route in and is worth planning for early.
Moving across from a broader software or electronics job after a year or two, having picked up C and some hardware exposure. Reasonably common.

Show 2 more

A degree apprenticeship in electronic or software engineering - an alternative to the traditional graduate route rather than a route for graduates, but worth knowing it exists.
A master's or PhD in a relevant area (embedded systems, robotics, signal processing, RF). Not required for most jobs, but normal in research-heavy areas like space, defence research and advanced driver assistance.

What employers ask for

A degree in electronic engineering, electrical and electronic engineering, computer engineering, computer science, physics, mechatronics or robotics. Unlike general software roles, the subject does matter somewhat here - employers want evidence you understand hardware, not just code. Computer science graduates get hired readily if they can show low-level or hardware project work.
A 2:1 is the most commonly stated requirement, though plenty of smaller employers care far more about what you've built than your classification and will interview a 2:2 with a strong project portfolio. Some large schemes also set A-level or UCAS point thresholds.
Practical C programming. This is close to non-negotiable - embedded work is still overwhelmingly C, with C++ common and Rust appearing in some places. Python is useful for test scripts and tooling.
Demonstrable hands-on experience: a final-year project, a placement, Formula Student or robotics team, or personal projects on Arduino, STM32, Raspberry Pi Pico or ESP32. Being able to talk through something you actually debugged carries a lot of weight at interview.

Show 2 more

Security clearance eligibility for defence, aerospace and some government-adjacent work. This usually requires UK residency for a number of recent years and can rule candidates in or out regardless of technical fit - check before applying.
Professional qualifications are not needed to start, but many employers support working towards Incorporated Engineer (IEng) or Chartered Engineer (CEng) status, usually through the IET or IMechE.

Skills that matter

C programming with a clear mental model of memory

You are manipulating pointers, fixed-size buffers and hardware registers directly, with no garbage collector and often no operating system to catch your mistakes.

Systematic debugging on real hardware

When a device freezes once an hour, you need a method - narrowing down whether it's your code, the compiler, the circuit or the power supply - rather than guessing and recompiling.

Reading datasheets and electronic schematics

Almost every new feature starts with working out from a chip manufacturer's documentation which registers and timings you need, and tracing which microcontroller pin is wired to what.

Understanding of real-time behaviour, interrupts and concurrency

Embedded code often has hard deadlines, and a huge proportion of nasty bugs come from an interrupt firing halfway through something else and corrupting shared data.

Test discipline and version control

Firmware on a shipped product can be expensive or impossible to update, so catching defects before release matters far more than in web software.

Explaining software constraints to non-software colleagues

You'll regularly need to persuade a hardware or mechanical engineer that a design decision costs you weeks of firmware work, before the board is committed to manufacture.

Putting these on a CV? We counted which skills 12,914 live graduate adverts ask for, and what to do with the answer — part of our application advice.

Where it leads

Graduate/junior engineer: you work on well-defined pieces of a larger system - a driver for one sensor, a bug fix, a test harness - with code reviewed closely. Typically the first year or two.
Embedded software engineer: you own whole modules or subsystems, do board bring-up, and are trusted to make design decisions. Most people reach this within roughly two to four years, though it varies by employer and how much you're exposed to.
Senior engineer: you design the firmware architecture for a product, set coding and test standards, review others' work and act as the software voice in product-level design discussions.
From there the path usually forks. Technical: principal or lead engineer, systems architect, or specialist in an area like functional safety, embedded security, RTOS internals, DSP or hardware-software co-design. Management: team lead, engineering manager, then head of engineering. Many employers now have genuine parallel technical and management ladders, but not all do - at smaller firms promotion may mean taking on management whether you want it or not.
Common sideways moves include systems engineering, hardware or FPGA design, test and verification, field applications engineering (technical pre-sales for chip vendors), or contracting - day-rate contract work is widespread in this field, particularly in automotive and defence, and experienced engineers often move into it. Timelines across all of this vary widely.

What people get wrong

“It's a software job, so you can do it from a laptop anywhere like a web developer.”

Much of the work needs physical access to prototype hardware, test rigs and lab equipment, so embedded roles are generally more office- and lab-based than mainstream software roles. Hybrid arrangements exist but fully remote embedded jobs are relatively unusual.

“Embedded means working with old, unexciting technology because it's all still written in C.”

C dominates because it gives precise control over memory and timing on chips with tiny resources, not because the field is stagnant. The actual products - electric vehicle powertrains, satellites, surgical robots, machine learning running on microcontrollers - are often more technically demanding than typical application software.

“You spend your time writing new features.”

A large part of the job is investigation: reading datasheets, reproducing intermittent faults, and proving whether a problem is yours or the hardware's. Debugging and integration often take more time than writing the original code.

“It pays much less than web or app development, so it's the less commercial choice.”

Starting salaries are often somewhat lower than top-paying general software roles, but experienced embedded engineers - especially in safety-critical, automotive, semiconductor or defence work - are in persistent short supply and are paid accordingly. Contract rates in the field can be high.

Where this varies

The day-to-day differs enormously by sector. In safety-critical work (medical devices, aerospace, automotive, rail, nuclear) you'll spend a substantial share of your time on requirements, documentation, traceability and formal verification against standards such as IEC 62304, DO-178C or ISO 26262 - the pace is slower and the paperwork is real work, not an afterthought. In consumer electronics and startups, releases are faster, process is lighter and you may be the only firmware person on a product. Semiconductor companies focus more on low-level drivers, silicon bring-up and support for customers using their chips. Company size matters too: at a large employer you might own one subsystem for a year, whereas at a small one you could be doing firmware, PCB testing, production test scripts and customer support in the same week. Geography also clusters - Cambridge and the Thames Valley for semiconductors and connectivity, Bristol and the South West for aerospace and defence, the Midlands and the North West for automotive and industrial, central Scotland for electronics and offshore technology.

See all 12 live Embedded Software Engineer jobsFrom employers' own careers sites, updated daily Tailor your CV for this roleFree with an account, 3 a month

General guidance about the role across the UK market, not about any specific employer. Entry routes and requirements vary — always check the individual job advert.