Employer guide
How to interview a sales engineer
Four stages, one scorecard and a demo exercise that tests tailoring rather than free consulting — run the whole loop inside ten working days.
Updated July 2026
What to assess
Five dimensions — and where each one is actually tested.
| Dimension | The question behind it | Where you test it |
|---|---|---|
| Technical depth | Can they hold a conversation with the buyer's engineer without deferring? | Architecture whiteboard, not trivia |
| Communication | Can they explain the same thing to a CISO and to a platform engineer? | Demo to two personas |
| Discovery skill | Do they find the problem behind the stated requirement? | Live discovery role-play |
| PoC ownership | Can they set, defend and close out success criteria? | Structured PoC interview |
| Commercial judgement | Do they know when to disqualify rather than promise roadmap? | Panel scenario question |
The demo / PoC exercise
- Send a one-page brief 48 hours ahead: persona, business problem, two constraints, and sandbox access.
- Invite written discovery questions in advance. Answer them as the buyer would — this is half the assessment.
- 30-minute demo to a persona played by your AE, with two planned interruptions (a hostile technical question and a scope-creep request).
- 15 minutes on how they would scope this as a PoC: success criteria, timeline, who signs off.
- Score independently before debriefing. No group scoring.
Never ask for a bespoke build against a live prospect's requirements, and never run the exercise beyond two hours of candidate work.
Interview scorecard
Copy this into your ATS. Score 1–5 per dimension, weight, then debrief.
| Dimension | Weight | 1–2 — below bar | 3 — at bar | 4–5 — above bar |
|---|---|---|---|---|
| Technical depth | 25% | Deflects detail | Answers confidently in one domain | Credible across the stack; corrects the panel politely |
| Discovery | 25% | Jumps to demo | Asks about the use case | Uncovers unstated constraints and decision criteria |
| Demo craft | 20% | Feature tour | Tailored to the brief | Three things that matter to that persona, told as a narrative |
| PoC ownership | 15% | Never owned one | Ran PoCs someone else scoped | Wrote criteria, held the timeline, closed out formally |
| Commercial judgement | 10% | Promises roadmap | Escalates appropriately | Disqualifies a bad fit and explains why |
| Collaboration | 5% | Blames the AE | Works to the process | Improves the process for the whole pod |
Hire at a weighted average of 3.4+ with no dimension below 2. Anything else is a pass.
Good questions to ask
Ask for specifics; follow every answer with 'who decided that?'
- “Walk me through the last proof of concept you personally scoped. Who set the success criteria?”
- “Tell me about a deal you lost on technical grounds. What would you change?”
- “How do you handle a buyer's engineer who has already chosen a competitor?”
- “Where do you draw the line between what the product does today and what's on the roadmap?”
- “How do you and your AE decide when a deal is technically qualified?”
- “Describe the worst security questionnaire you've owned end-to-end.”
Red flags
Any two of these together is a decline.
- Demos features rather than the buyer's use case, even after a brief.
- Cannot name the success criteria of any PoC they've run.
- Claims the technical win in every deal and blames the AE for every loss.
- Over-promises roadmap in the interview — they will do the same with your customers.
- Talks only about product, never about the buying committee.
- Needs the deck. A strong SE can whiteboard the architecture cold.
How to structure the panel
Keep the whole loop inside ten working days.
| Stage | Length | Who runs it | What it decides |
|---|---|---|---|
| 1. Screen | 30 min | Talent or hiring manager | Level, motivation, comp expectations |
| 2. Technical discovery | 45 min | SE leader | Discovery skill and technical depth |
| 3. Demo / PoC exercise | 60 min | SE leader + AE | Demo craft, tailoring, handling interruptions |
| 4. Panel | 45 min | AE, product, CS | Collaboration, commercial judgement, PoC ownership |
Based on our placement data
The exercise and scorecard that work — and the mistakes that don't
The exercise that predicts performance best in our placements is a 48-hour tailored demo: give the candidate one written persona, one business problem and a sandbox, then let them come back with discovery questions before the session. Score the questions as heavily as the demo. Panels that instead ask for a cold demo of their own product select for memorisation, and panels that hand over a live prospect's requirements are asking for free consulting — strong candidates withdraw.
Weight the scorecard toward discovery and technical depth (25% each). Across our debriefs, PoC ownership history was a stronger predictor of a successful hire than product or domain knowledge.
The three most common hiring mistakes: interviewing only for product knowledge; no AE in the loop, so nobody tests the partnership; and a slow process — counter-offer rates run around 4% above advertised packages and good SEs are gone inside two weeks.
Based on our placement data — illustrative placeholder figures.
Custom benchmark
Get a custom benchmark for the exact role you're hiring
Published ranges are a starting point. Send us the role, level, location and stack and we'll return a benchmark tuned to your hire — plus who's available right now.
Methodology
Figures are medians drawn from placement records, offer letters and employer briefs across the last 12 months, expressed as 25th–75th percentile ranges. Base is fixed cash; OTE is base plus variable at 100% attainment, excluding equity. All numbers currently shown are illustrative placeholders. Read the full methodology.
Pre-sales recruitment
Want a shortlist that clears this bar?
Send us the vacancy and a pre-sales specialist comes back within one business day with an initial market view and who's available now.