Responsibilities:

In this position, you will work across the services that make up the control plane, supporting the effective delivery of a system every machine in the fleet depends on.

You'll have the opportunity to remove whole classes of failure and raise the bar for the engineers around you, contributing directly to the success of the System Software function.

Key responsibilities include:

• Take on the problems that span the whole control plane - the durability and recovery contracts the rest of the design rests on.
• Make a machine's own assessment of its readiness something the rest of the control plane can rely on.
• Do the deep diagnosis of failures that only appear on a live system, under real load.
• Remove whole classes of failure across the fleet, rather than instances of them.
• Draw the boundaries between our services, settle them in writing, and move the code across them yourself.
• Make the correctness of a design demonstrable rather than argued.
• Build the tooling and test infrastructure that let the whole team move faster.
• Evolve how our services are deployed and operated as the fleet grows.
• Raise the bar of everyone around you through the code you write and the reviews you give.

Requirements:

To be successful, you will need deep systems engineering experience, a track record of operating services where losing data is not an option, and the judgement to tell a problem worth solving structurally from one worth patching. We're looking for someone who wants to stay hands-on in the code at this level and can contribute effectively within a fast moving, highly technical team.

You'd be a great fit with:

• Expert systems engineering skills. Our System Orchestration layer is written in Rust, so either solid Rust experience or deep proficiency in another systems language and the appetite to work in a Rust codebase, including async programming.
• Deep experience building and operating stateful networked services in production, exposed over gRPC or REST, with a real grasp of error handling, observability and failure modes.
• A track record with data durability and correctness - persistence design, crash recovery, and migrations against live data you cannot afford to lose. We use PostgreSQL.
• The instinct to reach for determinism when chasing a timing or interleaving bug, rather than for more logging.
• Depth in the scheduling and workflow landscape - Temporal, Hatchet, Airflow, Slurm, Postgres-backed queues - and the judgement to borrow from it rather than reinvent.
• A track record of pinning down failures that others could not.
• A habit of settling design questions in writing, with the options compared as peers.
• Excellent communication skills both within software and across disciplines.

This is a hands-on engineering role: you would be writing this software alongside our other staff engineers, not directing others who write it. You'll play an important part in shaping the services that support our work in building the world's most advanced quantum systems. Previous exposure to quantum systems is not required.

Responsibilities:

In this position, you will work across the services that make up the control plane, supporting the effective delivery of a system every machine in the fleet depends on.

You'll have the opportunity to remove whole classes of failure and raise the bar for the engineers around you, contributing directly to the success of the System Software function.

Key responsibilities include:

• Take on the problems that span the whole control plane - the durability and recovery contracts the rest of the design rests on.
• Make a machine's own assessment of its readiness something the rest of the control plane can rely on.
• Do the deep diagnosis of failures that only appear on a live system, under real load.
• Remove whole classes of failure across the fleet, rather than instances of them.
• Draw the boundaries between our services, settle them in writing, and move the code across them yourself.
• Make the correctness of a design demonstrable rather than argued.
• Build the tooling and test infrastructure that let the whole team move faster.
• Evolve how our services are deployed and operated as the fleet grows.
• Raise the bar of everyone around you through the code you write and the reviews you give.

Requirements:

To be successful, you will need deep systems engineering experience, a track record of operating services where losing data is not an option, and the judgement to tell a problem worth solving structurally from one worth patching. We're looking for someone who wants to stay hands-on in the code at this level and can contribute effectively within a fast moving, highly technical team.

You'd be a great fit with:

• Expert systems engineering skills. Our System Orchestration layer is written in Rust, so either solid Rust experience or deep proficiency in another systems language and the appetite to work in a Rust codebase, including async programming.
• Deep experience building and operating stateful networked services in production, exposed over gRPC or REST, with a real grasp of error handling, observability and failure modes.
• A track record with data durability and correctness - persistence design, crash recovery, and migrations against live data you cannot afford to lose. We use PostgreSQL.
• The instinct to reach for determinism when chasing a timing or interleaving bug, rather than for more logging.
• Depth in the scheduling and workflow landscape - Temporal, Hatchet, Airflow, Slurm, Postgres-backed queues - and the judgement to borrow from it rather than reinvent.
• A track record of pinning down failures that others could not.
• A habit of settling design questions in writing, with the options compared as peers.
• Excellent communication skills both within software and across disciplines.

