Employee review · Chennai

iNextLabs Review: An Honest Account From Someone Who Worked There

I am writing this because I could not find an honest account of this company when I was deciding, and I think people deserve one before they sign. This is my own experience and my own opinion. I have kept it to what I saw directly.

Ratings at a glance

It is not really an AI company

This is the part I would most want someone to know before joining, because it is the gap between the pitch and the day job. iNextLabs presents itself as an AI company. In my experience it runs like a traditional services business with AI in the branding.

The founder's way of running things belongs to a different decade — top-down decisions, little appetite for how modern engineering teams actually work, and a management instinct that treats an AI product team like a billable services unit. If you are joining expecting the environment of an AI product company, that is not what this is.

It is also not a startup in the way people use that word, and not a mid-sized company either. It sits in between, with neither the speed and ownership of a startup nor the structure and guardrails of a larger organisation.

No real product structure or vision

There was no stable answer to what the product was supposed to become. Direction shifted with whoever had spoken to the founder most recently. There was no roadmap I could plan against, no clear product ownership, and no process that survived contact with a deadline.

For an engineer this is the expensive kind of chaos. You build something, the target moves, and the work is quietly dropped — not because it failed, but because nobody decided what it was for in the first place.

They talk extremely well. The pitch is polished, the meetings sound impressive, and the story is convincing. My advice: do not take it at face value. Judge it against what is actually shipping and how people are actually treated.

Culture, and how people are let go

This is where I have the strongest view. Accountability ran downhill. In the situations I saw, when something went wrong between a junior person and someone senior, it was the junior person who left. I did not once see it land the other way. Seniority functioned as protection rather than responsibility.

If you are joining in a junior role, go in understanding that. I would not count on this organisation to stand behind you if you ever needed it to, and I would be especially cautious about recommending it to women.

The Chennai office

A small thing that says a lot. People would smoke and then walk straight back into the room, and the whole room would smell of cigarettes. Everyone just worked through it. It is a basic failure of common courtesy toward the people sitting next to you, and nobody with authority treated it as a problem worth fixing.

I mention it because it is the kind of detail that tells you what the culture tolerates. An organisation that will not address something this obvious and this easy to fix is not going to handle the harder things well.

The notice period

Resigning is where I would warn people most practically. Once I was on notice, I was effectively left waiting. Messages went unanswered and routine steps were allowed to drift with no explanation.

If you are leaving, protect yourself:

• Put every request in writing, on email, with dates.
• Keep your own copies of your resignation, acknowledgements and any approvals.
• Ask for your relieving letter and full and final settlement in writing, early, and follow up in writing.
• Do not assume anything verbal will happen. Assume you will have to chase every step.

What was genuinely good

I will not pretend there was nothing. I had real autonomy over hard technical work. I led voice agent development, owned the Deepgram partnership, and built a production speech-to-text, text-to-speech, retrieval and LLM stack that real businesses ran their call workflows on. That is genuine experience and very few places would have handed it to me that early.

So if you do end up there, that is where the value is: take the hardest technical ownership you can get, learn fast, document what you build, and keep your own record of it. Just go in with clear eyes about everything around the work.

Would I recommend iNextLabs?

No. The engineering exposure is the one real upside, and it does not outweigh working somewhere with no product direction, a leadership style a decade out of date, a culture that protects seniority over fairness, and an exit process that leaves you chasing your own paperwork.

If you are weighing an offer and want to ask me something specific, I am reachable at mamlesh.va06@gmail.com. I will tell you what I told you here.

Common questions

Is iNextLabs a good place to work?

In my experience, no — I rated it 1.5 out of 5. The autonomy and the production voice-AI work were genuinely good. Culture, leadership clarity, product direction and the exit process were not.

Is iNextLabs really an AI company?

It markets itself as one. In my experience it operates like a traditional services company with AI in the branding, and the management style did not resemble an AI product company.

Is iNextLabs a startup?

Not in the usual sense, and not a mid-sized company either — it falls between the two, without the speed of one or the structure of the other.

What is the notice period like at iNextLabs?

In my case, poor. Expect unanswered messages and delays. Keep everything in writing and assume you will have to chase each step yourself.