Build software that stays in production
A decade of delivery, a senior engineering team in Surat, and client products running in production for companies around the world. Whoever builds a thing here is the person who supports it.
See open rolesSenior engineers, real ownership, production software
You work directly on the product with direct access to the people making the decisions. Ownership here is genuine, and it starts early.
Remote, office, or in between
The studio is in Surat. Where you work from is a conversation, not a policy — people here work fully remote, from the office, or somewhere between the two.
One team, full stack
We are not split into silos that hand tickets across a wall. The same team carries a product from discovery through build, launch, and the support that follows.
Long engagements, not churn
Most of our work is with clients we have built alongside for years. You get to see what you shipped hold up in production, and to fix it when it does not.
Open source, genuinely
The stack leans on open source and so does the way we think about it — using it, understanding it, and giving back to it rather than treating it as free inventory.
Fewer credentials, more evidence
We care much more about what you have built and how you think about it than where you studied. Show us something real and talk us through the parts that went wrong.
- You finish things. A feature that is 90% done is not done, and you would rather say so than let it ship quietly.
- You can read a codebase you did not write without rewriting it first.
- You talk to the person with the problem. Client context is part of engineering here, not something filtered through a manager.
- You care what happens after launch — the bug report, the slow query, the migration nobody wants to run.
No live vacancies — introduce yourself anyway
There are no live vacancies at the moment. We read every application that arrives and keep strong ones on file — when a role opens, that is where we look first.