Roles they hire for
- Motor control firmware engineer
- Battery management firmware engineer
What they emphasise
- High-speed motors
- Battery packs
- Sensors in appliances
Brush up on
BLDC motor controlFOC basicsBMSADC samplingFault protection
How the rounds usually run
A typical consumer hardware loop for embedded roles. Companies vary by team and seniority.
Recruiter screen
- Background, role fit and logistics
Example: Walk me through your current project in two minutes.
Technical phone screen: C coding
- Live C coding: data structures, bit manipulation, memory
- Explaining your code and edge cases out loud
Example: Implement memmove and explain how you handle overlap.
Loop: embedded system design
- Architecture for a device feature end to end
- Power, memory and real-time trade-offs
Example: Design firmware for a wireless earbud's charging case.
Loop: RTOS, concurrency and debugging
- Scheduling, synchronization, priority inversion
- Hardware and software debugging with scopes and schematics
Example: Explain priority inversion and two ways to prevent it.
Hiring manager and behavioural
- Ownership, cross-functional work and judgement
Example: Tell me about a time you shipped under a hard deadline. What did you cut?
Practice questions
Original questions written for Dyson's focus areas, not leaked ones.
- Explain field-oriented control at a level a firmware interviewer expects.
- How do you protect a motor driver from over-current within microseconds?
- Design state-of-charge estimation for a vacuum's battery pack.
- How do you synchronise ADC sampling with PWM in a motor controller?
- What safety checks would you run before spinning a motor at power-up?
Your prep playlist
Design rounds to practise
Themes are inferred from Dyson's public product lines.
Take an AI mock round styled on Dyson, with follow-ups that probe what you missed.
Start a mock round