Senior Staff Program Lead, Cloud Engineering

Crusoe•Sunnyvale, CA

3d•$230,000 - $280,000

About The Position

Crusoe is looking for a Senior Staff Program Lead, Cloud Engineering to join their growing team. This role is crucial for ensuring that Crusoe's Cloud Engineering organization can meet its promises to customers regarding capacity readiness and reliability. The position involves leading Engineering Operations, which acts as the operating system for Cloud Engineering leadership to align on outcomes, execute effectively, and maintain customer trust. The role will own standing programs focused on continuous operational improvement, such as SLOs, incident follow-up, change safety, capacity delivery tracking, and operational data management. The successful candidate will build systems to support weekly executive reviews, ensuring accountability and driving decisions. This is a strategic role that advises leadership on operational execution and aims to establish clear ownership, shared metrics, and a consistent operating cadence across the organization. The ideal candidate will have a technical background and a deep understanding of production systems to effectively engage with senior engineering leaders.

Requirements

10+ years in software engineering, SRE, technical program management, or a technical product role, with close proximity to production systems.
A track record of leading org-wide programs at the staff level or above.
Proven ability to drive accountability across senior engineering leaders without formal authority.
Comfortable starting as a team of one and driving impact without an immediate team.
Experience operating in high-growth infrastructure environments where processes are still being built.
Ability to work across teams without formal authority and build trust through follow-through.
Skill in transforming messy, multi-source data into a clear picture of organizational health.
Ability to identify key metrics that drive decisions over numerous dashboard metrics.
Experience designing operating rhythms (weekly reviews, business reviews, incident reviews) that are actively used by leaders and are light for contributing teams.
Scrappy, low-ego, high-drive individual contributor who builds programs and tooling independently.

Nice To Haves

Time spent at AWS, GCP, Azure, CoreWeave, Lambda Labs, or a similar cloud provider.
Experience running an SLO, incident review, or change management program at a cloud or infrastructure company.
Familiarity with incident.io, Opsgenie, PagerDuty, or similar incident management platforms at scale.
Background in AI/ML infrastructure.

Responsibilities

Lead Engineering Operations, acting as the operating system for Cloud Engineering leadership to agree on outcomes, execute, and keep promises to customers.
Own standing programs that improve operations weekly, including SLOs, incident follow-up, change safety, capacity delivery tracking, and operational data.
Build systems that feed the weekly executive Engineering Operations review, ensuring risks have owners, dates, and next steps.
Define and track key operational metrics such as usable capacity, SLO attainment, MTTD and MTTR, customer-found incidents, on-time capacity delivery, milestone slip, change failure rate, follow-up closure rate, and change policy compliance.
Partner with engineering, SRE, data engineering, and product teams to ensure operational data accuracy and establish a single source of truth for metrics.
Collaborate with engineering, TPM, product, SRE, data scientists, customer success, and data center operations to ensure smooth operations across all functional areas.
Work towards a single pane of glass for understanding the organization's operational health.
Own the weekly executive Engineering Operations review, including building systems, data, and pre-reads.
Run the weekly operations planning forum and partner with Product on a monthly business review.
Make ownership explicit by defining clear accountable owners, swimlanes, and articulated outcomes for programs and metrics.
Hold teams accountable for commitments, drive incident follow-ups, overdue actions, and slipping milestones to closure.
Operate as an individual contributor initially, proving out programs, metrics, and cadence before requesting headcount.
Make the case for additional capacity as scope grows and assist in hiring and onboarding new team members.
Own the evolution of the operating system, retiring ineffective processes and minimizing overhead on engineering teams.