Valuefy Solutions Reviews

- Appraisals often felt influenced more by favoritism than actual performance. - Requirement management was inconsistent. When concerns about unclear requirements were raised, the response was often "Just do it." Later, the same senior developers were told, "You should have informed me earlier," even though the issue had already been raised. - Requirement documents were frequently updated. After development was completed, the same Business Analysts who prepared the documents would sometimes ask, "What is this?" and, when shown the documented requirement, respond with "I haven't seen it," leading to unnecessary confusion and rework. - Many senior team members had spent 8–10 years on the same project, resulting in limited exposure to modern technologies and engineering practices. Instead of mentoring and guiding developers, feedback often focused on blaming others rather than solving problems or helping the team grow. - After adopting AI tools like Claude, unrealistic expectations were created. Statements such as "Management built a module in just 2–3 hours. What are you all doing?" were used to compare AI-generated prototypes with production-ready development, ignoring the complexity of enterprise software. - Upper management appeared to have limited visibility into the actual technical challenges and often relied heavily on feedback from a few senior members. - Management and senior staff often felt like a family, where accountability did not seem equal. Mistakes by senior staff were often overlooked, while employees were expected to bear the consequences of senior staff. - Senior members often shared responsibility during development but, when issues arose with users or clients, the blame was shifted to junior employees instead of taking shared accountability.