Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Ask HN: Getting back into an IC role as a manager

news.ycombinator.com

Post reply on HN
Print view View original

21–27 of 27 posts

Re: Ask HN: Getting back into an IC role as a manager

#21

Post by lightbendover »

zaphirplane wrote: post #16
bad_username wrote: post #3

You may consider switching to an architect track. An architect is still considered an IC in that one does not _manage_ people. But one still is a leader and a "multiplier" of value, because the designs enable multiple engineers to build large solutions. Architects solve technical problems, and often are expected to code the initial or the most important parts of their solutions. This role is sometimes called "staff e…

How does a Senior manager maintain the technical skills to be an architect. I guess companies come in all shapes

I managed to at a BigTech, it involved (1) a lot of hours, (2) seeing everything built from the ground up and thus knowing how it all fit together (the real short-cut way to appear 10x), and (3) remaining very hands-on with design at times, perhaps selfishly, to the chagrin of the engineers. Lost 90% of my ability/will to code, but my architecture ability remained exemplary compared to the IC engineers.

Re: Ask HN: Getting back into an IC role as a manager

#22

Post by gardenhedge »

bad_username wrote: post #3

You may consider switching to an architect track. An architect is still considered an IC in that one does not _manage_ people. But one still is a leader and a "multiplier" of value, because the designs enable multiple engineers to build large solutions. Architects solve technical problems, and often are expected to code the initial or the most important parts of their solutions. This role is sometimes called "staff e…

An architect position will have OP spending most of their time in meetings rather than coding. It is also a funny position because your manager can literally get you to do anything. It's not really a fully defined role.

Re: Ask HN: Getting back into an IC role as a manager

#23

Post by gardenhedge »

mbarr wrote: post #17
tiborsaas wrote: post #13

Earlier quoted context omitted.

What a confusing term for such a simple concept, I assume no engineer manages anybody unless they have lead or something similar in their title.

IC stands for Individual Contributor, i.e. non-management positions. It's pretty common in the industry.

I don't think it's used in Europe, is it?

Re: Ask HN: Getting back into an IC role as a manager

#24

Post by harshalizee »

bad_username wrote: post #3

You may consider switching to an architect track. An architect is still considered an IC in that one does not _manage_ people. But one still is a leader and a "multiplier" of value, because the designs enable multiple engineers to build large solutions. Architects solve technical problems, and often are expected to code the initial or the most important parts of their solutions. This role is sometimes called "staff e…

I'm not really sure. The really good principal engineers that I've worked with were incredibly technical and churned out a lot of code while also sitting thru a lot of meetings. I've never seen anyone in that role who came from being a manager

Re: Ask HN: Getting back into an IC role as a manager

#26

Post by tooltitude »

I did this from more or less managerial role to IC. It was hard initially, i.e. but I got used to it. The most helpful thing was that I continued coding in my free time, so there was some re-learning curve, but it wasn't too steep.

The key here is finding a company which values IC as much as manager which unfortunately isn't true for every company.

Re: Ask HN: Getting back into an IC role as a manager

#27

Post by tooltitude »

bad_username wrote: post #3

You may consider switching to an architect track. An architect is still considered an IC in that one does not _manage_ people. But one still is a leader and a "multiplier" of value, because the designs enable multiple engineers to build large solutions. Architects solve technical problems, and often are expected to code the initial or the most important parts of their solutions. This role is sometimes called "staff e…

Architect roles are great if they give you architectural problems to solve. It wouldn't be so great if it's just a manager without managers' power.
Post reply on HN