Sales Forecasting & Pipeline Management interview questions

What a strong answer covers

• Each stage should have exit criteria based on something the buyer did, which is verifiable, rather than something the rep did, which is not.
• Examples include the buyer confirming a problem and a budget range, granting access to the economic buyer, agreeing an evaluation plan with dates, or starting a procurement or legal process.
• Stages should map to how customers actually buy in that business rather than to an internal sales ritual, and there should be few enough of them that reps apply them consistently.
• Consistency is the whole point: conversion rates, velocity and coverage are only informative if a stage means the same thing across every rep and every deal.
• A strong answer mentions that stage definitions need maintenance as the product, price point or buyer changes, and that stage inflation is the failure mode to watch for.

Where people lose the point

• ×Defining stages by seller activity such as demo delivered or proposal sent.
• ×Building so many stages that reps interpret them differently.
• ×Never revisiting the definitions as the business changes.

What a strong answer covers

• A weighted forecast applies a probability to each open deal, usually derived from stage, and sums them, which is mechanical and works well over a large pipeline and a longer horizon.
• A commit forecast is judgement-based: only deals the forecaster will stand behind this period sit in commit, with best case and pipeline categories holding the rest.
• Weighted numbers break down on small numbers of large deals, because no individual deal closes for a fraction of its value.
• Commit is normally more accurate in the current period because it prices deal-specific evidence, which is exactly what a stage-based probability cannot see.
• A strong answer runs both, using weighted as a check on pipeline shape and commit as the reported number, and notes that category names and definitions vary by company.

Where people lose the point

• ×Treating a weighted number as the forecast in an enterprise business with few, large deals.
• ×Allowing commit to become a category reps use for optimism rather than evidence.
• ×Not defining what commit means, so it means something different to each rep.

What a strong answer covers

• Coverage is the ratio of open pipeline value in a period to the quota or target for that period, used as a leading indicator of whether enough opportunity exists to hit the number.
• The appropriate ratio is derived from the business's own historical win rate and how quickly deals move, so it differs by segment, product and sales motion rather than being a universal figure.
• It is only meaningful if the underlying pipeline is clean, since stale deals and stage inflation manufacture coverage that does not exist.
• Coverage should be read by close date cohort and by segment rather than in aggregate, because healthy total coverage can hide a specific period or team that is short.
• A strong answer notes that coverage is a diagnostic to trigger action on pipeline generation early, and that reps who know it is measured can inflate it, which is why it is inspected rather than trusted.

Where people lose the point

• ×Quoting a fixed industry ratio as if it applied to every business.
• ×Reading coverage in aggregate and missing a short period or team.
• ×Trusting coverage without any pipeline hygiene behind it.

What a strong answer covers

• Ask about the economic buyer: who signs, whether the rep has met them, and what that person said in their own words about why this is happening.
• Ask about the compelling event: what forces a decision by this date, and what happens to the customer if it slips a quarter. A deal with no compelling event usually slips.
• Ask about the decision and paper process: who else has to approve, whether security, legal or procurement are engaged, and how long those steps have taken at this customer before.
• Ask about competition and the alternative, including doing nothing, and what the customer says would make them choose otherwise.
• A strong answer asks for evidence rather than assertion (a written mutual plan, an email confirming next steps, a meeting on the calendar) and moves the deal out of commit if the evidence is not there, while coaching the rep on the specific gap.

Where people lose the point

• ×Asking only what percentage the rep would put on it.
• ×Accepting they are really excited as a reason to keep the deal in commit.
• ×Challenging the number without helping the rep close the gap.

What a strong answer covers