Responsibilities:

In this position, you will work across the services that make up the control plane, supporting the effective delivery of a system every machine in the fleet depends on.

You'll have the opportunity to remove whole classes of failure and raise the bar for the engineers around you, contributing directly to the success of the System Software function.

Key responsibilities include:

• Take on the problems that span the whole control plane - the durability and recovery contracts the rest of the design rests on.
• Make a machine's own assessment of its readiness something the rest of the control plane can rely on.
• Do the deep diagnosis of failures that only appear on a live system, under real load.
• Remove whole classes of failure across the fleet, rather than instances of them.
• Draw the boundaries between our services, settle them in writing, and move the code across them yourself.
• Make the correctness of a design demonstrable rather than argued.
• Build the tooling and test infrastructure that let the whole team move faster.
• Evolve how our services are deployed and operated as the fleet grows.
• Raise the bar of everyone around you through the code you write and the reviews you give.

Requirements:

To be successful, you will need deep systems engineering experience, a track record of operating services where losing data is not an option, and the judgement to tell a problem worth solving structurally from one worth patching. We're looking for someone who wants to stay hands-on in the code at this level and can contribute effectively within a fast moving, highly technical team.

You'd be a great fit with:

• Expert systems engineering skills. Our System Orchestration layer is written in Rust, so either solid Rust experience or deep proficiency in another systems language and the appetite to work in a Rust codebase, including async programming.
• Deep experience building and operating stateful networked services in production, exposed over gRPC or REST, with a real grasp of error handling, observability and failure modes.
• A track record with data durability and correctness - persistence design, crash recovery, and migrations against live data you cannot afford to lose. We use PostgreSQL.
• The instinct to reach for determinism when chasing a timing or interleaving bug, rather than for more logging.
• Depth in the scheduling and workflow landscape - Temporal, Hatchet, Airflow, Slurm, Postgres-backed queues - and the judgement to borrow from it rather than reinvent.
• A track record of pinning down failures that others could not.
• A habit of settling design questions in writing, with the options compared as peers.
• Excellent communication skills both within software and across disciplines.

This is a hands-on engineering role: you would be writing this software alongside our other staff engineers, not directing others who write it. You'll play an important part in shaping the services that support our work in building the world's most advanced quantum systems. Previous exposure to quantum systems is not required.

Responsibilities:

In this position, you will work across the services that make up the control plane, supporting the effective delivery of a system every machine in the fleet depends on.

You'll have the opportunity to remove whole classes of failure and raise the bar for the engineers around you, contributing directly to the success of the System Software function.

Key responsibilities include:

• Take on the problems that span the whole control plane - the durability and recovery contracts the rest of the design rests on.
• Make a machine's own assessment of its readiness something the rest of the control plane can rely on.
• Do the deep diagnosis of failures that only appear on a live system, under real load.
• Remove whole classes of failure across the fleet, rather than instances of them.
• Draw the boundaries between our services, settle them in writing, and move the code across them yourself.
• Make the correctness of a design demonstrable rather than argued.
• Build the tooling and test infrastructure that let the whole team move faster.
• Evolve how our services are deployed and operated as the fleet grows.
• Raise the bar of everyone around you through the code you write and the reviews you give.

Requirements:

To be successful, you will need deep systems engineering experience, a track record of operating services where losing data is not an option, and the judgement to tell a problem worth solving structurally from one worth patching. We're looking for someone who wants to stay hands-on in the code at this level and can contribute effectively within a fast moving, highly technical team.

You'd be a great fit with:

• Expert systems engineering skills. Our System Orchestration layer is written in Rust, so either solid Rust experience or deep proficiency in another systems language and the appetite to work in a Rust codebase, including async programming.
• Deep experience building and operating stateful networked services in production, exposed over gRPC or REST, with a real grasp of error handling, observability and failure modes.
• A track record with data durability and correctness - persistence design, crash recovery, and migrations against live data you cannot afford to lose. We use PostgreSQL.
• The instinct to reach for determinism when chasing a timing or interleaving bug, rather than for more logging.
• Depth in the scheduling and workflow landscape - Temporal, Hatchet, Airflow, Slurm, Postgres-backed queues - and the judgement to borrow from it rather than reinvent.
• A track record of pinning down failures that others could not.
• A habit of settling design questions in writing, with the options compared as peers.
• Excellent communication skills both within software and across disciplines.