
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.
QFlow needs quantum systems engineers who can make provider behavior understandable to product users. You will work on OpenQASM/Qiskit/Cirq-style circuit handling, simulation expectations, provider schema checks, route rationale, queue status, and evidence packets. The goal is to help teams run serious pilots without scattering context across notebooks, cloud consoles, screenshots, and private spreadsheets. You will help define what a safe, inspectable quantum run record should contain.
The outcomes this role is expected to make visible and dependable.
Experience and working habits that make the hiring review easier.
How the role is supported day to day.
The process is structured around practical review and clear next steps.
Full Time / Remote / Mid Senior
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.