Careers

Every company claims a good culture. The more useful question is what actually happens on a normal Tuesday, so that is what this page answers.

e10 Infotech has been building software in Mumbai since 2011. Twenty five engineers, more than 200 delivered projects, clients in over 25 countries, and no sales team. How we work is the reason that arithmetic holds together, so it is worth writing down properly.

The short version

Small teams with real ownership. Work judged by what it changed rather than by how many hours went into it. The founder still writes production code, which keeps the engineering standard honest and the estimates realistic.

How the work actually runs

Project teams are small, usually two to four people, and one person carries the outcome end to end. That person talks to the client directly. We do not park account managers between the engineer who built something and the person using it, because what gets lost in translation costs more than the occasional awkward call.

Work is asynchronous by default. The team covers more than five time zones for clients in over 25 countries, so a culture that needs everyone online at the same moment would break by Wednesday. Decisions get written down where the next person can find them. Meetings happen when a call genuinely needs several heads at once, and they end when the decision is made.

You ship it, you run it

Whoever builds a feature supports it in production. There is no handover to a separate maintenance team that inherits somebody else's shortcuts. It changes how people write code, because when you know the 2am alert is yours, you handle the error case the first time.

The same logic is why uptime work is treated as engineering here rather than as a junior tier. The person keeping client applications alive at 3am has as much standing as the person who wrote them.

What AI changed, and what it did not

AI accelerated workflows moved into every project in 2024 and delivery got roughly three times faster. The interesting part is which pieces of the job disappeared. Scaffolding, boilerplate, first draft tests and migration scripts are largely handled now. Architecture, trade off calls, and knowing which feature to talk a client out of are still human work, and that is what we hire for.

Nobody here is measured on lines of code or tickets closed. If a model writes the first draft and you spend the afternoon deleting two thirds of it, that afternoon was the valuable part.

Hours, leave, and the honest bit about crunch

Normal weeks are normal weeks. Nobody tracks keystrokes, and nobody is asked to stay in a chair after their work is done to look busy.

Launch weeks are sometimes long. That is true here, and it would be dishonest to pretend otherwise on a careers page. What we work hard to avoid is making it routine, because a permanently tired team ships bugs, and those bugs come back to the same people who wrote them. When a deadline is genuinely at risk, the first conversation is with the client about scope, not with the team about weekends.

The office, and the remote part

The development centre is at B-110, Bhoomi Hills, Thakur Village, Kandivali East, Mumbai. It is a real working office and anyone who thinks better around other people is welcome in it. It is also not compulsory. Most of the team is remote first, and a delivery record across 25 countries from a Mumbai base is the argument that settled that debate for us.

Six things we hold each other to

Your first month

What we look for

Degrees matter less than evidence of having finished things. A side project that real people use tells us more than a certification. Because the team is spread across time zones, writing clearly is close to a technical skill here, and people who can explain a trade off in four sentences tend to do well.

The other thing we watch for is comfort saying "I do not know yet". Engineers who bluff cost projects weeks.

What we are not

We are not a body shop billing seats by the month. We do not have an unlimited leave policy that nobody feels safe using. We do not keep people on one framework for five years, which is why the same engineers move between custom software, web applications, mobile builds and SaaS products.

If you want a fully specified ticket handed to you every morning, this will be frustrating. Scope here usually arrives as a business problem rather than a solution.

Who runs the people side

Anuj Pandey sets engineering direction and still writes code alongside the team, which is why technical decisions get argued on merit rather than seniority. Sanjay Dubey owns operations and the people function, covering hiring, HR and clearing problems before they reach an engineer's desk. He was an engineer himself for decades, so the tooling requests usually get approved.

Open roles

We hire slowly and only when the work is there. Current openings include application maintainer, customer success executive and sales and marketing executive.

If nothing listed fits but you think you should be here, write to us anyway through the contact page and tell us what you have built.

Frequently asked questions