How to Actually Evaluate a Sales Engineer
Most SE reviews run on vibes and recency. Here's the 8-dimension, 6-point framework I use to make the call defensible, and the agent that runs it for you.
Ask three managers to rate the same Sales Engineer and you’ll get three different answers, each built from a different sample. One remembers the demo that saved a flagship deal. One remembers the POV that slipped two weeks. One just talked to the AE who loves working with them. None of them is wrong, and none of them is a rating you can coach against or defend in calibration.
The problem isn’t that SE performance is unknowable. It’s that the signal is spread across deals, calls, and rooms no single person sees all of, so reviews drift toward the loudest deal and the last conversation. “She’s solid” is a conclusion. It tells you where the manager landed, not how they got there, and it gives the SE nothing to act on.
The fix is to score the practice, not the person, across a fixed set of dimensions, on a scale, with an evidence test: a conclusion isn’t a score until there’s a specific behavior behind it. I run eight dimensions on a 6-point scale. Here’s what each one measures and the question that surfaces the gap.
The eight dimensions
Product Knowledge
How deeply does the SE know the solution, and can they hold their own in an advanced technical conversation without backup? Strong looks like handling a deep dive solo, knowing where the product genuinely doesn’t fit yet, and being someone engineering respects in a technical thread. Developing looks like leaning on a specialist whenever the question gets hard, or repeating gaps they haven’t moved to close.
Could they run an advanced technical deep dive with no support, and do they know exactly where the product falls short today?
Presentation and Communication
How well do they communicate across audiences, from a skeptical architect to an executive sponsor? Strong looks like running a first meeting independently, carrying the full arc of the deck, and shifting register between a technical and a business room without losing either. Developing looks like a good demo that only works for one kind of audience, or a presenter who can answer questions but can’t command the room.
Can they hold an executive audience and a technical audience in the same week, and tailor the story to each?
Sales Partnership
How well do they partner with the seller to qualify, build champions, and win? Strong looks like an AE who seeks them out by name, an SE who qualifies with MEDDPICC unprompted and builds a business value assessment on their own, and someone sales leadership pulls into their hardest deals. Developing looks like an order-taker who runs the demo they’re handed and stops there.
Does sales leadership ask for this person by name on the deals that matter, and what happens when they do?
Domain and Industry Expertise
Do customers treat them as a trusted advisor on the problems the solution solves, or as a product demonstrator? Strong looks like a customer leaning in during discovery because the SE understands their world, the competitive field, and the business outcome, not just the feature list. Developing looks like deep product fluency with shallow roots in the customer’s actual problem.
In discovery, do customers treat them as an advisor on their problem, or as the person who drives the demo?
Learning Agility
How quickly and proactively do they pick up new technologies, concepts, and market shifts? Strong looks like getting fluent on a new product or a new competitor fast, and being technically well-rounded beyond the core stack. Developing looks like waiting for formal enablement, or staying narrow when the market moves.
When something changed recently, a new release, a new competitor, a new buyer, how fast did they get current, and did anyone have to push them?
Drive and Ownership
How self-directed are they, and do they do the right things without being asked? Strong looks like consistent work nobody assigned, and catching the thing that fell through the cracks before you did. Developing looks like solid execution that only happens under active oversight. One caution here: a newer SE who needs more structure isn’t the same as low drive. The question is whether they’re self-directed for where they are in their career, not whether they need zero support.
What do they do consistently that nobody asked them to do, and what falls through the cracks unless someone follows up?
Coachability and Growth Trajectory
Do they act on feedback consistently, and is the overall trajectory moving the right way? Strong looks like feedback that sticks, behavior that visibly changed after a coaching conversation, and someone who asks for input rather than waiting for it. Developing looks like nodding in the moment and reverting by the next deal. This one is about direction as much as level: a 3 climbing is a different bet than a 4 sliding.
Point to a piece of feedback you gave them. What actually changed afterward?
Team and Organizational Impact
What do they contribute beyond their own deals? Strong looks like the enablement session others rely on, the RFP library they seeded, the demo environment the pod reuses, the junior SE they quietly mentor. Developing looks like a strong individual contributor whose contribution stops at their own number. The test I like: if they left tomorrow, what would the team notice first, and what would quietly disappear?
If they walked tomorrow, what would the team lose beyond their pipeline?
The scale and the read
Each dimension gets a score from 1 to 6:
| Score | Meaning |
|---|---|
| 6 | Exceptional, clearly above role level, a model example |
| 5 | Excellent, consistently exceeds expectations |
| 4 | Strong, fully meets expectations, no meaningful gap |
| 3 | Developing, partially meets expectations, positive trajectory |
| 2 | Needs improvement, below expectations, limited progress |
| 1 | Needs attention, significant gap, flat or negative trajectory |
Six points sounds precise, but the move that makes it usable is to band first and narrow second. Before you argue 4 versus 5, answer the easier question: is this a performing area for them, or one that needs development? Once you’ve picked the band, the exact number is a short conversation, not a standoff. Four is the line. At or above it, you’re building on a strength; below it, you’re closing a gap.
The evidence test is what keeps the whole thing honest. A score needs a behavior behind it, a deal, a call, a specific thing they did or didn’t do. “He’s great with customers” caps out until you can say which customer and what happened. This isn’t bureaucracy. It’s the difference between a review the SE can act on and a number they’ll quietly dismiss.
Use it on yourself
The same eight dimensions work as a self-assessment, and most SEs never take the time. Rate yourself honestly, ask for the evidence on your own 5s, and you’ll have a sharper read going into your review than your manager does, plus a list of where the two of you are likely to disagree. That gap is the most useful part of the conversation.
One caveat in both directions: a score taken from a short observation window is a snapshot, not a verdict. If you’ve only watched someone for a quarter, say so in the writeup and plan to revisit. Trajectory matters more than any single reading.
Run it
I built a Claude skill that runs this whole framework as a guided conversation. It pulls context from your connected tools first, walks the eight dimensions one at a time and keeps asking for the specific behavior behind each score, then hands back a scorecard, a spider diagram, per-dimension development notes, and a Word doc formatted for a formal review.
SE Performance Evaluator
Runs this framework as a guided conversation and outputs a scored report, spider diagram, development notes, and a downloadable Word doc.
If you want the narrower companion, the AI Fluency Rubric for Sales Engineering scores one slice of this in more depth: how fluently an SE actually uses AI in the job.