Hardware Engineer

A hardware engineer designs, builds and tests the physical electronics inside products - circuit boards, sensors, power supplies, radio modules, control systems and the enclosures and cabling around them. In the UK this work sits mostly in sectors like defence and aerospace, semiconductors and chip design, medical devices, automotive, scientific instruments, telecoms and consumer electronics. You typically work in a team alongside software/firmware engineers, mechanical engineers and manufacturing staff, turning a product requirement into something that can actually be made, certified and sold.

Starting salary: £28k–£36k
Live graduate jobs: 26 open now
Main way in: Graduate schemes at large engineering employers
They usually ask for: A degree in electronic or electrical engineering is the…

Approximate graduate salary

Typically around £28,000–£36,000 to start, though this varies widely - large defence, semiconductor and chip-design employers and London/Cambridge-area roles tend to sit at or above the top of that range, while smaller firms and regions with lower living costs often start lower. Chartered status and specialisation in areas like RF or analogue IC design tend to lift pay significantly later on.

What you'd actually do

Drawing schematics and laying out printed circuit boards (PCBs) in design software such as Altium, OrCAD or KiCad - deciding which components go where, how tracks are routed, and how the board will be manufactured.
Choosing components from manufacturer datasheets: comparing microcontrollers, regulators, op-amps or connectors on cost, availability, power consumption and temperature range, and checking parts aren't about to go obsolete.
Bench testing: soldering prototype boards, probing them with an oscilloscope, multimeter or logic analyser, and working out why a board that should work doesn't - a large share of the job is debugging.
Writing and running test procedures, then writing up results - test reports, design review documents, bills of materials (the list of every part in a product) and change notes. The documentation load is heavier than most graduates expect, especially in regulated sectors.

Show 3 more

Sitting in design reviews where colleagues pick apart your schematic, and reviewing other people's in turn.
Working with manufacturing: answering questions from the assembly house, investigating boards that failed in production, and tweaking designs so they're cheaper or easier to build.
In chip-focused roles, writing hardware description language (Verilog/VHDL) to describe digital logic, and running simulations before anything is physically built.

How graduates get in

Graduate schemes at large engineering employers - defence, aerospace, automotive, rail, energy and big electronics firms. These are the most structured route, usually with rotations across design, test and manufacturing, and often tied to working towards chartered status. Applications typically open in the autumn and involve online tests, a technical interview and sometimes an assessment centre.
Direct entry as a junior/graduate hardware or electronics engineer at a smaller firm, design consultancy or start-up. Very common - most UK electronics employers are SMEs, and they hire when they have a vacancy rather than on a yearly cycle. Less structure, but often more hands-on design work early.
A year in industry or summer placement during your degree, converted into a graduate offer. This is one of the strongest routes in - placement experience with real PCB design or test work carries a lot of weight at interview.
Degree apprenticeships in electronic engineering, where you're employed from the start and study part-time. A route into the same jobs without the traditional graduate route, though you'd normally choose it at 18 rather than after a degree.

Show 2 more

Via a master's or PhD for specialised areas - RF and microwave design, analogue IC design, power electronics, photonics. For chip design and research-heavy roles a postgraduate degree is common, though not required for board-level work.
Sideways from a test, repair or technician role, sometimes with an HNC/HND topped up to a degree. Slower and less common for graduates, but real.

What employers ask for

A degree in electronic or electrical engineering is the standard expectation. Physics, computer engineering, mechatronics and some general engineering degrees are widely accepted if you can show electronics content; a pure computer science or maths degree is a harder sell for board-level design.
Typically a 2:1, though this genuinely varies - large graduate schemes often set 2:1 as a filter, while smaller firms care more about what you've built and will interview a 2:2 with a strong project portfolio.
Evidence you've actually made something electronic work. Final-year project, placement, hobby projects, Arduino/Raspberry Pi builds, FPGA work, Formula Student, robotics club - interviewers will ask you to talk through a circuit you designed and what went wrong with it.
An IET-accredited degree matters if you want chartered engineer status later. An accredited MEng is the cleanest path to CEng; an accredited BEng usually needs further learning on top. This affects your career ten years out, not your first job.

