Consequential problems
The systems you build move money and carry patient records. Nothing here is a toy.
✦ Careers
Small team, consequential problems.
We hire systems thinkers and give them the autonomy to architect. The systems you build move money and carry patient records.
Life here
What you get.
Strategic autonomy
We hire systems thinkers and let them architect, not just implement.
Venture upside
We build ventures we own, and you share in what we launch.
AI-equipped by default
Every engineer here works with AI leverage. It is how a small team ships six platforms.
Deep mentorship
Technical and strategic mentorship from people who have shipped it before.
Small team
No layers between you and the decision that matters.
What we look for
The four things we read for.
You design before you type.
You can say what a system should make impossible, and what you rejected to get there.
You have shipped something that stayed up.
Not a demo. Something with users, data and a failure you had to answer for.
You use AI as leverage.
The advantage is holding architectural context across a large build, not typing faster.
You finish.
The last ten percent is the part that decides whether an operation can actually run on it.
How we hire
Four steps, about two weeks.
- 01
Send the work
A repository, a system you designed, or a written account of a decision you made and what it cost. No cover letter.
- 02
A conversation
Forty five minutes with an engineer about something you have built. We are listening for how you reason about boundaries and failure.
- 03
A real problem
One of our actual architecture problems, discussed live. Nothing timed, nothing whiteboarded under pressure, nothing you would never do on the job.
- 04
Offer
Within a week of the last conversation. We tell you where you would sit, what you would own, and what we expect in the first quarter.
The set-up
How the week is shaped.
- Where
- Remote first, with a Lagos hub for the people who want a room
- How
- Async by default, two fixed calls a week, no standups
- Cadence
- Working software every two weeks, against real data
- Ownership
- One engineer owns a surface end to end, design through operation
Open roles
Where we need people.
Nothing on the list fits?
Send the work anyway. We open roles around people more often than we hire against a job description.
Have a problem worth solving?
Tell us what is not working, what you are trying to build, or where you want to go next.
What happens next
01You describe the operation.
02We reply within one business day.
03If there is a fit, we tell you what the next step looks like.