Thoughtworks reviews

The company has been going through difficult times and is trying to re-establish itself competitively in the market, with frequent layoffs and strong pressure for results (which did not exist before) You often don’t have someone closely following and supporting your development journey, which makes internal growth more difficult You often end up working more for the client than for Thoughtworks, shifting from the company’s culture to the client’s culture (which can be good or bad depending on the project) For Product Managers, many projects tend to be much more operational than strategic Performance evaluation is very subjective, with no clear individual-level goals to track Sometimes you will work alone, with no other thoughtworker

The company promotes a strong narrative around innovation and engineering excellence, but in practice, this vision is being compromised by a growing imbalance between professional rigor and subjective work dynamics. There's a noticeable shift: Personal opinions, co-creation sessions, and non-technical frameworks like design thinking often override data-driven engineering decisions and best practices. While collaboration and empathy are important, the growing tolerance for a lack of technical depth has created an environment where structured engineering input is sidelined. Bringing architectural guidance, design patterns, and evidence-based recommendations to the table is often met with resistance or hostility, making it increasingly difficult to uphold technical standards. This creates frustration for engineers committed to quality and leads to a high rate of rework and failed initiatives.