If you're trying to join as a Lead, please don't join - Lead Data Scientist Tiger Analytics Employee Review

If you're joining as a Lead in one of the newer managed service engagements, this is what you're likely facing. The project would start with subpar scoping and requirement gathering, this responsibility is carried by the Consultant Team (comprising of Engagement Manager, Business Analyst and Delivery Partners - they don't ask the right questions in these initial meetings done during pitch. I say this as I attended a lot of the pitch meetings), this leads to less resources being hired than required. There is a rotten culture of blaming the technical team for everything that has transpired. So when the project starts and the client changes scope and requirement from left to right, rather than go back to the requirement document, aligning with internal teams, create governance and discuss timelines, the consultant teams are scared to make a discussion/negotiation with the clients and agree to all of the clients whims. It then leaves you to execute in the remaining time while moving things from pillar to post. And if you don't get things done (which is the case sometimes), you'll be blamed. While the quality of people being hired at the grassroot level (within the Data, App, DevOps and ML domains) is good, the same cannot be said of hires done at the senior management level. Some of these are folks with a lack of vision, spine and direct mindedness. So when it comes to executing projects, the only people being held accountable would be the technical team whereas no such thing exists for the management team. When you're dealing with these things during execution phase, you can be mentally and physically exhausted and possibly leave within a short duration. WLB is awful, toxic environment is prevalent. Do not join if you're trying to as a Lead. If you're a new graduate - learn the work, technologies and go for better opportunities later on.