Crusoe
Cloud Support Engineer
About this role
Crusoe seeks a Senior Cloud Support Engineer to provide technical support for its GPU-based cloud computing platform, serving customers in AI/ML and scientific computing. You'll troubleshoot infrastructure issues, manage on-call rotations, and collaborate with internal teams to ensure customer success in a fast-paced, innovative environment.
What you'll do
- Deliver technical support to customers via Zendesk, meeting SLAs and maintaining 95%+ satisfaction scores
- Participate in 24/7 on-call rotation to resolve critical infrastructure and customer issues
- Diagnose and resolve VM, hardware, and scaling-related issues using CLI tools and internal systems
- Triage alerts, coordinate maintenance windows, and conduct node delivery testing
- Collaborate with SRE, Networking, and Storage teams on root cause analysis and issue resolution
- Create onboarding materials, knowledge base documentation, and standard operating procedures
What they're looking for
- Linux command-line interface (CLI) and system administration
- Git version control and code collaboration
- Kubernetes and container orchestration
- Workload management tools (Slurm, Terraform)
- Cloud monitoring and observability (Grafana, alerting systems)
- HPC technologies (Infiniband, RDMA, RoCE, SDN)
- AWS, Azure, or GCP platform experience
- Customer support and technical communication
Opens the official application on the employer’s site. No login required.
Crusoe
Crusoe builds AI infrastructure and data center systems, including cloud platforms, modular facilities, and manufacturing operations. The company is hiring engineers across software, mechanical engineering, facilities management, instrumentation, and CNC programming to design, optimize, and operate its mission-critical infrastructure.
View all jobs at CrusoeLikely interview questions
- Describe your experience troubleshooting infrastructure issues in cloud or HPC environments—what tools and processes did you use?
- How have you handled on-call escalations with competing priorities, and how did you maintain CSAT during incidents?