An enterprise AE needs to do more than describe a large deal. You need to know what they sold, who they worked with, and which parts they handled themselves.
Start with your own accounts and buying process. Then use the same deal review for each candidate. A familiar employer name or a big quota number does not answer those questions.
Define what enterprise means for this job
Companies use the title differently. Put the actual account size, territory, buyer, and contract range in the hiring brief. State whether the AE inherits named accounts or must build the list.
Write down the work that makes your deals complex. It can include several buying teams, security review, legal approval, partner involvement, or a long implementation decision. Name the support available for those steps.
| Role detail | Decision to settle before hiring |
|---|---|
| Accounts | Named list, open territory, or defined vertical |
| Revenue ownership | New customers, expansion, or both |
| Pipeline | AE prospecting, SDR support, partners, and inbound |
| Buyer access | Existing relationships versus new introductions |
| Internal help | Solutions engineer, legal, security, executive sponsor |
| Commercial authority | Discount and contract approval boundaries |
| Travel | Actual customer visits and regional requirements |
If the account list is still under review, say so. Do not recruit against a territory that no one has approved.
Run a deal review instead of collecting highlights
Ask the candidate to choose a completed sale they can discuss without sharing confidential information. Let them use buyer roles and ranges instead of customer names or exact contract figures.
Work through these questions:
- What problem started the conversation, and how did you learn about it?
- Who used the product, who approved the budget, and who could stop the purchase?
- What did you do to get beyond the first contact?
- What changed between the first meeting and the signed agreement?
- Which objections or approvals delayed the deal?
- What did you handle, and what did your team handle?
- What did you stop promising because the company could not deliver it?
- What did the next team need to know after signature?
Keep asking for a concrete example when an answer stays general. “I built relationships” needs a description of the actions and the result.
Ask about a loss too
A won deal shows one outcome. A loss can show how the candidate spots weak opportunities and handles a bad quarter.
Ask when they first saw the risk, what they changed, and why they kept or removed the deal from the forecast. Give them room to explain a decision that was sensible even though the sale did not close.
Watch for explanations that blame everyone else without describing the seller's choices. Also avoid rewarding a polished failure story without asking what changed afterward.
Use the hiring scorecard to record specific examples. Keep “we did not learn enough” separate from “the candidate cannot do this work.”
Use a short account-planning exercise
Give candidates a fictional company, a product summary, and a small account list. Include enough information to compare priorities. Ask which account they would start with, what they need to learn, and how they would approach the first conversation.
Set a clear time limit and use the same materials for everyone. Score the reasons for the choices, the questions they ask, and the next steps. Do not ask them to hand over their real contact list or create a campaign for your live prospects.
One useful follow-up is: “Your first contact likes the product, but finance has another priority. What do you do next?” The answer can show whether the seller understands the buying process beyond a friendly champion.
Check the quota and ramp plan
Use your own deal size and win rate to see how many wins the target requires. Then check the account pool, sales cycle, and time available after ramp. The quota calculator makes the arithmetic visible.
Define early progress before expecting closed revenue from a long cycle. Account research, useful buyer conversations, and qualified opportunities can be part of the ramp plan. They need clear definitions. Activity counts alone do not prove a healthy pipeline.
Tell candidates what the company will supply. An enterprise title does not make up for missing technical help, unavailable approvals, or an account list with little room to sell.
Write the offer around the actual job
State base, OTE, credit rules, territory, travel, and support in plain language. Use the job description template and compensation plan guide before publishing.
For finalists, use reference questions tied to the specific gaps from the deal review. References add context. They do not replace your own assessment.
Common questions
Do enterprise AEs need an existing book of contacts?
Decide whether relationships are essential to this job or useful background. Do not assume a candidate can bring former customers or confidential contact lists.
Should I require a particular sales framework?
Ask candidates to explain their decisions in plain language. If your team uses a framework, check whether they can learn and use it. Acronyms alone do not prove selling skill.
