Account Executive interview questions

MEDDPICC turns deal confidence into a set of claims that must be backed by customer evidence.

• Metrics, Economic Buyer, Decision Criteria, Decision Process, Pain, and Champion form the original MEDDIC qualification.
• Paper Process and Competition expose two common late-stage risks: an unsigned contract path and an unchallenged alternative.
• I use blank fields as questions to resolve, not boxes to fill with assumptions, and I downgrade the deal when evidence is missing.

I structure discovery around the current state, business impact, desired outcome, and path to a decision.

• I first confirm why the buyer took the meeting and map the current workflow with volume, owners, tools, and failure points.
• I quantify consequences with questions such as hours lost per week, revenue delayed, error cost, and what happens if nothing changes this year.
• I close by replaying the problem in the buyer's words, agreeing on gaps, stakeholders, and a dated next step rather than jumping straight to a demo.

A product request describes a feature, while business pain explains the measurable consequence of not having the capability.

• If a prospect asks for dashboards, I ask who uses them, which decision is slow today, and what that delay costs.
• A useful pain statement has an owner, a baseline, and urgency, such as finance spending 80 hours per month reconciling forecasts before board reporting.
• I do not build a business case around an unowned preference because it rarely survives budget review.

I compare the quantified annual benefit with the total annual cost using assumptions the customer has validated.

• Benefit can combine labor saved, revenue gained, and risk avoided, but I label each input and avoid counting the same outcome twice.
• A simple ROI formula is (annual benefit - annual cost) / annual cost, while payback period is implementation cost divided by monthly net benefit.
• I show a conservative, expected, and upside case so the Economic Buyer can see which assumptions change the decision.

A metric is qualified only when the customer confirms the baseline, target, owner, and measurement source.

• I replace claims like faster onboarding with a baseline such as 21 days today and a target of 12 days by the next hiring wave.
• I ask whether finance, operations, or another team already reports the number and request the existing dashboard or calculation.
• If the value depends on an unverified estimate, I mark it as an assumption in the business case rather than presenting it as customer evidence.

The Economic Buyer is the person with final authority over the budget and the business outcome, not simply the most senior contact.

• I ask who can approve the purchase if all other stakeholders agree, whose budget pays, and who can stop the project.
• In a mid-market RevOps deal, the VP of Sales may sponsor the outcome while the CFO remains the Economic Buyer because the spend crosses an approval threshold.
• I verify the role through the customer's decision process and seek direct access before treating the opportunity as commit.

A real champion has influence, personal motivation, and a willingness to sell internally when I am not present.

• I test influence by asking how similar decisions were made and whether the person can bring the Economic Buyer or procurement into the process.
• I test commitment with a useful action, such as validating the business case, sharing internal criteria, or correcting the stakeholder map.
• Frequent replies and enthusiasm are not enough; if the contact cannot mobilize others, I record them as a coach rather than a champion.

I uncover how the customer will score options, then connect our differentiation to criteria tied to the business outcome.

• I ask what must be true technically, commercially, and operationally, who owns each criterion, and how competing options will be compared.
• I separate required criteria from preferences because a security requirement can eliminate a vendor while a nicer dashboard may not.
• I can introduce a missing criterion, such as implementation effort or adoption risk, but the customer must agree it belongs in the evaluation.

I validate each criterion with its owner, weight, required evidence, and place in the final approval.

• I ask who introduced the criterion and whether that person can block or recommend a vendor.
• I turn labels such as security or ease of use into a test, scorecard threshold, or documented business outcome.
• I compare the working team's scorecard with procurement and executive priorities because an unofficial criterion can overturn the published list.

I map every step between verbal selection and a bookable order, including owners, documents, dependencies, and service times.

• The path may include vendor onboarding, security approval, legal redlines, procurement negotiation, finance approval, and signature routing.
• I ask for standard turnaround times and approval thresholds, such as a CFO review for contracts above $100K ACV.
• I place those steps in the mutual action plan early because a verbal yes without a paper path is not a reliable close date.

