Electrical Engineer
Interview Questions.
15 practice questions across 13 skills — each with what the interviewer is really listening for. Prepare with intent, not guesswork.
Free · No signup · Grouped by skill
How to use this page
Don't memorise answers. For each question, read what the interviewer is looking for, then practise answering out loud in your own words with a real example. The notes describe strong answers and common red flags — they are for your prep, not a script.
Circuit Design
2 questionsWalk me through how you would design and verify a simple power supply circuit.
IntermediateWhat the interviewer is looking for: Strong answers cover requirements, topology choice, component ratings, and verifying with analysis and testing across load and temperature. Picking parts without checking ratings or margins is a red flag.
A design passed review but failed EMC testing. How do you approach the fix?
AdvancedWhat the interviewer is looking for: Look for systematic diagnosis of emissions/susceptibility sources, grounding, shielding, and filtering, not random component swaps. Ignoring EMC until late is a red flag.
PCB Design
1 questionWhat are the key considerations when laying out a PCB for a mixed analog and digital board?
AdvancedWhat the interviewer is looking for: Look for ground planes, separating noisy digital from sensitive analog, trace width for current, and decoupling. Ignoring return paths or EMI is a red flag.
Electrical Schematics
1 questionHow do you read and work from an electrical schematic you did not create?
BasicWhat the interviewer is looking for: Strong candidates trace signal and power paths, identify key nets and references, and cross-check with the BOM. Being unable to navigate a schematic systematically is a red flag.
Power Systems
1 questionExplain the difference between real, reactive, and apparent power and why power factor matters.
AdvancedWhat the interviewer is looking for: A strong answer defines each, explains the power triangle, and why a poor power factor wastes capacity and costs money. Confusing the three is a red flag for a power role.
Problem Solving
1 questionA circuit works on the bench but fails intermittently in the field. How do you debug it?
AdvancedWhat the interviewer is looking for: Look for considering temperature, vibration, noise, and marginal timing, and reproducing the condition methodically. Swapping parts randomly without a hypothesis is a red flag.
Attention to Detail
1 questionWhy is attention to detail on component ratings and datasheets so critical in electrical design?
BasicWhat the interviewer is looking for: Strong candidates know that exceeding a rating even briefly can cause failures, and always design with margin. Not reading datasheets carefully is a red flag.
Electrical Safety Standards
1 questionHow do you approach designing for electrical safety and compliance?
IntermediateWhat the interviewer is looking for: Look for awareness of relevant standards, isolation, protection, and creepage/clearance, treating safety as non-negotiable. Treating safety standards as optional paperwork is a serious red flag.
MATLAB
1 questionHow would you use MATLAB to analyse or simulate a system before building hardware?
IntermediateWhat the interviewer is looking for: Strong answers use simulation to validate behaviour and catch issues early, while knowing models are approximations to be verified. Trusting simulation blindly without hardware validation is a red flag.
PLC Programming
1 questionHow do you program and troubleshoot a PLC for an industrial control task?
IntermediateWhat the interviewer is looking for: Look for structured ladder/function logic, understanding I/O and timing, and safe troubleshooting on live equipment. Editing live control logic without safety precautions is a red flag.
Technical Documentation
1 questionHow do you document a design so a technician can build and service it correctly?
BasicWhat the interviewer is looking for: Strong candidates provide clear schematics, BOMs, assembly and test instructions, and revision control. Undocumented tribal knowledge is a red flag.
Embedded Systems
1 questionHow do you approach integrating a microcontroller and firmware needs into your circuit design?
IntermediateWhat the interviewer is looking for: Strong candidates plan for power, I/O, debugging headers, and firmware constraints early, collaborating with firmware. Designing hardware in isolation from firmware is a red flag.
Continuous Learning
1 questionHow do you keep up with new components and standards in a fast-moving field?
BasicWhat the interviewer is looking for: Strong answers cite concrete habits — reading app notes, following standards updates, hands-on experimentation. Vague 'I keep learning' with no specifics is a red flag.
Teamwork
1 questionDescribe working with mechanical or firmware teams to integrate your electronics.
BasicWhat the interviewer is looking for: Look for early collaboration on interfaces, connectors, and constraints, and adapting to their needs. Designing in isolation and discovering integration problems late is a red flag.
Behavioural & role-general
1 questionTell me about a design where you had to balance cost, reliability, and performance.
BasicWhat the interviewer is looking for: Look for a concrete trade-off with rationale and the outcome. 'I just made it work' with no engineering judgement shown is a red flag.