SlipstreamJobs tracks this role from the company's public career site. Apply directly on the employer's site.
Salary: USD 230,000 - 280,000 / annual
Crusoe is a vertically integrated AI infrastructure company building the energy and compute backbone for large-scale AI workloads. The company owns and operates the full stack from power generation through cloud services, positioning itself at the intersection of energy, manufacturing, and AI infrastructure.
You will own the execution operating model for Cloud Infrastructure, a 380-person organization scaling to 550. Currently, a handful of people hold the entire picture of priorities, dependencies, and execution health in their heads. Your role is to replace that with a scalable, systematic operating model that enables the organization to function at scale without losing visibility or coordination.
Key responsibilities include:
**Execution Ownership**: Own the view of engineering priorities across Cloud Infrastructure teams (compute, storage, networking, Crusoe Managed Kubernetes). Track what each team is committed to, what's actually moving, and where plan and reality diverge. Actively unblock cross-team dependencies—when a dependency stalls, you drive resolution, not just documentation. Drive major initiatives to committed dates and surface slips early enough for leadership to act.
**Operating Rhythm**: Run the Cloud Infrastructure staff meeting as a decision-making forum, not a readout. Partner with Product and Technical Product Management on planning cycles so they open with pre-work complete and priorities pre-negotiated. Coordinate with the Chief of Staff organization on headcount planning, operating rhythm, and strategic direction. Produce recurring leadership updates and executive readouts on execution health.
**Owning the Unowned**: Take on cross-cutting problems without natural owners and drive them to outcome or named ownership. Support the Chief of Staff on strategic projects spanning Cloud Infrastructure and Cloud Engineering.
**Systems of Record**: Drive Jira adoption and issue-tracking discipline until Jira becomes the actual source of truth teams work from. Own Jira, Confluence, and dashboard artifacts—structure, access, hygiene, automation. Build toward a view of execution health that leaders can read at a glance without human assembly.
You will start with incomplete documentation, informal processes, and major initiatives already in flight. You'll operate with full autonomy, using precise communication and follow-through to align cross-functional partners without formal authority. A large share of this role is written communication—single messages that make thirty engineers do the right thing without a meeting.
**Requirements**:
- 10+ years in technical program management, software engineering, or technical product role, close enough to production systems to read a design doc and identify real risks
- Track record driving multi-team technical initiatives to committed dates in infrastructure, cloud, or platform organizations (driving, not just coordinating)
- Evidence of building processes rather than administering them: designed an operating cadence or planning model, proved it in one place, drove adoption across other teams
- Ability to unblock without formal authority; engineering leads respond because you're precise about what you need, why, and by when, and you follow through
- Real fluency with issue tracking at scale; experience driving Jira adoption or equivalent migration where the hard part was behavior change, not configuration
- Ability to turn messy, multi-source data into clear execution-health pictures; prefer building the query to requesting the report
- Comfort with ambiguity and incomplete documentation
- Excellent written communication
- Scrappy, low-ego, high-drive mindset
**Bonus qualifications**:
- Time at AWS, GCP, Azure, CoreWeave, Lambda Labs, or similar cloud provider
- Hands-on familiarity with Kubernetes and operating-system or distributed-systems work at infrastructure layer
- Background in AI/ML infrastructure or large-scale GPU fleets
- Experience running operating-model or planning-process rollouts across multiple organizations with measurable adoption
- Working knowledge of Jira automation, Confluence, Grafana, or Sigma
- Appetite to grow this into a function and manage a small team as programs fan out
