Ask HN: Bullied into managing (again), how to stay on the IC technical track?
I've always worked at growth stage startups since transitioning to tech about 10 years ago. I started as an IC and built the technical foundations and when a team was needed, I declined the offer to manage. Well, eventually they didn't succeed at hiring a manager and designated me. I grew to own a large team of teams and function. I decided I was right the first time and really dislike most aspects of being a manager, and I left that company/role with the goal to become an IC again. When I was hired at latest company, I was extremely clear that I was not interested in anything on the management track and was hired as a senior IC. A few months ago, the functional lead ( my manager) was fired and I was forced to take over despite my being abundantly clear I did not want to and it would make me unhappy. It was promised to be interim until they could hire. After 2 months, there isn't even an open rec.
This has happened more than once now. I've been very clear about the type of growth I want, and don't want to manage peoples work and growth and be the shit umbrella of organizational politics. It drains me, I like solving technical problems and systems. I enjoy that and I'm good at it. Just because I'm a decent manager too doesn't mean I want to do it.
Do I just threaten to quit if I'm continued to be forced to manage a team instead of the IC role I was hired for? How can I avoid being put in this situation again? I made it very clear I was not interested and wasn't really given any choice not to.
24 comments
[ 3.1 ms ] story [ 64.4 ms ] threadThe answer, as always, is to tell them what you want and walk if you care enough about getting it that you'd rather work elsewhere than stay without it.
The longer term solution to this problem may be technical consulting.
If you don’t like that, you can still resist and ask for “Senior” level responsibility but people will slowly lose respect for you as you get older. That’s how humans work: we want the older people to lead us with their experience.
Is that really true? I debated this quite a bit in choosing to go back to being an IC. I get the expectation of mentorship with seniority (and maybe life experience/age) but I don't see how that necessitates being a people manager versus a technical lead to do so. I think that I so often provide that in my IC role is why I'm an attractive candidate to be pushed into management though.
The worst part is in this industry even your junior peers will tend to not respect your experience/wisdom. They will view you as a grumpy grandpa who rants about the good old days. Let alone non-peers.
Whereas in many other industries it's not like this. A senior surgeon or pilot is always respected by their junior peers. They can brag about having done 10,000 successful flights or surgeries etc... but in our field there's no similar metric that is valued.
The exception is if you are a superhero god-level famous IC which most of us are not.
Sometimes you get amazing manahers who may not be as informed as you and you don't think to grow their career. Instead of focusing on your task, find out what will make their manager value them more and accomplish that first. You need to be them and your own role, but only to the point where you can supplant their limitations.
As an IC you have to understand the reason people move to management in many cases is they are at their limits in a technical capacity so help them grow instead of forcing them to fend.
I used to ignore monthly sla reports because who cares but my manager was let go because our slas failed. He didn't understand how standard deviations work so I could have saved the job of a person who understood how to allow me to focus on the most important tasks.
I don't think you need to threaten to quit, just remind them of the terms of your previous agreement. If that fails to get results, don't be afraid to take a two week vacation this July to remind them that you're not the long term manager of this team. It sounds like you may need a mental health break, anyway.
To prevent this from happening in the future, I'd suggest telling people that you'd be comfortable being the interim manager for, say, two months, and will also require semiweekly status updates about the progress on seeking a new manager. You may also wish to leave management experience off your resume.
A sufficiently senior IC should help interview and attract management talent into a company. You need to consider it part of your job to hire a manager to take the ICs who get assigned to you.
I get the sense you're grey haired, and people look at you as a management option based on age and experience. Again, treat it as a core responsibility to help hire managers.
I’ll admit though that I’m biased and my own team is currently looking for high-level ICs (senior and principal) who want to stay and grow in that role. If you (or any readers) are interested message tyler@recroom.com
I’m a high-level IC who used to manage a team of 12. Company was more than happy to let me do IC work, hired a manager of my choice to fill my previous role, _and_ promoted me with pay increase after the transition. I’d say my work is ~50% coding, ~25% architecture discussions, 12% mentoring, and 12% leadership meetings.
I made a post about this three years ago (https://news.ycombinator.com/item?id=20532057) and unless you're very extroverted it sucks all the joy out of the field.
> How can I avoid being put in this situation again? I made it very clear I was not interested and wasn't really given any choice not to.
Like some others have said protect your manager, but I'd qualify that by saying provided they earn that protection and trust. Also, build a relationship where the manager is effectively working for you and then (eventually) with you.
You also have to ask yourself what sort of manager the company or the team needs. A people manager who can build connections with others and trusts (relies completely) on the team to work out the engineering? Or a technically-savvy manager, who can guide and mentor on the basics?
Not the easiest topic and these are not mutually exclusive, but depth in one usually means sacrificing the other.
Note: I'm the latter type and it's unfortunately an inhibitor to my own growth. Schmoozing is not something I can get comfortable with and soires like large company gatherings I just shut down (too much sensory input). But I'm loving how my team is growing and provide input on best practices, some architectural decisions (eventually I'll have to give this up), and technical evaluations.
You could be a great manager.
I would look at how your 'brand' comes over and work on making sure people see the value you bring as an expert IC outweighs that of being a manager.
The more you increase your value as an IC the more costly it becomes to use you as a manager. Then you can look for a job that understands that.
I hope this helps