Software Engineer, Non-Realtime Controllers

The Role

Quantum is now, and it's built here. Oxford Ionics, now part of IonQ, is pioneering the next generation of quantum computing. Using our world-leading trapped-ion technology, we're building the most powerful, accurate and reliable quantum systems to tackle problems that today's supercomputers cannot solve.

We're looking for an enthusiastic and highly technical Software Engineer for our Non-Realtime Controllers team who will thrive in our dynamic cross-disciplinary environment.

In this role, you will be responsible for working closely with our software engineers, our systems team, and our quantum scientists to build and operate the software that controls the hardware surrounding our quantum computers, contributing to the team’s mission of enabling our systems team to operate the physical quantum computers and our science teams to experiment building towards fault tolerant computation. Previous exposure to quantum systems is not required.

Responsibilities

In this position, you will work hands-on with hardware control end to end, from the device protocol up to a service running reliably across our fleet, supporting the effective delivery of non-realtime controllers that ensure that the critical supporting hardware of a quantum computer is observable, controllable and reliable (from cryogenic compressors to lasers, wavemeters, and various sensors).

You’ll have the opportunity to own areas of the hardware control surface end to end, from the device protocol up to a service running reliably across our fleet, contributing directly to the success of building utility-scale quantum computers.

Key Responsibilities Include

• Own a group of device controllers end to end, covering API design, implementation, rollout and ongoing operational health
• Make services robust against the ways real instruments fail and strengthen observability, health checking and alerting
• Bring devices onto our current framework, and roll the result out across the fleet without disrupting running experiments
• Work closely with the software, systems and science teams who depend on these services, and to ensure our work integrates seamlessly with the wider software architecture