Pros
Pros Talented ICs: There are genuinely brilliant engineers here. If you can fight through the noise, you'll find people who actually know how to build systems. The Mission: The product is interesting and ambitious, which makes the internal dysfunction even more heartbreaking.
Cons
Cons The "Drama Class" in Charge: Engineering culture has been cannibalized by non-technical "organizers" who seem to thrive on friction. Instead of removing roadblocks, they create them to maintain relevance. There is a constant stream of manufactured urgency and "alignment" meetings that produce zero code. This is quite recent. Technical Gridlock: The platform mono-repo is a mess of poor siloing. Because of the lack of boundaries, a "simple" task requires navigating a labyrinth of dependencies and architectural gatekeeping. What should take two hours takes two days because you’re constantly stepping on toes in a codebase that no one truly "owns." Release Deadlines: Timelines are set by people who want to hit their KPIs on paper (and only on paper). This leads to a permanent state of "crunch" where quality is sacrificed for optics, and "done" is better than "right." Politics Over Performance: Hard work is essentially invisible. The rewards go to those who put others down, who use the word "alignment" 10 times a day.