Staff Technical Programme Manager, Systems Software

Job description

About IonQ: IonQ, Inc . [NYSE: IONQ] is the world’s leading quantum platform and merchant supplier - delivering integrated quantum solutions across computing, networking, sensing, and security. IonQ’s newest generation of quantum computers, the IonQ Tempo, is the latest in a line of cutting-edge systems that have been helping customers and partners including Amazon Web Services, and AstraZeneca achieve 20x performance results and accelerate innovation in drug discovery, materials science, financial modeling, logistics, cybersecurity, and defense. In 2025, the company achieved 99.99% two-qubit gate fidelity, setting a world record in quantum computing performance . Headquartered in College Park, Maryland, IonQ has operations in California, Colorado, Massachusetts, Tennessee, Washington, Italy, South Korea, Sweden, Switzerland, Canada, and the United Kingdom. Our quantum computing services are available through all major cloud providers, while we also meet the needs of networking and sensing customers across land, sea, air, and space. IonQ is making quantum platforms more accessible and impactful than ever before. Role: System Software builds the software that runs IonQ's quantum computers: the runtime, orchestration, quantum tools, controllers and transport software that sit between the Quantum Operating System and the hardware. It is where a next-generation system either comes together or doesn't. We're hiring a Staff Technical Programme Manager to lead delivery across this stack. You'll report to the Group Program Manager, Software in our Programme Management Office and be matrixed to the VP, Software for day-to-day work. You'll work across five engineering teams (runtime, orchestration, quantum tools, controllers and transport) and the interfaces between them and their cross-functional stakeholders, serving several next-generation system programmes at once, with hardware being co-developed alongside the software and teams in both Oxford and the US. Those programmes draw on the same engineers, so the central problem of this role is making sure that capacity is spent by decision, not by default. We run a centralised PMO model. This role will not own engineering headcount or define product but it will make the programme around those things run. It carries real ownership of delivery: the plan, the trade-offs put in front of decision-makers, and the honesty of…