Account Executive interview questions

An AE owns the qualified opportunity from discovery through a signed agreement and clean handoff.

• I turn the buyer's problem into a defined business case rather than simply running calls and demos.
• I keep stakeholders, next steps, value, risk, and forecast status current in the CRM.
• I am accountable for closed revenue, quota attainment, and the quality of what Customer Success inherits.

A basic B2B cycle moves from prospecting and qualification to discovery, evaluation, negotiation, close, and handoff.

• Prospecting and qualification establish ICP fit and whether there is a real reason to buy.
• Discovery and evaluation connect the problem to a tailored demo, stakeholders, and decision process.
• Negotiation resolves commercial terms, then the signed deal moves to Customer Success with context intact.

Stage criteria keep pipeline and forecasts based on buyer evidence instead of seller optimism.

• An opportunity should enter discovery only after basic ICP fit and a relevant problem are confirmed.
• It should leave discovery only when impact, stakeholders, decision path, and a concrete next step are recorded.
• I do not advance a deal merely because I sent a proposal or held a demo.

A lead is a person or account showing possible interest, while a qualified opportunity has credible fit, need, and a buying path.

• A form fill or webinar attendee is not automatically pipeline because intent and relevance are still unknown.
• I create an opportunity after confirming an ICP account, a problem we can solve, and a reasonable next step.
• This distinction prevents inflated pipeline that consumes AE time but cannot close.

An ICP describes the type of company most likely to get value, buy successfully, and remain a good customer.

• I look at firmographic traits such as industry, company size, geography, and technology environment.
• I also use operational signals, such as a growing sales team or a manual process our product replaces.
• I compare each account with the ICP before investing discovery and demo time.

The ICP identifies the right company, while a persona describes a role inside it with distinct goals and concerns.

• A RevOps leader may care about forecast accuracy, while a sales manager cares about rep adoption.
• I adapt discovery questions and proof points to the person's responsibilities without changing the core value claim.
• A perfect persona at a poor-fit company is still a weak opportunity.

I rank accounts by fit and buying signals so the strongest combination receives attention first.

• Fit includes objective traits such as segment, use case, team size, and supported integrations.
• Signals include relevant hiring, leadership change, active research, or engagement from more than one contact.
• I keep low-fit accounts out of active pipeline even when one contact is friendly.

Qualification determines whether a problem is real, valuable, solvable, and likely to reach a decision.

• I confirm fit, pain, impact, stakeholders, timing, and the buyer's process before investing heavily.
• I treat qualification as an ongoing check because facts can change after the first call.
• A clear disqualification is useful because it returns time to opportunities with a credible path.

BANT covers Budget, Authority, Need, and Timing as a simple qualification checklist.

• I explore whether funds exist or can be created, rather than demanding a fixed budget immediately.
• I identify who approves the purchase and whether the problem is important enough to address.
• I validate a real decision window and next milestone instead of accepting a vague future date.

I discuss the cost and priority of the problem before asking how the buyer funds a solution.

• I might ask what the current process costs in hours, missed revenue, or outside services.
• Once value is clear, I ask whether this initiative has an allocated budget or competes for funds.
• I use an approved price range early enough to expose a major mismatch without forcing negotiation.

I map who evaluates, recommends, approves, signs, and will use the product instead of asking only who the decision-maker is.

• I ask how similar purchases were approved and who can stop this one.
• I verify the contact's influence through access to other stakeholders and knowledge of the process.
• If the signer is absent, I agree with my contact on a credible way to involve them.

A meaningful need explains why change matters, while timing shows when the buyer must act and why.

• I ask what happens if the problem remains unchanged for another quarter.
• I connect timing to an event such as renewal, hiring, launch, or a planning deadline.
• If there is no consequence and no dated event, I nurture the account rather than forecast it.

MEDDIC stands for Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, and Champion.

• Metrics quantify the result, while pain explains why the current state must change.
• Decision criteria and process show how the solution will be judged and approved.
• The economic buyer controls funds, and the champion helps the deal move internally.

Metrics are measurable business outcomes that make the value of solving the problem concrete.

• I translate a complaint like slow reporting into hours spent, delay length, or revenue at risk.
• I capture the current baseline and a realistic target, such as reducing weekly reporting from eight hours to two.
• I confirm the number with the buyer rather than inventing ROI from a generic calculator.

The economic buyer is the person with final authority over the funds and the business outcome.

• This person can approve spending or redirect the budget even if another team runs the evaluation.
• I learn their priorities and approval threshold from my contact before requesting access.
• A title alone is not proof, so I verify how the purchase will actually be signed off.

Decision criteria define what the buyer will evaluate, while the decision process defines how and when approval happens.

• Criteria may include integrations, security, usability, implementation effort, and price.
• Process includes evaluators, meetings, legal review, procurement, signer, and target dates.
• I document both because winning the scorecard does not help if the approval path is unknown.

A champion has influence, gains personally or professionally from the change, and actively sells for us internally.

• They share candid information about competitors, objections, and the decision process.
• They arrange access to stakeholders and complete agreed actions without repeated chasing.
• A friendly contact who likes the demo but takes no internal action is not yet a champion.

I use BANT for a quick early screen and MEDDIC for a fuller view once an opportunity deserves deeper work.

• BANT is efficient for simple inbound or short SMB cycles where four basic factors reveal viability.
• MEDDIC adds value when several stakeholders, evaluation steps, and quantified outcomes matter.
• I use only the detail the deal needs rather than turning a small purchase into enterprise paperwork.

I disqualify when fit, value, access, or a credible path to action is missing after direct validation.

• Clear product mismatch or an unsupported use case means we should not force a deal.
• No material pain, no consequence of delay, or no stakeholder willing to act makes timing unqualified.
• I record the reason and a future trigger in Salesforce so a useful nurture does not remain fake pipeline.

Discovery should establish the buyer's current state, problem, impact, desired outcome, stakeholders, and agreed next step.

• I enter with a few hypotheses but let the buyer's answers determine where to go deeper.
• I reserve time to summarize what I heard and ask the buyer to correct it.
• I leave with enough evidence to qualify, disqualify, or plan a relevant evaluation.