Production Engineer II

About the Role

This is an entry point into Production Engineering at Crusoe. You'll be one of the engineers keeping a multi-billion dollar, rapidly scaling AI cloud business online, from every GPU cluster to every customer workload and every SLA, while building foundational skills that turn into a Senior and Staff-level infrastructure career.

We're hiring several Production Engineer II roles across broad, cross-domain operations or deeper specialization in compute, storage, or networking.

What You'll Work On

• Triage and resolve production incidents: parse logs, correlate signals across services, and drive issues to root cause using logs, telemetry, and profiling
• Write real automation and tooling in Python or Go to reduce manual toil, including remediation scripts and health checks that catch problems before customers do
• Build and improve monitoring, alerting, observability, and telemetry so the team can see problems before they become incidents
• Participate in on-call rotations, respond to alerts, and contribute to blameless post-mortems
• Work directly with senior and staff engineers on real production engineering problems, and grow into more autonomy quickly

Depending on Your Team

• Own the health and reliability of production infrastructure supporting Crusoe's AI cloud, whether working cross-domain or going deep in one area
• Build breadth across Crusoe's infrastructure stack and grow toward a specialization (compute, storage, networking, or continued breadth) over time
• On some teams, go deep on one specialization (compute and GPU fleet reliability, storage and distributed storage systems, networking fabric and SDN, Managed AI, Inference, or Managed Cloud)
• On hardware-focused teams, help keep our GPU fleet, including NVIDIA and AMD hardware, running reliably under real production AI workloads
• Run validation testing on configuration changes, firmware updates, and infrastructure modifications before they touch production
• Learn directly from senior and staff engineers who own the hardware and reliability standards for their domain, and grow toward owning more of that surface area yourself

What You'll Bring

• A CS or EE degree, bootcamp, or equivalent hands-on experience, plus genuine interest in infrastructure and systems reliability over application development
• 3 to 5 years of working proficiency in Python or Go (comfortable writing and debugging real code, not just shell one-liners)
• Familiarity with Linux fundamentals: processes, networking, filesystems, and how hardware and software interact
• Comfort in a fast-paced, high-ownership environment with a real on-call rotation
• Strong communication skills to write incident summaries and work across teams

Mindset

• Curiosity about how distributed systems fail and a habit of asking "why" past the first answer
• Openness to either broad cross-domain work or early specialization in one domain

Nice to Have

• Exposure to Kubernetes or container orchestration
• Exposure to GPUs, HPC environments, kernel internals, or systems and validation engineering coursework or projects
• Prior on-call, NOC, IT ops, or lab/systems administration experience, plus personal projects, open source contributions, or coursework touching distributed systems, low-level systems, or hardware