Workforce Architecture for Quantum Operations — Operating Quantum Computers

A quantum platform is operated by a workforce, not by a single heroic physicist or one exceptional infrastructure engineer. The required skills cross physics, control systems, cloud operations, compiler engineering, security, scientific computing, and product management. The organization should design roles deliberately.

The NIST NICE Framework provides a structured vocabulary for cybersecurity work roles, tasks, knowledge, and skills [R194]. Quantum operations needs a similar role map, adapted to the physics-and-platform context.

Diagram loads as you read

Workforce Architecture for Quantum Operations · Figure 1

View diagram source

flowchart TB
    Platform[Quantum platform] --> Physics[Device and physics operations]
    Platform --> Control[Control and embedded systems]
    Platform --> Software[Runtime and platform engineering]
    Platform --> Science[Algorithm and validation engineering]
    Platform --> Security[Security and governance]
    Platform --> Product[Product and customer operations]

Role families

Family	Core responsibility
device operations	maintain hardware state, calibration quality, facilities interfaces
control engineering	manage timing, pulse, firmware, RF, FPGA, and feedback systems
runtime engineering	build brokers, APIs, schedulers, evidence stores, and developer tools
compiler engineering	maintain mappings, target models, optimization passes, verification suites
validation science	design benchmarks, statistical methods, and reproducibility protocols
governance and security	manage access, controls, evidence, threat models, and compliance
product operations	translate platform capability into user-facing service contracts

Diagram loads as you read

Role families · Figure 2

View diagram source

mindmap
  root((Quantum operations workforce))
    Device operations
    Control engineering
    Runtime engineering
    Compiler engineering
    Validation science
    Governance and security
    Product operations

Responsibility matrix

Diagram loads as you read

Responsibility matrix · Figure 3

View diagram source

flowchart LR
    Change[Change request] --> Device[Device ops]
    Change --> Compiler[Compiler team]
    Change --> Runtime[Runtime team]
    Change --> Security[Security]
    Change --> Science[Validation]
    Device --> CAB[Change advisory]
    Compiler --> CAB
    Runtime --> CAB
    Security --> CAB
    Science --> CAB
    CAB --> Decision[Approve, defer, or reject]

A RACI matrix should exist for every high-risk operating process: calibration promotion, compiler target release, runtime routing policy, external claim approval, evidence retention change, and provider onboarding.

Skills ladder

Diagram loads as you read

Skills ladder · Figure 4

View diagram source

stateDiagram-v2
    [*] --> Learner
    Learner --> Operator
    Operator --> Maintainer
    Maintainer --> Architect
    Architect --> Reviewer

Level	Expected behavior
learner	can run approved workflows in sandbox
operator	can execute runbooks and detect abnormal state
maintainer	can change components under review
architect	can design new control loops and contracts
reviewer	can approve high-risk changes and external claims

Avoiding single points of human failure

The platform should measure staffing resilience.

Diagram loads as you read

Avoiding single points of human failure · Figure 5

View diagram source

flowchart TB
    Capability[Capability] --> Primary[Primary owner]
    Capability --> Backup[Backup owner]
    Capability --> Docs[Runbook]
    Capability --> Drill[Recent drill]
    Capability --> Review[Reviewer pool]

Questions to ask:

Which systems have only one qualified operator?
Which runbooks require tacit knowledge?
Which approvals stop when one person is unavailable?
Which vendor relationships depend on one internal champion?
Which scientific methods cannot be independently reviewed?

Training loops

Diagram loads as you read

Training loops · Figure 6

View diagram source

flowchart LR
    Curriculum[Curriculum] --> Practice[Practice labs]
    Practice --> Shadow[Shadowed operations]
    Shadow --> Drill[Exercise participation]
    Drill --> Certification[Internal qualification]
    Certification --> Recert[Periodic recertification]
    Recert --> Curriculum

Training should include simulated incidents, evidence review, cost analysis, provider routing, and ethics of external claims. Quantum literacy alone is insufficient.

Chapter close

Workforce architecture is platform architecture. If responsibilities, skills, backups, and review authority are unclear, the technical stack will inherit those ambiguities.