Declining engineering culture, poor leadership
Declining engineering culture, poor leadership
Compensation and benefits are decent. Good coworkers.
The engineering culture is on a steep decline.
There is forced stack ranking for performance reviews that's naively focused on short-term impact.
Engineering leadership (VPs specifically) is terrible and holds no accountability for themselves, instead trying to pass down accountability to others lower in their reporting chain. They are unable to push back on product initiatives and instead want ICs to be blamed for not pushing back on initiatives we don't believe in.
This is a terribly inefficient way to do things.
WLB is declining because of all this, and burnout across orgs is on the rise. Multiple high performers are unhappy and have already left or are in the middle of plans to leave.
Stop passing the blame and accountability for working on the wrong things.
Engineering VPs should be able to spot bad initiatives and stop them instead of waiting for ICs to push back.
Build back a more empathetic and supportive work culture before it is too late.
Additional Ratings
Was this helpful?
LinkedIn Interview Questions
LinkedIn Interview Experiences
Staff Software Engineer
I had a two-hour phone interview, followed by onsite interviews. I went through the process twice. The first time was a decently good experience. The second time was the worst interview experience of my life. It's hard to believe plain luck matter
Staff Software Engineer
Recruiter called. They were very professional. Phone screen: 2 questions. Onsite: 6 rounds. * 2 technical coding rounds (one basic question about merging intervals, the other about trees) * 1 design interview * 1 craftsmanship interview *
Staff Software Engineer
Standard hiring process, same as other big tech companies. First, I received a phone call from the recruiter who explained the role. Then, there were two one-hour phone screens: the first was behavioral, and the second was a coding interview using C
Staff Software Engineer
San Francisco, California, United StatesJanuary 1, 2020I had a two-hour phone interview, followed by onsite interviews. I went through the process twice. The first time was a decently good experience. The second time was the worst interview experience of my life. It's hard to believe plain luck matter
Staff Software Engineer
Mountain View, California, United StatesFebruary 1, 2016Recruiter called. They were very professional. Phone screen: 2 questions. Onsite: 6 rounds. * 2 technical coding rounds (one basic question about merging intervals, the other about trees) * 1 design interview * 1 craftsmanship interview *
Staff Software Engineer
Sunnyvale, California, United StatesJanuary 1, 2017Standard hiring process, same as other big tech companies. First, I received a phone call from the recruiter who explained the role. Then, there were two one-hour phone screens: the first was behavioral, and the second was a coding interview using C
