TL;DR:
Join this company only if it is genuinely your last resort to keep body and soul together. The culture is deeply dysfunctional, the work is misrepresented, and systemic issues remain unaddressed year after year.
Culture & Working Environment
Before joining, I saw negative Glassdoor reviews and assumed the issues were isolated to a few teams. Within a month, it became clear that the problems are organization-wide. After raising concerns and being promised change, I gave the company another year. Nothing improved; in many ways, the situation worsened. I would suggest additionally looking up the company by its former name "SE2" on Glassdoor for slightly older reviews, most of which are still relevant.
The workforce is split into two clear groups:
• Employees who joined in the last 2–3 years — professional, respectful, collaborative.
• Long-tenured employees — the source of a deeply entrenched culture characterized by mistrust, escalation, gatekeeping, and open hostility. This behavior is normalized and, at times, encouraged by management.
A high degree of suspicion permeates every layer. Project managers, product managers, developers, and QA frequently question one another’s competence. Most strong performers leave within a year once they understand the environment.
People & Behavior
A handful of long-standing employees hold disproportionate power because critical system knowledge lives only with them. This creates an environment where:
• documentation is kept minimal or opaque
• information is shared selectively
• teams become dependent on specific individuals
• abrasive conduct goes unchecked
Some senior individuals routinely speak to colleagues and clients in ways that are unprofessional and shocking to witness. Because their knowledge is essential to the company’s legacy system, they operate without meaningful oversight.
One team leader with a long history of complaints has been associated with yelling, bullying, issuing questionable PIPs, withholding work, and creating hostile work conditions across multiple teams. This is openly known inside the company. HR is ineffective at addressing these issues and often aligns with management even when evidence contradicts the narrative.
There have been incidents where threats were made in anger—for example, a leader telling someone, “If this happens again, I will grab your neck.” The underlying problem was missing documentation, not employee incompetence.
Technology & Knowledge Management
The core system has been evolving for nearly twenty years, with little to no usable documentation. Whatever exists is hard to search, incomplete, or outdated. Only a few senior employees understand the system fully, and they become gatekeepers by necessity or design.
This results in:
• new employees unable to work independently
• project delays caused by missing context
• high frustration among QA and development teams
• severe bottlenecks whenever senior staff are unavailable
I was discouraged multiple times from sharing full context with cross-functional teams. When I ignored that advice, provided complete background, and wrote detailed stories, projects consistently finished on time with zero confusion — a stark contrast to the norm, and frequently received appreciation for it. Developers and QA regularly approached me for clarification on tasks written by other tenured product managers because their stories lacked clear objectives or background.
Workload & Resourcing
Despite constant inflow of new projects, the company frequently downsizes or chooses not to replace departing employees. It is not unusual for a single product manager to be involved in 20 concurrent projects in a single sprint. There is consistent context-switching, with something or the other screaming for attention every 5-10 minutes, which causes a massive hit in productivity.
A typical day:
• 70% resolving escalations and putting out fires
• 30% project management
• <1% actual product management
The pressure is relentless (glorified as a "fast-paced environment"), and prioritization is often impossible. Random requests appear demanding explanations for work completed a year prior, even though the company enforces logging time in 15-minute intervals. After spending an entire day reconstructing old work, the final conclusion often ends up being: “It should have been logged under a different Jira ID.”
Product Management Reality
The role advertised as “product management” is effectively a renamed configuration analyst/business analyst position.
Key realities:
• No real product ownership exists.
• Requirements are dictated by clients.
• There is no functional roadmap.
• Leadership has spoken about building a roadmap for years with zero visible progress.
• PMs spend most of their time on administrative firefighting, not product strategy.
Additionally, PMs are pressured to maintain high billable-hour percentages, even though they have no control over the nature of their assignments. Internal fixes and enhancements — essential for product stability — are discouraged because they are not billable.
Rushed scoping regularly leads to misreading client requirements. When timelines slip, the explanation becomes: “The system is more complex than expected.” Some projects end up being delivered without billing simply because initial requirements were misunderstood.
Client Relationships
Long-term clients have learned to be skeptical. They often request more detailed documentation or test cases because past experiences have taught them not to rely solely on the company’s explanations.
Some clients now poach employees from the company simply to deal with the company more effectively.
HR & Management
HR struggles to enforce accountability and often contradicts itself. Policies are inconsistently explained. Only the highest-level HR leader communicates clearly and reliably.
Favoritism is widespread:
• Mistakes by long-tenured employees are consistently overlooked.
• Newer employees are held to a different, stricter standard.
When senior PMs make documentation errors, they tend to assign blame immediately. Even when presented with evidence, the incident is brushed off as an “oops moment,” with no accountability.
Well-being & Mental Health
A deeply concerning pattern emerges once you speak openly with colleagues:
• Several employees report being on medication for work-related anxiety or depression.
• One PM shared that they nearly crashed their car due to a panic attack triggered by work stress.
• Others report daily reliance on anxiety medication simply to function normally.
The normalization of this distress is alarming.
Treatment of Offshore Teams
Offshore employees face especially harsh conditions:
• routinely asked to work until 3–4 a.m.
• required to remain in the office late to attend meetings scheduled solely for North American convenience
• assigned work avoided by North American teams
• given limited learning or growth opportunities
This creates a two-tier system where offshore staff bear a disproportionate burden.
Why This Review Exists
I wrote most of this over a year ago but held off posting it to give leadership a chance to address these long-recognized problems. After waiting and watching things worsen, I believe candidates deserve a realistic picture before making a decision.
Final Verdict
Hard pass.
Unless your financial situation leaves you with no alternative, this company will offer little in terms of culture, career development, psychological safety, or true product management experience.
