Sales Representative interview questions

Owning a full-cycle sale means I am accountable from target account selection through signed contract and handoff.

• I create or accept the opportunity, run discovery, qualify it, demonstrate the solution, negotiate, and close.
• At every stage I secure a buyer action and record evidence in the CRM rather than advancing on seller activity alone.
• After signature I give implementation or customer success the goals, stakeholders, promises, and risks captured during the deal.

I turn the quota into an account-level plan based on potential, timing, and the pipeline I need to create.

• I segment the territory by ideal customer profile, company size, use case, and buying signals, then name the highest-potential accounts.
• I compare current qualified pipeline with the coverage required for my historical win rate and calculate the remaining prospecting gap.
• I assign weekly account and pipeline targets, then review conversion and coverage every week rather than waiting for month end.

I segment accounts by expected value and likelihood to buy so effort follows opportunity, not just account size.

• Fit includes industry, headcount, geography, technology, and the problems our strongest customers already solve with us.
• Intent includes hiring, funding, leadership changes, product launches, contract renewal dates, and engagement with our company.
• I use tiers with different service levels, such as one-to-one research for tier one and lighter sequences for lower tiers.

I prioritize accounts where strong fit overlaps with a timely reason to change.

• I score fit against the ICP and add observable triggers such as expansion, a new executive, or a known contract deadline.
• I check relationship paths, prior opportunities, product usage, and relevant contacts before treating an account as cold.
• I refresh priorities weekly because a high-fit account without timing should not crowd out one showing active demand.

I protect time for both, using stage risk and pipeline coverage to set the split.

• Near-term qualified deals receive the work required to reach their next buyer commitment, not unlimited follow-up.
• If coverage is below the level implied by my win rate, I increase daily prospecting blocks until the creation gap closes.
• I keep prospecting on the calendar even in a busy closing week because stopping today creates an empty quarter later.

A relevant outbound message links a specific business signal to a problem I can credibly help solve.

• I open with an observation about the account, not generic praise or a paragraph about my company.
• I state one likely consequence in the buyer's language and support it with a short, comparable customer result.
• I ask for a small next step, usually a brief conversation to test whether the issue is real, rather than forcing a demo.

I use a planned sequence of calls, emails, and social touches that adds a new reason to respond over time.

• A typical cadence runs for two to three weeks, with denser touches early and enough spacing to avoid repetitive noise.
• Each touch changes the angle, such as a trigger, a quantified problem, a customer example, or a useful resource.
• I track replies, conversations, meetings, and opportunities by channel and persona, then adjust the sequence from conversion data.

I open a cold call with context, permission, and a concise reason the conversation may matter.

• I identify myself, mention the account-specific trigger, and ask for roughly 30 seconds instead of pretending the call is warm.
• I describe a problem seen in similar companies and ask whether it is relevant before pitching features.
• If the buyer engages, I move into two or three discovery questions and agree a proper follow-up rather than forcing a full demo.

I match personalization effort to account value and use information that changes the sales hypothesis.

• Tier-one accounts get research on strategy, stakeholders, current tools, and a trigger that supports a tailored point of view.
• Lower tiers use segment-level pain and reusable proof, with only the account and persona details that affect relevance.
• I avoid decorative personalization such as hobbies because it consumes time without explaining why the buyer should change.

I judge outbound by pipeline created, then use activity and conversion metrics to find where it is breaking.

• I track accounts worked, connects, positive replies, meetings held, qualified opportunities, and sourced pipeline value.
• Conversion by persona, segment, message, and channel is more useful than one blended reply rate.
• I also watch meeting-to-opportunity conversion because high booking volume with weak qualification wastes closing capacity.

Self-sourced pipeline is qualified opportunity value created by my own prospecting rather than handed to me as an inbound lead.

• I count it only after the account meets the same qualification and stage-entry rules as any other opportunity.
• The CRM source, originating activity, creator, and opportunity value must be recorded consistently so attribution is auditable.
• I report both the amount and percentage of total pipeline because $300K means different things against different territories and quotas.

I calculate the gap between required pipeline and the qualified pipeline expected from inbound or partner sources.

• Required pipeline starts with the revenue target divided by the relevant historical win rate, adjusted for deals already open.
• I convert the remaining value into opportunities using average deal size, then into meetings using meeting-to-opportunity conversion.
• I spread those targets across the weeks left in the period and add an early buffer because late-created deals may miss the sales cycle.

Discovery determines whether a meaningful business problem exists and whether both sides should invest in a sales process.

• I learn the current process, pain, measurable impact, desired outcome, stakeholders, timing, and decision path.
• I test assumptions with follow-up questions instead of treating the call as a form to complete.
• The call ends with a mutually agreed next step tied to what we learned, or a clear disqualification if there is no fit.

I structure discovery around context, diagnosis, impact, buying process, and an agreed next step.

• I confirm the agenda and the buyer's reason for taking the meeting before asking about their current state.
• I move from broad process questions to specific pain, consequences, priority, and what a successful outcome would change.
• I summarize the buyer's words, check that I understood correctly, and reserve time to decide whether another meeting makes sense.

The best discovery questions expose how the current process works, where it fails, and what that failure costs.

• I ask what happens today, who is affected, how often the issue occurs, and what workaround the team uses.
• I follow with the effect on revenue, cost, risk, customer experience, or employee time and ask for available numbers.
• I ask why the problem deserves attention now and what happens if nothing changes this quarter.

I turn pain into a buyer-owned business impact using their volumes, rates, and costs.

• If a manual task takes 20 hours a week across five employees, I confirm the loaded labor cost instead of inventing a savings figure.
• For revenue problems, I examine volume, conversion, deal value, and delay to estimate the size of the missed outcome.
• I restate the calculation and ask the buyer to correct it, then record both the number and its source in the CRM.

Discovery is complete enough when I can explain the problem, impact, priority, buying path, and reason for the next step using buyer evidence.

• The buyer has confirmed a concrete outcome and why maintaining the status quo is costly or risky.
• I know who is involved, what decision criteria matter, and what event or deadline shapes timing.
• Both sides have accepted a dated next action, such as a tailored demo with the required stakeholders.

BANT covers Budget, Authority, Need, and Timeline, and I use it as a guide rather than a rigid interrogation.

• Need comes first because budget and executive attention usually follow a problem with measurable impact.
• Authority means understanding the decision roles, not demanding access to one person called the decision-maker.
• Budget and timeline are explored through funding process, competing priorities, approval dates, and the cost of delay.

BANT can identify basic fit, but it is too shallow for deals with created budgets, committees, and complex approvals.

• A prospect may have a serious need before a formal budget exists, so rejecting them on that field alone loses valid opportunities.
• The framework does not fully test measurable impact, decision criteria, internal champion strength, or procurement process.
• I keep BANT for an initial screen and add deeper qualification as deal size and stakeholder complexity increase.

Beyond BANT, I qualify the economics, decision mechanics, internal support, competition, and evidence required to win.

• I identify the metric the buyer wants to move and who owns the financial or operational result.
• I map decision criteria, approval steps, procurement, legal review, stakeholders, and the target decision date.
• I test whether a champion will sell internally and whether the real competition is another vendor, an internal build, or no decision.