←back to thread

20 points emthrowaway123 | 3 comments | | HN request time: 0.69s | source

How are you all thinking about your careers and making this move?

I'm going on 10 years of management with another 6-7 years of IC experience. I'm starting to see directors at big tech companies that are not only younger than me, but with far less management experience. Granted, I did get a few unlucky breaks - first startup got acquired and the parent company brought their own execs in, second startup promised me a director role but wasn't a good fit, and my current role is in a bigger tech org and they're not promoting from within and all recent hires are from the C-suite's previous company.

I could probably go to a smaller company and be a director, but that would be a step back in terms of scale and money.

A lot of companies aren't hiring in the US like they were, so growing organically seems like a poor strategy.

Is there a secret I'm missing?

Show context
nostrademons ◴[] No.43346888[source]
I don't really want to be a director. As an EM you're still somewhat involved in the technical details, your work is more deterministic, and your scope is small enough that you can act with integrity and don't need to make the hard ethical calls. But as my director put it, "the job is all of the responsibility and none of the power". And my former director (who made it up to SVP of a 12,000-person organization) said that "At that level, you are more like a portfolio manager than an engineering manager."

If your job is going to be a portfolio manager anyway, you're often better off being an actual portfolio manager. You make more money, pay lower taxes, and have more working flexibility. If you make most of your money from a W-2, even if you're the CEO, you've taken a bad deal. The real money is in ownership.

But that said, if you really want to be a director, here's some strategies I've observed for getting there.

1.) Scope and headcount. It's really all about headcount - that is the qualification for being a Director. Increased scope is how you get the headcount.

2.) Find out what upper management wants. Volunteer for it. That is how you get the scope.

3.) Attach strings to every request that your team takes on. "Well, we could be doing [important executive ask], but we don't have resources for it right now. If you gave us headcount for it, though, we'll make sure that it becomes our top priority." Attach a quid pro quo to everything. That is how you get the headcount.

4.) The same goes for requests from peer teams, but there needs to be some finesse here so you aren't labeled as difficult to work with. Oftentimes, it's best to dribble out easy requests as a teaser of good faith, but then say that for any larger projects, you need a line item in their budget that donates headcount to your team.

5.) Ruthlessly inflate the difficulty of everything you do. "Oh, why did it take 2 months to move a button around on the screen? We needed to get alignment from product and UX, then we needed to check with 2 other teams, then we needed to make sure that it works on all the platforms we support, we needed to make sure it didn't adversely impact the click-streams to advertisements on the page, ..." (Note that in some companies, it really does take 2 months to move a button around on the screen. If you work in one of those companies, message it as taking 6 months.). This is also your way to provide work/life balance to the people underneath you. If they want to work 4 hour days, this is good for you, because it means you need twice as much headcount to accomplish the same task.

6.) Deliver on your commitments, but only to the extent that it looks good in a demo or PowerPoint. VPs aren't up-to-speed on the details; that's why they are VPs, and have hundreds of people under them to worry about the details.

7.) If you do get called out on the details, offer some excuse and then request headcount to fix it.

8.) If your department is about to implode, immediately start talking to executive recruiters so you can get a director title elsewhere.

9.) Actually just start talking to executive recruiters anyway. It usually takes something like 18-24 months to get a director role externally, so if one happens to land in your lap, take it.

replies(2): >>43347159 #>>43348647 #
1. aprdm ◴[] No.43347159[source]
> 1.) Scope and headcount. It's really all about headcount - that is the qualification for being a Director. Increased scope is how you get the headcount.

Scope != headcount, in matrix orgs (like big tech) there are directors with very small orgs (5-10 people)

replies(1): >>43348492 #
2. nostrademons ◴[] No.43348492[source]
But you typically don't get to be a director with an org of 5-10 people, at least not in engineering, which OP indicated he's in. (It's different in other functions. PM/UX directors frequently have 10-15 people under them, and my wife is a deputy director in finance and has 2 reports. Her boss is the director and has 3 indirects, just her and her reports. I joke that their management chain really is a chain. Startups are also different - I once interviewed for a VP role at a startup that had 8 employees.)

For that promotion to director, you usually need at least 50 reports and at least 2 levels of management. And then the span of responsibility for (senior) director goes on up to about 500 reports. It's not unusual to have directors with less than that - but usually that is because they once had a big org, their scope and responsibility decreased in some re-org, but upper management is keeping them around so they have a deep leadership bench. Another re-org and they can easily end up with 500+ people again.

replies(1): >>43348850 #
3. aprdm ◴[] No.43348850[source]
Well I got to director in big tech with an org about 35 people and now I have around 15 people but bigger scope, and others have done with similar numbers too. Depends on the culture I guess, some cultures are all about empire building, others about impact / scope