English

Path From SE to Senior SE and SE Manager

It's year two. Your win rate is good, your demos are tight, AEs request you by name on the harder deals, and your skip-level just asked, "So what's next for you?"

You freeze.

Stay IC and get bored? Go strategic on the named accounts? Take the manager rec your boss keeps hinting at? Or pivot to Product like that teammate did six months ago who now seems weirdly happy?

Four paths. All valid. Almost no honest content about how to choose. Most of what's out there assumes the answer is "manager" because that's what's visible on the org chart.

Here's what nobody says out loud: SE careers are non-linear by design. The role sits between sales, engineering, and product, which means there are exits in three directions plus the IC ladder. Defaulting to "manager because that's what's next" is how good SEs become mediocre managers. The real question isn't "what's the promotion?" It's "where does my edge compound?"

This guide gives you the inventory before the title. Most SEs pick the title and reverse-engineer the skills. That's how careers stall.

The Four Paths, Honestly Described

Most SEs only see two (IC or manager) because that's what their company shows them. Here are all four.

Path 1: Senior SE (enterprise complexity)

You stay IC, but the deals get harder. Six-figure ACVs, sometimes seven. Security questionnaires that read like compliance audits. Twelve-person evaluation committees. You become the SE the team brings in when a deal is shaky.

What it requires: pattern recognition across 100+ deals, calm under exec scrutiny, comfort with ambiguity. You don't get rattled when the CISO loops in late and asks why your encryption story differs from the website. You've seen that movie.

What it doesn't require: managing people. Coaching juniors informally, sure. Owning performance reviews and PIPs, no. This is a real summit, not a holding pattern. Strong technical discovery skills compound the longer you stay here.

Path 2: Strategic SE (named accounts)

You move to 3-5 named logos and play a multi-year land-and-expand game. You become a quasi-account-team-lead, working with one or two AEs on accounts where the deal cycle is 9-18 months. You stop thinking in quarters and start thinking in renewals.

What it requires: relationship stamina, business acumen well beyond product knowledge, willingness to play long games. You need to enjoy reading 10-Ks and listening to customer earnings calls.

What it doesn't require: managing a team. But it does require influence without authority, since you'll coordinate CSMs, support, PMs, and AEs without owning any of them.

Path 3: SE Manager (people)

You stop carrying a quota. You start carrying a team. Your day fills with hiring loops, ride-along feedback, headcount planning, and admin work nobody warned you about. Your wins are your team's wins now, which is a different chemistry, and not everyone likes it.

What it requires: real interest in other people's growth, tolerance for admin, willingness to give up the demo high. The SEs I see thrive on this path share three traits: they get more energy from a teammate's win than their own, they're calm when someone disappoints them, and they treat "I made a hard call about a person" as a craft worth getting good at.

This is not a default. It's a calling. If you're not sure whether you want it, you almost certainly don't. The good SE managers I know either knew at month 18, or had a manager who pulled them aside with reasons that weren't "you've been here a while."

Path 4: Product pivot (PMM or PM)

You move into Product Marketing (owning technical positioning, sales enablement, competitive intel) or Product Management, working on roadmap with engineering. The SEs who do this often describe the first six months as "I forgot how much I missed building things."

What it requires: writing skills (product work is mostly writing), comfort with longer feedback loops, and willingness to take a perceived "lateral" that's often a vertical in disguise.

Why this path is underused: it feels like leaving. It isn't. Internal pivots into PMM and PM are common and usually well-received because the SE-to-Product path is one of the highest-signal hires Product orgs can make. You already know the customer, the product, and the competition. They just have to teach you the rituals.

The Four-Path Self-Assessment

Score yourself honestly. The point isn't to validate the path you already picked. It's to surface the one that fits the skills you have and enjoy using.

Rate each statement 1-5 (1 = strongly disagree, 5 = strongly agree).

Section A. IC Deep (Senior SE signal)

  1. I get more satisfaction from solving a hard technical problem than from any other part of my job.
  2. I'd rather work the toughest deal on the team than coach three teammates through medium ones.
  3. I'm energized by security reviews and compliance questionnaires, not drained by them.
  4. When a deal goes sideways, my first instinct is to go deeper on the technical truth, not to manage the room.

