Staff Software Engineer, System Orchestration

Entangled Future; Oxford; Hybrid; GBP 90,000 - 150,000; Full time

Job summary

IonQ in Oxford, United Kingdom is seeking a Staff Software Engineer for the System Orchestration team within System Software. This hands-on role focuses on building and operating software that calibrates systems, decides next steps, and records actions for our quantum computers.

You will work with runtime, systems, and operator teams, contributing to a fault-tolerant control plane and scalable deployment practices to keep machines busy and productive.

Responsibilities

• Take on the problems that span the whole control plane - the durability and recovery contracts the rest of the design rests on.
• Make a machine's own assessment of its readiness something the rest of the control plane can rely on.
• Do the deep diagnosis of failures that only appear on a live system, under real load.
• Remove whole classes of failure across the fleet, rather than instances of them.
• Draw the boundaries between our services, settle them in writing, and move the code across them yourself.
• Make the correctness of a design demonstrable rather than argued.
• Build the tooling and test infrastructure that let the whole team move faster.
• Evolve how our services are deployed and operated as the fleet grows.
• Raise the bar of everyone around you through the code you write and the reviews you give.

Job description

Staff Software Engineer, System Orchestration at IonQ, Oxford, England, United Kingdom. A lead-level full time position in the Compute - Engineering team, listed under software engineering.

The Role

We are looking for a highly technical Staff Software Engineer to join our System Orchestration team in System Software at Oxford Ionics. In this role, you will be responsible for building and operating the software that keeps our systems calibrated, decides what they do next and keeps the record of what they did, contributing to the team's mission of keeping our quantum computers running useful work around the clock.

The trapped-ion quantum computers we are building will control 10,000 ions within two years, and all of that has to be kept in tune - settings that drift over minutes, hours and days. Without it a computer does not stop; it quietly starts producing invalid output.

Calibration routines, scientists' experiments and customer workloads all compete for physical hardware, and our team builds the control plane that arbitrates that: it schedules and prioritises programs, hands exclusive access to one at a time and takes it back cooperatively, streams results while a program is still running, and keeps the record of everything that ran. It runs on every quantum computer in our fleet. Its job is to keep that machine busy and productive: running quantum programs rather than waiting in between, and running them in spec - on a machine still hitting the fidelity it is meant to hit.

The ambition is for that to run without a person in the loop: machines that assess their own readiness, call for the calibrations they need, and keep a full history of how they were tuned.

You'd work closely with the runtime team who own real-time control, the systems teams who build and maintain our quantum computers, and the operators and scientists who run them.

This is a hands-on engineering role: you would be writing this software alongside our other staff engineers, not directing others who write it. You'll play an important part in shaping the services that support our work in building the world's most advanced quantum systems.

Responsibilities

• Take on the problems that span the whole control plane - the durability and recovery contracts the rest of the design rests on.
• Make a machine's own assessment of its readiness something the rest of the control plane can rely on.Do the deep diagnosis of failures that only appear on a live system, under real load.
• Remove whole classes of failure across the fleet, rather than instances of them.
• Draw the boundaries between our services, settle them in writing, and move the code across them yourself.
• Make the correctness of a design demonstrable rather than argued.
• Build the tooling and test infrastructure that let the whole team move faster.
• Evolve how our services are deployed and operated as the fleet grows.
• Raise the bar of everyone around you through the code you write and the reviews you give.