Work that goes into production.
Small team, short feedback loops, and software that real people use — not slides about software.
How we work
What it is actually like.
Remote-first
Overlapping hours rather than fixed ones. Where you work is your business.
Two-week cycles
No death marches to an arbitrary date. Sustainable pace is a delivery strategy, not a perk.
Ship in week one
You put something into production early. Nobody learns a codebase by reading it.
Written-first
Decisions survive the meeting. That is also what makes remote work properly.
Maintenance counts
Time is set aside for upkeep and learning, not just new features.
Small team
You will be close to the client and the decision. That cuts both ways.
Hiring
Four stages, about two weeks.
We give a decision within a week at every stage, and feedback whether or not you go forward.
A conversation
Thirty minutes on what you want to work on and what we are doing. No whiteboard.
A paid exercise
Close to real work, scoped to a few hours, and we pay for your time. Never a take-home marathon.
A technical discussion
You walk two of the team through your solution and the trade-offs you made.
Terms
Offer, salary and start date. We give a decision within a week at every stage.
Open positions
None right now.
We would rather say that than advertise roles that do not exist. If you would be a good fit anyway, send us something you have built and tell us what you would want to work on.
Send an introductionAdd real vacancies here with title, responsibilities, requirements, location, level and closing date.
Equal opportunity
We hire on evidence of ability and do not screen on university. We will make reasonable adjustments at any stage of the process — just ask.
Where we are
Nairobi, Kenya
EAT — UTC+3