Pine Labs

The company is worth considering only if you are switching for a significant salary hike. However, after joining, you may find that existing employees with less experience than you are being paid more. On the positive side, the learning opportunities are good, and the technologies used are modern and up to date.

1. The company claims to have 1,000–5,000 employees, but there are hardly 200+ developers; the majority of the workforce is in sales.

2. There is no documentation for the existing systems, yet managers expect new hires to take ownership and work on them like experts from day one.

3. There is a significant amount of internal politics. Many employees are unwilling to share knowledge because they fear losing their importance or dependency within the organization.

4. The CEO and CTO create excessive pressure from the top, resulting in a stressful work environment.

5. The management has changed significantly over the past 5–6 months, and several managers with more than 10 years of experience have resigned in large numbers.

6. There is no structured knowledge transfer (KT) plan for new hires.

7. No KT videos or documentation are available for existing or legacy services, making onboarding difficult.

8. If you need assistance from another team, you often have to chase people around, as there is no streamlined process for inter-team collaboration or support.

9. The internal politics are so severe that some employees are unwilling to hand over services or share knowledge with new team members, even when instructed by management. As a result, proper functional knowledge transfer (KT) is often not provided.

10. Tasks are assigned without adequate guidance or support. Functional requirements are frequently unclear, and the existing system architecture and workflows are not explained, making it difficult for new developers to contribute effectively.

11. There is significant pressure to use AI tools such as GitHub Copilot to complete tasks, but management often overlooks the fact that developers need a solid understanding of the existing modules and business logic before implementing enhancements. Without proper knowledge transfer, there is a higher risk of introducing changes that could break existing functionality.

1. Implement proper documentation and structured knowledge transfer (KT) for all legacy systems and services.

2. Foster a collaborative culture where knowledge sharing is encouraged and internal politics are minimized.

3. Set realistic expectations for developers—AI tools like GitHub Copilot can assist with coding but cannot replace functional knowledge or fully understand complex legacy systems without proper context.

4. Build a culture of recognition and constructive feedback. Managers should appreciate employees for good work just as readily as they point out mistakes. Constant criticism without acknowledgment of achievements negatively impacts morale and motivation.

5. Why is there no in-person HR? Whom should an employee talk to in case of a dispute with my manager or peers? There is only a Jira ticketing system, which takes several days to provide a resolution. At least give your HR team some authority to handle such cases effectively.

6. And trust me, many employees are not happy with the current management that has been in place for over 10 years. Most of them are simply trying to survive until they find a better opportunity.