Free AI ScanLife at Mandelbulb
The doors here
actually open.
Most companies put an open door policy on a values slide. Ours gets measured in stranger places. When we are on a panel at a summit, or standing at a government showcase, or at our own booth on an expo floor, it is majorly our engineers out there and not the founders. When we lose a deal, the whole company hears which one and why. And this year the building stopped work for a morning so that everybody could build something nobody had approved.
01 / Out in the world
It is majorly engineers out there. Not the founders.
Industry summits. State government deeptech showcases. University campuses. Our own stand on an expo floor. The default in this industry is that the people sent into those rooms are the leadership team, because being seen gets treated as a reward for seniority. We treat it as part of the job.
The engineer who built the system is the one who presents it, takes the hard question from the floor, and gets the credit in the room. That is not generosity, and it is not a diversity of speakers exercise. It is the fastest method we know for making somebody senior. You find out what your work is really worth the moment you have to defend it in a room full of people who did not build it.
It also keeps us honest. A founder can describe a deployment in the abstract. An engineer has to answer what happens when the source system goes down at 2am, standing in front of the customer who would be the one calling at 2am.
The rooms vary on purpose. A conference panel. A state government pavilion. A campus expo where the audience is students who have never put anything into production. Different rooms ask different questions, and whoever goes is picked for having done the work rather than for being senior enough to be trusted with a microphone.
Elsewhere on the floor, and at the front of the room
02 / The open door
Open Door is a policy here.
Not a poster.
The only test that matters is whether you can reach the person who can actually decide. The founders sit on the same floor as the engineering team. There is no calendar gate, no skip level protocol, and no request that has to travel through three managers before it reaches somebody with the authority to say yes.
The access runs in both directions, which is the part people underestimate. If you think a direction is wrong, you are expected to say so to the person setting it, and not to a friend at lunch. Access without candour is only proximity, and proximity on its own improves nothing.
It is why the rest of this page is possible at all. A ninety day pairing. A workshop that exists because somebody offered to teach it. A slot on a panel. Four hours of company time for a hackathon. Every one of those started as somebody walking up to a founder and asking.
None of this scales by itself, and we know that. It holds because it is practised in front of everybody, most obviously in the room described below.
03 / Townhall
We read out the numbers most companies keep to themselves.
Every company townhall covers the wins. Ours also covers the deals we lost and the reason we lost them, the targets we missed and by how much, and the real numbers underneath both. What is working, and what is not working yet.
That is uncomfortable exactly once. After that it changes how people work. An engineer who knows which account is at risk prioritises differently from an engineer who has been told everything is fine. A team that has watched a lost deal explained properly stops repeating the thing that lost it.
It also settles an argument before it starts. When everybody has seen the same numbers, a decision can be disagreed with on its merits rather than guessed at, and nobody has to reverse engineer the strategy from which projects got staffed.
Transparency here is not a morale exercise. It is how a company that is still growing stays accurate about itself. Good news travels on its own. Somebody has to carry the rest into the room, out loud, with the number on the screen.
04 / How you grow
Four doors, and somebody is holding each one open.
Nobody was flown in to run the sessions on this page. Every workshop here is taught by one of our own engineers, standing in front of a room of their colleagues, walking through a system they are personally on the hook for in production.
That is a higher bar than it sounds. You cannot teach a walkthrough you have only read about, and you cannot survive the questions afterwards if you have not actually operated the thing. Teaching it is how people here find out they know it.
Your first ninety days, paired.
Every new engineer is paired with a senior engineer for their first 90 days. Not a buddy for onboarding paperwork. A working pair, on real code, with a named person who is accountable for whether you land.
Workshops run by our own engineers.
Skill development workshops here are taught by the people who already run that thing in production. The person at the front ships with the stack they are teaching, so the questions afterwards are the useful kind.
Certifications, sponsored.
The company pays for the certification the work in front of you actually needs. You do not have to build a business case for getting better at your job.
Leadership training from the founders.
Leadership training is taught by the founders themselves. It is not outsourced to a vendor with a generic deck. If you are moving into leading people here, you learn it from the people who built the place you are leading in.
05 / What we celebrate
The office gets decorated, and the whole company is in the room.
Festival season is the one you can see from the doorway. Marigolds wound around the pillars, everybody dressed for it, the whole office in one room and nobody watching the clock.
Women's Day is celebrated at this office the way Diwali is. Same effort, same decoration, same turnout, everybody present. We are saying it that plainly on purpose, because it is easy to write a paragraph about initiatives and harder to say what actually happens in the building.
Then there are the days that are not on any calendar. Balloons strung across the ceiling over the desks. A floodlit ground and somebody taking their turn with the bat. Nine people at an arcade together. Five colleagues around a meeting room table with the laptops still open, taking a photograph in the middle of an ordinary hour.
06 / AZAAD 2026
On 13 August 2026 we stopped the entire company for four hours and told everybody to build anything.
“AZAAD is about the freedom to think beyond, challenge the norm, and build solutions that can shape a better tomorrow.”
Honouring freedom. Inspiring the future.
Every approved entry is in the showcase. Go and look at what four unsupervised hours produced.
Join us
The door is open. You are expected to walk through it.
We hire across machine learning, data platform, product engineering, infrastructure and delivery, in India, Singapore and remote. If what you have read here is the way you want to work, the roles are listed and the inbox is real.