Quantum recruiting combines two conditions that encourage exaggeration: specialists are scarce, and the field attracts heavy investment and attention. McKinsey estimated in 2022 that there was one qualified candidate for every three quantum job openings (McKinsey). Investment in quantum start-ups reached US$12.6 billion in 2025 (McKinsey). Candidates and employers both have an incentive to exaggerate, candidates about their experience and employers about their technology. Because the subject is hard, both can go unchallenged if the person on the other side of the table lacks the expertise to ask the right question.
On both sides, the answer is to ask for the evidence that would exist if the claim were true. This guide lists the warning signs in résumés and in job descriptions and the questions that test them.
Red flags in quantum résumés
Titles out of proportion to the role
“Chief Quantum Scientist” at a three-person startup straight after a degree, or “Quantum Research Visionary,” says little. Look at the size of the organization and what the person actually did.
Solo claims for team results
Quantum research and engineering are collaborative. A candidate who claims to have invented a post-quantum algorithm alone, or to have led a processor build as an intern, needs to explain the context. The algorithms the US National Institute of Standards and Technology (NIST) standardized in 2024 came out of an eight-year public process involving cryptographers worldwide (NIST).
Every keyword, no specifics
A résumé that lists quantum machine learning, quantum key distribution (QKD), topological qubits, error correction, and blockchain without describing what the candidate built or measured suggests surface familiarity. Hiring managers should give detailed work in two areas more weight than mentions of 10.
Publications or patents that can’t be found
Papers and patents leave public records. A “Nature publication” that no index contains, or patents with no numbers, is a warning sign.
Performance claims without conditions
“Achieved a 1,000× speedup with a quantum algorithm” needs a problem, a baseline, hardware or simulation details, and ideally independent validation. Quantum speedups are usually narrow, and many apply only in theory.
Claims and the evidence to ask for
| Claim | What to ask for |
|---|---|
| “Built a quantum processor in my lab project.” | The platform, the supervisor, and the paper, poster, thesis chapter, or repository describing it. Building a processor is a team effort, so ask what the candidate’s part was. |
| “Invented a new post-quantum algorithm.” | The algorithm’s name, where it was published, and whether it was submitted to a standardization process or analyzed by others. |
| “Lead developer of a quantum software library.” | The repository. Commit history shows who did the work. Ask about a technical problem the candidate solved in it. |
| “Co-inventor on three quantum patents.” | Patent or application numbers, which can be checked on Google Patents or the US Patent and Trademark Office (USPTO) database. |
| “Expert in every quantum SDK.” | A specific project in each. A strong candidate can discuss one or two frameworks in depth. |
| “Demonstrated logical qubits.” | The paper, the code used, and the logical error rate compared with the physical error rate. |
Press politely and specifically: “That sounds substantial. Which group was it in, and was it published? I’d like to read it.” A genuine candidate will be glad to point you to the work.
Red flags in quantum job descriptions and pitches
Employers exaggerate too. Candidates should watch for these signs in listings and in what interviewers say.
Buzzword roles
A “Quantum AI Blockchain Engineer to drive disruption” with no concrete responsibilities suggests the employer has not defined what it needs.
Experience requirements the field can’t supply
A requirement for 10 years of ML-KEM (formerly CRYSTALS-Kyber) implementation experience, for an algorithm NIST standardized in 2024, shows a template written without understanding the field.
Three jobs in one
A listing that requires superconducting hardware design, cryptographic algorithm research, and machine-learning deployment describes three specialists. It usually means the team has not worked out the role. Whoever is hired will be expected to do all three jobs.
Timelines no published roadmap supports
IBM’s public roadmap targets a fault-tolerant system with 200 logical qubits in 2029 (The Quantum Insider). A startup promising a 1,000-logical-qubit fault-tolerant machine next year is promising five times as many logical qubits as IBM’s 2029 target, two years sooner. Ask what it has demonstrated so far.
Qubit counts without error rates
Physical qubit counts have grown quickly, and on their own they say little about usefulness. Ask for gate fidelities, coherence times, and whether any logical qubits have been demonstrated. Our guide to decoding quantum job descriptions explains those terms.
Secrecy combined with extravagant claims
Some stealth is normal for a startup. Be wary of a startup that combines stealth with claims that only its team has solved a hard problem but can point to no publications, demonstrations, or recognizable people.
Partnerships and records you cannot confirm
A genuine partnership with a university, national laboratory, or large company is usually documented in a press release, a joint paper, or a grant record. If a claimed “world record” or partnership appears nowhere outside the company’s own materials, treat it as unconfirmed.
Employer claims and how to test them
| Claim | How to test it |
|---|---|
| “Delivering a full-stack quantum solution in six months.” | Ask what exists today and what the six-month deliverable actually is. A credible employer separates the prototype from the long-term goal. |
| “Our processor is ready for commercial use.” | Ask which modality, what the error rates are, and whether there are published benchmarks or customer results. |
| “We partner with [a major university or company].” | Ask for the scope of the collaboration and any joint publication or announcement, then check the partner’s own site. |
| “Our device solves this problem a million times faster than classical computers.” | Ask for the paper or benchmark, the classical baseline used, and whether anyone outside the company has reproduced it. |
| “We need someone who can do theory, hardware, and software.” | Ask which of these is the main job. If the answer is “all of them,” expect a role without focus. |
Ambitious companies exist in this field, and some will succeed. Credible ones are open about their challenges and answer technical questions with data. The people they employ have earlier work you can find.
Due diligence for hiring managers
Ask for specifics
When a résumé claims a new algorithm, ask how it works, what it improves on, and what hardware or simulation it ran on. Candidates who did the work enjoy explaining it.
Check the record
Look up papers on Google Scholar or arXiv and patents in the USPTO database or on Google Patents. Check that the topics match the claimed expertise.
Use a short technical exercise
The exercise can be informal. Asking a candidate to reason through a relevant problem, such as the qubit and error-rate considerations for a small Grover search circuit, reveals depth quickly.
Bring in an expert
If your own quantum knowledge is limited, involve a team member, an adviser, or an external specialist in critical interviews. An experienced quantum engineer will be able to tell within a few questions whether a candidate’s answers have technical substance.
Ask references precise questions
“The candidate says they led the error-correction work. How would you describe their role?” The quantum community is small, and colleagues will often be candid.
Distinguish breadth from depth
A career that moves quickly across hardware, software, and cryptography may reflect versatility or a lack of depth. Ask the candidate to name their strongest area and go deep there.
Due diligence for candidates
Research the employer’s track record
Look for publications, patents, open-source contributions, and team members known in the field. Be cautious with a company that claims advanced technology and has no public footprint.
Ask about the team and resources
How large is the quantum team, and what are their backgrounds? Is there an in-house lab, or access to hardware through cloud providers? If the company is building hardware, can it show you what exists?
Clarify the role
If the listing covered everything from algorithms to hardware testing, ask which is the primary focus.
Test the timeline
Ask what the milestones are for the next one to two years and what your targets would be in the first six months. Ambitious goals are fine if the company has a plan to reach them.
Ask how claims were validated
If the company cites a breakthrough, ask how it was benchmarked and whether external researchers have checked it.
Talk to current or former employees
In a short conversation, someone who has worked there can tell you more than you will learn from the website. If many former employees left after short tenures, ask why.
Watch how they respond
Strong employers welcome informed questions. An interviewer who becomes defensive, or who asks little about your actual skills while working hard to sell the role, is showing you a warning sign.
The cost of inflated claims
Inflated claims fail eventually. The candidate who overstated their experience struggles in the role. Employees leave the employer that oversold its technology once they see that the technology does not match what they were told. Both failures cost money and credibility, in a field small enough for reputations to travel quickly. Asking for evidence politely and consistently is ordinary quality control.
Our listing standards set out what every listing on Quantum Careers must include. Employers who want help defining a senior role, or vetting candidates for one, can talk to our executive search team. Candidates can browse roles and research the employers behind them on our company pages.
First published November 1, 2025. Revised November 10, 2026: an unsourced anecdote and statistics were removed, McKinsey’s estimate was corrected to its original 2022 date, and the qubit-count examples were rewritten to reflect current hardware and to distinguish physical from logical qubits.
