Right Fit, Right Role: Why Hiring Isn't One-Size-Fits-All

Glenda Navarro

Sep 23

3 min read

Four black puzzle pieces arranged in a square on a glowing white-blue background.

A mechanical engineer with ten years at a manufacturing plant can walk into most production floors and be productive by week two. Hand that same résumé to a company hiring for R&D, and it might not even clear the first screen, not because the candidate isn't sharp, but because R&D hiring and traditional engineering hiring are, in practice, two different sports wearing the same uniform.

I've placed both kinds of engineers. The traditional hire is judged on execution: can this person take a known process and run it well, catch the defect before it ships, hit the throughput number. The R&D hire is judged on something harder to screen for: can this person sit with a problem that has no known answer yet and still make progress.

Why R&D Hiring Breaks the Usual Playbook

Most engineering job descriptions are written around a track record. Years of experience, specific tools, certifications, a history of solving problems the company has already solved before. That playbook works fine for traditional engineering hiring, because the job is largely about repeating expertise reliably.

R&D hiring asks a different question: how does this person behave when the answer isn't in the manual? A candidate coming out of a rigorous scientific training background, a PhD lab, a national lab, a deep-tech postdoc, may have thinner "years of experience" on paper, but they've spent years being wrong in public, redesigning an experiment on the fly, and defending a hypothesis that didn't survive contact with the data. That is its own kind of expertise, and it doesn't always translate into a keyword match.

I see this constantly in manufacturing and industrial engineering searches too, not just in obviously research-driven fields. A hiring manager will ask for '5+ years of process experience' on a role that's really asking someone to solve a problem the plant has never faced before, when what they actually need is someone who has never seen this exact failure mode and is comfortable saying so out loud on day one.

What Traditional Engineering Hiring Still Gets Right

None of this is a knock on traditional engineering hiring. A production floor with a live customer order does not want someone treating the line like an open research question. Process discipline, documentation, and the instinct to follow a spec exist because they prevent expensive mistakes. If I'm placing a Quality Engineer or a Production Supervisor, I am absolutely screening for that track record, and I'd be doing my client a disservice if I didn't.

The mistake is applying that same lens to an R&D seat, or worse, applying the R&D lens to a production seat. I've watched companies pass on a strong process engineer because they "didn't seem curious enough," and pass on a brilliant research scientist because they "lacked hands-on manufacturing experience." Both misses come from grading the wrong test.

How I Screen for the Difference

When a client comes to me for an R&D hiring search, the questions in the intake call change. I'm asking less about tools and more about how a candidate handled a project that failed, what they did when the data contradicted the plan, and how comfortable they are presenting an unfinished answer to a room that wanted a finished one.

For traditional engineering hiring, the questions stay closer to the ground: what did you own, what broke, how did you know it was fixed, and what would you do differently with the same resources. Both conversations matter. They're just not the same conversation.