Section B. IC Strategic (Strategic SE signal)

  1. I'd rather own 4 logos for 3 years than 40 deals for 1 year.
  2. I read my customers' earnings calls or annual reports without being asked.
  3. I'm comfortable with wins that take 18 months to materialize.
  4. I enjoy coordinating across teams more than I enjoy executing alone.

Section C. People (SE Manager signal)

  1. A teammate's win genuinely makes my week better, sometimes more than my own.
  2. I'd happily trade demo prep time for 1:1 prep time.
  3. I'm willing to have a hard conversation about someone's performance even when I like them personally.
  4. I'm interested in hiring as a craft, not just as a thing I have to do.

Section D. Product (PMM/PM signal)

  1. I'd rather write a 5-page positioning doc than build a 30-slide pitch deck.
  2. I notice patterns across deals and want to fix them at the product level, not just route around them.
  3. I'm okay with feedback loops that take quarters instead of weeks.
  4. I'd take a "lateral" move if it put me closer to building the thing.

Scoring

Add each section. Your highest section is your strongest signal. If two sections are within 2 points, you have a real choice, not a default. If your highest section is below 14, you're not ready to pick yet. Run two more deals and re-score in three months.

Honest patterns I see:

  • High A + low C: stay IC. The people-leadership tax will erode you.
  • High B + high C: you'll likely end up an SE leader on a strategic accounts team. Real role, just under-named.
  • High D + low everything: leave SE for Product faster than you think. You're miscast.
  • All within 2 points: no clear edge yet. Run more deals before picking.

Conversation Scripts

Career conversations stall because most SEs don't know what to say. Four scripts for the four moments that matter.

Script 1: Your manager asks "what's next for you?"

If you're not sure yet:

"Honest answer: I'm not ready to lock in a direction yet. I want to spend the next 90 days being deliberate about it. I'd like to take on one stretch deal in the enterprise segment, sit in on one hiring loop with you, and have one conversation with someone in Product about their pivot. After that I'll come back to you with a clearer answer. Does that work?"

Why this works: it doesn't punt, it doesn't fake commitment, and it gives your manager something to track. Managers respect "I'll be deliberate about this" more than "I want to be a manager" said with no conviction.

If you've decided you want Senior SE, not manager:

"I've thought about this. I want to go deeper on the IC track, not into management. The deals I want to be running in two years are the ones we currently bring [name of senior IC] into. Can we talk about what would get me ready for that?"

