What to Actually Put in a Quantum Job Posting (So Candidates Don't Bounce)
A checklist for writing quantum job postings that convert — specific about stack, honest about degree requirements, and free of buzzword filler.
Quantum talent is scarce enough that a vague job posting is a real cost — the candidates who actually understand the field will bounce off buzzword-heavy postings faster than they'll bounce off an honest, specific one, even if the honest one sounds less impressive on paper.
Lead with the stack, not the mission statement
Name the qubit modality if hardware is involved. Name the SDK or framework if software is involved. A candidate who's spent time with Qiskit, Cirq, or pytket will self-select in or out much faster from "you'll build calibration software for our superconducting qubit platform using a Qiskit-based control stack" than from "join our team building the future of computing."
Be honest about degree requirements
If a PhD is genuinely required for the work — foundational research, deep theory — say so plainly. If it isn't, don't default to "PhD preferred" out of habit; it discourages strong non-PhD candidates from applying to roles they'd actually be qualified for. Industry-wide, only around 19% of quantum postings genuinely require a PhD, versus roughly 80% in academia — most of the field just isn't research hiring. See our breakdown of where PhDs actually matter in quantum hiring if you're unsure which category a role falls into.
Include a comp range if you can
Pay transparency is increasingly standard practice in tech hiring generally, and quantum is no exception — a posting with a real range gets taken more seriously by experienced candidates who've learned to treat "competitive salary" as a non-answer. It's also a genuine differentiator right now, not table stakes: on our own board, only about 13% of active postings currently disclose a salary range at all, so publishing one puts you ahead of most of the market rather than just keeping pace with it.
A quick checklist
- Qubit modality or tech stack named explicitly
- What the person will actually own or ship in the first year, not just a list of duties
- Degree requirement stated honestly — required vs. preferred, and why
- Comp range, if your company can share one
- No "rockstar," "ninja," or unexplained superlatives
Looking to reach quantum-specific candidates directly rather than a general tech audience? See how Superposition Jobs works for employers.
Frequently asked questions
Should a quantum job posting always name the qubit modality?
Yes, whenever hardware is involved. It's one of the fastest ways for a qualified candidate to self-select in, and its absence is one of the clearest signals of a vague, under-scoped posting.
Should every quantum job posting require a PhD?
No. Defaulting to 'PhD preferred' out of habit discourages strong non-PhD candidates from applying to roles — like most engineering, technician, and business roles — where a doctorate genuinely isn't necessary.
Does including a salary range actually help a quantum job posting perform better?
It tends to, since experienced candidates increasingly treat 'competitive salary' as a non-answer and take postings with a real range more seriously.
How many quantum job postings actually include a salary range today?
Not many — on our own board, only about 13% of active postings disclose one. That makes a real comp range a genuine point of differentiation right now, not just a compliance checkbox.