Senior Staff Technical Program Manager, Cloud Engineering Operations

Crusoe is on a mission to accelerate the abundance of energy and intelligence. As the only vertically integrated AI infrastructure company built from the ground up, we own and operate each layer of the stack — from electrons to tokens — to power the world's most ambitious AI workloads. When you join Crusoe, you join a team that is building the future, faster.

We're in the midst of the greatest industrial revolution of our time. The demand for AI compute is boundless, and power is a bottleneck. We're solving that — with an energy-first approach that makes AI infrastructure better for the world and faster for the people innovating with AI.

We're looking for problem-solving, opportunity-finding teammates with a sense of urgency, who believe in the scale of our ambition and thrive on a path not fully paved — people who want to grow their careers alongside a team of experts across energy, manufacturing, data center construction, and cloud services.

If you want to do the most meaningful work of your career, help our customers and partners advance their AI strategies, and be part of a high-performing team that believes in each other, come build with us at Crusoe.

About This Role

Crusoe's Cloud Engineering organization is 380 people today and hiring toward 550. Cloud Infrastructure is the layer everything else runs on — the compute, storage, and networking that turn racks of GPUs into a cloud, plus Crusoe Managed Kubernetes, the product customers use to run containers against them.

At 380 people, cross-team execution still works because a handful of people hold the whole picture in their heads. At 550 it does not. This role exists to replace that with an operating model.

You'll own how Cloud Infrastructure executes: how priorities get set, how dependencies get unblocked, how work gets tracked, and how leadership sees the truth without having to ask. You'll build it inside Cloud Infrastructure first — one org, as a design partner, close to the work — and then take what holds up and drive adoption across the rest of Cloud Engineering.

The ideal candidate has a technical background (software engineering, TPM, or technical product in an infrastructure context) and enough fluency in distributed systems to hold engineering teams to a shared definition of done without needing it translated. They embody servant leadership and full ownership, taking vague directives with complete autonomy to tactfully collaborate with cross-functional partners and deliver outcomes.

What You'll Be Working On

Execution inside Cloud Infrastructure

- Own the view of engineering priorities across Cloud Infrastructure: what each team is committed to this quarter, what's actually moving, and where the plan and reality have diverged.

- Coordinate and unblock teams on major initiatives spanning compute, storage, networking, and Crusoe Managed Kubernetes. When a dependency stalls, you're the one who gets it moving, not the one who documents that it stalled.

- Drive initiatives to committed dates, and surface slips early enough that leadership can act on them rather than absorb them.

- Measure time-to-unblock on cross-team dependencies and drive it down. If it can't be measured today, that's the first problem to solve.

Operating rhythm

- Run the Cloud Infrastructure staff meeting: agenda, pre-work, decisions captured, actions closed. The meeting should produce decisions, not a readout.

- Partner with the Cloud Product and Technical Product Management org on planning cycles so each cycle opens with pre-work complete and priorities pre-negotiated, and functions as a decision forum rather than a discovery exercise.

- Partner with the Chief of Staff organization and its program managers on headcount planning, the operating rhythm of the org, and strategic direction. You own execution inside the org; they own the org-wide layer. Keep that seam clean.

- Produce the recurring leadership updates and executive readouts on Cloud Infrastructure execution …