Hardware Development Engineer

About the role

Hardware Development Engineer defines circuit solutions and validation platforms that turn system requirements for Graphcore processor systems into buildable hardware. The role connects board design, bring-up, validation, and production across a single workflow.

Software engineers turn product ideas into working code. Engineers work in small teams, review each other's work, and ship in small batches. Most teams follow agile practices such as sprints and daily standups. Engineers also write tests, fix bugs, and improve performance. The field values clear communication as much as technical skill. Engineers spend part of every week on planning, code review, and debugging, not just writing new code. The ability to explain a technical decision in plain words separates strong engineers from the rest.

Key facts

What you'll do

Evidence-based measurements and reviews guide design decisions, linking silicon, architecture, software, and PCB CAD specialists. Schematics, layout constraints, and testable hardware are produced when system requirements are converted into circuit solutions and validation platforms. Boards move from definition through schematic capture, layout support, bring-up, and production transfer to reach volume production.

Requirements

Strong digital circuit design and validation skills are required, including DCDC regulators, power delivery, resets, clocks, and control interfaces. Experience developing processor-based systems and working with interfaces such as Ethernet, PCIe, DDR, USB, QSPI, and JTAG is necessary. Practical lab depth in bring-up, debug, margin testing, and validation using oscilloscopes, logic analysers, and signal generators is essential. Understanding of server architecture, such as BMC, NIC, and SSD, with SERDES experience adds further value. An ownership mindset, clear communication, and the confidence to challenge, decide, and work across disciplines are required. Applicants must have the legal right to work in the UK as this requirement is mandatory. No visa sponsorship or support for visa applications is available for this role.

Practical notes

Typical interview steps

Hiring for engineering roles usually starts with a recruiter screen, followed by one or two technical rounds. Candidates often solve a coding problem, discuss past projects, and answer system design questions. Some loops include a take-home task. Final rounds typically cover team fit and give candidates a chance to ask questions. Interviewers look for how you break down an unfamiliar problem, not just whether you reach the answer. Practicing a few problems aloud and reviewing your own past projects are the best preparation.

Good to know

Hardware engineers design and validate physical systems that bring processors to life. Digital circuit design, power integrity, and signal integrity are central to this field. Teams rely on measurements, design reviews, and margin data to make decisions. Oscilloscopes, logic analysers, and signal generators are standard tools for bring-up and debug. Collaboration across architecture, firmware, software, and PCB CAD is common in hardware roles. Evidence-based challenges guide decisions in high-performance compute environments.

Questions to ask

Useful questions for the interview: what a typical week looks like, how work is assigned, what tools the team uses, and how feedback works. Asking how the role has changed recently and what the team wishes it had known when joining is also reasonable. Questions about the manager's priorities are especially valued.

Career growth

Engineering careers usually progress from individual contributor to senior, staff, and principal levels. Some engineers move into management and lead teams of five to twenty people. Others stay on the technical track. Growth follows demonstrated impact, not tenure alone. A typical engineering ladder has clear levels with defined expectations for scope, quality, and mentorship. Moving up usually requires owning outcomes end to end rather than completing assigned tickets.