31–40 of 345 posts
[flagged]
Police is a protected title but anyone can be a thought police. One can be a spin doctor without any academic acumen. Notice how when qualified, the words take on a broader and sometimes illustrative meaning than when used in isolation. Context matters.
Ugh. Pain. I'm hiring, and I've been filtering out resumes that are heavy on these kinds of metrics.
Because I literally get thousands of entries with these kinds of wording. Often with excessively precise numbers, like "by 23.5%".
My problem is that it's hard to tell the amount of real work it took to do that. It might have been as stupid as creating an additional index in the database, or it might have involved a deep refactoring across multiple systems with a zero-downtime gradual rollout.
I would prefer something like: "I worked as the hands-on leading developer to do a large-scale refactor on the highly loaded front-end network routing system, resulting in user-visible latency decrease on the Youtube front page".
For me the key words are: "hands-on" (and not just writing a product brief and getting resources for it), "large-scale refactor" (so likely not just creating an additional database index), "highly loaded".
I wonder what it was that the amazing managers taught him. I've never had an experience with managers that would leave such an impression on me. Fellow developers, sure; but not managers.
Promotion at Google, as in many places, is tough. Status is allocated partially on level, so it sucks to not see that growth.
Sometimes lack of promotion can be not having the right opportunities.
It's fair to leave a company for whatever reason.
For any other L4->L5s, or anyone wanting to become a senior engineer, it's worth self reflecting on whether there's improvement that can be made from failed promotion attempts.
> people all across the org knew me and said I was indispensable to the company and were surprised that I wasn't already at an L5/6 level.
No one in a large org is indispensable, but many are very valuable. Many L4s are very valuable, but at doing L4 work. It's not a value judgement.
L4->L5 is a step of responsibility: can you be trusted to handle a multi quarter project, without much supervision.
> I helped launch/lead features on YouTube, I led teams, I designed and implemented systems that were still in use to that day by many people
The details aren't clear here, but sometimes an engineer can be leading projects, and need supervision: poor delivery, poor communication, poor outcomes.
"Too little impact" in this context can mean "you needed too much supervision" or "too little impact per $TIME_PERIOD" meaning you can have delivered great technical solutions, but not at the rate or level of independence needed to meet the mark.
Again, not meeting this mark isn't a value statement. It's a different type of work, but it happens to be incentivized with more $$$.
> In the software engineering world, we exist on a ladder. We call this ”Leveling”. That bubble is not the world, I exist outside the ladder and I am legion.
I wonder if the author had attempted to transfer to a different part of the company first, since a different organization might have more room to grow. It might not be possible to do a transfer plus a promotion simultaneously, but it's likely a less stressful option than leaving the company.
Reading this I feel like I live on another planet. I recognize this guy seems to only be dealing with FAANG type companies, but the disconnect from my own reality is so vast it’s hard to reconcile. I have never worked anywhere with the L4/L5/whatever crap. No one I have worked with has either. It sounds downright dystopian that people are reduced to a basically a number (if you leave out the L). I am assuming he left…
I've been at three FAANGs now and my experience has been that nobody really cares about your level for day-to-day work. The only times it has ever come up for me is when a) I was part of assembling a new team and we needed a mix of juniors and seniors or b) when some dangerous action like deploying during a holiday code freeze needed approval from an L9+ by policy, so you had to go find that person and justify it to…
And??? Where did you go? Did you get L5/L6? Or did you just leave and not get another job? What a wild article to have the interviews so prominently featured but not have a conclusion.
>This duality is exhausting. It forces you to lie by omission to people you respect. You can't tell your team, "I can't take that ticket because I need to study dynamic programming." You just have to work faster.
Guess what promo will get you? More context switching. Maybe that’s a thing to work on.