Software Engineer, Compute

Role Description

The Compute team's mission: any engineer, using AI, should be able to stand up and operate a stateful service at production scale with no meaningful infrastructure knowledge required. We build the tiering zones, guardrails, and AI skills that make this possible. Reliable, observable, and self-service by design.

This is a software engineering role. You'll spend real time writing code:

• Platform APIs
• Internal tooling
• Deployment pipelines
• Automation that replaces the support tickets

Infrastructure fluency matters; infrastructure specialization is not the lead. What matters most is product instinct:

• Understanding your users (product engineers)
• Measuring whether they're getting unblocked
• Treating developer experience as feature acceptance criteria

The platform is yours to own, not just build:

• When ArgoCD fails and every team's deploy is blocked, that's your page.
• When a product engineer can't figure out why their service is OOMKilling and there's no useful error surface, that's your design failure to fix.

A Software Engineer will grow their infrastructure depth on the job; what we need on day one is:

• Strong SWE fundamentals
• Genuine curiosity about the infrastructure layer
• Sharp instincts about what makes developer tooling frustrating versus useful

Qualifications

• Strong SWE fundamentals: shipped production services, writes readable and operable code, can debug distributed system failures across layers you don't fully own
• Product instinct: you measure adoption, treat low usage as a design failure, and change things based on user feedback rather than your own assumptions
• Developer experience sensibility: you identify friction in CLIs, APIs, and deployment workflows and design for clear affordances, actionable error states, and progressive disclosure
• Kubernetes in practice: you've operated services on K8s, can debug scheduling failures, write RBAC policies, and work out why a pod won't start. You're willing to be paged for the platform you build.
• Infrastructure as code in a team context: you've modified production IaC alongside other engineers and understand why declarative infrastructure and change safety matter

Requirements

• Deep K8s internals: cluster lifecycle, admission controllers, custom controllers/operators
• ArgoCD or another GitOps tool in production
• GKE or managed Kubernetes at scale
• Ruby or Rails (we integrate with Ruby systems)
• Experience in a regulated or high-trust environment

Benefits

• Medical, dental, and vision coverage
• 3% 401(k) contribution
• Unlimited PTO
• Quarterly mental health days
• Family planning benefits
• Professional development stipend
• Wellness benefits