Pros
* Good learning if you land in a strong project/team
* Exposure to real production systems and debugging - Opportunity to work across frontend, backend, APIs, GraphQL, Kafka, and integrations
Cons
* Service-based company, so project quality depends entirely on client allocation
* Priorities change frequently and can feel unstable
* Tight deadlines and release pressure are common
* Workload can become difficult when multiple urgent initiatives overlap
* Requirements are sometimes unclear or still being figured out during implementation
* Communication and planning between teams can be inconsistent
* Engineers may need to context-switch often between bugs, releases, reviews, and new features
* Work-life balance can suffer during busy periods
* Some teams rely heavily on a few contributors, creating pressure and dependency risks
* New engineers may feel overwhelmed initially due to the pace and ambiguity
* Experience varies heavily depending on manager and client project