At a Glance
- Tasks: Lead the hardware test team for cutting-edge quantum computing systems.
- Company: Join IonQ, a leader in quantum technology innovation.
- Benefits: Competitive salary, flexible work options, and opportunities for growth.
- Other info: Dynamic environment with a focus on collaboration and innovation.
- Why this job: Be at the forefront of quantum computing and make a real-world impact.
- Qualifications: Experience in software testing and CI/CD processes required.
The predicted salary is between 63000 - 77000 £ per year.
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. Joining Oxford Ionics means becoming part of a global IonQ team that is transforming the future of quantum technology - faster, at scale, and with real world impact.
We are looking for a HIL (hardware-in-the-loop) Test Manager to build and lead the team that owns our hardware test infrastructure: the systems our quantum-computer control software is tested on before it ever touches a real quantum system. Every software and science change is validated against shared test systems before it reaches a quantum computer. We are now investing in the next generation of these: representative QA systems for fast feedback, and staging systems as close to a production quantum system as possible, with all the real-time and non-real-time hardware. You will define these systems, build them with our manufacturing team, and own them through their life: maintenance, upgrades to each programme baseline, and availability to the teams that depend on them.
This is a build-from-scratch role with budget and rack space already allocated. You will also act as our test architect: we have deep physics and engineering expertise, and you will bring the formal software-testing experience to shape what gets tested where (simulation versus real hardware) and how testing gates releases. You will start with one engineer hire alongside you and grow the team deliberately, turning the test estate into a reliable service the engineering teams depend on.
Responsibilities:
- You will own the hardware test estate end to end and define how it is used. That includes making the estate self-service, with clear reservation and scheduling, published state and availability, and runbooks. Teams own their tests and what they gate on; your team owns the rigs and the plumbing.
- You will hire, develop and lead a small team, starting with a hardware-focused test systems engineer, and work across the business with the wider Quantum System Infrastructure (QSI) teams, Compute IT, Facilities, Manufacturing, Software and Science.
- Key responsibilities include:
- Own the hardware test estate: today's CI systems through to the new QA and staging systems for our current and future quantum-computer programmes.
- Define the test-system architecture: which systems exist, what each one represents, and how teams use them.
- Plan and deliver new test-system builds with Manufacturing, and own ongoing maintenance and upgrades so every test system tracks its programme's current baseline.
- Shape the testing strategy with the software teams: what runs in simulation or against emulators, what requires real hardware, and how hardware-in-the-loop results gate releases.
- Drive automation throughout: provisioning, firmware flashing, recovery and configuration of test systems as code, not manual effort.
Requirements:
We are looking for an experienced test leader who can bring structure, ownership and pace to how we validate software against real hardware. We treat QA and test as one discipline. You will have a working knowledge of modern CI/CD (GitHub Actions or comparable) and an automation-first instinct: repeatable and reliable over manual and heroic. You will be able to guide and review test-automation development in Python or similar; you direct the code, you do not have to be its main author.
These systems serve many teams, so strong collaboration and low ego matter: you will need to bring people with you as ownership and ways of working evolve. You will be comfortable with ambiguity and building from scratch in a fast-moving technical environment. Experience in quantum computing is not required. Experience with complex hardware and software systems or similarly demanding engineering environments is an advantage.
You'd be a great fit with:
- A strong software testing and QA background covering test strategy, test infrastructure and continuous integration. This is the core requirement.
- Experience owning test infrastructure where software is validated against real hardware, for example network and security appliances, autonomous vehicles, drones or defence systems, robotics, or other embedded products.
- Test-architecture capability: designing representative test environments, deciding what to test where, and balancing simulation against hardware-in-the-loop.
- Practical understanding of the pitfalls of testing with hardware in the loop, such as flaky devices, contention for rigs and environment drift. Deep hands-on electronics skills are not required.
- Experience leading or building a small testing team or function.
Hardware-in-the-loop (HIL) Test Manager in Oxford employer: Oxford Ionics
At IonQ, we pride ourselves on being at the forefront of quantum computing innovation, offering a dynamic work environment where collaboration and creativity thrive. As a Director, Systems Software, you will not only lead a talented team but also have access to exceptional career growth opportunities, competitive compensation, and a comprehensive benefits package that includes flexible working arrangements and private medical insurance. Join us in College Park, Maryland, and be part of a world-class community dedicated to shaping the future of technology.
StudySmarter Expert Advice🤫
We think this is how you could land Hardware-in-the-loop (HIL) Test Manager in Oxford
✨Join Local Tech Meetups
Get out there and mingle with fellow developers by joining local tech meetups. It’s a fantastic way to meet people who might be working at Oxford Ionics or know someone who does. Plus, you can pick up some trendy tech skills and trends while you're at it!
✨Contribute to Open Source Projects
Show off your coding chops by jumping into open-source projects. Not only does this give you practical experience, but it also gets you noticed in the dev community. You'll create a killer portfolio that speaks volumes about your skills to Oxford Ionics.
✨Tap into Online Developer Communities
Don’t underestimate the power of online developer communities like GitHub, Stack Overflow, and even Reddit. Participate in discussions, share your projects, and build your visibility. We can often find opportunities through these channels that can lead to a full-time gig at companies like Oxford Ionics.
✨Explore Job Boards Specifically for Tech Roles
Keep your eyes peeled on job boards that focus on tech roles. Sites like TechCareers or Stack Overflow Jobs can often have listings for companies like Oxford Ionics that might not show up on broader job sites. Make it a habit to check these regularly, and don’t hesitate to apply directly through our website!
We think you need these skills to ace Hardware-in-the-loop (HIL) Test Manager in Oxford
Some tips for your application 🫡
Show off your coding skills:When applying for a software engineering role, it's super important to showcase your coding skills. Make sure your CV includes your tech stack, any relevant programming languages you’re comfortable with, and examples of projects you've worked on. If you have a GitHub profile, link it up! We love to see code in action.
Tailor your portfolio:For a full-time role, we’d expect to see some solid examples of your work in your portfolio. Make sure to include at least two or three projects that highlight your problem-solving skills and your ability to work with different technologies. Focus on the projects that are most relevant to the position at Oxford Ionics.
Craft a killer cover letter:Your cover letter is your chance to stand out—make it personal! Explain why you want to work at Oxford Ionics and how your skills align with the role. Show us your passion for software development. We dig enthusiastic candidates who understand the value of collaboration and continuous learning!
Be clear and concise:When it comes to writing your CV and cover letter, clarity is key. Avoid jargon that could confuse us and stick to simple, direct language. Highlight your achievements with quantifiable results where possible, and keep everything easy to read. A well-organised application goes a long way!
How to prepare for a job interview at Oxford Ionics
✨Brush Up on Your Coding Skills
For a full-time software engineering role, it's crucial that we stay sharp with our coding abilities. Expect technical questions that might involve solving problems on the spot or discussing algorithms. Practise on platforms like LeetCode or HackerRank to get comfortable with the types of questions that often come up.
✨Know Your Tools and Frameworks
Make sure we’re well-acquainted with the tools and technologies listed in the job description. Familiarise ourselves with any specific frameworks or programming languages mentioned. If Oxford Ionics uses React or Node.js, for instance, be ready to discuss how we’ve used them in previous projects or coursework.
✨Showcase Your Projects
Bring along a portfolio that highlights our best work. This could be code samples, GitHub repositories, or any side projects we’ve built. Make sure we can talk through our thought process for each project, especially the challenges we faced and how we solved them—this shows our problem-solving skills in action.
✨Prepare for Behavioural Questions
While technical skills are key, full-time positions also require cultural fit. Be ready to discuss our previous experiences and how we handle teamwork, conflict, and deadlines. Brush up on the STAR method—Situation, Task, Action, Result—to clearly articulate our past experiences when discussing how we've contributed to a team.