Backend Software Engineer

We’re looking for someone who has owned systems in production—and dealt with what happens when they break. This role is for engineers who understand that distributed systems fail, data is imperfect, and reliability is earned through experience—not theory.

This is a fully remote role looking for candidates within the US.

What you’ll do

• Build and operate backend services that run in production at scale
• Own services end-to-end: design, deployment, monitoring, and incident response
• Design systems that handle retries, partial failure, and eventual consistency
• Define and enforce contracts between services (APIs, schemas, interfaces)
• Debug real production issues across application and infrastructure layers
• Work closely with platform teams to deploy and operate services in Kubernetes
• Improve CI/CD pipelines, testing, and release processes

What you’ve done

• Built and operated production systems—not just written features
• Debugged incidents where things actually broke (not just local bugs)
• Worked in distributed systems and understand failure modes
• Designed or worked with versioned APIs and backward compatibility
• Been responsible for service health (metrics, logging, alerting, on-call)
• Written code in a real programming language (Python, Java, Go, C#, etc.)
• Experience deploying and operating services in Kubernetes
• Comfortable debugging both application code and infrastructure issues
• Experience with streaming systems, pipelines, or large-scale data
• Background in regulated environments where access and audit matter

If you haven’t owned systems in production, this role is not a fit.