The compensation and benefits package is good.
The work environment at the company is very problematic, characterized by poor management, office politics and a complete disregard for engineering quality.
The biggest issue is the layer of middle managers, who appear to be promoted on tenure or political alignment rather than leadership skill. They are fundamentally untrained in managing people, offering technical mentorship, or protecting their teams from unrealistic demands. Their primary function is to act as project trackers, pressuring engineers to close tickets without understanding the technical trade-offs.
Career progression is not tied to merit or quality of work, but to visibility and internal politics. Decisions are made in back-channels, and there is a sense of favoritism. This creates a toxic, low-trust environment where teams are siloed and collaboration is non-existent. There is more effort spent on managing "perception" than on solving problems.
Quantity-Over-Quality Engineering Culture: The engineering teams are run like a feature factory. The only metric that matters is closing the ticket and fast release. There is no incentive to follow good engineering practices.
Code Quality: The codebase is a direct result of this. It is brittle, unmaintainable, and drowning in technical debt.
Attitude: Engineers are not rewarded for writing clean, scalable code; they are rewarded for speed. This has cultivated an attitude of just "getting it done" and moving on, leaving a mess for the next person.
I had an initial call with a recruiter where we discussed past experiences and what I was looking for in my next role. The recruiter was pleasant and the conversation was laid-back.
The usual three-step process follows initial calls. This process does not use LeetCode, unlike other big tech companies. Overall, it was a good experience, and I would interview again. System design questions are standard compared to other compani
Pros: * Streamlined scheduling for recruiter and technical interviews. * Screening for multiple locations and teams. Cons: * One hour technical interview was supposed to be 45 minutes for coding, but since the question involved multiple parts (up
I had an initial call with a recruiter where we discussed past experiences and what I was looking for in my next role. The recruiter was pleasant and the conversation was laid-back.
The usual three-step process follows initial calls. This process does not use LeetCode, unlike other big tech companies. Overall, it was a good experience, and I would interview again. System design questions are standard compared to other compani
Pros: * Streamlined scheduling for recruiter and technical interviews. * Screening for multiple locations and teams. Cons: * One hour technical interview was supposed to be 45 minutes for coding, but since the question involved multiple parts (up