We hire for what you have built, not for how the CV reads
One team, working on systems that go into production and stay there. If that is the work you want, the process below is how we get to it.
Where the work happens
We run as one team, not as a delivery pod behind an account manager. The engineer who writes a service is the engineer who talks to the client about it and the engineer who gets paged when it misbehaves.
Most of what we build replaces something that already runs, so the work is rarely a blank page. Reading an existing system carefully, and changing it without breaking the business on top of it, is the skill we value most.
We do not list a role for every hire. If your work fits the practices below, write to us with it, and we will tell you honestly whether there is something to talk about now or later.
The four things we actually read for
Work we can read
A repository, a shipped product, a system you can walk us through. What you have built tells us more in ten minutes than a CV does in an hour.
Judgement about scope
Knowing which problem to solve first, and which one to leave alone, matters more here than knowing every framework. Most of our work replaces something that already runs.
Writing that holds up
Half of engineering here is a clear message to a client, a legible pull request, or a decision written down so the next person does not have to guess.
Care after launch
We run what we build. Monitoring, incident response and the unglamorous follow-through are part of the job, not somebody else's problem.
Four steps, and you always know where you stand
A conversation
Thirty minutes with an engineer, not a screening call. What you have worked on, what you want to work on next, and what we are actually building.
A real problem
A short exercise drawn from work we have done, sized to an evening. We read the reasoning, not just the result, and we pay for anything longer than that.
The team you would join
A call with the practice you would sit in, going through your exercise and a system you have built, both directions.
An offer in writing
Scope, level, compensation and who you report to, written down before you decide. No exploding deadlines.
The practices you could join
No role listed for you? Write anyway.
Send the work you are proudest of and a line on what you want to build next. A person reads it.