
Infrastructure
Provider, queue, and observability paths need careful ownership.
Role context
The day-to-day work stays close to product surfaces, infrastructure paths, learning delivery, or review sessions depending on the role.
Model quantum circuit, provider, simulator, and hardware target metadata in product-friendly ways.
Hands-on experience with at least one quantum SDK such as Qiskit, Cirq, PennyLane, Braket, CUDA-Q, or OpenQASM workflows.
Work directly on multi-provider quantum workflow infrastructure.

Infrastructure
Provider, queue, and observability paths need careful ownership.

Studio surface
The work reaches the editor, run state, and evidence packet.
More roles
Education
Shape QFlow Academy lessons, article-paper curation, hands-on exercises, and learning paths for teams adopting quantum workflows.
Infrastructure
Own the production foundation for QFlow Studio: Docker, Postgres, Redis, Kafka, runner services, backups, observability, and secure operations.
Product Engineering
Build the core QFlow Studio surfaces that turn quantum ideas into editable workflows, reviewed evidence, and clean team handoffs.
Product engineering
This role sits close to product code, provider execution, operational review, and the systems that keep workflow evidence dependable. Workflow surfaces, service behavior, and release quality.
(c) 2026 QFlow Studio. Professional quantum workflow infrastructure.
Security: security@qflow.studio