11–20 of 27 posts
I don't understand the IC role at all. How one transition to that after being a member of a very specific team? Does that mean they are like a bee flying from one flower to the next?
IC means that you are not managing anybody. So basically every developer who doesn’t have any reports is IC.
Upon reflection, if you really miss coding I'd recommend finding something part-time or a Solutions Engineer role.
I don't understand the IC role at all. How one transition to that after being a member of a very specific team? Does that mean they are like a bee flying from one flower to the next?
IC means that you are not managing anybody. So basically every developer who doesn’t have any reports is IC.
The engineer-manager pendulum: https://charity.wtf/2017/05/11/the-engineer-manager-pendulum...
Questionable advice - is there a path back from CTO to engineer? https://charity.wtf/2022/07/29/questionable-advice-is-there-...
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…
Earlier quoted context omitted.
IC means that you are not managing anybody. So basically every developer who doesn’t have any reports is IC.
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.
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.
Would I do it again, no unless it was within my current company. Jumping to another company after not being hands on for a few years was very difficult. Especially when it came to the system design questions.
Edit: Now that I've made the transition, its great. It was a slow start with the coding aspects. The management background helps a lot for interactions with my peers and junior developers. My peers already think I should be at least the next level in the IC track, but that is probably because I take on responsibilities outside my immediate area.
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…