Comment by ryandrake | Hacker News Reader

Comment by ryandrake | Hacker News Reader

Parent Full thread

Yea, I used to accept "Do 'It' for +N% salary" but homie don't play that game anymore. The problem with accepting additional comp without advancement is:

1. Salary will plateau eventually. I know early in your career it doesn't seem like it will, but trust me: It will. I don't care what company you are in, or how good you are, "Fourth Senior Software Engineer From The Left" is never going to be making $1M/yr. (Not that that should necessarily be your goal, but it illustrates that you will plateau at some point.)

2. When you keep job hopping for more money but no change in level, you risk gaining "1 year of experience 20 times" instead of 20 years of experience. You're sacrificing long term career growth for short term salary bumps. I did this for years and ended up shooting myself in the foot long-term. My college friends, who instead played the Title / Ladder Climbing game, are all much better off than I now. They're all job-secure VPs, SVPs, and CxO's in their companies vs. me who still doesn't even have any direct reports, and is one of many interchangeable worker bees.

No more doing that for me. I'll only accept, at a minimum, a level jump at this point.

It sounds like you're an individual contributor and want off that track and on to the management track.

Or to you, is "management" simply the next level beyond individual contributorship? I won't work for an employer that doesn't plan for career advancement in BOTH tracks - management is great, but for every one of you who sees career advancement as managing others, there's someone like me who wants to stay the hell away from that while still finding room to advance my career as an individual contributor.

Any thoughts?

Very few companies have a legitimate “parallel but equal” tech track for IC’s that remains IC all the way up. At some point on the totem pole you end up managing. All roads upward point to it. I currently work for a company that has a robust stack of levels for software engineers, but nobody at the “director equivalent” tech level is an actual IC.

I love the concept of having VP-level IC “wizard” roles who don’t have to manage, but have never seen it in practice.

I've seen those roles at Microsoft, Amazon, and other big tech companies.. Like you implied, though, they all plateau in compensation around $800k or so.

These roles definitely exist, but it's worth counting the relative numbers at each level for Manager/Senior Manager/Director/VP vs IC's at that level.

Generally, there's wayyy less of the IC roles, which essentially means that people who want advancement are often gonna end up on the management track.

At my most recent company engineering managers made less than the engineers they managed and staff engineers usually made more than directors. So if you wanted to go the management track for advancement it meant a pay cut for at least a few years.

I can't speak for the direct OP, however outside of exceedingly large companies, rarely do you get to just be a major contributor and still climb past a certain point. Microsoft and Google have things like distinguished engineers but most people never reach these levels, because you have to be truly outstanding to attain them, and often, they too are really good at managing their sphere of influence.

As a Staff Engineer I'm just a really engineering focused manager "lite" if you will, (in so many ways, maybe I'm not doing enough justice here, but its how it feels day to day).

I like it, because I'm managing the architecture side of things and still involved in engineering decisions I care about, but I have both direct people working with me that I'm accountable for, as well as a 2nd level of accountability for the entire organization. I still get to commit code and do exploratory research, which is nice, but its not the highest percentage of work I do. So much of it is overseeing the implementation details of other engineers, providing guidance to both engineering as an org, or individual engineers, or being involved in product roadmap so that our architecture evolves flexibly enough to meet where we want to go, writing documentation and diagrams, giving technical presentations etc.

All told, at some point, you have to be a manager, even if its not a direct "manager" role, per se.

You hit it pretty spot on. There's still a lot of management expected at those levels, it's just of an influential type instead of an authoritative type. Which is often even harder to wield effectively. You're still expected to go out and force-multiply, because the bottom line is a single person worth of productivity can only go so far.

Yes, much harder without authority over a budget and staff.

Reply on news.ycombinator.com