Hardware Engineer interview questions, with worked answers

How to use these questions

Many hardware interviews put a schematic in front of you, or describe a board that misbehaves. Think aloud: what the circuit should do, what could go wrong, what you would measure first and why. Then tell them about a board you designed, the hardest bug you found on it, and how it ended.

What a hardware engineer is expected to know

• The circuit: circuit designAsked in 33% of hardware engineer ads (as of 5 Nov 2026).Design analogue and digital circuits from a requirement, with the calculations that show they work in every corner., power suppliesAsked in 13% of hardware engineer ads (as of 5 Nov 2026).Design converters and power supplies that stay efficient, cool and stable under load. and microcontrollersAsked in 2% of hardware engineer ads (as of 5 Nov 2026).Choose a microcontroller and design the power, clocks, reset and interfaces around it. or FPGAsAsked in 8% of hardware engineer ads (as of 5 Nov 2026).Know when programmable logic fits, and work with the people who write its VHDL or Verilog..
• The board: PCB designAsked in 20% of hardware engineer ads (as of 5 Nov 2026).Plan a board's stack-up, placement and routing with the layout engineer, and review the layout before it is made., signal integrityAsked in 2% of hardware engineer ads (as of 5 Nov 2026).Keep fast signals clean: impedance, terminations, return paths and the checks that prove them. and electromagnetic compatibilityAsked in 21% of hardware engineer ads (as of 5 Nov 2026).Design so the product neither disturbs other devices nor is disturbed by them, and pass the tests..
• The product: design for manufacturingAsked in 3% of hardware engineer ads (as of 5 Nov 2026).Design boards that the factory can build and test reliably, with the suppliers' rules in mind., testing and the safety standards of the industry.
• The team: firmware, layout, mechanics, test and production.

Tools come up side by side and none is a must: Altium Designer, KiCad, Cadence OrCAD and Allegro, or the Siemens tools that were Mentor Graphics for schematics and layout; LTspice or another SPICE simulator for circuits; oscilloscopes, logic analysers and spectrum analysers in the lab. Panels want the reasoning more than the tool.

From requirement to board

How do you go from a requirement to a schematic?

What they check: a method from need to circuit.

Short answer: "I list the functions, interfaces, power budget, environment, cost and the standards the product must meet, then draw a block diagram and agree it. For each block I choose an approach and the key parts, do the calculations, simulate the critical parts and draw the schematic. A schematic is the drawing of every part and connection; it should carry the reasoning too, in notes a reviewer can follow."

The full answer: Most late changes trace back to a requirement nobody wrote down.

A weak answer: "I copy the reference design from the datasheet." Follow-up: "The reference design does not meet your temperature range." Say what you check.

How do you choose components, and what do you check besides the cost?

What they check: parts chosen for the product's whole life.

Short answer: "Beyond the function and the cost, I check the ratings with margin over temperature, availability from more than one source, the lifecycle status, the package for assembly, and qualifications the industry needs, such as automotive grades. I ask the buyers early, because a part that cannot be bought is a redesign later."

The full answer: The cheapest part is expensive if it is out of stock when production starts.

A weak answer: "I take whatever the distributor has." Follow-up: "Your main part goes on allocation for a year." Say what you do.

How would you design the power supply for a board with several voltage rails?

What they check: power as a design, not an afterthought.

Short answer: "I add up the current of every rail with margin, then choose switching regulators where efficiency matters and linear ones where noise matters. I check the start-up order the chips need, the input protection, the ripple each load can take, and the heat. On the board, short loops and a solid ground keep the converters quiet."

The full answer: Many board problems that look like logic faults are power faults.

A weak answer: "One regulator per rail and done." Follow-up: "The processor resets when the radio transmits." Say where you look.

What do you watch for in a PCB layout, and how do you work with the layout engineer?

What they check: the link between circuit and copper.

Short answer: "I give the layout engineer a placement plan, the critical nets with their rules, the stack-up and the current paths, and I sit with them for the critical areas: power, fast signals, sensitive analogue parts and connectors. I review the layout against a checklist before it goes out, because changes cost a new board run."

The full answer: A good schematic can still become a bad board.

A weak answer: "Layout is the layout team's job." Follow-up: "The analogue signal is noisy only on the board." Say what you check.

What is signal integrity, and when does it start to matter?

What they check: high-speed basics.

Short answer: "Signal integrity is how cleanly a signal arrives: without reflections, crosstalk or too much loss. It matters when edges are fast compared with the length of the trace, for example on memory, high-speed serial links or long buses. Then I control impedance, keep return paths unbroken, terminate where needed, and simulate or measure the critical links."

The full answer: It is the rise time, not the clock frequency, that decides.

A weak answer: "Only for very fast clocks." Follow-up: "A link fails only at high temperature." Say what you suspect.

EMC, heat and the lab

How do you design a board to pass EMC testing the first time?

What they check: compliance designed in.

Short answer: "Electromagnetic compatibility means the product neither disturbs other devices nor is disturbed by them. I plan it from the start: solid ground planes, small current loops, filtered connectors, controlled edges, and shielding where needed. I run pre-compliance scans on early prototypes so the formal test is a check, not a surprise."

The full answer: A fix at the test lab costs a week; a fix in the layout costs an hour.

A weak answer: "We fix EMC at the test house." Follow-up: "The product fails at one frequency." Say how you find the source.

How do you handle thermal design on a dense board?

What they check: heat as a limit you plan for.

