A Pathetic company, disappointing experience!!!! - Lead Engineer Innodata Employee Review

1.0
25 Mar 2020
Recommend
CEO approval
Business outlook

Pros

Pros include:- Location, outside eateries, parking inside the building, DJ's on every festival/occasion

Cons

I Worked in the organization for about 6 months, and believe me after 9 years of experience, 6 months are enough to access/understand an organization. My experience was very disappointing and I would highlight below points everyone should consider before joining:- 1.) This is prima facie not an IT company, it’s a KPO. What it means is that the company does not have an IT mindset. 2.) Managers follow micromanagement. 3.) It lacks good clients, so the funding is not that good. 4.) The infra is too bad means desktops, laptops with very poor configuration. 5.) Most of the projects does not follow any SDLC, most of the CR’s are done on the fly, the company lack and does not follow basic/best practices like documentation, there was no documentation for my project consisting 9 resources. This company is so cheap, that they have blocked (Lien Marked) my last month salary after crediting it into my account because I resigned(formally resigned because of the above facts) and they speculated that my intensions were not good. My EMI’s and my credit card bills bounced and I have been fined. It was like a harassment that I felt when I was in the company.

Explore other reviews about Innodata

5.0
2 Feb 2026
Recommend
CEO approval
Business outlook

Pros

Great place to work with consistent communication.

Cons

Days can get repetitive and dry

2.0
12 Apr 2026
Recommend
CEO approval
Business outlook

Pros

Some flexibility Work from home

Cons

One thing I really didn’t enjoy about the guidance: our client sets a bench mark of having 85% “utilization”. Basically stating that of the 40 hours worked, 85% of that must be in “production code”, so about 35ish hours a week. The rest of the time can be spent reviewing emails, guidelines, etc. The project manager basically had management tell people that they could be 2.5 hours in other codes, and about 37.5 should be in production. If this is a decision from a client, then great, but it seemed to me the project manager was just trying to get every little bit of production possible out of people. I’m under the impression that if employees are treated like people and given proper breaks, the quality of work will be way better. If you force them to sit for 7.5 hours or a 8 hour day in front of a screen, the quality will be worse. The client says it’s 85% utilization, so why are we telling our employees they need to be in production for 37.5 hours out of the day? It just seems dishonest. Data annotation work can be tough and some of the tasks are repetitive and can take a lot of concentration. Half of the admin, forgets what it’s like to work in the queues, and drive these numbers blindly. Meanwhile, half of their job consists of chatting on teams all day.

See reviews by: Helpful|Rating|Date|All