Crusoe’s Cloud Engineering organization is 380 people today and hiring toward 550. When we sell capacity, we make customers two promises: it will be ready on the date we said, and it will work while they use it. At this scale, keeping those promises doesn’t happen by accident anymore. This role exists to make sure it happens on purpose.
You’ll lead Engineering Operations: the operating system that lets Cloud Engineering leadership agree on outcomes, execute, and keep its promises to customers. You’ll own the standing programs that make operations better every week (SLOs, incident follow-up, change safety, capacity delivery tracking, and operational data) and build the systems that feed the weekly executive Engineering Operations review. You don’t just report when a metric slips; you find the owner, hold them to the commitment, and make sure a decision happens fast.
You’ll start as the first hire in this function, working solo while you prove out the model above. As the mandate holds up, you’ll shape how the function grows: what to build, who to bring in, and what to keep lean.
This isn’t a role scoped to a single program or a single dashboard. You will be a strategic advisor to leadership on whether teams are actually executing operationally, and the person who makes clear owners, shared metrics, and a steady cadence stick across the org.
The ideal candidate has a technical background (software engineering, SRE, Technical Program Management, or product in an infrastructure context) and is close enough to production systems to hold senior engineering leaders to what they committed.