Garden's mission is to keep developers productive and happy in the cloud-native era.
Docker, Kubernetes and other cloud-native technologies have made us better than ever at operating our systems in production, but the day-to-day development experience has been left lagging behind.
Developers spend less time in flow, and more time waiting for builds, debugging scripts, or otherwise fighting their tools. We're here to fix that.
Our platform—which includes our open source core product—allows developers to work on distributed systems in remote, production-like dev environments while enjoying the same fast and frictionless feedback loops we've come to expect when developing a single service locally.
It's a platform that democratizes the kind of advanced developer tooling that only the largest software companies have the resources to build and maintain.
We're still a small team and you'd be joining at a time where you can have a huge impact on our product and our culture. If you've ever thought to yourself that something's not right with our modern development workflows, now's your chance to help fix it!
What you'll do
Garden Cloud is a distributed web application that runs on Kubernetes (AWS’s EKS to be precise) and uses Postgres as its main data store. You will work together with Anna, our SRE, on advancing how we deploy and operate it.
More specifically, in your first six months:
- You’ll get to know and work with a team of passionate engineers who are on a mission to fix how cloud native software is developed.
- You’ll work closely with Anna in designing and implementing our incidence response process, based on data from our monitoring stack (Prometheus, Grafana, Loki, and more).
- You’ll work with Anna and the rest of team on charting out a path from our current single-tenant deployment model to a multi-tenant one.
...and in you first year:
- You and the SRE team (which will have grown to at least three at this point) will be at the forefront of executing on our deployment model migration.
- You’ll use your experience of operating databases at scale (we use Postgres) to help us avoid having to learn “the hard way”.
What we're looking for
Garden is growing its team, platform and user base at the same time. We are looking for someone to help us build out our existing platform to fit the needs of that growth.
- You have extensive experience with distributed systems (or micro-services) and the cloud native technologies used to build and run them.
- You have considerable experience with Kubernetes, IaC tools such as Terraform, and cloud platforms such as GCP and AWS.
- You have considerable experience with running databases at scale.
- You're passionate about developer tooling and productivity.
- You're happy to work with a team that values trust, openness, and collaboration.
We're a small team that tries to keep things simple and lean—and that applies to our interview process as well.
The very first step is a 30 - 45 minute intro call with James, our Head of People. This is where we'll discuss the role, salary, and availability.
Next step is a 30-minute call with Eythor, our CTO. The goal is to give both parties a chance to get to know one another and ask questions and discuss the role and culture at Garden.
After that there's a 60-minute technical interview with Anna and one other engineer. There are no string reversal algorithms though. Instead, we anchor the conversation in things you've actually done in the past and dig deep into those.
The final step is a 60-minute presentation where you present work you’ve done to the engineering team. Depending on the role, this may be something you’ve done in the past or an assignment we design. We want everyone involved in the process, so this is also a chance for you to meet more people from the team and vice versa.