Lack of Diversity in Leadership: The reporting chain is highly homogeneous, with most leads and managers coming from the same country or background. This creates an insular culture where engineers from different backgrounds often find it difficult to have their voices heard or their contributions recognized.
Chaotic Codebase and Poor Knowledge Transfer: Many systems appear to be patched together from multiple open-source projects with no unified architecture. There’s a noticeable absence of documentation, design rationale, or operational guidelines. Pull requests often contain little or no context, and it’s not uncommon to see over hundred high-severity issues logged weekly as a result.
Toxic Hierarchical Culture: Long-tenured, high-level engineers dominate team dynamics. They can be dismissive or even hostile to improvement ideas, sometimes publicly accusing others of having “ulterior motives.” Management consistently fails to address this behavior, enabling a culture where intimidation is normalized.
Authoritarian Management Style: Reasonable questions or requests from team members can trigger disproportionate reactions. The culture discourages open discussion or questioning of decisions. In some cases, when managers are challenged in public settings, they appear unprepared to explain their rationale and instead respond defensively.
HR System Lacks Independence: HR can redirect back to the management chain you may be reporting. Should you persist, HR might conduct a vague "investigation," but they refuse to provide timelines, methodologies, or updates. In some cases, escalating further has reportedly led to sudden termination with no stated cause.
