I'm at the crossroads. In my current role as software development manager, I wear different hats - sometimes I am project manager, sometimes Business Analyst, sometimes programmer, scrum master, product owner, or just a support guy.
What is the next role or progression after Software Development Manager role? How have you all progressed?
The way to progress as a manager is to develop the vision to grow the scope of your team, justify additional headcount, and groom some of your tech leads to become managers under you.<p>If done well, the optics are that you have a strong upwards trajectory as a leader and are well respected by your teams and executive leadership. From here, it's fairly easy to continue to move upwards toward an upper management role.<p>If done poorly, the optics are that you are an empire builder and not capable of actually moving the company forward, or supporting your people effectively. You will be not be respected and many people, including your own reports, will talk behind your back end eventually you will be pushed out.<p>Another path up requires a patron or sponsor. This might be your direct boss who moves up and takes you with them.<p>The last option is waiting for your boss to quit and be given the opportunity to take their job by your boss's boss. The best bosses will groom you for this.
The fact that you wear different hats suggests that you are more hands-on than the typical manager in a mid/large company. In order to progress you might need to show leadership, P&L accountability, business knowledge. Technical prowess is rarely the path to upper management levels.<p>If advancing your career is your ambition, then you might need to side-shuffle into a role where you do more management and direct others to perform the roles that you current perform from time to time.
I went back to IC at a bigger company, make more money, and spend a lot more time with my family. The perspective from being a manager helps me understand how to work with my management. I have turned down a couple of manager roles in my current company since then.
Depends on the org. At mine, you go from manager to sr. manager (maybe that means another team under your belt, but still keeping your total reports manageable). From there, the next level up is Director, then VP, then CTO.<p>I recommend The Manager's Path by Camille Fournier. It takes you all the way from individual contributor to CTO. <a href="https://www.amazon.com/Managers-Path-Leaders-Navigating-Growth/dp/1491973897" rel="nofollow">https://www.amazon.com/Managers-Path-Leaders-Navigating-Grow...</a>
I am adjusted my scope for only project management and its roles, kinda of like niching my responsibilities away from those other roles you have mentioned. It allowed me to enjoy my work a great deal more and I am learning as well.<p>I have found the book "The Manager's Path: A Guide for Tech Leaders Navigating Growth and Change" by Camille Fournier thought provoking for me.
VP Engineering / Head of Software is probably a good next step - some orgs have different paths but I would say seeing as you are focusing more on the actual engineering & product processes rather than tech strategy this is a senior management / exec role to move up to!