Show 2 more

Security clearance eligibility for defence, nuclear and some aerospace roles - usually requiring UK residency for a set period. Worth checking early, because it rules some employers in or out regardless of your CV.
Some roles ask for specific tool or language familiarity (Altium, MATLAB/Simulink, VHDL/Verilog, LTspice, Python for test automation). Rarely a hard requirement at graduate level, but naming tools you've used helps.

Skills that matter

Systematic fault-finding

When a prototype misbehaves you need to form a hypothesis, isolate one variable and test it, rather than randomly swapping components - this is the single most-used skill on the bench.

Reading datasheets properly

Component behaviour, limits and recommended layouts are buried in dense manufacturer documents, and most beginner design errors come from skimming them.

Comfort with the underlying physics and maths

Signal integrity, noise, thermal behaviour and power budgets all come back to circuit theory and electromagnetics, and simulation tools won't save you if you can't sanity-check the answer.

Some coding, usually C and Python

Hardware engineers routinely write small firmware routines to exercise a board and Python scripts to automate test equipment and crunch measurement data.

Design for manufacture and cost awareness

A design that works on your bench but can't be assembled reliably or costs too much per unit is a failed design, so you're constantly trading performance against part cost and availability.

Clear technical writing and explaining designs to non-specialists

You'll defend your design in reviews, hand it over to software and manufacturing colleagues, and produce the test and safety evidence that regulators or customers demand.

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 hardware engineer - working on sub-sections of a board under supervision, doing a lot of test, build and documentation while you learn the company's tools and processes. Typically the first couple of years.
Hardware engineer owning complete designs - you take a requirement, produce the schematic and layout, see it through prototype, test and into production, and are the person others ask about that product.
Senior or principal engineer, leading the hardware for a whole product or specialising deeply in an area such as RF, power electronics, analogue design, FPGA or safety-critical systems. Chartered status (CEng via the IET) is often pursued around this stage; timelines vary a lot and are not fixed.
A fork in the road: a technical track (principal/chief engineer, technical authority, architect) or a management track (team lead, engineering manager, programme management). Many employers deliberately offer both so you don't have to manage people to progress.
Longer term, routes out include systems engineering, technical sales and field applications engineering (explaining complex components to customers), product management, engineering consultancy, or founding a hardware start-up. Timeframes here vary enormously by sector and employer size.

What people get wrong

“It's mostly soldering and building things with your hands.”

Most of the week is spent at a computer - in schematic and layout software, in simulation, in spreadsheets of components, and writing documents. Bench time is real but it's a minority of the job, and in large organisations technicians may do much of the building.

“Hardware engineers don't need to code.”

Almost all hardware roles involve some programming - C or embedded C to bring a board to life, Python to automate test rigs and process data, and in chip-oriented roles VHDL or Verilog, which is a full design language in its own right.

“The design is the job, and once it works you're done.”

Getting a prototype working is often the quick part. Qualification testing, EMC (electromagnetic compatibility) and safety compliance, obsolescence management, production yield problems and documentation can occupy far more of a product's life than the original design.

“All hardware engineering is essentially the same job.”

Designing a multi-layer digital board, designing an analogue sensor front-end, designing a radio at gigahertz frequencies and designing silicon are very different disciplines with different tools and maths. Your first job tends to steer which one you become known for, so it's worth choosing deliberately.

Where this varies

The title covers a very broad spread of work. In defence, aerospace, rail, nuclear and medical devices the pace is slower and governed by standards, traceability and formal design reviews, and security clearance or regulatory approval can shape everything you do; documentation is a large part of the job. In start-ups, consultancies and consumer electronics you'll typically cycle through prototypes much faster, touch mechanical and firmware work as well, and have far less process around you. In semiconductor companies (the UK has notable clusters around Cambridge, Bristol and Southampton) "hardware engineer" may mean designing logic in Verilog or VHDL and running simulations, with no soldering iron in sight. Geographically, electronics work clusters around Cambridge, Bristol/Bath, the South Coast, the Thames Valley, the Midlands, Edinburgh and parts of the North West rather than being evenly spread, so location often constrains which sector you can realistically enter.

See all 26 live Hardware 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.