• Deal with the pattern with data rather than impression: show what they committed versus what closed, and where the gap came from, which makes the conversation about a fixable habit rather than character.
• Work the current deals individually against evidence, because the fix is at deal level and a blanket haircut teaches nothing.
• Diagnose which failure it is, since happy ears, weak qualification, no access to the economic buyer and inability to say no to a customer are different problems with different coaching.
• Agree a specific standard for what belongs in commit and hold the next forecast to it, so the rep experiences the definition rather than being told about it.
• A strong answer separates the reported number from the coaching: adjust the roll-up so the business is not surprised, tell your own manager the adjustment and why, and keep working with the rep rather than quietly discounting them forever.

Where people lose the point

• ×Applying a percentage haircut to the rep's number and calling it managed.
• ×Passing their number up unchanged to avoid a difficult conversation.
• ×Treating optimism as dishonesty rather than diagnosing the underlying gap.

What a strong answer covers

• Find the reason and be specific: no compelling event, a procurement cycle nobody mapped, an unengaged economic buyer, or a customer who is polite rather than interested.
• Reset the close date to something the customer's own process supports rather than to the end of the next period, and record what has to be true for it to hold.
• Enforce a hygiene rule so deals cannot slip indefinitely, whether that is a limit on pushes before the deal is re-qualified or a defined close-lost reason, since chronic slippage is what makes coverage meaningless.
• Close deals as lost when they are lost. A no is more useful than an open deal that has not moved for two quarters, because it frees time and cleans the data.
• A strong answer looks at slippage in aggregate to spot whether it clusters by stage, segment or rep, since that points at qualification or process rather than individual deals.

Where people lose the point

• ×Pushing the close date to the next period without changing anything about the deal.
• ×Keeping dead deals open so the pipeline looks healthy.
• ×Treating every slip as a one-off rather than looking for the pattern.

What a strong answer covers

• Set the purpose explicitly: it is a risk and action conversation, not a status recital, and the data should be updated in the system before the call rather than during it.
• Spend the time where it changes outcomes: deals that moved category, deals with material risk, and anything new large enough to alter the quarter.
• Require evidence for commit deals as a norm, so that bringing evidence is routine rather than a sign of being singled out.
• Leave with actions and owners rather than adjectives, and make it safe to move a deal out, since a culture that punishes bad news guarantees late surprises.
• A strong answer separates the forecast call from deal strategy and coaching, which need a different format and more time than a roll-up allows.

Where people lose the point

• ×Reading the pipeline report aloud deal by deal.
• ×Making it punitive, which trains reps to hide risk until the final week.
• ×Trying to do deal coaching and roll-up reporting in the same meeting.

What a strong answer covers

• Quantify the gap and its composition first: how much is deals at risk, how much is pipeline that never existed, and what would have to close to recover.
• Escalate early with the number and the plan attached, since the damage from a miss is mostly in the surprise and in the decisions others made assuming the number.
• Work the recoverable part specifically: deals that could be pulled forward legitimately, stalled deals with a real path, and the constraints you could remove for the reps working them.
• Do not manufacture recovery through discounting or terms the business will pay for later, and say plainly if that is the only route available.
• A strong answer starts the next period's pipeline generation immediately rather than spending the whole quarter on rescue, and diagnoses the cause so the same gap does not repeat.

Where people lose the point

• ×Holding the number until the final weeks and hoping.
• ×Buying the quarter with discounting that damages the next one.
• ×Fighting for the current quarter while generating nothing for the next.

What a strong answer covers

• Age in stage and overall deal age, since a large pipeline full of deals that have not moved is not a pipeline.
• Stage-to-stage conversion rates, which show where deals actually die and whether qualification is happening early or late.
• Sales cycle length and velocity by segment, because a deal created too late to complete a normal cycle cannot close in the period regardless of its value.
• Distribution and concentration: how much of the number depends on a handful of large deals, and what happens to the quarter if the largest one slips.
• Creation rate against what is needed for future periods, plus data quality itself such as missing close dates or next steps, since bad data invalidates every other measure.

Where people lose the point

• ×Reporting total pipeline value with no aging or conversion view.
• ×Missing concentration risk in a small number of large deals.
• ×Analysing a pipeline whose underlying data quality has never been checked.