Hacker News new | ask | show | jobs
by NikolaNovak 1232 days ago
"promotion is more about consistent level N+1 behavior, while one could get a high performance rating by solving many level N problems."

Not all companies are like this, and I find it common that new employees are not sufficiently taught what their company is like :

A) you have been performing well as N,promotion means "we feel / hope you're ready to work as N+1 in the future "

B) you've done great as N and have repeatedly performed N+1 tasks successfully. Promotion means "we recognize what you've already been doing "

First one is "proactive" and represents faith you'll do well at next band. In principle all you have to do is do your job well. There is risk though that you man not succeed after promotion if next band has radically different role or skillset.

Second one ensures you're prepared for your new band, but you cannot there just by doing your job well, and many people are unaware or don't have opportunity to do tasks of next band in their current role

5 comments

I've seen B cause issues too.

The duties of level N and N+1 are often a little different. If they're different enough, then it can be difficult to demonstrate N+1 while also doing N work. You're option is to work two jobs at once or, as I more commonly see, do the bare minimum of N work and focusing on N+1 work. This can look like the teammate who's focusing on division-wide initiatives at the expense of implementing the things their team is actually assigned - leaving their teammates to pick up the slack.

This is certainly not inevitable, and I'm definitely not saying B is a bad way to do things - just that this is a failure case I've seen of that model. The other, of course, is "why spend a year doing N+1 work here at an N salary when it's easier to just get hired as an N+1 at a new company today?"

One successful way I've seen this down is to proactively give people ownership of sub-projects with collaboration, or leadership scope N+1. It is explicitly acknowledged (so no shadow work that your team is covering to support) and acts as a way to gauge maturity, while limiting risk.
Yep...we had a whole slew of people acting like N+1s on my team a couple years ago. Everyone trying to "lead" everyone else. Load of horseshit. Just get the work done. Meanwhile I feel like I'm penalized for not attempting to micromanage everyone else. My scores are great for N but I guess I'll never get N+1.
I've seen B cause issues for great devs. It seems like if you're an ok or good dev with management qualities you're much more likely to get promoted than if you're a fantastic dev with management qualities. You're too important to delegate management tasks to, so you never get the required experience to move up.
a victim of your own success.

the idea that there's no path for ICs beyond management is insulting and degrading to the hard working creatives and engineers out there. Don't give up there's a place for you, you just need to look a LOT harder and in places you wouldn't expect. Play the numbers its a statistics game.

Oh this hasn't happened to me, I've been pretty proactive about interacting with both my direct manager and several levels above them, but I have seen it happen to other devs. Especially ones from east Asia who seem to culturally focus a lot more on doing a great job on N level tasks instead of focusing on N+1 level tasks.
Thanks for the call out! There are definitely companies that go with (A), but in all the companies I've been at, (B) is the model.

As others have responded, there are definitely trade offs with different models. The way I've seen (B) worked well is:

* Given a project, separate out the "level" of different axes. A project could have level N technical scope, but level N+1 collaboration scope, etc.

* Let the level-N engineer handle one level N+1 axis at a time, with supervision on other axes.

* And if they ace one axis, then back off and give them more responsibilities on the other axes, for the same project or subsequent projects.

Of course there are also scenarios where someone is just thrown into the deep end. They will either sink or swim :)

Has anyone been stuck in a position where you seemingly cannot land a promotion because you've had to keep taking on more responsibilities, to the point where you're beyond qualified for the next level, but you're not yet able to excel past it to the next level beyond that?

- Must achieve the highest performance rating for current responsibilities to qualify for promotion.

- But current responsibilities are actually level N+1½.

- Sometimes struggle with the responsibilities from level N+2.

- Never get promoted due to inconsistent N+2 performance.

To go from level N to N + 1, one must learn to embrace the succ.