/careers

Looking for a job?
Yes!

What are we looking for

Roles with a real impact, agency, out-of-the-way managers and low bureaucracy.

Department: Platform Engineering
Locations: Amsterdam (remote) · London (remote) · Berlin (remote) · Barcelona (remote) · San Francisco (hybrid) · Seattle (Hybrid)

Department: Platform Engineering
Locations: Amsterdam (remote) · London (remote) · Berlin (remote) · Barcelona (remote) · San Francisco (hybrid) · Seattle (Hybrid)

Department: Software Engineering
Locations: Amsterdam (remote) · London (remote) · Berlin (remote) · Barcelona (remote) · San Francisco (hybrid) · Seattle (Hybrid)

Department: Software Engineering
Locations: Amsterdam (remote) · London (remote) · Berlin (remote) · Barcelona (remote) · San Francisco (hybrid) · Seattle (Hybrid)

Department: Open Source & Community
Locations: Amsterdam (remote) · London (remote) · Berlin (remote) · Barcelona (remote) · San Francisco (hybrid) · Seattle (Hybrid)

Department: Customer Success
Locations: Amsterdam (remote) · London (remote) · Berlin (remote) · Barcelona (remote) · San Francisco (hybrid) · Seattle (Hybrid)

Have fun: We have fun first and foremost, with our colleagues, with the managers (sometimes), and we do not believe in strict hierarchies. Karaoke is the go-to activity for offsites.
Start with the problem: Before designing a system, we understand the workflow, the users, the constraints, and what failure costs. We solve the problem that exists, not the one that makes the architecture look clever.
Stay technical: We stay close to the implementation, inspect the code and systems, and test assumptions against reality. If we cannot get close to the work, the strategy is probably decorative.
Automate the boring bit: When work repeats, we map the workflow, remove unnecessary steps, and automate the rest with clear ownership. The third repetition should become a tool, not another calendar event.
Deliver: We keep shipping high-quality, scalable, and maintainable software. We run extensive tests in CI, consider how to best handle CD and deploy to staging, test, and production, while keeping the loop observable and feeding insights back.
Explain the trade-off: We explain cost, risk, time, reversibility, and who owns the outcome. Engineers, leaders, customers, and internal users should understand what they are agreeing to.

Principles that guide our actions and decisions

Transparency: Open and honest communication; a hard no is better than a sweet yes.
Integrity: Doing the right thing, even when no one is watching.
Reliability: Being dependable and consistent in delivering, even when it is hard.
Creativity: Thinking outside the box and innovating instead of sticking with the status quo.

Looks compatible.