Short answer: "I estimate the losses of each hot part, check their limits at the highest ambient temperature, and plan copper areas, vias, spacing and airflow with the mechanical team. Then I measure with thermocouples or a thermal camera on the prototype in the enclosure, not on the bench."

The full answer: Parts that run hot fail earlier, even when they do not fail today.

A weak answer: "The heatsink will take care of it." Follow-up: "The board is fine open but fails in the closed case." Say what you do.

Walk us through the bring-up of a new prototype board.

What they check: a careful, safe first power-on.

Short answer: "Bring-up is the first power-on and check of a new board. I inspect it first, check for shorts on the rails, then power it from a current-limited supply, one rail at a time if I can. I check voltages, clocks and resets, then load a simple test firmware with the firmware team and test each interface. Every finding goes into a list for the next revision."

The full answer: A bring-up plan written before the boards arrive saves days.

A weak answer: "I plug it in and see what happens." Follow-up: "One rail draws too much current." Say what you do next.

A board fails in the lab and you do not know why. How do you debug it?

What they check: a method under pressure.

Short answer: "I make the fault repeatable first, then narrow it down: which boards, which conditions, what changed. I form a hypothesis and test it with the oscilloscope or a logic analyser at the right point, and compare with a working board. I change one thing at a time and write down what I find."

The full answer: The note you wrote at two in the afternoon solves the bug at six.

A weak answer: "I swap parts until it works." Follow-up: "The fault disappears when you touch the probe to the board." Say what that tells you.

When would you use an FPGA instead of a microcontroller?

What they check: choosing the right building block.

Short answer: "A microcontroller runs software and fits most control tasks at low cost and power. An FPGA is programmable logic: it fits when you need many things to happen in parallel, tight timing, fast interfaces or signal processing that software cannot keep up with. It costs more in parts, power and design effort, so I need a clear reason."

The full answer: Many products use both, each for what it does well.

A weak answer: "FPGAs are always faster, so I use them." Follow-up: "The product must run on a battery for a year." Say what changes.

Reviews, production and the team

As a senior hardware engineer or lead hardware engineer, how do you run a design review of a junior hardware engineer's board?

What they check: reviews that catch problems and teach.

Short answer: "A design review is a planned check of a design by people who did not draw it. I ask for the schematic, the calculations and the requirements a few days before, go through a checklist for power, interfaces, protection, test points and parts, and ask the designer to explain the hard parts. Findings get an owner and a date. I make sure the junior engineer leaves knowing why each finding matters."

The full answer: A lead engineer is judged by how few problems reach the prototype, not by who found them.

A weak answer: "I look at it when I have time." Follow-up: "The designer disagrees with a finding." Say how you settle it.

What does design for manufacturing mean to you, and how do you work with the factory?

What they check: designs that can be built at volume.

Short answer: "Design for manufacturing means designing a board that the factory can build and test reliably and at the planned cost. I check footprints, spacing, panel layout and test access with the factory's rules, and I ask the production and test engineers to review the design before release. After the first runs I look at the yield and the failures with them."

The full answer: A board that works on the bench but fails in production is not finished.

A weak answer: "The factory will tell us if there is a problem." Follow-up: "The first batch has many solder defects on one part." Say what you check.

How do you plan for component obsolescence over a product's life?

What they check: thinking in product years, not prototype weeks.

Short answer: "Obsolescence means a part goes out of production. I choose parts with a long expected life and a second source where I can, watch the lifecycle notices with the buyers, and plan a last-time buy or a redesign before the part runs out. For long-lived products, such as industrial or medical ones, I keep the design easy to update."

The full answer: A product that sells for ten years outlives many of its parts.

A weak answer: "We will deal with it when it happens." Follow-up: "A part goes end of life with six months' notice." Say what you do.

How do you work with the firmware team where hardware and software meet?

What they check: a shared view of the board.

Short answer: "I agree the pin map, the start-up order, the interfaces and the test hooks with the firmware team early, write them down, and change them only with their agreement. During bring-up we debug together, because many faults sit at the border, and I give them a simple hardware test plan to run."

The full answer: A bug is nobody's fault until it is understood.

A weak answer: "If it works in hardware, it is a software bug." Follow-up: "The firmware team wants a pin you already used." Say what you do.

How do safety standards change the way you design, for example in cars or medical devices?

What they check: awareness of regulated work.

Short answer: "In regulated products the standard shapes the process: in cars the international ISO 26262 for functional safety, in medical devices the international IEC 60601. I work to the safety requirements, add the analyses they ask for, such as failure modes and their effects, document every decision and keep changes under control. The safety team and the test lab say how a standard applies to our product."

The full answer: Safety is a design property, not a test at the end.

A weak answer: "Compliance handles the standards." Follow-up: "A single part failure could switch a motor on." Say what you design in.

Where can AI help a hardware engineer, and where must the engineer decide?

What they check: sober use of new tools.

Short answer: "AI tools can summarise datasheets, suggest parts, check schematics against rules, and help with routing and test scripts. I would still check every value against the datasheet, keep confidential designs inside approved tools, and keep the design decisions and sign-off with engineers who answer for them."

The full answer: A wrong value from a confident tool still burns a board.

A weak answer: "AI will design the boards." Follow-up: "A tool suggests a part that does not exist." Say how you would catch it.

Your CV for these questions

Each hardware line on your CV invites the questions above: which board, what was hard, what you measured. Give each one a line that makes a lead engineer want the story:

Hold your CV against a hardware engineer job with the free score; then prepare the board story for the area it finds thin, from the requirement to the measurement.