Engineering culture specifically has turned into a political game of who can put up the most diffs and ERDs. You are now stack ranked amongst your peers and put into PIP, does not meet bar, bar, above expectations, and exceeds expectations. Know now that the above expectations and exceeds expectations is exceptionally rare, and the percentage allowed in that bucket is very, very low. Over the past two years, the number of people put on PIP and in the does not meet expectations requirements has increased a lot. Without warning, too, really. I have seen good people put in the does not meet expectations bucket who are actually the smartest and team leads. And what is the reason for it?
Oh, you are below on diff count for a certain amount of months; surely, that means you are slacking on your velocity. Oh, you only wrote one ERD over the past couple of months. I don't care that it is 50 pages and is one of the biggest projects on the team. You clearly don't have enough impact if you only delivered one of the most major projects on the team. You have to deliver 5 or 6 projects per half minimum. That is the name of the game now.
You will see everyone, from people who coast to even the smartest people in the company, put up code changes that are essentially just one-liner log or metric changes and go around begging teammates for stamps just so they can hit their diff count at the end of the month. What does this accomplish?
Remove this productivity metric tracking nonsense and using it as a core benchmark for performance. It just ruins morale and stops actual meaningful work from being done. I've seen most of the good engineers in my org leave the company because of this.
The first interview was conducted via Zoom, and some questions were asked about my previous experiences. I then had one interview focusing on algorithms and data structures. I received positive results, so I passed to the next phase, where four mor
Surprisingly, the interview felt quite straightforward, especially for a senior role. I started with a technical screen, where I was asked to design an Uber Eats cart service. It caught me off guard initially, but then I remembered a specific mock I
Above average interview process. Although, in the end, I was told that I didn't present things I wasn't asked to present. This is confusing and frustrating. Please ask directly for what you want to hear.
The first interview was conducted via Zoom, and some questions were asked about my previous experiences. I then had one interview focusing on algorithms and data structures. I received positive results, so I passed to the next phase, where four mor
Surprisingly, the interview felt quite straightforward, especially for a senior role. I started with a technical screen, where I was asked to design an Uber Eats cart service. It caught me off guard initially, but then I remembered a specific mock I
Above average interview process. Although, in the end, I was told that I didn't present things I wasn't asked to present. This is confusing and frustrating. Please ask directly for what you want to hear.