Why this works: you name the path, you name a model (a real person who's where you want to be), and you ask for tangible inputs.

Script 2: The skip-level ask

You need a sponsor who isn't your direct manager. Skip-levels make great sponsors because they have wider visibility and no quota dependency on you.

"Hi [skip-level], I'm trying to be more deliberate about my career planning over the next 12 months and I'd value your perspective. Could I get 25 minutes? Specifically, I want to ask how you'd weigh going deeper as an IC versus moving into management, and whether there's a pattern you've seen in SEs who got that decision right or wrong. Happy to come prepared."

Why this works: clear ask, clear time bound, clear topic, signals you've done the work.

Script 3: The Product coffee chat (without burning bridges)

You want to understand the PMM or PM pivot without your manager hearing "they're a flight risk" through the grapevine. Go through the front door, not the side door.

To the Product person:

"Hey [name], I noticed you came over from SE about 18 months ago. I'm taking the Product pivot seriously as one of the paths I might choose, and I'd love 30 minutes to hear how the move actually went. Specifically: what surprised you, what you'd tell your past self, and what you'd want to see in someone's resume if they were making the same move. No agenda beyond that."

To your current manager, proactively:

"Heads up: I'm doing some career exploration over the next quarter. I've got a couple of conversations lined up, including one with [Product person] about her pivot. I want you to hear it from me first. None of this changes anything I'm doing on the team."

Why this works: you tell your manager before they hear it from someone else. Most "flight risk" reads come from the manager being surprised. Removing surprise removes most of the political risk.

Script 4: The internal mobility ask

You've decided. You want to move. Here's how you make the formal ask without it being a surprise:

"Over the past three months I've explored a few directions and I've concluded I want to move into [PMM / PM / Strategic SE on the named accounts team]. I'm not asking you to make this happen for me. I'm asking for two things: your blessing to talk to [hiring manager] formally, and your honest read on what timing works for the team. I'd rather make this transition cleanly with you than awkwardly around you."

Why this works: clean, declarative, gives them control over timing without giving them veto over the move.

Common Pitfalls

I've watched SEs make the same mistakes for years. The ones that compound:

Defaulting to manager because it's the visible ladder. Your company shows "Senior SE" and "SE Manager" on the same level, and you assume the right move is the one with people under you. Pick based on the inventory, not the org chart.

Ignoring the Product pivot because it feels like leaving. It isn't. The teammate who pivoted six months ago and seems weirdly happy didn't leave. They redirected.

Choosing based on title. "Senior SE" sounds like a promotion. "SE Manager" sounds like leveling up. Those instincts aren't correct. Title is the output. Inventory is the input.

Assuming Senior SE is "just more years." Senior SE is a different craft, not a longer version of your current one. If you've been an SE for three years and still feel rattled by execs in the room, time alone won't fix that.

Letting your manager pick because they need a backfill. Your manager has incentives. One is keeping the team whole. Sometimes their advice is about you. Sometimes it's about them. Notice which one is happening.

Your 6-Month Skill Plan Template

Once you've picked a path, write the plan. The point is to make it specific enough that someone could audit it.

Path I'm building toward: [Senior SE / Strategic SE / SE Manager / Product pivot]

The 3 skills I don't currently have:
  1. [e.g., running a security review for a regulated buyer]
  2. [e.g., writing a positioning doc that survives a sales review]
  3. [e.g., giving direct performance feedback to a peer]

The deals or projects that will build them:
  1. [e.g., shadow Sarah on the FinServ deal in Q2; lead the security review section in Q3]
  2. [e.g., partner with PMM on the Q3 competitive update; own the [competitor] tear-down]
  3. [e.g., start informally mentoring the new SE hire; own one weekly office hour]

My sponsor (NOT my direct manager):
  [Name + role + cadence, e.g., "[Skip-level], 30 min/month"]

How I'll know it's working:
  - [Specific signal at month 3]
  - [Specific signal at month 6]

If you can't fill the deals/projects column with specifics, the plan isn't real. "I'll work on executive presence" is not a plan. "I'll lead the exec readout on the [name] deal in Q3 with [VP] coaching prep twice" is a plan.

How Rework Supports the Path Decision

The skills inventory is also a tracking problem. Most SEs lose track of which deals exposed them to which skills, which makes the conversation vague when it should be precise. Rework Work Ops lets you tag deals with the skills they exercised ("enterprise security review," "multi-stakeholder demo," "exec readout") and pull a real inventory at month 18 instead of guessing. Share the view with your sponsor so career conversations work off data, not memory. Once you've picked a path, the reps and metrics you track shift, and Work Ops handles the new dashboard. Work Ops starts at $6/user/month; Rework CRM is $12/user/month.

Three Signals the Conversation Worked

You'll know your career conversation moved you forward when these are true:

1. You can name your path in one sentence without hedging. Not "probably manager but maybe Strategic SE." A clear sentence: "I'm going deep on enterprise IC for the next two years." If you're still hedging, run more deals and re-score.

2. You have a sponsor who isn't your direct manager. Skip-level, cross-functional VP, or external mentor. Someone who advocates for you in rooms you're not in, and whose career doesn't depend on whether you stay on the team.

3. You have a 6-month skill plan tied to specific deals and projects. Not aspirations. Deals. Projects. Names. Months.

The SEs who plateau aren't the ones who pick the wrong path. They're the ones who never pick deliberately and end up wherever the gravity of their org pulled them.

You don't owe your company a default. You owe yourself a real choice.

Learn More