The four capability areas that actually differentiate Account Executives — with concrete exercises, what good looks like, and how to score them consistently.
Most AE interviews test the wrong things. They spend forty minutes on career history, fifteen on "why this company," and five on a hypothetical objection question the candidate has rehearsed four times.
What they barely touch is the actual job. An Account Executive spends their day doing four things: discovering real problems, demonstrating value, navigating objections, and making judgment calls about where to spend time. If your interview doesn't surface those four, you're evaluating a completely different skill set — interview performance.
The design principle
Every exercise should require the candidate to do something, not describe doing it. Description rewards preparation. Doing reveals capability.
Discovery is the highest-leverage skill in the AE role and the one most commonly faked. Anyone can ask "what's your biggest challenge?" The difference between a strong and average AE shows up in the second and third questions — the ones that follow up on what was just said.
The exercise: Give the candidate a one-paragraph company brief and ask them to run a 12-minute discovery call with you playing the buyer. Hold back the real problem — make them earn it.
Strong signals
Weak signals
A demo isn't a feature tour. It's an argument that the product solves the specific problem you just found. The test is whether the candidate tailors, or delivers the same deck they'd give anyone.
The exercise: Pick up directly from the discovery call. "Okay, show me how this would work for us." Give them a generic product sheet and three minutes to prepare.
What you're watching for: do they reference the specific pain the buyer described? Do they skip features that don't map to it? Do they check in — "does that match how your team works today?" — or do they monologue for eight minutes?
The strongest tell: whether they can articulate the buyer's problem better than the buyer did. That's the skill that makes a demo land, and it can't be faked from a script.
This is where interviews most often go soft. "How do you handle 'we don't have budget?'" invites a rehearsed framework. A real objection delivered mid-conversation exposes the reflex.
The exercise: Interrupt the demo with a genuine pushback — not a soft one. Try "honestly, we're already using something and switching sounds like a lot of work." Then see what happens in the next thirty seconds.
Weak response: discount or defend
Drops price, or immediately lists switching benefits. Both signal that the objection was heard as an attack rather than information.
Adequate response: acknowledge and answer
Confirms the concern, gives a reasonable counter. Professional, but still transactional — it treats the objection as a question to be resolved.
Strong response: get curious
"What's the part of switching that worries you most?" The objection becomes a doorway to the real decision criteria. This is the behaviour that predicts closing.
The least-tested and most predictive area. Deal judgment is the ability to look at an opportunity and accurately assess whether it will close, when, and what will kill it.
The exercise: Present a real (anonymised) deal and ask three questions. "Will this close this quarter?" "What's the biggest risk?" "What would you do next week?"
Strong AEs give you a specific answer with reasoning. They'll say something like: "No — the economic buyer hasn't been in a conversation since the proposal. My champion is enthusiastic but junior. Next week I'd ask the champion to set up a 20-minute call with their CFO framed around payback, and if that doesn't happen I'd push my forecast out."
Weak AEs hedge. "It feels pretty good, they were engaged, I'd follow up and see." Hedging on deal judgment at interview usually becomes inaccurate forecasting on the job — which is a different, quieter, equally expensive problem.
The exercises are only half the work. The other half is making sure two interviewers watching the same candidate land on the same conclusion.
Define the rubric before the interview. Four categories, five-point scale, written descriptors for what a 2 and a 4 look like.
Score independently, then discuss. Discussion before individual scoring produces consensus bias — the loudest interviewer's read wins.
Record or transcribe when you can. Memory degrades fast and reconstructs in the candidate's favour. An artifact keeps the evaluation honest.
Set a hire threshold and hold it. Decide in advance that you won't hire below a 3 average on any single category, regardless of how likeable the candidate is.
All of the above is buildable internally. It also requires scenario design, buyer-script writing, rubric calibration, interviewer training, and consistency across every hiring manager in the org. In practice most teams do it once, enthusiastically, and then drift back to unstructured conversations by the third hire.
That drift is why a standardised external assessment helps. We wrote about how to design a predictive one in How to Run a Sales Roleplay Assessment, and how Showcazz provides it as infrastructure in Know Who Can Sell.
If you're on the other side of the table, this is good news. Interview processes that test real behaviour reward people who can actually sell, not people who've memorised the right answers.
Practise the four areas out loud, with a real person pushing back. Read what hiring managers watch in a discovery call and be ready to handle "let me think about it" without flinching.
And if you're wondering whether you're ready to make the move at all, SDR to AE: How to Know You're Actually Ready is the honest checklist.
Showcazz runs candidates through discovery, demo, objections and deal review — and scores every one against the same rubric so you can compare on capability.