Community Engineer (m/f/d)

About Garden

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 developer 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 as an individual contributor 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

As a Community Engineer, you’ll empower Garden’s community champions, steer the direction of our OSS product by bridging feedback to our engineering teams, and speak directly with Garden’s users in service of making Garden the best user experience it can be.

More specifically you’ll:

• Create demo projects, tutorials, and various other creative content to ease adoption of Garden for DevOps Engineers, SREs, and developers.
• Think big and create your own community initiatives to drive adoption and activate our community.
• Speak directly to our engineering teams with feedback from the community, write GitHub issues, and facilitate community contributions to Garden OSS.

Who you are

• You’re passionate about developer productivity and removing obstacles to a smooth, easy developer experience.
• You love technical writing and love helping people to understand complex technical topics in an accessible way.
• Connecting with community whether on the stage or informally has been an important part of your career or you think it could be, given the opportunity.

Here’s your chance to bring your passion to Garden’s community and customers with examples and technical content that accelerate their delivery pipelines.

Qualifications

• You have 2+ years of Kubernetes experience.
• You have excellent interpersonal and written communication skills.
• You’re passionate about open source products and communities.
  • Experience writing code (in particular in Node.js/Typescript) is a big plus but not a requirement.
• You’re happy to work with a team that is still figuring a lot of things out, and values trust, openness, and collaboration while doing so.

We explicitly encourage applications from groups that are underrepresented in tech. We celebrate and encourage diversity of race, religion, color, sex, gender identity, sexual orientation, age and thought. Diversity is easier said than done but it’s one of our founding principles to provide a diverse and inclusive environment.

Working at Garden

• A culture fostering individuals and teams to do their best work in a friendly, positive, diverse and inclusive environment.
  • A policy of no meetings Tuesday through Thursday. We respect your right to Deep Work.
  • Competitive compensation
• You can work fully remote or join us at our HQ in vibrant Berlin, Germany (see Remote’s Country Explorer for a list of all countries we support)
• Wellness stipend and membership in Berlin
• Your own work computer of your choice with OS of your choice (macOS, Linux, or Windows)
• 2000 euro yearly professional development stipend

Our Process

We’re a small team that tries to keep things simple and lean—and that applies to our interview process as well.

The first step is an intro call with our Director of People. The goal is to give both parties a chance to get to know each other, ask questions and discuss the culture at Garden, as well as to talk about salary and availability. The next step is an Interview with someone from our Community Engineering team and CTO. It will give both parties a chance to get to know one another and to discuss the role.

After that you’ll have a 60-minute technical interview with our engineers. We have a real conversation about things you’ve actually done in the past and dig deep into those.

The final step is a 60-minute demo + Q&A followed by a 30 minutes conversation with our Director of People. In the demo you present work you’ve done in the past to people from our engineering teams. We want everyone involved in the process, so this is also a chance for you to meet the rest of the team and vice versa.