The 18-Month Goodbye: Why Your Best SE Leaves a Team They Love [77]
This episode explores why high-performing solution engineers leave teams they genuinely enjoy, using the real case of Priya who departed after 18 months because she couldn't see a clear path to leadership. The hosts argue that vague growth promises and informal mentoring without real authority create a false waiting room, and that honest conversations about actual timelines and available seats are essential to retention.
Summary
The episode opens with Nate recounting the departure of Priya, a top-performing SE who ran the Lunch and Learn series, had the highest engagement scores, and seemed genuinely satisfied with the team. When asked why she left, Priya revealed the issue wasn't compensation or role satisfaction—it was the complete absence of a visible path to leadership. She had mentored juniors informally for a year but recognized that without an official leadership position, her ambitions couldn't be realized.
Nate admits his mistake was assuming ambition only manifests as desires for titles or money, when actually Priya wanted responsibility for someone else's development. He had defended informal leadership opportunities as a "proving ground" to test whether SEs truly want management roles, but Ava reframes this as a "waiting room" with no posted wait time. The core problem: Nate had 12 SEs and only one management seat—his own—making the vague promise of "loads of room to grow" technically true but completely useless.
The episode then pivots to the competitive disadvantage of silence. Priya's new employer was direct: "We'll need someone running this team within the year." This tangible timeline made the decision easier, and Nate realizes that by not being honest about the four-year wait (if there was one), he left space for a recruiter to write the narrative instead.
Ava then shares a contrasting example where a new SE manager inherited two people who had applied for her job and didn't get it. In the first month, she asked each what they wanted to be responsible for and by when, then gave them honest answers—including "not here, not within two years" for one person. That person left but found a team elsewhere; the other stayed after receiving genuine accountability with a specific date (regional expansion in Q3) and actual budget and headcount, not just a title.
The critical insight emerges: "Ownership means decisions. Everything else is a job title with a bow on it." Nate's move after Priya's departure was to give someone actual ownership of onboarding, hiring input, and ramp design, with veto power on new hires—not just a leadership label.
About this episode
Ava's strongest SE left after eighteen months from a team she loved, because the path to leading anything was never made concrete. Nate and Ava dig into why silence about timelines costs you your best people, and what an honest version of that conversation sounds like.
Key Insights
- Nate observed that high performers who leave are often the ones who remain happy until departure—they 'just vanish on a Tuesday'—whereas dissatisfied employees are easier to spot and intervene with earlier.
- The hosts argue that vague promises of growth ('loads of room to grow') are technically true but completely useless because they provide no actual information about when leadership opportunities will materialize, leaving ambitious employees in an undefined waiting room.
- Ava claims that silence about advancement timelines is actively harmful because it cedes control of the narrative to external recruiters and competitors, who will provide specific, honest timelines that make their offers more compelling than a vague internal promise.
Topics
Transcript
Hey there and welcome to Leading Pre-Sales, the show for solution engineering leaders who want to build teams that drive revenue and not just demos. My name is Tim and I'm the co-founder of SE Rockstars and together with Jan, we've coached over 350 solution engineers and their leaders across several dozens of companies. Every conversation you hear on this show is based on real coaching situations, real challenges, real problems that SE leaders like you are dealing with right now. None of this is made up. We use AI to bring these stories to life through our two hosts, Nate and Ava, but the insights come straight from the trenches. Each episode gives you one actionable takeaway you can…
Full transcript available for MurmurCast members
Sign Up to AccessMore from Leading PreSales | The Solution Engineering Leadership Show
Core vs. Context: When Your SEs Should Let a Build Deal Go [92]
The episode teaches solution engineering leaders to distinguish between core and context business functions when customers consider building custom solutions versus buying software. SEs should let lightweight, context-focused builds go while fighting harder for core capabilities, and leaders must publicly validate this approach to change team culture.
The Iceberg Under Every Build Deal [91]
Solution engineering leaders need a standardized five-year cost model to evaluate Build vs. Buy decisions in the AI era, grounded in hidden maintenance costs and opportunity expenses rather than vendor pitches. The key is creating an 'iceberg checklist' of often-overlooked costs and having customers co-create the financial analysis rather than presenting a pre-built case.
Leaderboards, Not Cameras [89]
The episode examines why AI adoption dashboards and leaderboards often fail to drive behavior change, and proposes an alternative approach: publicly sharing AI workflows that actually shipped on real deals, ranked by peer reuse rather than usage metrics.
Your SEs Just Inherited the Customer's Bill [88]
Solution engineers must own usage estimation and sizing in consumption-based pricing models, even though they don't set prices. When SEs fail to accurately estimate how often workflows trigger, customers face billing surprises that damage relationships and renewals.
Rebrand or Real Role? The FDE Test [86]
The episode examines whether Forward Deployed Engineers (FDEs) represent a genuinely different role from Solution Engineers or merely a rebranding strategy. Through analysis of real job postings and market trends, the hosts present a three-question test to distinguish authentic FDE positions from SE roles with inflated titles.