Staff Software Engineer, Non-Realtime Controllers

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.

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 Staff Software Engineer for our non-realtime controllers team who will thrive in our dynamic cross-disciplinary environment. You'd be working closely with our skilled software engineers, our systems teams who operate the physical quantum computers, and our world-leading quantum scientists to build and operate the software that controls the hardware surrounding our quantum computers. Previous exposure to quantum systems is not required.

You will take on our most demanding hardware integrations and the framework work that makes every other controller better. This is a hands-on engineering role: you would be the most experienced engineer writing controllers, not the one directing others to write them.

Responsibilities

This is a hands-on engineering role. Your influence comes from the code you ship and review, and from the problems you take off everyone else's plate.

Key Responsibilities Include

• Take on our most demanding device integrations, and do the deep diagnosis of problems that only appear against real hardware in a live lab.
• Remove whole classes of failure across the fleet, rather than instances of them.
• Improve the shared framework yourself, and bring the existing controllers along with each change.
• Build the tooling, simulators and test.