Pros
The team received a free lunch and drinks once a week, which was a welcome perk.
Cons
The company struggled with a clear long-term product vision. Business decisions often felt reactive, influenced by competitors rather than guided by any consistent strategy. Planning and prioritization were inconsistent. PRDs and tickets were expected quickly, often without broader initiative alignment, and multiple approval layers slowed execution. Roadmaps shifted frequently, sometimes within a single sprint, which made it hard for teams to plan with any confidence. The overall environment was fast-paced and high-pressure. The tech team worked under tight timelines with limited resources. Frequent syncs and check-ins kept the focus on moving tickets forward. For many team members, this created sustained stress. The product manager role was closer to project management than product ownership. A significant portion of time went toward tracking execution and moving tickets rather than shaping long-term direction. Performance discussions centered on feature deliverables and bug counts, not outcomes. Attrition was high. People were laid off or left frequently, which affected team stability and morale. Leadership measured performance through sprint boards. There was constant pressure to have PRDs written, tickets created, and three sprints planned ahead, even when the roadmap itself was not settled. There was rarely enough time to understand the working style before being expected to operate at full speed. There is room for stronger product leadership at the strategic level to match the company’s ambitions. This is an intense environment. If you are considering joining, be honest with yourself about whether this pace and pressure aligns with how you work best.
