A quantum software engineer may spend the week fixing a compiler or keeping a cloud service running. A quantum algorithm researcher may spend it testing whether a new method justifies the cost of a run. The two titles sound alike. Employers look for different evidence when they hire for each.
In our November 14, 2026 snapshot, employers mention a PhD in 29 of 122 software engineering listings and in 27 of 35 algorithm and applications research listings. We read each of those mentions. One software listing asks for a PhD and states no alternative. Twelve research listings do.
Candidates can use the comparison to decide which evidence to lead with. Hiring managers who write these roles can use it to choose a title.
How we separated the two groups
We sorted listings by job title. The software engineering group has titles such as Software Engineer, Developer, Compiler Engineer, DevOps Engineer, and Site Reliability Engineer. The research group has titles such as Quantum Algorithms Scientist, Quantum Applications Scientist, and Quantum Algorithm Researcher. We left out managers, interns, and error correction titles, which are covered in the error correction careers guide. We then read the titles and removed listings whose work is something else, such as business development, FPGA design, and experimental physics.
The software engineering group has 122 listings from 30 employers. The research group has 35 listings from 13 employers. Both groups are narrower than the role families in our other guides. The software family there has 147 listings and includes managers and security engineers.
A listing is one advertisement on an employer’s careers site. We counted words in listing text. A listing that does not name a skill may still expect it.
What quantum software engineers build
Software engineers at quantum companies build the software between the user and the qubits. We see four kinds of work in the titles.
- Compilers. A compiler turns a user’s circuit into the operations one machine can run. QuEra, Infleqtion, and planqc all list compiler roles.
- Control and runtime software. These engineers write the software that runs experiments on the hardware and returns the results. Part of it is timing-critical. Atom Computing lists a Senior Software Engineer for control systems. IonQ lists Software Engineer, Non-Realtime Controllers at three levels, for the services that monitor and control supporting hardware such as lasers and cryogenic compressors.
- Cloud platforms and operations. These engineers operate the service customers log in to. IonQ lists a Staff Backend Software Engineer, Cloud Platform and a Staff Site Reliability Engineer.
- Scientific software and simulation. These engineers write numerical libraries, simulators, and tools for experimental teams. IQM lists a Software Engineer, QPU Numerics. D-Wave lists a Senior Scientific Software Developer who builds software tools for its processor development scientists.
These engineers mostly apply established software engineering to an unusual machine. An engineer who has built compilers, distributed systems, or laboratory control software has done comparable work.
What quantum algorithm researchers do
Algorithm researchers decide what a quantum computer should run and estimate what the run will cost. Employers describe three parts of the work in the listings.
- Algorithm design. They invent or improve algorithms and prove how the cost grows with problem size.
- Resource estimation and benchmarking. They estimate the logical qubits, operations, and runtime a fault-tolerant machine needs to solve a useful problem. They also compare the result with strong classical methods. Employers mention resource estimation, complexity, or fault-tolerant algorithms in 18 of the 35 listings.
- Applications. They work with customers in chemistry, materials, or optimization to choose which problems to run. IonQ lists Quantum Applications Scientist roles for life sciences.
Phasecraft, a company that develops algorithms, has eight of the 35 listings. QuEra, IonQ, and Quandela have four each.
The two sets of requirements compared
| What listings mention | Software engineering (122 listings) | Algorithm and applications research (35 listings) |
|---|---|---|
| Mention a PhD | 29 | 27 |
| Mention publications | 5 | 24 |
| Name Python | 92 | 23 |
| Name C++ | 55 | 11 |
| Name Rust | 43 | 1 |
| Mention compilers | 37 | 3 |
| Mention automated testing or CI/CD | 69 | 2 |
| Name a cloud platform or Kubernetes | 45 | 0 |
| Name a quantum toolkit such as Qiskit, Cirq, or CUDA-Q | 16 | 16 |
Employers mention a PhD in 24% of the software listings and 77% of the research listings. Employers also treat the PhD differently in the two groups.
| How the listing treats a PhD | Software engineering | Research |
|---|---|---|
| Asks for a PhD and states no alternative | 1 | 12 |
| Accepts a master’s degree or equivalent experience instead | 11 | 9 |
| Lists a PhD as preferred or welcome | 17 | 6 |
| Does not mention a PhD | 93 | 8 |
We classified each mention by reading it. Another reader could place a few listings differently.
Employers mention publications in 24 of the 35 research listings. The other 11 need a closer read. Some of those employers may accept a thesis or technical work as evidence of research ability.
Employers name a quantum toolkit in 16 of the 122 software listings. They name Python, C++, Rust, testing, and cloud tools far more often. A strong engineering record is therefore relevant to most of these listings. Check the duties of each one before you decide whether quantum evidence would strengthen the application. Candidates who want that evidence can start with an open-source toolkit. NVIDIA publishes CUDA-Q as open source, and IBM does the same with Qiskit.
Titles that mix the two
Six listings on the board combine both words in the title. Five are Quantum Algorithm Engineer titles, at Oxford Quantum Circuits, QuantWare, Phasecraft, and Sygaldry Technologies. We counted them in the research group. Infleqtion lists a Quantum Software Engineer – Algorithms & Applications, which we counted in the software group.
Candidates should look first at the main output the employer expects. An employer that expects new methods, experiments, and research results is describing a research role. An employer that expects dependable software, interfaces, and releases is describing an engineering role. Some roles need both. Ask how the employer will judge success in the first six months. We explain how to read requirement lists in decoding quantum job descriptions.
Hiring managers should state the expected output in the title and in the opening paragraph. For title choice, see how to write a quantum job description.
Posted salary ranges
Thirteen employers posted the 56 annual US dollar ranges we found on software engineering listings. Seven employers posted the 12 ranges we found on research listings.
| Group | Ranges | Median posted range | Median midpoint |
|---|---|---|---|
| Software engineering, all levels | 56 | US$150,000–200,000 | US$178,000 |
| Software engineering, mid-level | 18 | US$133,500–171,500 | US$155,500 |
| Software engineering, senior | 19 | US$146,000–191,000 | US$172,500 |
| Software engineering, lead or principal | 17 | US$175,000–235,000 | US$201,500 |
| Algorithm and applications research, all levels | 12 | US$148,000–211,000 | US$180,000 |
We set the levels ourselves from each title. Oratomic opens two of its software listings to all experience levels. We left those two out of the level rows.
The median midpoint is US$178,000 in the software sample and US$180,000 in the research sample. Twelve ranges is a small sample. The two groups also have different employers and levels. We cannot conclude from these figures that the two careers pay the same.
The median posted range pairs the median minimum with the median maximum. The median midpoint is the median of each listing’s own midpoint, so it need not fall halfway between the two. Employers describe most of these ranges as base salary, and a range is not an offer. For the method, see the salary snapshot, which reports figures from November 12.
Where the roles are
Employers mark 91 of the 122 software engineering listings on-site, 26 hybrid, and five remote. They mark 31 of the 35 research listings on-site, two hybrid, and two remote. Employers mark 75 of all 1,287 listings on the board remote, which is a similar share. For the pattern across the board, see remote quantum jobs.
We class 51 of the software listings as mid-level, 40 as senior, and 29 as lead or principal. Two are open to all experience levels. We class 22 of the research listings as mid-level, five as senior, and eight as lead or principal.
How to choose
Choose software engineering if you want to ship code that other people run every day. Employers value testing discipline, performance tuning, and careful interfaces. Ninety-three of the 122 software listings do not mention a PhD.
Choose algorithm research if you want to work on open questions and publish. A PhD is the common route. Twelve of the 35 research listings ask for one outright. Nine more accept equivalent research experience or a master’s degree.
Bring evidence that fits the role. For an engineering role, show a contribution with tests, benchmarks, and documentation. For a research role, show an algorithm comparison that states its assumptions, its classical baseline, and the cases where the method fails. We describe the move from academic research to a company in from postdoc to industry.
People do move between the two. A researcher who enjoys building tools can apply for scientific software roles, where employers value research experience. An engineer who wants to become an algorithm researcher needs a research record, and most people build one in a PhD.
Candidates who want to work on hardware in a laboratory can start with the guide to control electronics roles instead.
Browse the open software and algorithm roles on Quantum Careers.
