Careers
Build things that get run.
Not demoed. Not piloted. Run — by people on a shift, on a deadline, with something real depending on the answer being right.
What we look for
A short list, held firmly.
We do not screen for pedigree. We screen for how someone behaves when handed a problem that matters and no ticket telling them what to do with it.
You want the whole problem
The interesting work here is end-to-end: the domain, the data model, the failure mode and the person who has to use it at the end of a long shift.
You are careful by instinct
We work in domains where a quiet wrong answer does real harm. We look for people whose first question is how it fails.
You will go and look
Nobody designs a good operational system from a desk. We expect you to sit with the people doing the work before proposing how they should do it.
How we work
Few people, wide scope.
Teams here are small on purpose. That means the scope handed to any one person is unusually wide — you are unlikely to be given a ticket, and much more likely to be given a problem, a domain expert to talk to, and the expectation that you will come back having understood it.
That trade cuts both ways. Wide scope means real authorship: the schema, the edge cases, the exact words on the button — yours to get right, with your name quietly on all of it. It also means there is nowhere to park a decision you did not think through. People who want this arrangement tend to already know they want it.
How we hire follows how we work: deliberately, and through real conversation rather than a filter. We pay attention to how someone thinks through an unfamiliar problem, not to where they trained.
The company is based in Bengaluru. The working arrangement for a given role — how much is in a room together and how much is not — is something we settle with you rather than announce up front. What does not flex is the bar: a small team, wide scope, and real ownership of what you build.
The honest part
The work is uneven. On purpose.
Recruiting pages like to promise that every week is the interesting kind. Ours are not, and pretending otherwise would be a bad way to start a working relationship. The weeks come in kinds, and they do not arrive in equal measure.

Architecture weeks
Whiteboards, tradeoffs, the deep and satisfying kind of thinking. These are the weeks careers pages are written about, and they are as good as advertised.
Migration-script weeks
Somebody's records have to arrive intact, in order, with nothing silently dropped on the way. Unglamorous, exacting — and the trust everything else runs on is earned exactly here.
Sitting-in-a-facility weeks
A plastic chair, a busy corridor, watching someone use the thing you built while their attention is entirely elsewhere. Humbling every time. Also where the real design work happens.
If only the first kind sounds like work to you, we are probably not the right place. If all of them do, keep reading.
Open roles
What's open right now.
Nothing for a named role at this moment. The team grows only when a gap becomes undeniable — which is often exactly when the right unsolicited note arrives.
If the way we work sounds like where you want to put your attention, write to us anyway. Tell us what you would want to own, and why — small companies make roles for the right person more often than large ones do.