Emerging Personas and Tools for Hybrid Quantum-HPC Systems

The world of computing is standing at a quiet but profound crossroads. On one side sits the familiar, powerful machinery of high-performance computing, the massive supercomputers that have long helped scientists model climate patterns, simulate new materials, and solve complex equations. On the other side is the emerging field of quantum computing, which uses the strange rules of the subatomic world to process information in ways that classical machines cannot. For years, these two worlds operated in separate lanes. But as quantum machines have grown from tiny experiments into processors with tens or even hundreds of tiny units of information, a new reality has taken shape. Scientists and engineers are now stitching these two technologies together, creating hybrid systems where a quantum processor works hand-in-hand with a classical supercomputer to tackle problems that neither could solve alone. This fusion, often called quantum-centric supercomputing, promises to unlock solutions for everything from designing better batteries to understanding the fundamental forces of nature. Yet, as these systems come online in major research centers around the globe, a new challenge has emerged: the people who build, run, and use them come from vastly different backgrounds, and they often speak different technical languages.

A recent paper by researchers from IBM and Oak Ridge National Laboratory seeks to bring clarity to this growing ecosystem by mapping out the specific roles of the people involved. Instead of treating everyone who touches these systems as a single type of "quantum user," the authors identify six distinct groups, or personas, each with their own unique goals, tools, and data needs. The study highlights that as these hybrid systems mature, the most critical work is happening at the boundary where the quantum and classical worlds meet. Three new roles have emerged to manage this complex interface: the operator who keeps the lights on, the system engineer who builds the bridges between technologies, and the software developer who writes the code that makes them work together. By defining these roles, the researchers hope to create a common language that allows the diverse teams working on these systems to share information effectively and build tools that truly serve everyone's needs.

The paper begins by acknowledging that while the hardware is becoming more capable, the human element is becoming more complicated. In the early days of quantum computing, a single physicist might have handled everything from calibrating the machine to running the experiment. Now, with systems integrated into massive data centers, the work has split into specialized tracks. The authors describe six key personas that populate this landscape. First are the quantum kernel and library developers, the architects who design the fundamental building blocks of quantum algorithms. They focus on making circuits run efficiently on imperfect hardware, constantly trying to squeeze the most accurate results out of machines that are still prone to errors. They are the ones thinking about how to correct mistakes as they happen, ensuring that the quantum calculations remain reliable even when the underlying physics is noisy.

Working alongside them are the domain scientists, the experts in fields like chemistry or machine learning who want to use these machines to solve real-world problems. These users do not care about the intricate details of how the quantum circuits are built; they care about the answer. They view the quantum computer as a powerful tool to speed up their specific research, looking for ways to mix quantum steps with classical steps to get results faster and cheaper. Their primary concern is whether the hybrid system can deliver a solution to their scientific question within a reasonable timeframe and budget, regardless of the specific type of quantum hardware being used.

However, the paper argues that the most significant shifts are occurring in the three new roles that sit between these two groups. The QCSC operator is the person responsible for the day-to-day health of the entire system. They manage the scheduling, ensuring that the expensive quantum resources are not sitting idle while classical computers wait, and vice versa. They must also handle security, making sure that the right people have access to the right machines, and monitor the system for any signs of trouble, from a failing quantum processor to a network glitch. Their job is to keep the complex machinery running smoothly so that the scientists and developers can focus on their work.

Then there is the QCSC system engineer, the builder who constructs the actual connections between the quantum and classical worlds. This role involves co-designing the hardware and software stacks so that the quantum processor looks and acts like a standard, manageable part of the supercomputer. They work to create interfaces that allow different types of quantum machines to be used without rewriting the software every time. Their goal is to make the integration seamless, hiding the complexity of the quantum hardware so that the rest of the system can treat it as just another resource, like a graphics card or a storage drive.

Completing this trio is the QCSC HPC software developer, the expert in classical computing who writes the programs that orchestrate the hybrid workflows. These developers design the scripts that tell the system when to switch from classical processing to quantum execution and back again. They are focused on minimizing the time it takes for data to move between the two types of processors, ensuring that the system does not waste time waiting for information to travel. They build the tools that allow domain scientists to run their complex experiments without needing to understand the deep technical details of the quantum hardware.

The final persona identified is the quantum physicist, who acts as the feedback loop for the entire system. While they do not build the hardware, they are the ones who diagnose why a machine is performing poorly. They use specialized tools to probe the quantum processor, looking for the specific physical causes of errors, such as interference or signal loss. By understanding how the machine behaves under the stress of a busy data center, they can adjust the settings to improve performance, ensuring that the quantum processor remains reliable even as it is used by many different users.

A crucial finding of the paper is that each of these six groups needs different kinds of information to do their jobs. The researchers mapped out the specific data categories that each persona relies on, from the temperature and power usage of the facility to the detailed error rates of the quantum processor. For instance, the operator needs to see a broad view of system health and resource usage to make scheduling decisions, while the quantum physicist needs granular data about pulse sequences and error signatures to tune the machine. The domain scientist, meanwhile, cares mostly about the final results and the time it took to get them. The paper suggests that without a consistent way to represent and share this data, the entire system will struggle to function efficiently. If the tools used by the operator cannot talk to the tools used by the developer, or if the data the physicist collects cannot be easily understood by the scientist, the potential of these hybrid systems will remain locked away.

The authors emphasize that as these systems grow, the roles of the operator, system engineer, and software developer will become increasingly vital. A single data center might host different types of quantum machines, each with its own quirks and requirements, creating a massive administrative burden. The correctness of the scientific results will depend heavily on how well the classical and quantum parts are coordinated, and the ability to move workflows between different machines will be essential for the field to scale. By clearly defining who does what and what data they need, the paper provides a foundation for building better tools and standards. It is a call to action for the community to stop treating these systems as a collection of isolated parts and start viewing them as a unified ecosystem where people, tools, and data must work in harmony. The path forward is not just about building better quantum computers, but about building the human and technical infrastructure that allows them to be used effectively by the diverse teams that will drive the next era of scientific discovery.