Backend / Infrastructure Engineer

TLDR

• You know how to run and scale real web infrastructure
• You know Git deeply, including hosting it at scale
• Work with a GitHub cofounder on developer tools you'll use yourself
• Fast paced startup environment. Get shit done fast.

What you'll do

Join us for an exceptional opportunity to collaborate with a GitHub cofounder on next generation version control tools, in SF, Berlin or remote. We are looking for an experienced backend and infrastructure engineer to help us take a web service from working to production-grade — reliable, observable, and ready to scale to millions of developers.

You'll own the backend and infrastructure that our tools depend on. That means taking services from prototype to production, keeping them fast and cheap under load, and building the Git hosting layer that everything else stands on. You'll work on tools you personally use, in a small, fast-moving team.

Key Responsibilities:

1. Productionize and scale web services — capacity planning, load testing, and performance tuning.
2. Design, build, and operate infrastructure on AWS, with a focus on reliability and cost.
3. Build and scale Git hosting and Git-backed services, drawing on a deep understanding of Git internals.
4. Set up observability — metrics, logging, tracing, and alerting — so we know what's happening before our users do.
5. Own CI/CD, deployment pipelines, and infrastructure-as-code.
6. Harden services for security, backups, and disaster recovery.
7. Collaborate with the rest of engineering to make the whole system faster and simpler.
8. Be on the hook for keeping production healthy, and for making incidents rare and boring.

Required Skills & Qualifications:

1. Proven experience running and scaling production web infrastructure.
2. Deep, hands-on knowledge of AWS.
3. Strong Git skills, including its internals, workflows, and best practices — bonus points for experience hosting Git at scale.
4. Comfortable with infrastructure-as-code (Terraform, Pulumi, CDK, or similar) and CI/CD.
5. Solid grasp of networking, databases, caching, and observability.
6. Experience with a backend language (Rust, Go, TypeScript/Node, or similar) — enough to read and write the services you operate.
7. Excellent problem-solving skills and a bias toward pragmatic, maintainable solutions.
8. Strong verbal and written communication skills, and the ability to work independently on a small team.
9. The rest of the normal bullshit bullet points that are probably AI generated these days.