Unstable environment with unrealistic expectations and poor support - AI Analyst Innodata Employee Review

2.0
17 Sept 2025
Recommend
CEO approval
Business outlook

Pros

Salaries were credited on time. There was also exposure to a variety of AI and LLM related projects, which could benefit early career professionals looking to gain broad experience.

Cons

The work environment was often chaotic and extremely high-pressure. KPIs were unrealistic, and employees were expected to meet demanding performance standards with minimal training, even after being shifted to completely different projects. Raising concerns about tools or workflows was routinely dismissed or blamed on the employee. There was little consistency across teams, and the appeals process for quality reviews rarely worked in time to make a difference. In some cases, employees were told their roles were being elevated, but salaries remained the same despite the added workload. Many ended up working 10–12 hour days for the same entry-level pay. Leaves were very difficult to get approved, even for health-related reasons. Instead of allowing time off, the company often asked employees to simply “work less” that day but still meet targets. If there were any technical issues, even completely out of your control, you were still expected to make up the hours later in the week. Overtime was paid, but people were sometimes guilt-tripped into agreeing to it. Firings happened without warning or proper process. Overall, there was no transparency, consistency, and basic support systems needed for long-term growth or stability.

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