Sales Manager interview questions

I start with the sources of revenue, because one growth target can hide very different sales jobs.

• I separate new business, expansion, renewal, and any channel contribution so each has its own owner and assumptions.
• I use recent conversion, deal size, and cycle data as a baseline, then adjust only for named changes such as a new segment or product.
• I make dependencies on marketing, product, and customer success explicit rather than burying them inside the sales target.

I show both views side by side and treat the gap as a decision, not as a spreadsheet error.

• The bottom-up view comes from productive headcount, ramp, realistic attainment, and expected pipeline by segment.
• If it falls short, I price the available choices: more hiring, better conversion, higher average value, more time, or a lower target.
• I will support an ambitious stretch, but I keep the committed forecast anchored to capacity the business can actually fund and execute.

I phase the target around when revenue can realistically close, not around a tidy calendar split.

• I account for seasonality, renewal dates, procurement cycles, and the current pipeline already likely to land early in the year.
• New hires contribute according to their ramp curve, so planned headcount does not appear as full capacity on day one.
• I keep a separate view of bookings and recognized revenue when contract timing makes those curves different.

I focus on assumptions that compound through the model or have no clear owner.

• Small changes in win rate, average deal value, or sales cycle can create a large capacity claim, so I compare them with cohort history.
• A new product or market gets a conservative base case until there is evidence from qualified demand, not just a large addressable market.
• I record an owner and review date for each material assumption so the plan can be revised before a miss becomes inevitable.

A useful capacity model converts funded roles into productive selling time and attainable revenue.

• I model filled seats, hiring dates, attrition, ramp by cohort, leave, and expected attainment rather than multiplying quota by planned headcount.
• Capacity is split by role and segment because an enterprise AE, an SMB rep, and an overlay do not produce revenue in the same way.
• I reconcile the model to actual output each quarter so it becomes a planning instrument, not an annual finance artifact.

Theoretical capacity is quota on seats; productive capacity is what staffed and ramped sellers can reasonably deliver.

• Open roles contribute nothing, and new hires contribute only along an observed ramp curve.
• Even tenured reps rarely produce at exactly quota, so I use an attainment distribution rather than assuming everyone reaches 100 percent.
• That more conservative view prevents us from funding expenses against revenue that exists only in the org chart.

I derive coverage from conversion and timing by segment instead of applying one company-wide multiple.

• If a segment closes one in four qualified opportunities, roughly four times coverage is a starting point, not a guarantee.
• I adjust for stage mix, deal concentration, cycle length, and whether the pipeline can still close inside the period.
• I review coverage alongside creation rate, because a healthy opening balance can hide a pipeline problem for the next quarter.

A credible quota sits where market opportunity, seller capacity, and the compensation budget can all support it.

• I start with the revenue target and cost envelope, then test the implied attainment against historical distributions and territory potential.
• Quota must be high enough to fund target earnings but not so inflated that only a small minority can reach it.
• I document what changed from the prior year so managers can explain the number rather than present it as a finance decree.

I allocate quota against measurable opportunity, then use judgment where the data is incomplete.

• I compare account potential, whitespace, renewal base, historical production, and local sales cycles rather than splitting the target evenly.
• Existing account value and net-new opportunity are separated so a mature book is not confused with easy growth.
• Before finalizing, I inspect outliers with frontline managers and publish the logic so perceived fairness does not depend on private negotiation.

I change quotas only when the underlying opportunity or role has materially changed, not merely because results are behind plan.

• A territory split, product withdrawal, major account transfer, or delayed start date can justify a documented adjustment.
• Normal execution risk and a difficult quarter remain part of the original commitment.
• Any exception follows one policy and includes compensation treatment, otherwise the loudest manager gets the best deal and trust collapses.

I choose the unit that best matches how customers buy, then build territories around comparable opportunity.

• Geography works when coverage and local relationships matter; industry or account tier works better when expertise and buying complexity drive wins.
• I size potential with account and market data, but I also test travel, language, partner coverage, and seller workload.
• The design must leave clear ownership, because a mathematically balanced map still fails if two teams can claim the same buyer.

I rebalance midyear only when structural unfairness is large enough to outweigh the cost to customer relationships and seller focus.

• I separate a weak territory from weak execution by comparing potential, penetration, cycle length, and rep tenure.
• If the gap is temporary, I prefer overlays, lead support, or a quota adjustment to moving active accounts.
• When a move is unavoidable, I protect open deals with named ownership, compensation rules, and a joint customer handoff.

I use differences in buying motion and service cost, not an arbitrary employee-count label alone.

• Typical deal value, stakeholder count, security and procurement needs, sales cycle, and expansion potential tell me when a distinct motion is justified.
• The boundaries must be simple enough for routing and stable enough for teams to learn their segment.
• I review accounts near the boundary for economics, because moving them upmarket can add expensive coverage without improving win rate or retention.

I add an overlay when scarce expertise materially improves complex deals without obscuring account ownership.

• A product, industry, or technical specialist makes sense when a generalist cannot build enough depth across every opportunity.
• The account executive still owns the commercial outcome, while the overlay has explicit entry criteria and credit rules.
• If the specialist joins routine deals or creates duplicate customer contact, the extra coordination cost is greater than the expertise gained.

I optimize account moves for customer continuity first and internal fairness second.

• Ownership changes happen on a defined calendar unless customer risk requires an exception.
• Open opportunities have clear credit and transition rules so the outgoing seller is not punished for creating value.
• The customer gets one named handoff with context, while CRM history and next commitments move before the new owner takes contact.

Commit means there is buyer evidence for closing in the period, not that the rep feels confident.

• I expect a confirmed business problem, decision process, commercial path, and a dated next step with the buyer.
• Legal, security, procurement, and budget risks must have owners and timelines rather than vague green status.
• The definition stays consistent across teams so leadership can aggregate commit without translating each manager's private language.

I use a light weekly operating cadence and reserve deeper reviews for changes that need a decision.

• Reps update customer facts before the meeting; the meeting is for risk, help, and movement between forecast categories.
• Frontline managers own deal inspection, while the senior review looks for cross-team patterns and material changes to the number.
• I avoid asking the same deal story at three levels, because duplicate inspection drives CRM theater instead of better judgment.

Manager judgment should challenge the model with customer evidence, not replace data with intuition.

• I compare the rep's category with stage history, slippage, activity quality, and what the buyer has actually confirmed.
• Any override carries a short reason so we can later learn whether the manager saw a real signal or repeated a bias.
• When data and field judgment disagree, I often show a range rather than force false precision into one number.

I measure accuracy, bias, and stability together so a cautious miss is not mistaken for good forecasting.

• Accuracy shows distance from actuals, while bias reveals whether a manager consistently calls high or low.
• I track how the forecast changes through the period, because a perfect call made on the last day has little planning value.
• The review focuses on recurring causes such as weak exit criteria or procurement timing, not punishment for every honest change.

I use a range when a few unresolved outcomes can materially move the period and the uncertainty is real.

• The lower bound reflects business with strong buyer evidence; the upper bound adds named upside with clear dependencies.
• I explain which assumptions move us through the range rather than presenting it as statistical decoration.
• As the period advances, the range should narrow, and failure to narrow is itself a signal about process quality.