Home
Solutions ▾
Our work
Resources
Careers
Gurugram-based, with chances to get out to the programmes we build for.
Our software runs where it matters most: in programmes serving people who have few alternatives. That shapes the job more than any perk does. We build for real field conditions rather than a demo environment, so you will meet the people using what you build. Teams are small and the accountability is real: you are trusted to make the call rather than wait for permission. And the same open-source ethos that shapes what we build shapes how we work, transparently and without unnecessary gatekeeping.
The things that make the week work, and where to get the detail.
Health cover and a standard leave policy, both shared in full during the hiring process.
Meals are provided at the Gurugram office.
We work a hybrid week out of Gurugram. Where a role allows it, we are flexible about the days and where the work happens.
The team gets out of the office together through the year, as well as the annual gathering that brings everyone into one room.
Exposure to real engineering and delivery problems, with senior people close by.
We use AI in our work and provide subscriptions where a role needs them, and always for learning. The same data confidentiality policies apply to that as to everything else.
Exact policy documents, covering leave, insurance and notice periods, go to every candidate before you accept an offer. Ask us anything at that stage.
Six commitments that decide whether something is ready to leave the building, and how we behave while getting it there.
We start from the partner’s problem, not our product. Success is how well the technology fits the way they already work, not how elegant it looks to us.
Zero regressive bugs: an error found once is documented and added to the automated tests, so it cannot happen twice. And a pixel-perfect interface, because the UI is how we show respect for the person using it.
Most decisions are reversible. We make them and move, rather than waiting for certainty that is not coming. A week spent deciding is a week the programme did not have.
We are measured by what changed for the programme. Hours logged, tickets closed and slides produced are not the same thing as a result.
Our bar sits above the brief. We do not ship something we would not be willing to run ourselves, and we say so when a shortcut is being proposed.
We say what we know and what we do not. Problems are flagged the moment we see them, not on the delivery date. Beneficiary and client data is handled as if it were our own.
You'll work close to the problem, on software that runs real health, livelihoods, education and governance programmes. It reaches people in places most software never does.
Small teams, real ownership, and the space to do the work properly. Most people get out to the programmes we build for, and see how the work lands.
Gurugram, the programmes we build for, and the sessions we run in between.
Engineering, delivery, data, quality and operations.
Long enough to have learned most of this the hard way.