Ways in
Experienced engineers.
Bring what you have shipped and operated. Architecture decisions sit with you rather than being handed down, and you stay with the system afterwards.
See open rolesWhat you own
Real systems from the first architecture session through to live operation, rather than a slice of someone else's design.
Direct contact with the people using what you build, with no account layer in between.
Work delivered in two to four week increments, demonstrated and accepted before the next one starts.
More than twenty production engines underneath the client systems, so the same problem is rarely solved twice.
How we hire
You write to us: a few paragraphs and a link. We would rather read about one system you have run than a list of technologies.
A conversation: about an hour, with an engineer rather than a recruiter. What you built, what broke, what you did about it.
A technical session: a problem close to the real work. An integration, a data model, a failure you have to diagnose. No whiteboard algorithms.
A decision: you hear back either way, with a reason.
Send us your work
A short introduction and a link to something you have built and operated is enough to start a conversation.