> Individual contributor sounds like a human resources rebrand for lower pay or power.

I’ve been in companies using this term for the last decade and definitely do not think this is the case. If anything it’s a movement to empower people that don’t want to be on a manager track by offering them a precise term to describe their track.

It simply means people with no direct reports.

I’ve understood IC to mean individual contributor for over a decade. I think the industry just over uses acronyms and as a result you end up with collisions.

IC to me means a developer who has no interest in managing people.

Depending on the place, it can mean different things. I've seen it also mean "team member" or used for senior engineers whose roles (navigating across different teams on short/mid-term important/investigation/transformation projects not necessarily visible on the official R&D roadmap) makes it difficult to attach them to a particular team/specific role.

The people and places that handled well this level of fuzziness do so _thanks to_ a good amount of trust, care and shared vision.

It means someone who is not a people-manager. That is, someone who _contributes_ to the team/company by actually doing things, rather than by supporting/directing the work of others.

Trying to think of other words for this... programmer, software developer, software engineer. But those words are all role-specific. IC has the advantage of conveying that the person is not managing, but is generic with regards to role. Non-manager works, but that emphasizes the negative.

Hmm.....

An IC is a role without positional authority but the company will indoctrinate you with “lead by influence” internal training courses and tell you that you can effect change purely by your charm and will question why you can’t get that person or department to solve their bugs. It’s all part of the we-are-a-flat-hierarchy mantra and you know we are all equal (in skill, drive and initiative).

At my last job my team were at one time referred to as "onshore resources" despite all being employees and in the same office.

Principal engineer roles are pretty desirable. I know a number of managers of engineers who wish they had gone a PE route rather than a management one.

I know very few PEs who say "Oh, I wish I had a whole team to manage, worry about hiring/retention, reviews, administration, etc"

How about a label given to a track that runs parallel to manager?