Reference file

Worked example

worked-example.md

title: Worked example, enterprise AE final round description: A full run from raw feedback to the debrief card, for a fictional enterprise AE hire with a split panel.

Worked example: enterprise AE, final round

A fictional mid-size software company is hiring an enterprise AE. The final round had three interviewers. The recruiter debriefed the candidate the same afternoon. All names are invented.

Raw inputs

VP Sales (written, before discussion): "Strong. Ran a great role play, handled the pricing objection well. Knows the space. Keen to move."

Senior AE, peer interview (written): "Nice person. Good stories. When I asked how they built pipeline in their last role they mostly talked about the inbound team. Could work."

Sales engineer (written): "Fine. Didn't ask me a single question about the product or the integration work, which is where our deals get stuck."

Candidate debrief (by the recruiter): "Loved the VP. The role play went really well. Peer chat was relaxed. I think they liked me. My only question is the territory split, and I've got a second round elsewhere on Friday."

Classification

Row Panel read Candidate read State
Objection handling VP: "handled the pricing objection well" "Role play went really well" ALIGNED
Pipeline generation Peer: "mostly talked about the inbound team" "Peer chat was relaxed" BLIND
Technical curiosity SE: "didn't ask me a single question about the product" Not mentioned BLIND
Overall conviction VP strong, peer and SE lukewarm "I think they liked me" DIVERGENT (panel vs panel)
Territory Not raised by panel "Only question is the territory split" BLIND (the other way)

Language flags

  • Peer: "Could work." Vague positive. Forcing question: "Which gap, and how long before it costs us a deal?"
  • SE: "Fine." Vague positive. Forcing question: "If they were the only candidate, would you hire them?"
  • The VP is the outlier, two points above the other two interviewers. That is the most important fact on the map.

The debrief card

Candidate A / Enterprise AE / Round 3 (final) / [date]
Reads in: VP Sales, Senior AE, Sales Engineer + candidate (recruiter) | Missing: none
Panel conviction: 3 "Could work" (peer), "Fine" (SE); VP at 5 is an outlier
Candidate intent: 4 "Loved the VP", open question on territory, rival process Friday
BLIND (3): Pipeline was mostly inbound (peer); no product curiosity (SE);
           candidate's territory question not yet answered
DIVERGENT (1): VP rates a hire, peer and SE do not
Slow-no flags: "Could work" (peer), "Fine" (SE). Forcing questions sent to both
Bias flags: none
Momentum: 1. Ask candidate for their best self-sourced deal, start to finish. Recruiter, tomorrow 12pm
          2. VP answers the territory question in writing. VP, tomorrow 5pm
          3. 20-minute follow-up with the SE on a live deal scenario. Hiring manager books, before Friday
Decision: Advance to offer now? Yes / No
          Broker the pipeline concern before deciding? Yes / No

Why this is the right call

The VP's enthusiasm would have carried the room in an open discussion, and an offer would likely have gone out on Thursday. Two interviewers had a specific, unshared doubt about the one thing an enterprise AE is paid for: building their own pipeline. The candidate had no idea. The move gives them a fair chance to show a self-sourced deal before Friday, which is also the deadline set by their other process. If the example is strong, the panel moves to 4 and the offer goes out a day later with everyone behind it. If it is weak, the company avoided a mis-hire that would have taken two quarters to show up.