Careers

Work with seniorengineers who ship.

We hire people who've already built production systems. No junior rotations, no on-the-job training at the client's expense.

0
Engineers across 5 offices
0%
Fully remote
0 days
Standard work week
$0k
Annual learning budget
No middle managersFour-day work weekWrite the docsShared on-callEquity from day oneNo surprise demosShip it, then talk about itNo middle managersFour-day work weekWrite the docsShared on-callEquity from day oneNo surprise demosShip it, then talk about it
How we hire

Four conversations. No puzzles.

01

Apply

Send code, not a cover letter. A GitHub profile, a past project, or a writeup of something you shipped tells us more than a resume.

02

Technical conversation

An hour with two engineers from the team you'd join. We talk through real systems you've built — what broke, what you'd change.

03

Working session

Half a day, paid, on a real anonymized problem from our backlog. Pair with us, ask questions, use whatever tools you'd normally use.

04

Offer

We decide within a week. If it's a yes, you'll know exactly who you're working with — because you already have.

What you get

Benefits designed by engineers.

01

Senior-only engineering culture

No layers of middle management. You work with people who have shipped production systems for a decade.

02

Real equity, real stakes

Meaningful equity grants, transparent compensation bands, annual refresher cycle.

03

Learning budget, no approval

$5,000 annual budget for books, courses, conferences. Spend it on what makes you better.

04

Work from where you think

Headquarters in San Francisco, but 60% of the team is fully remote across four continents.

05

Four-day work week

We work Monday through Thursday. Fridays are for deep work, side projects, or rest. Since 2022.

06

Hardware of your choice

Top-spec MacBook Pro or Linux workstation, dual 4K displays, mechanical keyboard of choice. Up to $6,000.

From the team

What it's actually like.

I stopped explaining basic concepts in every meeting. Everyone here already knows why the naive solution doesn't scale.
Daniel Osei
Staff Data Engineer · Data & Analytics · Bangalore
Four-day week sounded like a gimmick until I noticed my code on Fridays was worse than my code on Mondays. Now Friday is for the stuff that actually needs quiet.
Grace Lindqvist
Senior Platform Engineer · Cloud & Infrastructure · Remote
The working session was the first technical interview that actually looked like the job — I paired with two engineers on a real backlog ticket, no whiteboard, no trick questions.
Naomi Whitfield
Security Architect · Cybersecurity · London
Before you apply

Questions people actually ask.

Yes, for roles based in offices where we hold a sponsoring entity — currently the US, UK, and Singapore. Flag it in your application and we'll deal with it early, not at the offer stage.

Yes. 60% of the team works remote across four continents. We don't run timezone theater — you're expected to overlap with your team's core hours, not be online around the clock.

Two to three weeks from first email to offer in a normal case. The paid working session is the only step that takes half a day; the other three conversations are under an hour each.

Yes. A few of our current roles were built around a specific person who applied without a matching opening. Tell us what you'd want to work on.

We tell you specifically why, not with a form rejection. Several people we've turned down reapplied a year later and got in.