PCB Bring-Up & Debug interview questions
Taking a new board from bare to working, and diagnosing it when it is not.
Interviewers rarely ask you to define anything here. They describe a symptom, a measurement, or a constraint and watch how you reason. The 6 concepts below are what a strong answer draws on, and they are exactly what this product weights up when a job posting mentions bring-up, bringup, debug.
What interviewers probe
- Bring-Up SequenceCore
- Power rails before clocks before communication before function, and why the order matters.
- Short & Overcurrent DiagnosisCore
- Localizing a short with a bench supply, thermal camera, or voltage gradient.
- Rail VerificationCore
- Checking magnitude, ripple, sequencing, and transient response on every rail.
- Clock & Reset Verification
- Confirming oscillators start, PLLs lock, and reset releases cleanly.
- Rework & Isolation
- Lifting pins, cutting traces, and isolating a subsystem to bisect a fault.
- Intermittent Faults
- Making an intermittent failure reproducible before trying to fix it.
Understand these first
These sit underneath pcb bring-up & debug and come from other topics. If this material keeps failing to stick, the gap is usually here rather than in the topic itself.
An example question
Bench supply set to 12 V with a 500 mA current limit. The board should draw about 150 mA at idle.
You power a brand-new board for the first time and current draw immediately hits the supply's limit. Walk me through how you would debug it.
What a strong answer covers
Leave the current limit engaged — it is protecting the board and it is also the measurement. Drop the voltage until the board draws its limit at a low voltage, which turns the short into a small, safe heat source. Then localize: measure resistance to ground on each rail with the supply off and compare against expectation; a rail at a few ohms or less is the suspect. With low voltage applied at the current limit, either use a thermal camera or feel for the warm part, or measure the millivolt gradient along the ground and power planes to walk toward the short. Consider the likely causes in order of prior probability: a solder bridge under a fine-pitch part, a backwards polarized part such as a tantalum or a diode, a wrong footprint or a rotated regulator, and a wrong-value component. If it is not localizable, bisect — lift the enable on downstream regulators or cut a supply trace to isolate sections.
- Uses the current limit as a tool rather than defeating it — Keeps the board safe and turns the fault into a measurable, survivable condition.
- Proposes a localization technique — Resistance to ground per rail, thermal imaging, or a voltage-gradient walk — something that narrows physically.
- Orders hypotheses by likelihood — Solder bridge and reversed polarity before exotic explanations.
- Has a fallback when localization fails — Bisecting the board by isolating sections or lifting regulator enables.
How this topic gets weighted
A posting that mentions bring-up, bringup, debug pushes pcb bring-up & debug up the curriculum, and the weighting is shown with the quote from the posting that caused it. Two candidates preparing for different roles get genuinely different plans from the same taxonomy — and because mastery is stored per concept rather than per application, what you learn here still counts on your next one.
Related topics
Practice pcb bring-up & debug against a real posting
Paste the job description you are actually interviewing for. The curriculum weights this topic against everything else the role needs, and the scheduler serves the questions that close your gaps fastest.