4 ms·
i agree with your point and it is why I have resisted becoming a manager at my current role at a FAANG. I was previously a manager for my team at my previous c
by dagmx 5y ago
i agree with your point and it is why I have resisted becoming a manager at my current role at a FAANG.
I was previously a manager for my team at my previous company. However I got to both manage, and continue developing.
After switching companies, I've been offered management positions multiple times. However the reality is that at a FAANG, you rarely see managers who get time on the box anymore.
I know a lot of managers who are happy to not split the time between management and dev work, and power to them. However I don't want to risk the atrophy of skills.
When I interviewed here, the biggest concern most people had in my interview panel was "you've been managing. Can you still dev in a non management role?"
Frankly that's how a lot of the industry is. Managers don't get the time to dev. Many like that aspect, but if you're planning to leave, well good luck because you won't be able to hold your own against the people you managed when vying for a non managerial role.
I've seen decided my best path is to be an individual contributor who has more weight. Effectively a lead (currently) or principal dev. It's the closest I can get to both ends of the spectrum.
- blub 5y agoManagement is a different career path though and coding is not one of the skills they require even for software management jobs. The problem is really more applicable to senior technical roles like tech leads, architects, where it is actually reasonable to expect them to be able to code.
- dagmx 5y agoThe problem is that it's not really treated as a different career path by many people. Lots of people leave management roles and try and apply for IC roles at other companies. It's also really difficult to go from management at one company to management at another for many people.