Public-evidence hiring
Unique-Fit Shortlist vs Keyword Recruiters: What “Mission Fit from Public Work” Means
When a hardtech founder compares specialist recruiters — and generic AI match tools — to DevMatch, what does unique mission fit from public work actually mean, and how does that method differ from network or resume screening and keyword matching?
This page explains the product language, contrasts three sourcing methods, and points to a shortlist you can run — not a placement-only pitch and not an attack on named firms. Unique mission fit from NASA reports, published papers, SBIR awards and code. Every signal traces to a real source, never a resume.
What “unique-fit shortlist” means on DevMatch
Fit is drawn from NASA reports, published papers, SBIR awards, and code. Unique mission fit from NASA reports, published papers, SBIR awards and code. Every signal traces to a real source, never a resume.
A shortlist is names with evidence attached and links back to sources — the same how-it-works steps as the product overview: paste a job description, run it against the index, receive a shortlist. “Unique fit” is mission and work-trace alignment. It is not a proprietary score we invent on this page.
Index framing, cited as published: 35M+ engineers, including 10M+ researchers. Robotics, materials, defense, software. That is the whole-index claim. This page does not invent a subset size by method.
What this page is not
Not a salary survey. Not a smear of named firms. Not invented placement outcomes or time-to-fill benchmarks.
Three sourcing methods
Choosing a method depends on urgency, access needs, and whether public traces exist for the role family. This is a method contrast, not a claim that one path always wins.
Network / resume screening (specialist recruiters)
Humans screen certifications, prior employers, and referrals. Strong when relationships and soft context matter. Still largely resume- and network-led. Specialist aerospace, firmware, and hardtech desks that own today’s search results work this way.
Keyword / Boolean / generic AI title match
Titles and skill strings. Fast at filling a pipeline. Weak when real fit is buried in reports, awards, flight stacks, or firmware traces. LinkedIn-style similarity and generic AI match tools are this method — they are not the same as a public-evidence index.
Public-evidence index (DevMatch)
Paste a job description. Run it against published work, technical reports, awarded contracts, and code. Receive a shortlist with source-linked evidence. You can paste a job description in chat. Sign in to run the search. Free platform credits, no card required.
When keyword and network methods break for hardtech
Titles overlap. Embedded, aerospace, robotics, and “defense” can describe very different work. Real fit often lives in verification, an RTOS, an award, a paper, or a named program — not in the title string.
Boolean and resume keywords catch self-report. They do not prove authorship or program context. That is a thin signal surface, not a claim that every resume is false.
Role-depth examples of the same method: public evidence for flight software, robotics firmware from public work, and defense engineers from SBIR awards. Those pages are method depth, not case studies.
How to brief a unique-fit shortlist
Send a job description
Paste a job description or posting link in chat. One JD is enough to start — no separate sourcing brief required.
We run it against the index
Engineers and researchers found through published work, technical reports, awarded contracts and code. Not through keywords lifted from a resume.
You get a shortlist that fits
Every name arrives with evidence attached and a link back to the source behind each signal.
Reading the shortlist
Every signal should trace to a source. Placeholder rows show layout only. Not a live run, not people we placed, and not a coverage claim. The homepage format sample is layout only — illustrative, not a live result for the job you pasted.
Inbound already in pipeline?
The same index runs against people already in your pipeline. Claims get checked against public work of every kind. Code, papers, technical reports, awarded contracts. Thin signal surfaces before anyone spends an hour on a call. A claim with no public trace is not a rejection. It is a question worth asking. See check inbound claims, or the homepage public-work check.
Agent path
Teams already in Cursor or Claude can run the same shortlist method through DevMatch MCP — the documented tools on that page and on pricing. This page does not invent extra tool names.
When to self-serve Platform vs use Placement
Platform: monthly credits for unique-fit shortlists (chat, MCP, Slack /devmatch). Reveal is free on a shortlist you already paid for. Connect email to outreach yourself.
Placement: for urgent roles, DevMatch sources, shortlists, and runs outreach. A card is required at submit ($0 today). Fee only when a hire from the shortlist is confirmed — $10,000 under a $200k base midpoint, $15,000 at $200k and above. Never stack Platform and Placement on the same hire.
See Platform vs Placement for plan ceilings and the credit meter. Neither path is claimed to convert better than the other.
Questions
Questions hiring teams ask
What does a unique-fit shortlist mean?
A unique-fit shortlist is a set of names whose mission fit is drawn from public work — NASA reports, published papers, SBIR awards, and code — with evidence attached and a link back to the source behind each signal. Unique fit is work-trace alignment with the role, not a proprietary score. Every signal traces to a real source, never a resume.
How does public-evidence sourcing differ from keyword recruiters?
Keyword and Boolean screens — and generic title-match tools — search skill strings and job titles. Specialist recruiters typically screen resumes, certifications, prior employers, and referrals. A public-evidence index runs a job description against published work, technical reports, awarded contracts, and code, then returns a shortlist with source-linked evidence. The contrast is method, not invented performance numbers.
When should a hardtech team still use a specialist recruiter’s network?
A specialist network is a reasonable choice when relationships and soft context matter more than a public trace — for example when the people you need are already known to a trusted desk, or when the role family leaves little published work. Choosing a method depends on urgency, access needs, and whether public traces exist for the role. No method always wins.
How does DevMatch run a unique-fit shortlist?
Paste a job description, run it against the index of engineers and researchers found through published work, technical reports, awarded contracts, and code, and receive a shortlist where every name has evidence attached and a link back to the source. Sign in to run a search. Free platform credits, no card required. The same method is available in chat, MCP, and Slack /devmatch.
When should a team use DevMatch Placement instead of self-serve Platform credits?
Use Platform when you want monthly credits for unique-fit shortlists in chat, MCP, or Slack /devmatch, then reveal names and outreach yourself. Use Placement for urgent roles when you want DevMatch to source, shortlist, and outreach — card at submit, $0 today, fee only on a confirmed hire. Never stack Platform and Placement on the same hire.
What to do next
Paste a job description and get a unique-fit shortlist — every name with evidence attached. Free platform credits, no card required.
Need outreach done for you? Submit a Placement role — card at submit, $0 today, fee only when a hire from the shortlist is confirmed. Never stack Platform and Placement on the same hire.