How to Hire Sales Engineers: The Hire-or-Pass Scorecard

You can do everything else right as an SE leader, but a bad hire will cost you more than a quarter of bad coaching. And most SE hiring is broken in a way that's easy to miss, because it feels rigorous: a stack of strong resumes, a few polished interviews, a debrief, an offer. Then three months in you realize you hired the resume and got blindsided by the person.

The fix is a scorecard — the same dimensions, the same questions, scored the same way for every candidate. Here's the one we'd build, and the interview bank that goes with it.

Why most SE hiring is broken

Look at what a typical SE job description screens for: five years of presales, a specific tech stack, a certification, industry experience. All of which tells you what someone has done — none of which tells you how they think or whether they'll grow. Filter hard on experience and domain and you get a shortlist of people with the same background, the same career arc, the same rehearsed answers. Then you pick the one who presented best, which is basically a demo of their demo skills. It's a terrible proxy for whether they'll succeed on your team.

The second failure happens in the debrief. Three interviewers, one candidate, three verdicts — "strong hire," "maybe," "pass" — and when you dig in, they were each grading on a different invisible rubric. One loved the technical depth, one worried about fit, one thought the role-play was weak. The decision comes down to who argues loudest, the most senior person usually wins, and the halo effect does the rest: one brilliant five-minute story about closing an impossible deal, everyone nods, and a 1-out-of-3 on coachability quietly gets forgiven.

A scorecard fixes both problems at once.

The scorecard

Six categories. For each, know what a genuinely strong answer sounds like and what the disqualifying version sounds like:

Category	A strong "3"	A weak "1" 🚩
Discovery & pain finding	Earns the right to ask, weaves discovery into the demo, understands why it matters	Skips straight to the demo with no pushback
Demo & presentation	Segments the room — business outcomes for the VP, daily workflow for users, security for procurement	"I'd show everyone the same demo"
Technical depth & learning	"I don't know — here's how I'd find out"; explains a complex concept to a non-technical VP without the jargon	Bluffs a confident wrong answer; or buries the room in jargon
Sales partnership & deals	Disagrees with the AE respectfully and with evidence; scopes a POC with success criteria and a written agreement	"I just do what the AE says" / "I build whatever they ask for"
Coachability & self-awareness	Names real, hard feedback and what they did with it; can point to a skill they deliberately improved this year	The "I work too hard" humble-brag; gets defensive
Situational role-play	Pivots a competitor jab into discovery; on a blocked deal, builds the business case and arms the champion	Trashes the competitor; "that's the AE's problem"

Two of these are non-negotiable: discovery and demo are the core SE skills, and a weak score in either is an automatic pass no matter how high the total. But the single best predictor of whether a hire works out long-term isn't on the technical rows at all — it's coachability. Skills you can coach; coachability you cannot. If someone debates feedback in an interview, where they're on their absolute best behavior, they will not take it six months in when the pressure is real.

Score it 1–3, during the interview

Pick six to eight questions for each interview, mix the categories, and score every answer on the spot:

• Use a 1–3 scale, not 1–5. With five levels everyone clusters at three, every candidate averages a 3.2, and you're back to gut feel. One-to-three forces a verdict. A 1 is weak — vague, defensive, no examples. A 2 is adequate — reasonable but generic. A 3 is strong — specific, self-aware, bar-raising.
• Write the score during the interview, not after. Afterwards you're reconstructing from memory, and your overall impression contaminates every individual data point.
• Score independently, before the debrief. No numbers get shared until everyone has committed theirs. That's what kills the loudest-voice effect.

A pro move if your team has the tooling: with the candidate's consent, record the interview with a conversation-intelligence tool and score the transcript against the rubric. It removes the memory problem and the halo effect in one step — you're grading what was actually said, not what you remember feeling.

Test with live scenarios, not war stories

The standard behavioral interview is a storytelling contest. "Tell me about a deal that went sideways" — every experienced SE has told that story fifteen times; the delivery is smooth and it tells you almost nothing about what they'd do on your team. Past performance is curated. Live performance isn't. Run real scenarios and score them:

• The multi-audience demo. "You're demoing to eight people — two end users, a technical architect, a VP of Operations, and procurement. Forty-five minutes. How do you structure it?" A weak answer: "overview, then technical details." A strong one opens with the VP's business problem, spends ten minutes on outcomes before touching the product, moves to the users' workflow, and saves procurement's security questions for the end — because leading there loses the VP.
• The competitor objection. You play the prospect: "A competitor does everything we need — why bother with you?" The weak answer trashes the competitor. The strong one pivots to discovery: "What are the top things driving your evaluation?" You never win by attacking; you win by understanding what the customer values.
• The blocked deal. "The tech team loves you. The CFO is blocking — doesn't see the ROI. What do you do?" "That's the AE's problem" is an instant pass. The strong answer builds the business case, quantifies the cost of inaction, and arms the champion to present upward.

Hire for domain, train for sales

The one place experience screening is defensible is deep verticals — fintech, life sciences, anything where a buyer expects you to speak their language on day one. But notice the move: the strongest play is often to hire the domain and train the sales. A former controller selling to CFOs already understands the month-end close and the compliance reporting; the gap is just how to run a meeting and position a solution — which is far more teachable than becoming credible in a complex domain from scratch. Teams that do this often see faster ramp, not slower, because the hard-to-teach part was already there. So weight the domain dimension by the role: a hard floor where the vertical demands it, trainable where it doesn't.

Hire or pass

When the scores are in, the call is almost made for you. Hire when the candidate scores 2 or 3 across most categories, has no weak score in discovery or demo, backs answers with specific real examples rather than hypotheticals, and shows genuine self-awareness and a willingness to learn. Pass when there are two or more weak scores across categories, any weak score in discovery or demo, answers that stay vague or generic, or defensiveness when challenged.

It's the floors and the pattern that decide it, not the average — and never the halo from one great story. The person who told the best deal story is not the same as the person who will raise your team's bar.

The takeaway

Stop interviewing for the resume and grading on vibes. Score every candidate against the same six dimensions, on a 1–3 scale, written down during the interview and independently before the debrief — and let the floors, not the average or the loudest voice, make the call. It's the difference between hiring the person who interviews well and hiring the person who'll actually raise your team's bar.