Electronic Design Engineer Interview Questions UK: 8 Real Questions and What Interviewers Want

Most Electronic Design Engineer interviews in the UK follow a pattern, and knowing it beats guessing. Below are eight questions from our bank of 12, each with a note on what the interviewer is really after.

Eight Electronic Design Engineer interview questions, and what the interviewer is thinking

1. Talk me through the stages of an electronic product design from requirements through to production, and where you would add the most value.

Why they ask: They want to see that you understand the full development lifecycle, not only schematic capture.

2. How would you choose a power supply architecture for a battery-powered product, for example when to use an LDO or a switching regulator?

Why they ask: Power design is central to nearly every electronic product.

3. How would you design the analogue front end for a low-level sensor signal feeding a microcontroller ADC?

Why they ask: Signal conditioning questions reveal real analogue competence.

4. What is component derating and worst-case circuit analysis, and why do you do them?

Why they ask: They want to know whether your designs will survive real-world variation and ageing.

5. How do you protect the inputs and power entry of a product against reverse polarity, overvoltage and ESD?

Why they ask: Protection design shows practical robustness and compliance awareness.

6. How do you verify that a design meets its specification before release, and what test coverage would you expect?

Why they ask: They want to see structured verification rather than ad-hoc bench testing.

7. Your new prototype board resets randomly when a motor on the same supply starts. How do you find and fix the problem?

Why they ask: They are testing your ability to diagnose real electronic faults methodically.

8. Tell me about a product you designed from schematic to production. What was your contribution and what did you learn?

Why they ask: They want proof of end-to-end ownership of a real design.

A sample answer to question 1

Talk me through the stages of an electronic product design from requirements through to production, and where you would add the most value.

I'd start by turning the customer or marketing needs into a measurable specification covering function, power, environment, size, cost and compliance. Next comes architecture: choosing the processor, power tree, interfaces and key components, with an early risk review of anything unproven. Then detailed design, with schematics, simulation of critical circuits in tools like LTspice, and a design review before layout is released. After that, board build and bring-up, then verification against the specification, including environmental and pre-compliance testing, before a second spin to fix issues. Finally, design for manufacture, the test strategy, documentation and transfer to production with a controlled bill of materials. I add most value early, in architecture and component choices, because mistakes there are very expensive later, and again in verification, where careful testing against the specification shows what really works. I also like closing the loop by reviewing production yield data.

Common mistake to avoid: Describing only schematic and layout; Ignoring compliance and manufacture

Want the rest?

Full model answers, key points and common mistakes for all 12 questions are on the Electronic Design Engineer interview questions page. The first five are free, no sign-up needed.