Live data from Hacker News

So You Want to be a Big Shot: Advice on playing the promotion game

davidreiscto.substack.com

11–20 of 38 posts

Re: So You Want to be a Big Shot: Advice on playing the promotion game

#11
post #2

The vast majority of devs are under 30. Already most people are "senior" after 5 years experience. What are we going to do when this cohort wants to get promoted into architects and managers in 10-20 years time? There just aren't enough senior jobs.

As with any scarce resource, the most effective people will get them.

This piece is to help people be marginally more effective and be one of the ones that gets it.

PS: your question assumes stable demand for software engineer, but I'm completely uncertain whether it will grow stay flat or disappear. It all will depend on how AI goes, as well and overall economic development and digitization of the economy.

Re: So You Want to be a Big Shot: Advice on playing the promotion game

#12
This is quite unsound advice, from someone who happened to grow their career in a period where the software industry was growing faster than it could find talent, so job hopping was the best way to grow.

Maybe not bad advice, just ineffective in any mature industry where promotions are typically internal, changing jobs will almost never land you into a more senior position - unless you are really, really good at CV stuffing and bullshiting your way through interviews - and leaving will usually "reset the clock" you accrued on the internal promotion ledger.

It this, more traditional setting, promotions are a power game and managers use promotions strategically to increase their own power in the company and gain allies. This means that you have a cooperation-competition relationship with your own manager: he either levels up and drags you too because he wants loyal people around, or he sees you as a potential competitor his own boss might promote into lateral teams that will then suck his resources. Knowing where you find yourself in this game, who are your allies, what does upper management want and how can you fulfill it and gain their confidence are the keys.

Re: So You Want to be a Big Shot: Advice on playing the promotion game

#13
post #5
post #2

The vast majority of devs are under 30. Already most people are "senior" after 5 years experience. What are we going to do when this cohort wants to get promoted into architects and managers in 10-20 years time? There just aren't enough senior jobs.

Staff and above are fundamentally different jobs to Senior, which is why Senior is a terminal level at most companies. It's about scaling yourself through others, and not everyone wants to do that, and that's OK.

It's not fundamentally different, and all engineers should be scaling their impact. Staff engineers who think like this tend to be the most useless engineers, since they eschew real work in favor of appearing politically powerful with lots of cross-team impact. Scaling impact is good, but real work often requires being deep in the trenches.

The engineering ladder is one of the worst things to happen to this industry. Sometimes cross-team is the easy stuff, and solving some deep technical issue has the most impact.

People here hate leetcode and IQ tests but they are far better filters than "job level" where I've seen many principal engineers failing to write basic code.

Re: So You Want to be a Big Shot: Advice on playing the promotion game

#14
This advice is not wrong, but honestly it could be way more cynical.

The first step to get promoted is to understand the promotion process of your current company, if they have a formal one. It took me one year to learn how promos work in my current company, and that was one whole year of progress lost.

Then if you really want to get promoted fast, you need to optimize to meet the promo criteria. Often that is in line with OP advice, sometimes it is against it. And above all, learn about scope, impact and visibility. Also learn about optics and politics. Sadly often promotions are not so much about your accomplishments, but how you present them and how people perceive them. The old advice of "work really hard and you will be rewarded" is moot if the right people don't know about it. Some people get promoted faster by doing less but promoting themselves harder and louder.

Even if you don't want to exactly game the system, it is still useful to know how it is played. For example, if you accomplish some extraordinary, spend a bit of effort letting higher ups know about it.

Re: So You Want to be a Big Shot: Advice on playing the promotion game

#15
In big tech, I have found the following to be critical for engineers.:

TLDR: Team selection is 70% of it.

1. Find team with high turnover, overall low tenure. Avoid high tenure teams at literally all costs. The politics will be high, and there will be a line to get promoted. Try to figure out if someone is being primed to be promoted. Do not join the team if this is the case.

