If you like the work you do and have no real wish to manage people, you’re in good company. A Visier survey of 1,000 US full-time employees found that only 38% of individual contributors said they were interested in becoming a people manager at their current organization. So wanting to grow without managing anyone isn’t a lack of ambition, and it isn’t unusual. It’s an ordinary position to hold.
The harder part is that many companies still pay as if management were the only real way up. Researchers at Northwestern’s Kellogg School worked from employee records at 43 firms. The data was assembled with Visier, the same company that ran that survey. The researchers found that individual contributors “earn less on average than managers do in every firm, at every level”. That doesn’t make the specialist path a dead end. But it does mean you can’t assume it works at your company just because it appears on the org chart. You have to check.
This guide walks you through how. We’ll start with what growth actually looks like when you aren’t adding people to a team, because it comes down to scope rather than titles. After that we’ll look at how to test whether your company’s specialist track is real or mostly decorative. We’ll also cover how to try managing people without staking your career on a guess. Finally, we’ll look at when taking the manager job or leaving is the better move.
What does career growth without becoming a manager actually mean?
An individual contributor (IC) is anyone whose job is doing the work rather than managing the people who do it. On the management track, growth is easy to see. You get a team, then a bigger team and then a team of managers. On the IC track nobody reports to you at any stage. What grows instead is your scope. That sounds like a vague word, but it describes something quite concrete.
Scope has four parts, and you can check each of them in your own job. The first is the size of the problem you own. Fixing a broken report is a small problem, but deciding how the company reports on revenue is a big one. The second is how much ambiguity you’re trusted to sort out on your own. Early in a career, someone tells you what to do and you do it well. Later you’re handed a messy situation, and you’re expected to work out what should be done about it without anyone telling you. The third is who’s affected by your decisions. A choice you make might change only your own work or your team’s, or it might change the work of people in three other departments. The fourth is time horizon. Are you responsible for this week’s output, this quarter’s results or what things look like two years from now?
Put those four together and the difference between levels gets much easier to see. A mid-level person gets a defined problem and a deadline. A senior person gets handed the question of what the problem is, and the people living with the answer sit in several teams. That’s real growth, even though the number of people reporting to you stays at zero.
Levels are scope, not titles
Job titles are a poor guide to level, because every company uses them differently. “Senior” at a 200-person software company and “Senior” at a bank describe different jobs. You might be comparing yourself with people at other companies or trying to picture your own next step. Scope is a much more reliable measure for both, because it describes what you’re actually responsible for rather than what your email signature says.
The table below shows what the shift from mid-level to senior can look like in six functions. It’s our illustration of the pattern rather than an industry standard or a research finding, so your company’s version will differ in the details. What matters is the change between the two columns. On the left, someone does a defined job well. On the right, someone owns the thing and makes the calls about it, including the uncomfortable ones.
| Function | Mid-level scope | Senior scope |
|---|---|---|
| Marketing | A lifecycle marketer builds and runs the campaigns in an agreed plan. | Owns the retention program, sets its targets, and decides which campaigns get cut when the numbers miss. |
| Finance | An analyst prepares the month-end schedules on time. | Owns the close process and signs off the policy behind it, including when the rules change. |
| HR | A specialist runs one onboarding or development cohort. | Designs the program that several business units run, and decides what it measures. |
| Sales | An account executive closes deals in a territory. | Owns the three largest accounts and decides the pricing exceptions on them. |
| Operations | A planner runs the schedule for one site. | Owns the planning process across two sites and changes it when it breaks. |
| Engineering | An engineer fixes and extends one service. | At staff level and above, sets the technical approach that several teams build against. |
Read across any row and you’ll notice that the senior column isn’t about doing more of the same work. It’s about making decisions. The senior person decides which campaigns to cut and when the rules change. They also decide what a program measures and which customers get a pricing exception. That’s why the right-hand column leans on strategic thinking and decision-making far more than the left does. If you’re trying to work out what’s standing between you and the next level, those two are a good place to look first.
Where IC career growth and the dual career ladder fit
You’ll often hear the IC track described as one half of a “dual career ladder”. The idea is simple. A company runs two parallel tracks: one for people who manage others and one for people who deepen their expertise. Senior roles on each are meant to carry comparable scope and pay. IC career growth is progress up the second track. The phrase to keep an eye on is “meant to”, because plenty of companies draw both ladders and only really fund one of them.
Engineering has done the most work on what the top of the IC track looks like, so it’s worth borrowing from even if you work in marketing or HR. AllVoices’ glossary entry on dual career ladders gives an example ladder. Its IC levels above Senior Engineer run Staff, Senior Staff and Principal. A Principal Engineer sits level with a Senior Director or VP. So on a well-built ladder, a very senior specialist can sit at the same level as an executive without managing anyone.
Will Larson documented staff-level roles at StaffEng. He describes being a staff engineer like this: “Being a Staff-engineer is not just a role.” He goes on to call it “the intersection of the role, your behaviors, your impact, and the organization’s recognition of all those things.” He sorts those roles into four archetypes: Tech Lead, Architect, Solver and Right Hand.
You don’t need the archetypes if you aren’t an engineer, but Larson’s definition carries over to any function. A senior finance analyst also has a role and a set of behaviors, plus an impact they can point to. They also need a company that recognizes all three. The first three are largely up to you. The last one is whether your company actually recognizes senior IC work. That’s the part you can test, and it’s what the next section is about.
Is your company’s IC ladder real? A test you can run this week
The quickest way to spot a ladder that only exists on paper is to look at pay, because that’s where the gap shows first. The Kellogg study put numbers on that gap: “at the bottom, individual contributors earn about 32 percent less than managers at the same level, while at the top, that penalty grows to about 63 percent.” The firms were medium-sized and large. They came from manufacturing, tech, finance and healthcare. So the higher individual contributors climbed, the further their pay fell behind managers at the same level.
Pay isn’t the only thing that can be lopsided, though. A senior IC can be paid fairly and still be left out of the rooms where decisions get made. AllVoices’ entry on dual career ladders turns the rest of it into a test: “If the L7 Principal Engineer has a smaller budget influence, less say in strategy, or lower visibility than the L7 Director, the track is nominal and ICs will still feel management is the real path.” A nominal track is one that exists in name only. The title is there, but the weight that should come with it isn’t. People notice, and the ambitious ones start drifting toward management because it looks like the only route that counts.
Five questions to ask before you plan around the track
Before you build the next few years around the IC track, it’s worth finding out how it works at your company in practice. The five questions below are a way to do that. You can answer most of them from what you already know, and the rest by asking one or two people. None of them requires you to announce that you’re unhappy. That matters because what you want at this stage is honest information. You don’t want a nervous conversation about whether you’re about to quit.
1. Who is at the most senior IC level in your function, and what do they own that a manager doesn’t?
This is the simplest check, and it often tells you the most. If the top of the IC track is real, someone should be standing on it. You should also be able to say what they’re responsible for. A good answer is a name and a specific thing like the pricing model, the close policy or the forecasting method. A bad answer is nobody, or someone whose title says senior while their week is a manager’s week without the reports.
That second kind of bad answer is easy to miss. Say your most senior analyst spends their days reviewing other people’s work and sitting on hiring panels. If they also field everyone’s problems, they’re doing a manager’s job without a manager’s title or pay. That’s also the job you’d be working toward.
If you don’t know who holds the role, ask your manager. It’s an ordinary question and nobody will read anything into it: “Who’s the most senior individual contributor in our function, and what are they responsible for?”
2. Does that person have the same budget influence, say in strategy and visibility as a manager at the same level?
This is the AllVoices parity test run on your own company. Once you’ve found your senior IC, compare them with a manager at the same level. You’re trying to find out whether being senior on the IC side buys you the same influence as being senior on the management side. If it doesn’t, the IC title works more like a consolation prize. That means choosing it would cost you influence you’d otherwise have.
The clearest place to look is planning. A good answer is that they sit in the planning meetings and their view changes the plan. A bad answer is that they’re consulted after the decision, or present to the executive team only when their manager is out. Being asked for your opinion once the plan is already set can look like influence from the outside. But it doesn’t change anything, and the person on the receiving end knows it.
3. What decision do they own outright?
Kris Drouet’s piece for KORE1 about the dual-ladder trap puts it as an instruction for engineering leaders: “Ask every staff engineer to name one decision they own outright.” It’s a sharp question because it’s very hard to fake. Plenty of senior people contribute to decisions. But far fewer get to make one and have it stick without someone above them signing it off.
Outside engineering the question is the same with the title changed. What does your most senior analyst or senior marketer decide without a director’s sign-off? A good answer names the decision. A bad answer starts with “they advise on.” Advice is useful, but it isn’t the same as deciding. If advice is all the senior IC level ever gets to give, the real decisions are still being made on the management side. So that’s where you’d have to go to make them.
4. Is pay band parity written down?
Most companies group salaries into bands, which are pay ranges attached to each level. What you want to know is where the senior IC band sits compared with the first management level. Ask HR or your manager which band the senior IC role sits in. The Kellogg figures are the reason to ask instead of assuming. If the gap showed up in every firm the researchers studied, it’s reasonable to check whether it shows up in yours.
Asking about pay can feel awkward, because it can sound like you’re weighing up another offer. It helps to frame the question as planning, which is what it is. Here’s a version that doesn’t sound like you’re halfway out the door: “I’m planning the next couple of years and I’d like to stay on the specialist side. Can you show me where the senior IC band sits against the first manager band?”
A good answer is a real answer, even an unwelcome one. If the senior IC band tops out below the manager band, at least you know where you stand and can plan around it. A bad answer is “it depends on the person,” with no range attached. That can mean nobody has decided, which usually means things carry on the way they always have.
5. How much of the promotion rubric is about managing people?
Most companies that have a ladder also have a rubric. That’s the written list of what someone has to show to be promoted to each level. Drouet again: “Read the staff rubric and highlight every line that describes managing people. More than a third highlighted means you wrote a management job description.” Run the same exercise on your own function’s next-level criteria. Lines about hiring all count, and so do lines about building the team or developing direct reports.
This matters because the rubric quietly decides who gets promoted. If a third or more of the lines light up, the IC promotion is a manager promotion with the reports taken out. You’d be judged on how well you manage people while having nobody to manage. That’s a very hard case to win.
These questions only gather facts. The conversation about your own case comes after them, once you know what you’re working with. That’s the one about what you want next and what you’re asking for.
One illustrative case
Esme is a composite we’ve built for illustration, not a real person. She’s a finance analyst at a 600-person company whose ladder lists Senior Analyst and then Senior Analyst II. On paper, that’s a clear next step. Her problem was that she’d never seen anyone take it. As she put it: “We have a Senior Analyst II title. I’ve just never met one.”
So she ran the five questions. She found one Senior Analyst II in the finance group. That person worked in treasury and owned the cash forecasting method outright. That was a good sign. It meant the level existed and came with real authority, so it passed questions one and three. The rest was less encouraging. The Senior Analyst II pay band overlapped the Manager band by about a third at its bottom end. So the senior IC level only reached into the lower part of the manager range. The Senior Analyst II rubric also had two lines about building and developing a team. That’s an odd thing to ask of someone who doesn’t have one.
The ladder was half real, then. Esme didn’t quit, and she didn’t go in with a complaint. Instead she took what she’d found to her manager. That’s exactly why you gather facts first: it’s much easier to discuss a rubric line than a feeling. Her manager agreed the rubric read like a manager’s and offered her written scope on one next-level project. The project was redesigning the month-end close across two legal entities, with Esme as the decision owner on the new timeline. She took it. The band question went to HR, who said the ladder was under review and wouldn’t change that cycle.
At her next review, Esme had the project on her record and the same band. Her rubric still asked her to build a team she doesn’t have. That’s a mixed result, and it’s worth being honest that it can go this way. The test didn’t fix her company’s ladder. What it did was turn a vague sense of being stuck into specific points she could raise. It also got her one piece of senior-level work she wouldn’t otherwise have had.
If there is no ladder at all
Plenty of mid-market companies have no written levels at all. If yours is one of them, the five questions won’t get you far because there’s nothing to test. So write the level yourself. That can feel presumptuous, but it’s often the most useful thing you can do. That’s because it gives your manager something concrete to react to instead of a general wish to “grow”.
One page is enough. Describe the next level in your role using the four dimensions from earlier: the size of the problem, the ambiguity you’d handle, who’d be affected by your decisions and the time horizon. Finish with one line naming who decides that the level exists. That last line matters more than it looks. “My manager” and “my manager’s manager plus finance” lead to very different conversations, so you want to know which one you’re in before you start.
Take the page to your manager and ask one question: does this describe a role the company would pay for? Keep the meeting to that. The evidence that you’re already working at that level belongs to a separate conversation. So does the date you want a decision by. That conversation is the promotion case laid out in Script 2 of our guide to asking for what you want at work. Keeping them apart helps, because your manager can agree the level is real without feeling they’ve already agreed to promote you into it.
A small company may simply not have a next level to promote you into. The page will often show you that in the first meeting, and that’s worth knowing too.
If you’re the manager or HR partner who maintains a ladder, the five questions above work as your audit as well. Run them on your own senior IC roles before the people in them do.
How do you grow your career without becoming a manager, day to day?
The ladder test tells you whether the track exists. Actually climbing it is a different job, and it draws on several things we’ve covered in more depth elsewhere. You probably need one of them more than the others right now, so start with whichever sounds most like your situation.
If you keep waiting for permission before acting like the senior person, start with the chapter on leading before you have the title. It covers why stepping up feels like overstepping and the six behaviors that change how people see you. It also shows how that reputation becomes a promotion argument. Those behaviors are the same ones a manager’s promotion case rests on, so the IC track and the management track share their first mile.
If your problem is one specific person who needs to say yes, read the guide to influence without authority. It maps what that person values and gives you scripts for the ask. It also covers what to do after a no.
If you’re ready to make the case for the next level or you’ve just heard “not yet,” read how to ask for the project or the promotion you want. It has the promotion script and what evidence to bring. It also shows how to get a decision date.
If your work is technical and more of it now runs through other people, read why strong technical leaders still lose their best engineers. It’s written mostly for people moving into tech lead roles. So read it as a preview of what the next step will ask of you: the five people skills that start to matter once your decisions shape other people’s work.
If you’ve already stalled, our guide to getting past a career plateau is a good general place to start.
Narrower questions get their own pieces. Some are about being seen: making your work visible, communicating your impact and internal networking. Others cover leading a project without authority and mentoring as a senior IC. There are also pieces on what to do when you’re passed over and on asking for a raise.
Can you try management without betting your career on it?
Sometimes the real question isn’t whether your ladder works. It’s whether you’d actually enjoy managing, and that’s hard to know until you’ve done some of it.
“Management is not a promotion, management is a change of profession.” Charity Majors wrote that in The Engineer/Manager Pendulum in 2017. She argued that engineers should be able to swing between the two jobs more than once in a career. She wrote it for engineers, but the idea holds for anyone who has been offered a team and isn’t sure they want it. If managing is a different profession rather than the next rung up, taking it on is closer to trying a new career than accepting a reward. That’s why it’s perfectly reasonable to want a way back.
Guessing wrong is common, and it isn’t only the people taking the job who get it wrong. Gallup puts a number on it in How Managers Impact Team Productivity: “Gallup estimates that organizations choose the wrong person for a manager role 82% of the time.” If companies misjudge it that often, you shouldn’t rely on anyone’s guess about you. That includes your own. A trial lets you find out where you stand before the choice is permanent.
A time-boxed trial for any function
What follows is our suggestion, not a research finding. The idea is to treat your first taste of management as an experiment with agreed terms. That way you haven’t burned anything, whatever you learn. Before you say yes to a lead role, write down four things and get your manager to agree to them in writing. An email counts. Writing it down matters because people change jobs and memories differ. “Let’s see how it goes” also has a way of quietly becoming permanent.
1. What you’ll lead
Keep it bounded, so it’s clear when the trial starts and when it ends. Acting team lead for one review cycle works, and so does a project with two or three people. Managing an intern or a contractor counts too, and so does running a vendor relationship. Each of these gives you real responsibility for other people’s work without handing you a permanent team.
2. How long
One to two review cycles. That’s long enough to sit through the hard conversations, like telling someone their work isn’t good enough. Those are the moments that tell you the most about whether you want this job. But it’s also short enough that going back doesn’t need explaining.
3. The return terms
Same title, same band and same manager if you go back. This is the easiest term to forget to ask for, but it’s the one that makes the trial safe. Stepping back can look like failing without it. Your old role may also have changed shape while you were away.
4. How you’ll judge it
Whether you were good at it matters less than whether you want more of it. Skill comes with practice, but wanting to spend your weeks on other people’s problems is much harder to manufacture. So after a few weeks of regular check-ins with the people reporting to you, ask yourself honestly whether you want more weeks like them. If the answer is no, you’re far from alone. A Robert Half survey of more than 1,000 US workers found that 59% said they “find more satisfaction in hands-on work than in managing others.”
The trial is also the cheapest honest read you’ll get on your leadership as a skill, separate from whether you like the job. You’ll see how you handle a difficult conversation or a missed deadline that isn’t yours. You’ll also see what you do when someone on your team disagrees with a decision.
If the answer is no, Majors already wrote the exit: “Then stop. Go back to building things. Wait til you get that itch again.” She was talking about code, but for a sales or HR IC building things means closing deals or designing programs. Going back isn’t a retreat. It’s the experiment giving you a clear answer.
What the trial can tell you, and what it can’t
A trial answers one question well: whether you want the daily work of managing. It can’t tell you whether the promotion path at your company is any good, because that’s what the ladder test is for. It’s worth running both, because they answer different questions. You could love managing at a company that underpays its managers. Or you could dislike it at a company whose IC track is excellent.
Here are two illustrative composites who ran trials and came out in different places. They aren’t real people.
Dominic is an account executive who ran a three-person sales pod for a quarter. The pod hit its number, so by the usual measure it went well. But when he looked back on the quarter, his verdict was short: “I missed the deals.” He’d spent three months helping other people close and realized he wanted to be the one closing. So he went back to enterprise accounts on the terms he’d agreed, and his manager hired the pod’s next lead from outside. Going back was straightforward because the return terms were settled before he started.
Lydia is an HR business partner. She led a cohort program for two cycles with two coordinators reporting to her. She’d assumed the program design would be the part she enjoyed. Instead she found she liked the conversations with her coordinators more than the program design, so she kept the role.
Neither Lydia’s case nor Dominic’s proves anything about anyone else. They’re here to show that a good trial isn’t necessarily one where you stay. Dominic’s trial did its job, because it gave him a clear answer and a clean way back.
When is moving into management the right call, and when is leaving?
Most of this guide is about growing without managing, but it would be dishonest to pretend that’s always the better choice. Sometimes the honest advice is to take the management job. There are three situations where it is.
The first is when your ladder fails the test and management is the only route to more scope and pay. Kellogg found that “in any given month, only about 0.5 percent of individual contributors switch to the managerial track,” and that those transitions “are linked to higher pay (about a 28 percent jump).” Very few people make the switch, but the ones who do tend to see a big jump. If your company’s IC track failed three of the five questions, staying an IC on principle means accepting the gap for as long as you stay. That can still be the right choice for you, as long as you make it knowing what it costs.
The second is when you notice that you want the conversations, not just the output. Some people go into a trial expecting to put up with the people side, but it turns out to be the part they look forward to. If the trial left you looking forward to the hour with someone who’s stuck more than to your own deliverables, that tells you something about the work you want. Take it seriously, even if you’ve always thought of yourself as a specialist.
The third is when the work you want to do needs headcount or budget you’ll never hold as an IC. Some problems need six people for a year. A senior IC can shape that work, but someone still has to own the people doing it. It may as well be the person who cares most about the result.
Leaving is the right call in a narrower case, when three things are all true. The ladder fails the test and you don’t want to manage. Your manager has also answered your one-page level document with “there’s nothing above this.” At that point you’ve checked the track, ruled out the alternative and asked directly for a next step. If none of that opened anything up, staying mostly means waiting.
If you do look elsewhere, take the test with you. Ask a recruiter or hiring manager the three questions that matter most. Who is at the senior IC level in this function? Where does that band sit against the first manager band? Who decides IC promotions? Their answers will tell you whether you’re moving to a real track or to the same problem at a different company. Norms on discussing pay bands vary by company and country, so use your judgment about how directly to ask the second one.
Don’t expect a new employer to change your mind about managing, though. The same Visier survey found that 36% of individual contributors were interested in managing at a different organization, against 38% at their current one. Two points is too small a gap to read much into. The share barely moves when the employer changes, which suggests that how people feel about managing tends to come with them. So if you’re leaving, leave for a better IC track rather than in the hope that management will feel different somewhere else.
People also move back. Majors’s pendulum swings both ways, and plenty of people return to IC work after years of managing. Taking a management job now doesn’t have to close the IC door for good.
The pay gap is the part this guide can’t fix. The evidence says individual contributors are paid less than managers in the firms the Kellogg team studied. But it doesn’t tell you whether your firm is one of them. If it is, choosing the IC track doesn’t close the gap.
Where do the skills behind this come from?
Every step in this guide runs on a short list of skills, and none of them is technical. Strategic thinking and decision-making are what separate the right-hand column of the scope table from the left. Collaboration is what lets your decisions land in teams you don’t run, and it matters more the further your scope reaches. Negotiation runs through the band question, the one-page level document and the trial terms. That’s because each of those is a conversation where you’re asking for something specific and need a clear answer. Influence and persuasion sit underneath most of it. If you’re building these as an individual contributor, Risely’s page for individual contributors shows what Risely offers on that path.
Merlin is Risely’s AI coach. It runs natively in Slack and Microsoft Teams, so the practice happens inside the tools your week already runs on. That makes it easy to use at the points in this guide that are hardest to do cold. You can rehearse the level-document conversation with your manager before you book it. You can talk through the trial terms before you say yes, including what you want in writing. After your first week leading a team, you can debrief what you liked and what you dreaded while it’s still fresh. Merlin only knows what you bring to it, not your company’s ladder. So bring your answers to the five questions with you. The average improvement on a target skill among people who coach with Merlin is 26% over 12 weeks.
Pick the question from the ladder test you’d least like to ask, and practice asking it with Merlin before you ask it for real.