Application Guide
How to Apply for Sr/Staff Software Engineer, Observability (Network Engineering)
at Crusoe
🏢 About Crusoe
Crusoe uniquely transforms stranded energy (like flared natural gas) into eco-friendly power for data centers, significantly reducing environmental impact. They combine cutting-edge technology with sustainability, making them an attractive choice for engineers passionate about both distributed systems and environmental innovation. Working here means contributing to a mission-driven company that's rethinking energy infrastructure.
About This Role
This role involves designing and operating scalable observability systems across multi-datacenter Kubernetes environments, specifically for network engineering. You'll architect end-to-end telemetry pipelines and build Crusoe's next-generation observability stack, enabling engineers to deeply understand distributed systems through metrics, logs, and traces. This position is impactful because reliable observability is critical for maintaining Crusoe's energy-efficient data centers and supporting their mission of sustainable computing.
💡 A Day in the Life
A typical day might involve collaborating with network engineers to instrument their systems, designing scalable telemetry pipelines for new data center deployments, and automating observability infrastructure with Terraform and custom Go/Python tooling. You'd likely spend time optimizing metric collection and storage costs while ensuring engineers have the visibility they need to maintain Crusoe's energy-efficient operations.
🚀 Application Tools
🎯 Who Crusoe Is Looking For
- Has 6+ years of experience with distributed systems, specifically focused on observability and monitoring in production environments
- Possesses deep expertise with Prometheus/Thanos/Mimir/Cortex for metrics, Fluent Bit/Vector/Loki/ELK for logging, and Jaeger/Tempo/OpenTelemetry for tracing
- Demonstrates strong programming skills in Go or Python for building automation, Kubernetes operators, and custom integrations
- Has hands-on experience running observability platforms on Kubernetes with infrastructure-as-code tools like Terraform
📝 Tips for Applying to Crusoe
Highlight specific experience with multi-datacenter Kubernetes observability, not just single-cluster setups
Showcase projects where you've built or scaled telemetry pipelines (ingestion, storage, querying, visualization) end-to-end
Demonstrate how you've used Go or Python to automate observability infrastructure provisioning and scaling
Emphasize any experience with network observability specifically, as this role supports network engineering
Connect your technical experience to sustainability or mission-driven work, showing alignment with Crusoe's environmental focus
✉️ What to Emphasize in Your Cover Letter
['Your experience designing and operating observability systems in production Kubernetes environments', 'Specific examples of building telemetry pipelines with the mentioned technologies (Prometheus, Loki, OpenTelemetry, etc.)', "How you've automated observability infrastructure using Terraform and custom tooling", "Why you're drawn to Crusoe's mission of transforming stranded energy into sustainable computing power"]
Generate Cover Letter →🔍 Research Before Applying
To stand out, make sure you've researched:
- → Crusoe's specific approach to using stranded energy for data centers and their environmental impact metrics
- → Their technology stack and any public technical blog posts or talks about their infrastructure
- → The challenges of observability in energy-efficient data center operations
- → How network engineering supports their overall mission of sustainable computing
💬 Prepare for These Interview Topics
Based on this role, you may be asked about:
⚠️ Common Mistakes to Avoid
- Only having experience with single-cluster observability setups rather than multi-datacenter environments
- Lacking hands-on programming experience in Go or Python for automation and custom integrations
- Being unable to discuss specific trade-offs between different observability tools (Prometheus vs. Mimir, Fluent Bit vs. Vector, etc.)
📅 Application Timeline
This position is open until filled. However, we recommend applying as soon as possible as roles at mission-driven organizations tend to fill quickly.
Typical hiring timeline:
Application Review
1-2 weeks
Initial Screening
Phone call or written assessment
Interviews
1-2 rounds, usually virtual
Offer
Congratulations!