Pros
Diverse Technical Exposure: One of the biggest wins here is that you aren't pigeonholed into a single legacy technology. Since joining, I’ve had the chance to work on both frontend frameworks and backend logic (Java ecosystem). If you show interest in a new stack, management usually supports it. Collaborative Culture: True to the name, "Associative" really emphasizes teamwork. The seniors I met when I joined in '22 were incredible mentors, and now that I am mentoring juniors, I try to pass that on. The "blame game" is rare here; we focus on fixing the bug, not the person. Ownership of Projects: Unlike massive MNCs where you might own just one button on a UI, here you get ownership of significant modules. You can see the direct impact of your code on the client’s business, which is very satisfying. Stability: Even during industry fluctuations over the last few years, the project pipeline at Associative has remained consistent.
Cons
Occasional Crunch Time: The deadlines can get tight, especially when we are nearing a client delivery. There have been weeks where I’ve had to stretch hours to ensure a release goes out bug-free. Process Ambiguity: As the company grows, sometimes processes struggle to keep up. We occasionally face "scope creep" from clients where requirements change mid-sprint, leading to rework. Better documentation and stricter change management are needed. Perks could be better: While the core salary is competitive, the "soft perks" (like wellness allowances or extensive remote options) are average compared to some tech giants.