no love lost - Generative Ai Associate Innodata Employee Review

1.0
Mar 12, 2026
Recommend
CEO approval
Business outlook

Pros

job was a good way to dip a toe in the AI chatbot training water and improve the end-user experience

Cons

There was either no work in the queue for days/weeks OR I was drowning in work - feast or famine because I was only working for one client as a contractor which made my employment tenuous. Onboarded with 200 other people on the same day - not a smart way to orient new employees! A person above me in the chain of command told me that Innodata terminated her earlier in 2026 along with over 100 other US-based employees. Canadians have received emails more or less warning them that if they were on the projects that ended, they might be also let go. She said the company is not in a good spot with that client. They were always a confidential client that we weren't supposed to speak about, so that might be why I don't see their logo on Innodata's website any longer. It was their workflows that were closed abruptly, after months of other projects also going underwater rapidly. My former co-worker does not see them continuing operations with Innodata for much longer. Innodata is making most positions contracted instead of salary, no benefits or laptops, and those contractors are reporting all over the place that Innodata has not been paying them for months at a time - some have not received a check since November 2025. HR is hanging up on employees who call to ask questions about the recent layoffs of over 100 people, They recently shut down 600 new contracts with overseas contractors who didn't even make it through training. They clearly are struggling to compensate everyone,

Explore other reviews about Innodata

5.0
Feb 2, 2026
Recommend
CEO approval
Business outlook

Pros

Great place to work with consistent communication.

Cons

Days can get repetitive and dry

2.0
Apr 12, 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