Careers
Work on software that reaches real users
We are small, we hire slowly and we are direct about what the job is. If you want ownership over systems rather than tickets from a queue, this is a good place to be.
What you get
The parts people ask about
Pay at the top of the local band
We benchmark twice a year against Kathmandu market data and adjust without being asked. Salary bands are shared internally.
Two meetings a week
One planning, one demo. Everything else is written. Long uninterrupted blocks are protected and nobody expects a reply after hours.
Real ownership
You own a system, not a queue of tickets. That includes the architecture decisions, the on call rotation and the conversation with the client.
A learning budget that gets used
Conference travel, courses and books, plus one Friday a month with no client work on it. Roughly nine in ten people spend the full budget.
Hardware you choose
Your pick of machine and peripherals on day one, refreshed every three years, yours to keep after four.
Health cover and leave that works
Family health cover, 24 days annual leave plus public holidays, and parental leave at full pay for six months.
Hiring
Four steps, about two weeks
We tell you where you stand after every step. If we say no, we say why. No unpaid take home marathons and no whiteboard algorithm theatre.
Written application
Send something you have built and a few lines on what you want to work on next. A senior engineer reads it. You hear back within five working days.
5 daysConversation
Forty five minutes with the person who would work alongside you. What you have built, what went wrong on it, what you would do differently.
45 minWork session
Three hours on a real problem from our backlog, worked through together rather than alone. We are watching how you think, not whether you memorised an algorithm.
3 hrsOffer
Numbers, band and scope in writing within two working days. We do not make exploding offers and we do not pressure you to decide on a call.
2 daysHow we operate
Six commitments we hold to
Tell the truth early
Bad news does not improve with age. If a milestone is at risk you hear it the week we know, with options attached.
Write it down
Decisions live in architecture decision records, not in someone's memory. New engineers get productive in days because the reasoning is on file.
Own the outcome
We do not close a ticket because the code compiles. It is done when it works in production for real users.
Build for the team after us
Every project is written so someone else can pick it up. Clever code that only its author understands is a liability we do not ship.
Protect focus
Two meetings a week, long uninterrupted blocks, no expectation of replying after hours. Good engineering needs quiet.
Pay attention to cost
We treat your cloud bill and your engineering budget as if they were ours, because getting invited back depends on it.
Nothing here fits you?
We hire when we meet someone strong, not only when a role is posted. Send us something you have built and what you want to work on next, and we will be honest about timing.
- A senior engineer reads every application
- No unpaid take home marathons
- We tell you where you stand within a week