Founding Distributed Systems Engineer

Role

As a founding engineer, you’ll work across the stack to solve problems as they come up and help build Archil volumes. You’ll have significant influence over the technical and product direction.

We’ll expect you to be able to:

• Be oncall for a production system to help our customers if anything goes wrong.
• Build out never-before-seen capabilities in a storage service
• Design distributed systems interactions for atomicity and idempotency
• Deploy infrastructure and generalize infrastructure across different clouds
• Operate through changing customer requirements with lots of ambiguity

Who are you?

• You have 3+ years of experience building and operating distributed systems (flexible).
• Ideally, you’ve worked at a startup before, so you know how chaotic this time can be.
• You’ve successfully resolved disagreements at work before, and you understand that the highest priority is helping our customers — not being right.
• You’re comfortable debugging problems that occur as a result of failures in multiple, different systems, using tools like metrics and logs.
• You’ve been paged at 3am to solve a complex production issue before.
• You’re knowledgeable about distributed systems: you get how consensus works, you know how to scale systems, and you know what pitfalls in API design to avoid.
• You’re familiar with how to optimize the performance of a system, including a general sense of how much latency different operations take, and what kind of bottlenecks could lead to a reduction in potential throughput.
• Most of all, you know how computers work from the silicon up. Someone once asked you in an interview “what happens when you go to Google.com”, and there wasn’t enough time in the interview to talk about all of the steps.

Why join us?

By building the highest-performance, simplest storage product in the cloud, we have a great chance of changing how the world builds the next-generation of applications (and with AI, more applications will be written in the next 5 years than ever before). We’d love for your to be a part of our journey.

How to join?

• Show us that you’re knowledgeable about the space that we’re working in on your application. It’s up to you how you do this, but one potential way is by answering one of the following questions:
  • How do you think our system works?
  • What do you think our biggest technical challenge is?
  • What would make our system not work?