Job search
Quantum Software Jobs: Separate Platform Engineering from Quantum Research and Hardware Roles
Read current quantum-company roles through platform responsibilities, scientific ownership and hardware deliverables before comparing qualifications.
Quantum software jobs can involve building reliable services, scientific data platforms and tools for specialist users. Some of that work draws on ordinary production software experience; other roles require ownership of quantum experiments, research methods or physical hardware. Read the responsibilities and qualifications together before assuming that a physics PhD is either essential or unnecessary.
The distinction is visible within one employer. Rigetti currently describes an internal software role where quantum background is optional, an experimental systems role requiring a relevant PhD, and a mechanical role with its own engineering requirements. This guide reviews those public descriptions checked on October 14, 2026, alongside explicitly fictional examples. We did not apply, run quantum experiments or test the employer's systems.
LandOffer publishes this guide. You can browse recent roles on LandOffer.ai, then inspect the employer's full posting. Your goal is to identify whether you would own a software service, a scientific conclusion or a physical system, and choose evidence that supports that responsibility.

Working at a quantum company does not define your role
A company's technology gives context to the work, but it does not establish every employee's specialty. A software engineer supporting scientists may need to understand their workflow well enough to preserve data meaning and build useful tools. That differs from being responsible for the experiment that produced the data or the scientific explanation of its results.
Start with the decision the employee must make. Are they deciding how a service handles changing clients, which experiment should test a hypothesis, or how an assembly should meet physical requirements? Those questions identify different forms of ownership even when all three people work together and use software.
Keep mixed responsibilities visible. A research-oriented engineer can write substantial code; a platform engineer can work close to instruments. Neither fact resolves the degree or experience requirements. Find the main output, the specialist knowledge attached to it and the person who evaluates its success. That tells you whether to prepare a software reliability example, a scientific result or a hardware design decision.
The examples here are a bounded view of current US descriptions at one quantum employer. They do not establish market-wide demand, a universal hiring route or the requirements of every compiler, control, high-performance computing or quantum-algorithm team.
Compare three current responsibilities at Rigetti
These descriptions were accessible through the employer's public job board at the review date. The pages did not supply an original posting date; continued availability needs a current check when you apply.
| Official role | Responsibility that changes the reading | Qualification boundary |
|---|---|---|
| Senior Software Engineer, Internal Systems, Berkeley or Fremont, hybrid | Data-intensive Python services, client compatibility, testing and platform observability | Production backend experience; physics, math or quantum background is an advantage rather than a requirement. |
| Lead Quantum Engineer, Systems Performance, Berkeley, hybrid | Lead experimental programs and improve superconducting quantum systems | Relevant PhD, technical leadership and hands-on cryogenic, RF and quantum-device measurement experience. |
| Senior Mechanical Engineer — Cryogenic, Berkeley, hybrid | Own mechanical architecture, drawings, prototypes and hardware qualification | Mechanical or related BS/MS, seven-plus years of hardware ownership and specialist design/analysis experience. |
The systems-performance role also mentions Python. Its scientific and experimental requirements remain central. The mechanical role uses analysis software, including tools such as SolidWorks and COMSOL or ANSYS, to make hardware decisions. Read those tool names beside the experimental or mechanical responsibility they support.
The software description names SQL, cloud experience and collaboration with scientific users. Compare those conditions with your own production work; a tutorial alone does not establish the professional responsibilities being described.
Interpret the PhD clause at the level of the posting
Rigetti's internal software description explicitly allows candidates to learn the domain and does not list a PhD minimum. That supports a narrow conclusion: this particular role should not be ruled out solely because you are not a quantum researcher. It does not prove that every software opening at this employer, or elsewhere in quantum computing, uses the same requirements.
In the experimental systems example, the degree is accompanied by direct measurement experience and a scientific record. Read that combination as a qualification for the work being owned. A doctorate in an unrelated subject, or Python experience alone, does not demonstrate the described experimental expertise.
The mechanical example shows another route: its education clause is not a physics-PhD clause. The role still requires substantial mechanical ownership and relevant operating-environment experience. Replacing “quantum specialist” with “software engineer” would lose the actual requirement instead of broadening your options.
Mark each clause as required, preferred or unclear, using the employer's wording. If a degree is absent from the visible description, retain that observation without inventing an internal screening policy. If an equivalence route is unclear, ask about that exact condition. A course certificate does not establish a waiver the employer has not offered.
Separate infrastructure work from scientific ownership
For a platform opening, look for evidence of a maintained system: interfaces, data contracts, migrations, release checks, failure diagnosis and users. These help you distinguish production responsibility from a personal notebook or a one-off analysis script. The latter can show useful learning, but its ownership and operating context are different.
For a research opening, look for the question the researcher must answer and the evidence used to evaluate the conclusion. Ask whether the employee proposes experiments, interprets measurements, develops an algorithm or turns a research method into dependable capability. Those tasks require different preparation. The systems-performance example above concerns experimental quantum systems, not a theoretical-algorithm vacancy.
For hardware, look for physical deliverables and qualification work. Using a simulator can support a design decision, while maintaining the simulator as a product is a different responsibility. If you know the tool but have not owned the described physical design, explain the limit directly.
High-performance computing is also contextual. Rigetti lists HPC experience as a nice-to-have in the software example. That is not evidence of a separate current HPC opening. If another posting emphasizes scheduling, compute resources or distributed workloads, inspect its own duties and constraints before treating it as quantum research or ordinary cloud operations.
A completed fictional handoff: keep scientific data interpretable
Consider Lena, a fictional software engineer maintaining a service used by two lab-analysis clients. The records and outcomes below are invented teaching examples, not a Rigetti implementation, an actual migration or a quantum experiment. They illustrate how platform work can support scientific users without establishing a scientific result.
An old client expects a duration in milliseconds. A new client uses a revised contract with duration in seconds. The same synthetic record, Q42, represents 125 milliseconds, which equals 0.125 seconds. The migration must preserve that meaning while the clients use different formats.
An unsafe translation would send the number 0.125 to a client that still interprets it as milliseconds. The numeric value looks valid, but the meaning changes by a factor of 1,000. A successful request or an accepted JSON payload would therefore be insufficient evidence that the handoff is correct.
Lena's fictional compatibility adapter keeps the two contracts separate. It returns duration_ms: 125 under the old format and duration_s: 0.125 under the new one. The legacy response identifies schema version 1; the new response identifies version 2. Both identify Q42, so the format change does not create a second experimental record. The completed record is:
| Consumer | Format and response | Meaning preserved |
|---|---|---|
| Legacy client | Version 1; Q42; duration_ms: 125 |
125 milliseconds |
| New client | Version 2; Q42; duration_s: 0.125 |
The same duration in seconds |
| Incorrect legacy translation | Version 1; Q42; duration_ms: 0.125 |
Wrong unit/value combination; reject this mapping |
The handoff memo is also complete. Lena owns the schema and compatibility change, checks both client outputs and documents the release boundary. The scientist owns the experimental context and interpretation of the measurement. The hardware engineer owns the relevant instrument assembly and its qualification. Preserving the data representation does not transfer either specialist responsibility to Lena.
In this fictional case, the supported application statement is: “Maintained client compatibility during a scientific-data schema migration, preserving duration units across two formats.” A claim that Lena improved qubit fidelity or discovered a quantum algorithm would go beyond the assumed work. The example provides no measurement or research evidence for those claims.

