Leading PreSales · 2026-06-26 · 6 min
Key moments - from our scoring
Substance score
34 / 100
Five dimensions, 20 points each
This episode examines two critical hiring signals for solution engineers: how candidates handle technical questions they can't answer, and their coachability when receiving feedback. Nate and Eva argue that the best candidates respond to unknowns with "I don't know, but here's what I'd do to find out," then reason through problems aloud rather than bluffing confidently. When testing coachability, the real tell isn't whether candidates accept feedback, but whether they show emotional honesty about past feedback (describing how it felt, not just what they did), and whether they can distinguish between valid notes and stylistic preferences. Tim and Jan's SE Rockstars framework emphasizes that coachability directly impacts operational efficiency - SEs who can't absorb feedback quickly waste manager cycles fighting resistance instead of building capability. This episode is essential for SE leaders hiring for roles that require constant adaptation to new products, competitors, and buyer expectations, and for anyone building interview processes that move beyond resume credentials.
The best response is "I don't know. But here's what I'd do to find out, and I'll get back to you by tomorrow." This signals honesty, resourcefulness, and respect for the other person's time, rather than bluffing or shutting down.
Test coachability by giving feedback on a roleplay that mixes one valid note with one stylistic preference. Candidates who take both without question are people-pleasers, while those who integrate the valid feedback but push back on style preferences show the confidence and humility needed for the role.
Ask "What's the hardest feedback you've ever received?" then listen for emotional honesty - whether the candidate names something real, describes how it felt, and shows they actually processed it, rather than delivering a rehearsed humble-brag answer.
The SE role changes faster than most tech roles due to new products, competitors, and buyer expectations. An SE who can't absorb feedback and adapt quickly will be effective for only one product cycle, while poor coachability forces managers to spend cycles fighting resistance instead of developing capability.
Ask a genuine technical question from your product space that the candidate probably won't know, and watch whether they bluff, shut down, or reason out loud by thinking through it logically - the latter indicates they can process new information in real-time customer meetings.
Our reviewer’s read on each dimension, with quotes from the episode.
The episode surfaces a few genuinely useful hiring tactics - the deliberate 'one valid + one style-note' feedback test and the over-coachability warning are non-obvious - but most of the runtime covers well-worn hiring wisdom (don't bluff, coachability matters) in a 6-minute format that limits depth.
I give feedback. That's a deliberate mix. One valid note and one that's a matter of style, not substance. If the candidate takes both without question. People pleaser.
Nobody talks over coachability. The candidate who agrees with everything changes their answer the moment you push back has no spine.
The over-coachability flip-side is a legitimate counterintuitive nuance that most hiring content ignores, and the structured feedback-mix test is a concrete tactical original; however, the framing pillars - self-awareness, coachability, reasoning-out-loud - are standard interview-advice canon.
The sweet spot is someone who listens, integrates what's useful, and pushes back when they genuinely disagree.
If they push back on the style note and explain why, that's the signal I want.
There are no real guests whatsoever - both hosts are explicitly AI-generated personas ('we use AI to bring these stories to life'), and the actual practitioner Tim provides only a brief framing intro and outro rather than substantive content delivery.
We use AI to bring these stories to life through our, uh, two hosts, Nate and Eva. But the insights come straight from the trenches.
I'm Ava.
The episode anchors its claims in a concrete hiring anecdote with a specific technical domain (API rate limiting) and offers one useful operational number (team of 20, manager burning half their cycles), but there are no company names, outcome data, conversion rates, or research citations.
my manager asks a technical question about our API rate limiting architecture. And the candidate, without missing a beat, gives this elaborate, confident answer. Completely wrong.
Seven years of pre sales, solid references.
The dialogue is a scripted AI exchange, making genuine follow-up pressure or productive disagreement structurally impossible; the questions are competent setups ('What's your approach?', 'So coachability isn't just a nice to have?') but function as cueing lines rather than real interrogation.
What's your approach?
Okay, so the bluffer is a red flag. What's the green flag version of that moment?
Computed from the transcript - who did the talking, and the words that came up most.
Hiring Series 2/4. Two interview moments that tell you more than any resume line - bluffing under pressure and how candidates handle real feedback. Part 2 of 4 on hiring the right SE. A candidate confidently answered a technical question completely wrong, and that moment told the interviewers everything. Two interview signals that predict an SE's ceiling: coachability and self-awareness. What Nate and Ava discuss The bluff vs. the "I don't know but here's how I'd find out" - and why reasoning out loud IS the job "What's the hardest feedback you've ever received?" - and why the emotional honesty matters more than the answer The over-coachability problem - the candidate who agrees with everything has no spine Testing whether candidates can distinguish real feedback from noise The move Add two moments to your next SE interview. First - ask a question the candidate probably can't answer. Bluff, shutdown, or honest reasoning? Second - give real feedback after a role-play, mixing a valid note with a matter-of-style one. Do they integrate, debate, or deflect? Those two moments tell you more about a person's ceiling than anything on their LinkedIn.
Transcribed and scored by The B2B Podcast Index.
Tim: Hey there and welcome to Leading Presales, 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, uh, two hosts, Nate and Eva. But the insights come straight from the trenches. Each episode gives you one actionable takeaway you can apply immediately whether you're already leading a team or working your way into that role. Alright, let's get into it.
Nate: I sat in on an interview last month that one of my SE managers was running strong candidate. Seven years of pre sales, solid references. Forty minutes in, my manager asks a technical question about our API rate limiting architecture. And the candidate, without missing a beat, gives this elaborate, confident answer. Completely wrong. Not even close.
Eva: And he didn't flinch.
Nate: Not a bit. Delivered it like he was reading from documentation. My manager looked at me. I looked at her.
Eva: We both knew that the answer was wrong.
Nate: That he was wrong for our team. Because that moment told us everything about how he'd behave in front of a customer. When a prospect asks a hard question and you don't know the answer, you bluff. That's how you lose trust in seconds.
Eva: Welcome to Leading Presales. I'm Ava.
Nate: And I'm Nate. This is part two of our series on hiring the Right se. Last episode we talked about why most SE hiring is broken today. The two signals that tell you more than any resume line ever will. Coachability and self awareness.
Eva: Okay, so the bluffer is a red flag. What's the green flag version of that moment?
Nate: I don't know. But here's what I'd do to find out and I'll get back to you by tomorrow. That sentence in an interview in a customer meeting anywhere tells me this person is honest, resourceful, and respects me enough not to waste my time with a guess.
Eva: I've started planting a question like that in my interviews. Something technical enough that the candidate probably won't know. Not a trick question, a genuine one from our product space. And I watch the best candidates say, I'm not sure, but let me think through it. And then they reason out loud. The worst ones either bluff or shut down.
Nate: Reasoning out loud is huge. That's the actual job in A customer meeting. You're constantly processing new information in real time. I don't need someone who has every answer memorized. I need someone who can work through a problem without panicking.
Eva: Let's talk about the other signal, coachability. Because I think it's harder to test for than people assume.
Nate: What's your approach?
Eva: I ask. What's the hardest feedback you've ever received? Then I shut up. The answer matters. But what matters more is the texture. Does the candidate name something real, describe how it felt, not just what they did about it? Or do they give me the humble brag? My manager told me I work too hard. That's not feedback. That's a performance.
Nate: The emotional honesty is the tell. If someone can say that. Feedback stung. And I was defensive at first, but eventually I realized they were right. That person has actually processed it. They didn't just memorize a good interview story.
Eva: And here's why this matters so much for ses. Specifically, the SE role changes faster than almost any other role in tech. New products, new competitors, new buyer expectations. An SE who can't absorb feedback and adapt is going to be great for exactly one product cycle. Then they're stuck.
Nate: I'd, uh, sharpen that at my scale. When one of my SE managers identifies a coaching gap, they need to close it fast. If the SE pushes back on every piece of feedback, the manager burns cycles, fighting instead of developing. Multiply that across a team of 20 and you've got a manager spending half their time managing resistance instead of building capability.
Eva: So coachability isn't just a nice to have personality trait. It's an operational efficiency issue.
Nate: It is. And there's a flip side. Nobody talks over coachability. The candidate who agrees with everything changes their answer the moment you push back has no spine. That person will crumble in a competitive deal when the customer challenges them.
Eva: So you want someone who can take feedback without abandoning their own judgment.
Nate: The sweet spot is someone who listens, integrates what's useful, and pushes back when they genuinely disagree. Confidence and humility in the same person? Rare. And when you find it in an interview, pay attention.
Eva: I test for that. Now, after the role play, I give feedback. That's a deliberate mix. One valid note and one that's a matter of style, not substance. If the candidate takes both without question. People pleaser. If they push back on the style note and explain why, that's the signal I want.
Nate: Smart. You're testing whether they can distinguish between real feedback and noise. That is the job.
Eva: What's the move?
Nate: Add two moments to your next SE interview. First, ask a question they probably can't answer, bluff, shutdown, or honest reasoning. Second, give real feedback on a roleplay. Do they integrate, debate or deflect? Those two moments tell you more about a person's ceiling than anything on their
Eva: LinkedIn Part 2 of, uh, 4 the Learner Beats the Knower. I'm Eva.
Nate: And I'm Nate. See you next episode.
Tim: Thanks for listening to leading presales. If you've got a question, a topic you'd like us to cover, or you just want to connect, reach out to me@timrockstars um.com and can you? And if what you heard today hit home and you want to talk about how to develop your SE team, feel free to book a discovery call@serockstars.com no strings attached. The link is, of course, also in the show Notes until next time, and keep leading from the front.
Other episodes covering the same guests and topics, from across The B2B Podcast Index.
The Current State of Agentic Retrieval - Qdrant RoundtableMLOps.community · features Eva59 / 100
What Makes Us Go: Retracing America’s First Road TripSteel Stories by U. S. Steel · features Nate52 / 100
How simple changes to coaching can elevate performance: Aditya KothadiyaThe Modern SaaS Podcast · on coachability assessment55 / 100
Why Your API Gateway Needs a Rate Limiter That Talks BackThe Developer Tools Podcast with Fexingo · on API rate limitingThirty Seconds That Sells [45]52 / 100Garbage In, Confidence Out [34]88 / 100Stop Hiring Resumes [29]52 / 100Your AE Won't Brief You - Now What? [28]60 / 100Follow the Breadcrumbs [44]