I think when you are a junior IC, you can easily see things in black and white. You can get worked up over perceived issues, judging too quickly, and can easily see things from an us vs them perspective. You need to be able to gain the full perspective on an issue. The saying "be curious not judgmental" is very front and center to engineering leadership.
So for example, when a coworker rants to you, don't amplify their rant. Try to de-amplify it. Ask questions, be curious about the other side, try to listen and validate, but don't take too much stock in their rant. This keeps you in a more objective, thoughtful problem-solving mindset, rather than the reptilian brain that responds with a 'fight or flight' fashion.
This is important for moving up in the leadership ladder because
(a) Emotional immaturity will stress out your superiors. You're seen as someone that needs to be 'managed' not someone productively getting your work done
(b) It helps you better see a solution to a problem in a more objective way, not a punitive way
(c) It creates blame-free leadership, where you focus on the dynamics between people and systems, not how one person screws up
When you can gather these facts and think about issues objectively, then you can create more informed opinions about the direction the team(s) should take, lead more effectively, and include everyones input getting much more buy-in.
@drdunce, it really does depend where you are starting from. Regardless, start hustling your network and build up an incredible profile. A PhD + MBA might be useful but most certainly not sufficient.
Alternatively, you could join a large tech company and try to grind your way up the ladder. That will depend a lot on your ability to navigate complicated politics and deliver on impactful projects.
2. Understand that responsibility and authority are inseparable. Be prepared to take fullest possible responsibility of results (good/bad/ugly) in exchange for true authority both formal and more importantly, informal.
3. Have a decent (B or better) set of relevant technical skills and then, consider it malpractice to further develop those skills on your team. You're now a developer of them.
4. Forget about your career, rather for your team members, figure out how you will AMP their careers - more Autonomy, more Mastery of their craft, and more Purpose (AMP).
5. Work on your RELATIONSHIP/LEADERSHIP skills by determining honestly what type of leader you are and will become. Hint, servant leaders, when necessary, will make severe personal sacrifices for their team members, not throw them under the bus to those higher up. They will love you for it.
6. Work on your communication skills / Lead some project meetings whether internal or external and involve everyone you can, while showcasing their contributions.
7. Develop a behavioral Code of Honor with Values congruent with those of the organization at large that you, first, and everyone on your team will subscribe to, and expect from each other. This is about Trust, particularly when the kitchen gets hot - and yes, the kitchen will get hot.
8. Without pissing off your current boss, craft an approach to get to someone who has the authority to make such a call and then, ASK....ASK. "if at some point, I was a developer and steward of a team with these attributes - A, B, C to this organization, what would we ideally help you accomplish over the next 18 months, and how would you know it was successful?
9. Oh and generally (not cause I know you) reduce the use of the word "I, Me, My" by like 80%.
There seems to be no causality (let alone stable correlation) between you getting this position and your education, years of experience etc etc.
I guess the best bet as with startups would be to just maximize your chances by getting on board of anything you expect to rapidly grow soon (and you feel you’d be able to handle the growth).
Be it a startup or a department in a big company where you feel you can make it.
Director has got to be able to step back from that. Understand and identify when the issue isn’t in engineering. Understand how to effectively collaborate and innovate with groups that are on much different cadences and timelines than we’re used to. I think https://www.reforge.com/blog/overcome-the-tech-strategy-spir... has a lot of very relevant thoughts. (Disclaimer: I have been the EIR for the course related to this post).
For an existing/established large tech company - I'd imagine STEM PhD + MBA, 10 years experience in a senior management role.