2. Further filter for teams that are somewhat business critical, legacy tech, and are failing all of the time.

3. Unfortunately, this one is very important. Find management that looks like you, was educated like you, and overall is very receptive to you on first interaction. DO NOT DOWNPLAY this. People at FAANG promote based on natural affinity.

4. Understand the parameters to get promoted, notify your manager of your intentions. DO NOT TRY TO INNOVATE. Hit all deadlines right on time or before. NEVER take on extra projects before hitting the deadline, removing all extra work, only ever work on tracked tasks with documented high profile outcomes.

5. Do this for 2-4 years, if you havent got promoted by then, leave.

Re: So You Want to be a Big Shot: Advice on playing the promotion game

#16
post #2

The vast majority of devs are under 30. Already most people are "senior" after 5 years experience. What are we going to do when this cohort wants to get promoted into architects and managers in 10-20 years time? There just aren't enough senior jobs.

> The vast majority of devs are under 30.

How do you arrive at this conclusion? “Under 30” but old enough to have graduated college leaves only ~8 years of career. Unless you think the majority of devs are retiring before the age of 45-50, this doesn’t make sense at all.

I think you might be in a bubble with a lot of young devs, but it’s a big industry out there. Devs don’t just disappear or retire when we hit our 30s. They’re probably just at different companies.

Re: So You Want to be a Big Shot: Advice on playing the promotion game

#17

This advice is not wrong, but honestly it could be way more cynical. The first step to get promoted is to understand the promotion process of your current company, if they have a formal one. It took me one year to learn how promos work in my current company, and that was one whole year of progress lost. Then if you really want to get promoted fast, you need to optimize to meet the promo criteria. Often that is in lin…

> Then if you really want to get promoted fast, you need to optimize to meet the promo criteria.

This gets repeated all the time, but it’s easy to overdo it.

It’s true that you’re not going to get promoted if you don’t meet the promotion criteria, so you have to meet the criteria if you want to move up.

However, I’m seeing more and more juniors who think promotion criteria are some game they’re going to min-max, and that I have to promote them if they check certain boxes. They do weird things like ignore their assigned work and spend all their time working on a high-visibility side project, or ignore the way work is assigned and try to do only the things they see as promotion-worthy. Or other times they’re just difficult to work with, unliked by their peers, and avoided by people who don’t want to deal with their politics. Then they can’t understand why we didn’t promote them to team lead despite their work on that one high-profile thing earlier this year.

If you play it too much like a game, it’s obvious and starts to backfire. If you go fully cynical on the process, it’s almost guaranteed to backfire. I’ve seen some people included in layoffs mostly because their constant promotion-seeking competitiveness turned into pervasive toxicity and everyone was looking for the first opportunity to remove them.

Maybe at some companies the pure game theory mode works out, but you have to build relationships and be a good person to work with. At some point, the “game theory” approach just looks like “do a good job and make relationships in the process”.

Re: So You Want to be a Big Shot: Advice on playing the promotion game

#18
My last employer had a policy of rotating managers every few years. Each had a different set of priorities. Then there's politics. I accomplished a project to the great pleasure of my manager and VP. A year or so later along with rotations, we were all dumped.

Re: So You Want to be a Big Shot: Advice on playing the promotion game

#19
If the point is to get better at your craft, pursuing rapid promotion (especially into management) is antithetical to the goal. Craft comes from practice.

I’m sure there are all sorts of cynical strategies that are more effective for getting promoted, but if you love programming then putting the love into your programming will probably work out alright for you.

Re: So You Want to be a Big Shot: Advice on playing the promotion game

#20

This advice is not wrong, but honestly it could be way more cynical. The first step to get promoted is to understand the promotion process of your current company, if they have a formal one. It took me one year to learn how promos work in my current company, and that was one whole year of progress lost. Then if you really want to get promoted fast, you need to optimize to meet the promo criteria. Often that is in lin…

don't game the system, make the system
Post reply on HN