How to Vet a Hardware Engineering Firm: 10 Questions to Ask Before You Sign

Hardware engineering firms all sound roughly the same in the first sales meeting — competent, friendly, eager to win the work. The differences appear over the next six to twelve months, when the project hits its hardest problems and the firm's actual depth, process, and incentives become visible. This article gives you the ten questions that surface those differences in one thirty-minute call, with the answers seasoned firms give and the red flags in the answers others give. For the higher-level decision on whether to engage a firm at all, see Hardware Engineering Firm vs In-House.

Why a Vetting Checklist Matters

A bad hardware engineering relationship can cost a startup six to twelve months and a quarter of its seed round before anyone notices the project is off the rails. The pain is structural: it is easier to drop hints of progress than to ship working hardware, and founders who do not yet know hardware cannot reliably distinguish between motion and progress. The questions below are designed to surface evidence-based answers, not vibes — answers a polished sales pitch cannot fake.

1. "Who specifically will do the work?"

The senior engineer in the sales meeting is often not the engineer who writes the schematic. Ask for names, roles, and seniority of every person who will touch the project, and ask what happens if any of them gets sick or leaves the firm.

• Good answer: specific names, LinkedIn-verifiable backgrounds, a documented staffing plan with backups
• Red flag: "our team" with no names — usually means a junior or an offshore subcontractor will do the actual work while the sales engineer remains the face

2. "Walk me through a project that went sideways."

Firms that have never had a project go sideways have either not shipped much or are not telling the truth. The recovery story is the real signal — how they caught the problem, who told the client, how the budget and timeline were renegotiated, what they would do differently.

• Good answer: specific project, specific failure mode (e.g. "our second-source IC didn't match the primary's behavior under thermal stress"), specific recovery (a written change-control, an extra spin paid for collaboratively, a postmortem that changed their process)
• Red flag: vague answers, blame on the client, or claims that nothing ever went wrong

3. "How do you price prototype spins?"

Complex boards usually need two to three prototype spins. The way a firm prices spins reveals how aligned their incentives are with yours.

• Good answer: spins are included in the milestone-based contract (usually two), with a written change-control if a third is needed
• Red flag: every spin is a new fixed-fee — the firm is incentivized to ship a board they suspect will need rework

4. "What is your supply-chain process?"

Supply-chain risk is the single biggest reason hardware products miss launch. A firm that second-sources every BOM line item upfront has a process that prevents this; a firm that selects parts on availability-today has a process that creates this.

• Good answer: every part on the BOM has a noted alternate; lifecycle status (Active, NRND, EOL) is checked via Octopart or distributor BOM tooling at schematic-complete; sole-sourced exotic parts require explicit client sign-off
• Red flag: "we'll deal with that at production" — production is the worst time to discover a sole-source has gone EOL

5. "Show me a DFM report from a past project."

DFM reports reveal what a firm actually pays attention to. Generic PDFs with bullet-list checklists are easy to produce and reveal little; annotated boards with crisp action items and root-cause notes reveal seniority.

• Good answer: a 5-to-15-page document with annotated screenshots, line-item action items, manufacturability scoring against IPC standards, and second-source notes
• Red flag: a checklist template with no project-specific details — usually means DFM is done by a junior reading from a script

6. "Do you require equity, royalties, or IP rights?"

The only acceptable answer is no, never. A service firm that asks for equity is asking to be paid twice for the same work — once in cash and once in the cap table — and is positioning to compete with you on future products.

• Good answer: 100% of the IP is yours under the engagement; the firm signs a mutual NDA before any technical discussion; no royalties on shipped units; no exclusivity on future categories
• Red flag: any hedging, any "deferred compensation" structure, any clause that grants the firm rights to use design elements on other projects

7. "How do you handle scope changes?"

Scope changes are normal in hardware projects — requirements evolve as the team learns. The firm's change-control process determines whether changes feel like collaboration or like extraction.

• Good answer: a written change-control template, a 24-to-72-hour turnaround on impact analysis (cost, schedule, risk), a sign-off from a named decision-maker on both sides before work begins on the change
• Red flag: change orders that arrive after the work is already done, or scope changes invoiced without a written quote

8. "What does a typical weekly status report look like?"

Cadence and visibility are the difference between a vendor and a partner. Ask to see an example status report from a similar project (sanitized for confidentiality).

• Good answer: a written weekly report covering what shipped, what blocked, decisions pending the client, next-week plan, and budget-to-actual against the milestone plan
• Red flag: "we'll send updates as we have news" — meaning silence during the hard weeks when you most need to know what is happening

9. "What happens to source files if the relationship ends?"

Source files — schematics, layout files, firmware repository, CAD — are the project's life. A firm that holds source files hostage is one project away from being unable to pay rent.

• Good answer: source files live in the client's version control or are delivered at every milestone; a final source-and-documentation handover is part of the contract closeout regardless of how the engagement ends
• Red flag: source files are described as "licensed for use" or "available upon project completion" — both phrases mean leverage over you

10. "Can I talk to two past clients?"

References matter, but the most useful reference is the unscripted one. Ask for two clients you can talk to without the firm pre-briefing them. Then ask the references: did the project finish on plan, did anything surprise you, would you hire them again.

• Good answer: the firm offers two unfiltered references, including one whose project was difficult — that's the harder reference to provide, and the most telling
• Red flag: hand-picked testimonials only, no live calls offered, or references who all worked on small-scope projects

How to Run the Call

These ten questions fit comfortably in a thirty-minute call if you cluster them: 1-2 on team composition, 3-4 on process, 5-6 on artifacts you can see, 7-8 on commercial structure, 9-10 on relationship end. The goal is not to interrogate — it is to look for the firm whose answers are specific, evidence-backed, and consistent with each other. Vague answers in one question often correlate with vague answers in the others.

Frequently Asked Questions

How many firms should I vet before deciding?

Three is a common sweet spot. One firm gives you no comparison; five exhausts everyone involved. Three lets you triangulate price, depth, and fit without dragging out the decision.

Should I sign an NDA before asking these questions?

Yes. Any firm worth working with signs a mutual NDA before the first technical discussion — that's table stakes. A firm that won't sign an NDA is telling you what they think about confidentiality.

How does inteRFace R&D answer these questions?

We are happy to walk through each one. Book a free thirty-minute call and we will give you specific answers, named references, and example deliverables. Pick a time at interfacernd.com/book.

Use This List, Even With Us

If you are evaluating engineering partners for a hardware project, run these ten questions against every firm on your shortlist — including us. Firms that hold up against the checklist tend to keep holding up over the project. Book a free consultation at interfacernd.com/book.