PCB Assembly Supplier Interview: 15 Questions and Red Flags
Direct answer: A useful PCB assembly supplier interview asks how the team handles a representative board, revisions, sourcing approvals, first-article release, test ownership, failures, and repeat builds. Red flags include universal capability claims, informal file control, unapproved substitution authority, and undefined test scope.
What decision does this guide support?
This guide gives hardware startups a structured interview that tests operating controls rather than presentation quality. Use the scorecard with a real package and record the evidence behind each answer.
Hardware Startup Supplier Interview
Ask for a process explanation and a sample record wherever possible. A credible answer should identify the decision, responsible person, evidence, and condition that stops work.
| Evaluation area | Strong evidence | Red flag / hold condition |
|---|---|---|
| Project fit | Ask which project characteristics trigger extra review or a different manufacturing route. | The supplier claims every project is a fit. |
| File control | Ask how revisions, variants, and superseded packages are separated. | The answer is to email the latest files. |
| Sourcing | Ask how source traceability, alternates, shortages, excess, and approval are recorded. | Equivalent parts may be purchased without engineering review. |
| Build control | Ask what evidence gates setup, first article, continued assembly, and rework. | Equipment is discussed but release decisions are not. |
| Test | Ask who owns fixtures, software, limits, data, and failed-unit disposition. | Testing means only power-on unless later specified. |
| Failure response | Ask for the issue report format, containment steps, decision owner, and closure record. | A failure is handled without preserving evidence. |
Start with project fit
Describe board technology, quantity, lifecycle stage, sourcing model, test expectation, and destination. Ask what characteristics would trigger extra engineering review, a different partner, or a recommendation not to proceed.
Ask how changes are handled
Request the method for identifying revisions and variants, blocking superseded packages, and applying a mid-build change. “Email the latest files” is not enough to prevent mixed baselines.
Ask for sourcing controls
Discuss source traceability, approved distributors, alternates, shortages, excess material, and approval records. The supplier should distinguish presenting an option from authorizing a functional change.
Ask how test scope is agreed
Clarify programming, fixture ownership, limits, data, calibration or reference needs, and failed-unit disposition. “Power-on test” should not be allowed to stand in for undefined functional coverage.
Ask what happens when a build fails
Request the issue-report format, containment action, preserved evidence, decision owner, and closure record. The response should show how affected units are identified before rework or continued production.
15-question interview scorecard
Score project fit, file control, sourcing, build control, test, and failure response. Give more weight to evidence from a comparable project than to an equipment list or broad promise.
Turn the interview into a selection record
- Use the same scenario. Give candidate suppliers an identical representative project.
- Capture evidence. Save example records, stated boundaries, and unresolved questions.
- Verify after award. Compare first-build behavior with the interview commitments.
Related Cyrionix resources
Review the PCB assembly services overview and low-volume supplier guide before shortlisting a partner.
