TemplatesTemplate · People & Careers
Support career ladder (IC + lead tracks)
A two-track support career ladder — individual contributor and lead/management — that spells out scope, expected skills, autonomy, and example responsibilities at every level, so reps and managers can agree on where someone stands and what closes the gap to the next level.
Copy it, rename the levels to match your org and pay bands, set your real targets, then use the per-level tables and readiness checklists to run promotion and calibration conversations.
A starting framework, not a mandate. Copy it, delete what doesn't fit, and rename the levels to match your org and pay bands. The point is to make "what good looks like at each level" explicit enough that a rep and their manager can agree on where they stand today and what actually closes the gap to the next level.
Two tracks share the first two levels, then fork:
- an individual-contributor (IC) track for people who grow by getting deeper and higher-leverage without managing anyone, and
- a Lead / Management track for people who grow by developing others and owning a team's outcomes.
Neither track is "up." They are two directions. Pay bands should overlap so nobody has to become a manager just to earn more.
How to read each level
Every level is described on four axes:
- Scope — the size and blast radius of what this person is trusted with.
- Expected skills — what they can reliably do, not just what they've been trained on.
- Autonomy — how much runs without a manager in the loop.
- Example responsibilities — concrete, recurring things they own. These are examples; swap in your own.
Levels are cumulative: L2 does everything L1 does, plus more. Titles are placeholders.
Leveling map
| Band | IC track | Lead / Management track |
|---|---|---|
| Entry | L1 · Support Rep | — |
| Established | L2 · Senior Support Rep | — |
| Fork point | L3 · Staff / Specialist | M1 · Team Lead |
| Senior | L4 · Principal (optional — define when you have the person) | M2 · Support Manager |
| Org | — | M3 · Senior Manager / Head of Support |
A move across tracks (Senior Rep to Team Lead, say) is a change of job, not just a promotion — expect a ramp, not instant fluency.
IC track
At a glance
| L1 · Support Rep | L2 · Senior Support Rep | L3 · Staff / Specialist | |
|---|---|---|---|
| Scope | One queue or channel | Complex and escalated cases across queues | A whole domain across the team |
| Autonomy | Works from playbooks; escalates the unclear | Resolves most cases alone; decides when to escalate | Sets the playbooks others follow |
| Leverage | Owns their tickets | Owns their tickets, unblocks peers | Fixes root causes so the tickets stop |
| Impact horizon | This shift | This week / sprint | This quarter and beyond |
L1 · Support Rep
| Axis | What it looks like at L1 |
|---|---|
| Scope | A single defined queue or channel (e.g. Tier-1 email or chat). Handles volume within team SLA. Owns their own tickets end to end but hands off anything outside the playbook. |
| Expected skills | Product fundamentals for the top ~80% of contact reasons; can follow a troubleshooting flow; writes clear, correct, on-brand replies; uses the helpdesk, KB, and macros correctly; reads customer sentiment and de-escalates basic frustration. |
| Autonomy | Works from documented playbooks and macros. Escalates anything ambiguous, risky, or outside policy. A lead reviews edge cases. Expected to ask rather than guess. |
| Example responsibilities | Resolve assigned tickets within SLA; keep CSAT and QA at or above team target; flag broken or missing KB articles; log recurring issues so trends stay visible; finish onboarding and product certifications. |
Signals of readiness for L2
- Consistently meets QA and CSAT targets for 2+ full quarters
- Handles the full L1 contact-reason range without routine escalation
- Peers ask them for help, and the answers hold up
- Has resolved genuinely hard cases without a lead driving
- Suggested or wrote KB / macro improvements that shipped
L2 · Senior Support Rep
| Axis | What it looks like at L2 |
|---|---|
| Scope | Complex, escalated, and cross-queue cases. May own a specialized queue (billing disputes, security, a specific product line). The person a case gets handed to when Tier-1 is stuck. |
| Expected skills | Deep product knowledge including edge cases; debugs from ambiguous symptoms; handles angry, VIP, or legal-adjacent replies without a manager; comfortable in logs, admin tools, and APIs as relevant; coaches by example. |
| Autonomy | Resolves the large majority of cases independently and decides when something truly needs escalating. Trusted to make judgment calls on goodwill credits, exceptions, and edge policy within stated limits. |
| Example responsibilities | Own the escalation / complex queue; act as point of contact for a product area; mentor 1-2 newer reps; run or contribute to QA calibration; author KB articles and macros; represent support in bug triage with engineering and product. |
At L2, the two tracks fork. Read both lists honestly — the goal is the right direction, not the "higher" one.
Toward L3 (Staff / Specialist)
- Recognized as the go-to expert in at least one domain
- Has driven a systemic fix (KB overhaul, macro redesign, process change) that measurably cut volume or handle time
- Influences how the team works without positional authority
- Energized by hard problems and depth, not by managing people
Toward M1 (Team Lead)
- People come to them for help and take the coaching well
- Steady under pressure; already thinks about team outcomes, not just their own numbers
- Wants to develop people and will trade hands-on work to do it
- Has covered for a lead (queue triage, standup, escalations) and it went fine
L3 · Staff / Specialist
| Axis | What it looks like at L3 |
|---|---|
| Scope | A whole domain across the team — a product area, a channel, a system (e.g. the API / technical queue), or a discipline (QA, KB, tooling). Impact is measured in problems that stop happening, not tickets closed. |
| Expected skills | Authoritative depth in their domain; designs the troubleshooting flows and playbooks others rely on; strong written communication for internal docs and cross-team proposals; data-literate enough to quantify a problem and its fix; influences the engineering / product roadmap with evidence. |
| Autonomy | Fully self-directed on ambiguous, open-ended problems. Sets the standards and playbooks the team follows in their domain. A manager sets direction and priorities, not method. |
| Example responsibilities | Own a knowledge or technical domain end to end; find and drive root-cause fixes with engineering and product; design QA rubrics or KB architecture; onboard and level up L2s in their specialty; run deep-dives on cost, quality, or volume drivers; represent support in cross-functional planning. |
A Principal / L4 tier can sit above this for the rare person operating org-wide. Define it when you actually have that person, not before.
Lead / Management track
People leadership is a different job, not a reward for being a great rep. Success is measured by the team's outcomes and the growth of its people. Great ICs do not automatically make great leads — protect them from being promoted into a role they'll resent.
At a glance
| M1 · Team Lead | M2 · Support Manager | M3 · Senior Manager / Head of Support | |
|---|---|---|---|
| Manages | 5-10 reps | Leads plus a function (~15-40) | Managers and the whole support org |
| Owns | Day-to-day delivery of one team | Performance, hiring, and roadmap for a function | Strategy, budget, and outcomes for support overall |
| Autonomy | Runs the team inside set goals | Sets team goals from org goals | Sets the org's goals and operating model |
| Time horizon | This week | This quarter | This year and beyond |
M1 · Team Lead
| Axis | What it looks like at M1 |
|---|---|
| Scope | First-line people leadership of ~5-10 reps. Owns the day-to-day: queue health, coverage, coaching, and QA for their team. Usually still handles some tickets and escalations. |
| Expected skills | Coaching and feedback, including hard conversations; QA calibration; reading a real-time queue and reallocating; running a useful 1:1 and standup; basic performance management; staying calm and setting the tone in a crunch. |
| Autonomy | Runs the team against goals set above them. Makes coverage and coaching calls independently. Escalates hiring decisions, formal performance actions (PIPs), and policy changes. |
| Example responsibilities | Weekly 1:1s and coaching; own team QA / CSAT / SLA; manage the schedule and the real-time queue; onboard new reps; run calibration; first approver for exceptions and goodwill above rep limits; surface staffing and morale issues early. |
Signals of readiness for M2
- Team consistently hits its targets and keeps its people
- Has hired, onboarded, and managed out reps
- Trusted with sensitive people situations without close oversight
- Thinks a quarter ahead, not just about this week's queue
- Can turn an org goal into a team plan
M2 · Support Manager
| Axis | What it looks like at M2 |
|---|---|
| Scope | Owns a function or a team-of-teams (usually through Team Leads) — roughly 15-40 people. Accountable for the performance, staffing, and continuous improvement of that area. |
| Expected skills | Managing managers and leads; workforce planning and forecasting; owning a set of metrics and reporting them upward; cross-functional partnership with product, eng, sales, and finance; hiring at scale; budget awareness; change management. |
| Autonomy | Sets team goals from org strategy and decides how to hit them. Owns hiring plans, tooling choices, and process for their function within budget. Escalates budget / headcount changes and org-level strategy. |
| Example responsibilities | Own function-level CSAT / SLA / cost and the headcount plan; develop and hold Team Leads accountable; run the hiring pipeline; own the QA program and coaching system; partner with product and eng on systemic issues; report to leadership; manage the tooling and vendor stack for their area. |
Signals of readiness for M3
- Function runs well without them in the room day-to-day
- Has grown leads into stronger managers
- Sets strategy, not just executes it; influences peers across the company
- Comfortable owning a budget and defending it
- Represents support credibly to executives
M3 · Senior Manager / Head of Support
| Axis | What it looks like at M3 |
|---|---|
| Scope | The whole support org, or a major region or segment of it. Owns the operating model, budget, headcount, tooling strategy, and how support shows up to the rest of the company. |
| Expected skills | Org design; multi-quarter planning and budgeting; executive communication and influence; vendor and tooling strategy; connecting support data to company outcomes (retention, cost-to-serve, product quality); building and keeping a leadership bench. |
| Autonomy | Sets the org's goals, structure, and operating model within company strategy and budget. The escalation point of last resort. Accountable to executive leadership for support's outcomes. |
| Example responsibilities | Own support strategy, budget, and org structure; set the metric targets and operating cadence; build the leadership team; own major tooling, vendor, and build-vs-buy decisions; carry the voice of the customer to the exec team; tie support outcomes to company goals. |
Compensation and fairness notes
- Keep the tracks paid in parallel. An L3 IC should be able to out-earn an M1, and often an M2. If the only way up is management, your best ICs either leave or become reluctant managers.
- Level the person, not the title. Someone can carry a "Senior" title while doing L2 work, or the reverse. Calibrate against the axes, not the business card.
- Write down the boundary between levels, especially where "meets" becomes "exceeds." Ambiguity there is where bias and favoritism creep in.
- Promotion is a lagging indicator. People should already be operating at the next level for a sustained stretch before the title and pay catch up — but set a cap on how long that stretch runs, or it turns into unpaid work at the higher level.
Running a calibration
Work through this per person before the promotion conversation:
- Which level best describes their sustained work over the last two quarters — not their best week?
- Do concrete examples back each axis: Scope, Skills, Autonomy, Responsibilities?
- Are they already doing next-level work, or is this a bet on potential? (Both are valid — just name which.)
- Would peers already at the target level agree they belong there?
- Is the gap to the next level written down, with owners and a rough timeline?
- Does pay match the level they're actually operating at?
Adapt before you adopt
This is a starting framework. Before you roll it out:
- Rename the levels and titles to match your org and pay bands
- Delete tracks or levels you don't need (small teams often stop at L2 + M1)
- Swap the example responsibilities for ones from your actual stack and policies
- Set the real numeric targets (QA %, CSAT, SLA) that define "meets" at each level
- Decide who owns leveling decisions and how often calibration runs
- Share it with the team — a ladder people can't see isn't a ladder
Continue exploring