The opportunity
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.
What you'll do
Own the technical direction: Set the architecture and scaling roadmap for Crusoe Cloud's container registry. Establish the patterns and standards the team builds against, and stay accountable for scalability, reliability, and maintainability over the long haul.
Ship end-to-end: Drive high impact changes from design through production, and stay accountable for their scalability, reliability and maintainability.
Push performance limits: Drive performance strategy across the system and get ahead of demand curves before they reach customers. Make the architecture tradeoffs that keep the registry dependable as it grows.
Multiply the team: Raise the team's technical bar through architecture, design, and code review, and through mentorship, while staying hands-on on complex challenges. Make the engineers around you more effective, not just yourself.
Drive technical strategy across teams: Influence designs across adjacent teams, align with product and other partners on priorities and tradeoffs, and lead the technical response when things break.
Distributed systems at scale: You have proven success designing, scaling, and hardening distributed systems, all while keeping them reliable under high-load production environments.
What they're looking for
- A performance-driven mindset: You set performance strategy and have deep, practical experience profiling, benchmarking, and optimizing distributed systems, with sound judgment about latency, throughput, caching, and resource tradeoffs at scale.
- Thrive in ambiguity: You thrive on transforming ambiguous performance problems into measured action and durable fixes. You work ahead of demand, identifying constraints before they reach customers.
- A track record of system level ownership: You've owned critical systems from design through production and carried them through operational pressure. You've made difficult calls under conflicting requirements and visible risk, and stood behind them.
- A customer-centric mindset: You keep the customers top of mind, and you can translate their needs into actionable changes in the codebase.
