Stripe’s infrastructure powers businesses all over the world. We process payments, run marketplaces, detect fraud, help entrepreneurs start an internet business from anywhere in the world, build world-class developer-friendly APIs, and more. If you’re an infrastructure engineer here, you’ll get to build distributed systems that are extremely reliable and scale-out horizontally on the cloud. At Stripe we care a very great deal about reliability as our users’ businesses depend on it.

You’ll be on a team that is building a distributed consensus service for the rest of Stripe engineering. You’ll make decisions with a significant impact on Stripe. There is a lot of work to do to make Stripe engineers’ work easier and our platform even more reliable than it is today, and we’d love for you to be part of it. We’re close to the people using our systems, so we constantly get feedback that we can use to make our platform better.

We’re looking for people with a strong background (or interest!) in distributed systems. We’d love to hear from you whether you’re a seasoned systems developer, or whether you’ve just learned you might like working with databases. Many of our infrastructure engineers work remotely, and we’d be happy to talk to you about the possibility of working remote.

Stripe’s infrastructure powers businesses all over the world. We process payments, run marketplaces, detect fraud, help entrepreneurs start an internet business from anywhere in the world, build world-class developer-friendly APIs, and more. If you’re an infrastructure engineer here, you’ll get to build distributed systems that are extremely reliable and scale-out horizontally on the cloud. At Stripe we care a very great deal about reliability as our users’ businesses depend on it.

You’ll be on a team that is building a distributed consensus service for the rest of Stripe engineering. You’ll make decisions with a significant impact on Stripe. There is a lot of work to do to make Stripe engineers’ work easier and our platform even more reliable than it is today, and we’d love for you to be part of it. We’re close to the people using our systems, so we constantly get feedback that we can use to make our platform better.

We’re looking for people with a strong background (or interest!) in distributed systems. We’d love to hear from you whether you’re a seasoned systems developer, or whether you’ve just learned you might like working with databases. Many of our infrastructure engineers work remotely, and we’d be happy to talk to you about the possibility of working remote.

• Design, build, and maintain the core distributed consensus algorithm and service used by all of Stripe’s engineering teams
• Debug production issues across services and levels of the stack
• Plan for the hyper growth of Stripe’s infrastructure
• Build a great customer experience for people using your infrastructure

1. Design, build, and maintain the core distributed consensus algorithm and service used by all of Stripe’s engineering teams
2. Debug production issues across services and levels of the stack
3. Plan for the hyper growth of Stripe’s infrastructure
4. Build a great customer experience for people using your infrastructure

‍

• Deep expertise in building distributed consensus service for the cloud with Consul, etcd or zookeeper. This consensus service will provide core support for a number of use cases across Stripe including service discovery, leader election, distributed locks and distributed configuration KV storage
• Think about systems — their edge cases, failure modes, and life cycles
• Know your way around a Unix shell
• Can debug complex problems across the whole stack
• Focus on the needs of our users, both internal and external
• Hold yourself and others to a high bar when working with production
• A metrics driven approach and can make informed decisions using data
• Are able to write high quality code (e.g. Go, Java etc)

It’s not expected that any single candidate would have expertise across all of these areas. For instance, we have wonderful team members who are really focused on their customers’ needs and building amazing user experiences, but didn’t come in with as much systems knowledge