Haven't taken any vacations of more than 5 days since 2011.
Constantly worry about my technical skills becoming obsolete - hence I have to do coding on the side.
Constantly worry about whether my managers will practice what I preach (kindness, coaching, caring, etc.) with their team.
Constantly worry about multiple deadlines for multiple projects, all under my responsibility but not direct control (I'm not a direct manager).
Hire 10-15 people at a time, campaign for some of them, they disappoint, become a burden for others and risk destroying the team - have to worry about that as well.
Get an e-mail at 10pm on a Friday that your best developer has been hired by Google at 2x the pay and there's nothing I can do about it. Another e-mail at Monday 11am saying that your worst developer has ALSO been hired by Google at 2x the pay. Spend 24/7/365 on how to prevent your entire team from jumping ship because of pay I cannot match.
Worry about managing up, sideways, down, and in the fourth dimension as well.
Kill to just be a developer, step back into IC role. Do well, less stress, gets asked to become a manager again because the previous 3 have been a disaster and the team elected you.
Go back to #1, rinse, repeat.
you should only touch your own buttons, not others', and whats outside of that is not your (id like to say problem, but thats not correct) fault.
It’s interesting though. I do put in fewer hours as a manager. At the same time as I’ve progressed up the management ladder my anxiety levels have followed. Quality of life has suffered. I’ve learned to live with near constant stress headaches, frequent jaw pain, and a host of other issues.
If you are a good manager now, you will let it transpire in your IC work and you will eventually be asked to step back into a manager role, because the team asked so.
Disclaimer: I’m about to say stuff that are just my impressions, without a lot of “I think” or “I believe.” Take those as implied.
Generally the stress of management is in coordinating various personalities and balancing competing priorities, while being on the hook for delivering results without having any direct impact on whether a project gets done to a high degree of quality. They rely on others’ expertise, some of whine may not be that reliable, and it’s stressful!
Directors and VPs have that stress plus they are more directly accountable to financial results. However, they have to be cheerful and optimistic and never show weakness or worry to an almost psychopathic degree. This may look like a good work/life balance externally but internally “work brain” and the weight of stress are relentless. The bad ones sublimate stress and occasionally explode and yell at their subordinates.
To engineers none of this looks like “work” because none of it produces concrete results. (I haven’t mentioned the endless word docs to read and write, and the spreadsheets, oh god the endless spreadsheets.) But it does accumulate a lot of stress and anxiety.
On the vacation side of things, seriously, take a vacation! It will be okay!
I have had to say in a meeting. Stop engineering the product and have the engineers handle the development life cycle.
Regardless, life won’t change just because the duties do. You have to make time off happen. The market is so starved for talent you can go somewhere else over night.
Director level is probably the worst - all of the grind but none of the glory.
VP at least you have some power and a lot more money, it 'feels' like something.
I think companies should pay technical people the same as managers up to at least director and there should be at least some parrallel technical tracks right up to the top i.e. Directors have Architects, VP's have Systems/Strategy Architects etc..
People on my team are actively encouraged to use their PTO on an on-going basis.