I treat competition as any credible alternative for the same budget, including an incumbent, internal build, and doing nothing.

• I ask what else the team is evaluating, why those options are attractive, and which stakeholder favors each one.
• I compare alternatives against agreed decision criteria instead of relying on feature-by-feature attacks.
• No decision is often the strongest competitor, so I quantify the cost of delay and confirm whether a deadline has a real business consequence.

I map each stakeholder by role in the decision, influence, stance, business priority, and next action.

• A typical map includes the champion, Economic Buyer, technical evaluator, procurement, legal, security, finance, and affected department leaders.
• I note relationships between people because a supportive user with low influence is different from a VP who can reach the CFO.
• The map drives an engagement plan, so every important stakeholder has an owner, message, and dated meeting rather than just a name in CRM.

I position broader access as necessary to build an accurate recommendation, not as a way around my contact.

• I ask the champion to co-host role-specific sessions with finance, security, and the executive sponsor, preserving their ownership of the process.
• Each meeting has a reason tied to that stakeholder, such as validating payback with finance or architecture with security.
• If access remains blocked, I state the resulting risk openly and lower forecast confidence rather than pretending the relationship is sufficient.

A mutual action plan should work backward from the customer's outcome date and assign every buying and selling milestone.

• It includes success criteria, validation steps, security and legal reviews, commercial approval, signature, implementation kickoff, owners, and dates.
• Dependencies are explicit, such as completing the data review before security approval or signing by June 15 to launch before peak season.
• Both sides edit and confirm the plan; a seller-only close checklist in CRM is not mutual.

I introduce the plan as protection for the buyer's target date and build the first version with them during a live call.

• I anchor it to a customer event, such as onboarding a new team by October 1, rather than to my quarter end.
• I ask the buyer to supply internal owners and realistic review times, which turns the document into their plan as well as mine.
• If they will not validate dates or owners, I treat that as weak urgency and adjust qualification instead of silently maintaining the plan alone.

I build the demo around the buyer's highest-value workflows and decision criteria, not the product navigation.

• I open by restating the agreed problems and success measures, then show two or three workflows using the buyer's roles and data shape.
• I connect each capability to a quantified outcome, such as reducing approval time from five days to one, and confirm relevance before moving on.
• I leave unrelated features out because breadth dilutes the business case and creates objections the buyer did not have.

I involve a Sales Engineer once technical fit or risk affects qualification, not only when a demo is already scheduled.

• Triggers include integrations, data migration, architecture, security controls, or a proof of concept that I cannot scope accurately alone.
• I give the SE a written brief with business pain, stakeholders, decision criteria, known environment, and the decision the next session must enable.
• Early involvement costs scarce SE capacity, so I reserve deep work for qualified opportunities while using standard technical material for basic questions.

Success criteria must be observable, agreed before the evaluation, and linked to the customer's decision.

• A useful criterion is processing a representative data set in under two hours with SSO and audit logs enabled, not simply users liked the demo.
• I record who validates each criterion and what evidence counts, such as a test result, stakeholder sign-off, or measured workflow time.
• I also agree what happens after success, including the commercial meeting and approval step, so validation does not become an open-ended trial.

I qualify security requirements early and run the review as a dated workstream with the right technical owners.

• I confirm required standards and controls, such as SOC 2 Type II, SSO, data residency, encryption, retention, and incident notification.
• I provide current security documentation through the approved trust portal and route unanswered items to security or the SE instead of improvising.
• I track questionnaire, architecture review, exceptions, approver, and target completion separately because one unresolved exception can hold the contract.

I map dependencies and start independent reviews in parallel as soon as vendor preference and scope are credible.

• Security can often review architecture while legal marks up the MSA and procurement completes vendor onboarding.
• Commercial terms that affect the contract, such as liability, data processing, and payment schedule, need named owners before final redlines.
• Parallel work shortens cycle time but can waste specialist effort on weak deals, so I gate it on confirmed pain, sponsor support, and a realistic decision date.