Yolo Group reviews

- Extremely low-trust culture and pervasive micromanagement. Professional boundaries were frequently crossed, minor human behaviors were policed, and employees were expected to justify schedules, flexibility, and working patterns despite formal policies allowing them. Official company policies were inconsistently applied at the team level, creating confusion, stress, and a lack of trust. - No onboarding or structured guidance within this team. New hires are expected to navigate systems, expectations, and workflows independently, leading to unnecessary frustration and inefficiency. - Feedback culture was poor and damaging. Feedback was often delayed, accumulated over time, and delivered in a harsh, non-constructive manner rather than addressed promptly and supportively. - Sexist and inappropriate comments were tolerated within the team. Harmful behavior was excused internally, while relatively harmless communication choices (eg: tone or style in company-wide tools) were scrutinized, revealing inconsistent standards and misplaced priorities. - Creativity, inclusivity, and initiative were actively discouraged. Efforts to make data more engaging and accessible to a broader audience were dismissed, with value placed almost exclusively on senior leadership opinions rather than team-wide collaboration. - Public comparison and indirect criticism were normalized instead of clear, constructive guidance, creating an environment where employees felt undermined rather than supported. - Team culture was negative, defensive, and lacking empathy. The team frequently spoke critically about stakeholders and reacted with hostility to basic professional norms, such as welcoming new colleagues or leadership changes. Raising concerns about this culture was met with deflection rather than reflection. - Lack of compassion for personal hardship. Even in the context of serious personal loss, flexibility and empathy were not extended, with deadlines consistently prioritized over employee wellbeing. - Compensation discussions were handled unprofessionally. Repeated remarks created an uncomfortable atmosphere around pay rather than focusing on performance, expectations, or growth. - Leadership failed to recognize or leverage individual strengths. Strengths were often reframed as weaknesses when they did not align with narrow priorities, while collaboration and team improvement efforts were dismissed. - Basic technical and organizational standards were neglected. The team resisted documentation, naming conventions, and maintainability practices. Concerns about code readability or long-term quality were met with defensiveness instead of support, indicating a lack of senior technical leadership. Overall, the environment was unsustainably toxic. Despite a short tenure, the cumulative impact on wellbeing was significant and long-lasting.