The lesson is more specific than “software skills transfer.” You need to identify the contract, the users, the failure you prevented and the outcome you can verify. In scientific environments, correct transport and storage matter, but interpreting what the underlying experiment demonstrates remains a separate question.
Choose evidence that matches the team's responsibility
If you have comparable real work, describe it in its actual setting. A healthcare research service, an industrial measurement pipeline or a lab-data application can show collaboration with specialist users. Explain what you maintained and what those users needed. Do not relabel a different field as quantum computing to make the example sound closer.
Useful platform evidence can include an interface transition, a diagnosed data error or a release that preserved client behavior. State how you checked the result and which decisions you owned. Distinguish observations of the software from conclusions about the science it supports.
A quantum tutorial can demonstrate curiosity and a bounded learning exercise. It does not establish production service ownership, direct device-measurement experience or a publication record. It is more useful when you can explain its assumptions and limitations than when you attach a broad “quantum engineer” label to it.
For specialist work, keep the same discipline. A research project may show strong experimental reasoning without demonstrating operation of a production platform. A hardware project may demonstrate assembly and qualification without proving that you maintained a data service. Choose the evidence the opening actually needs rather than expecting one credential to cover every technical responsibility.
Three fictional candidates reach different choices
Lena's assumed professional record includes production Python services, relational databases, cloud operations and collaboration with scientific users. She has no quantum PhD or hands-on quantum-device measurement record. The internal software direction is her closer functional match. She would present an actual software contribution and ask how the team teaches the domain and defines the first project.
Arun is a fictional candidate with a relevant PhD and direct quantum-device experiments, but no ownership of a production backend service. The experimental direction is closer to his assumed evidence. He should still compare leadership and industry requirements carefully. His research background does not automatically answer a platform team's questions about releases, client compatibility or operations.
Celia is a fictional mechanical engineer whose record includes cryogenic assembly design and hardware qualification. Her strongest evidence concerns the physical system. The hardware direction gives her a relevant comparison; a Python-heavy role may require additional evidence she has not supplied.
These are editorial choices based on assumed records, not eligibility decisions or hiring outcomes. Each candidate uses the comparison to choose a role to investigate and an example to explain. All three still need to check the full posting, location, employer conditions and current application availability.
Ask a narrower question before committing to training
Instead of asking whether quantum computing “needs a PhD,” ask whether the opening requires you to make scientific decisions or to build systems for people who make them. Then identify the explicit education and experience conditions. Answer it for the opening you are considering, using the employer's duties and qualification clauses.
Ask who interprets experimental results, who maintains the services that carry them and how much domain knowledge the first assignment requires. For a platform role, clarify which services and operating responsibilities belong to the employee. For a specialist role, ask which prior project evidence best demonstrates the required experience. Request details of any assessment from the recruiter rather than assuming a common interview format.
Choose one current opening and write a short note naming its responsibility, the requirement you can support and the gap you need to discuss. Browse recent roles on LandOffer.ai, then use the employer's description to complete that comparison before choosing a course or sending an application.
Sources and Further Reading
- Rigetti: Senior Software Engineer, Internal Systems — platform duties, production experience and optional domain background.
- Rigetti: Lead Quantum Engineer, Systems Performance — experimental leadership and specialist qualifications.
- Rigetti: Senior Mechanical Engineer — Cryogenic — mechanical deliverables and hardware requirements.


