The recurring bench
Same work, different titles.
Compiled from the published team pages and open postings of the control-layer and hardware companies: Qruise, Q-CTRL, QuantrolOx, IQM, Pasqal, Riverlane, QuEra, Quantum Machines, Zurich Instruments, Qblox. We describe the work rather than any company's job titles, because no two of them use the same words for it.
R-01
Pulse and optimal-control scientist
Titles vary: control physicist, QOC scientist
PhD physics, 0 to 6 years out
Designs and optimizes the waveforms that turn a noisy device into working qubits: optimal control, pulse shaping, gate tune-up. The most contested profile in the field, and the one with the shortest list of names.
Optimal controlGate calibrationPython
Hardest to hire
R-02
Device modeling and digital-twin scientist
Titles vary: research scientist, staff scientist
PhD plus postdoc typical
Builds the model of the machine from its own measurements, then turns it into an error budget that says which component costs which fidelity. Sits between theory and the bench and speaks to both.
Open quantum systemsSystem identificationModel learning
Deep pool, narrow fit
R-03
Fault-tolerance and decoding scientist
Titles vary: QEC scientist, decoder engineer
PhD, or strong CS with coding theory
Codes, decoders, and fault-tolerant architecture. Splits into a theory side and a real-time decoding side that is closer to hardware engineering than to physics, and the two rarely live in one person.
qLDPCDecodersReal-time
Fastest-growing demand
R-04
Benchmarking and performance scientist
Titles vary: system performance, characterization
PhD or MSc with a lab record
Measures what the machine actually does, defines the metrics the roadmap is judged on, and finds the limitation before marketing does. Quietly decides which claims a company can defend.
Randomized benchmarkingTomographyStatistics
Undervalued, decisive
R-05
Research software engineer, scientific stacks
Titles vary: scientific developer, quantum software engineer
MSc or PhD, physics-literate coder
Turns the physicists' notebooks into something other people can run: experiment frameworks, SDKs, compilation, simulators, tests. The role that decides whether the science ships or stays in a repository.
PythonC++Architecture
Broadest pool
R-06
Microwave and readout electronics engineer
Titles vary: RF engineer, embedded engineer
MSc or PhD electronics
The signal chain: microwave generation, arbitrary waveforms, readout, timing, and the firmware underneath. Rarely arrives from quantum; arrives from radar, telecoms, or scientific instrumentation.
RF and microwaveFPGASignal chain
Cross-industry hire
R-07
Cryogenics and hardware systems engineer
Titles vary: hardware engineer, systems engineer
Often non-PhD, deeply practical
Keeps the machine cold and stable: dilution refrigerators, wiring, vacuum, thermal budgets, and the standards the next system inherits. Thin in job ads, decisive in whether anything runs.
Dilution fridgesVacuumThermal design
Scarce, non-substitutable
R-08
Bring-up and integration scientist
Titles vary: solutions engineer, field scientist
MSc plus, travel-tolerant
Takes the stack onto somebody else's machine and makes it work: calibration on unfamiliar hardware, integration, incident resolution, and the workshop that teaches their team to run it.
On-site bring-upDebuggingCustomer-facing
Rising with installs
Compiled from companies' own published team pages and job postings, August 2026, and deliberately worded as descriptions of the work rather than copies of anyone's job titles. These are role archetypes, not individuals: no person, employer, or profile is described here. Company names identify the sources of the pattern and imply no relationship with QuantumRecruits.