What a business development loop really tests: pipeline, numbers and attribution
The pipeline walkthrough is the round that decides it. Somewhere in the second or third stage a hiring manager says “walk me through your current pipeline” and then goes quiet for ten minutes, and what happens in those ten minutes settles the loop. Most lists of business development manager interview questions treat that as one item among forty. It isn’t one item. It’s the interview.
Here’s the loop grouped by what each stage is testing, and where candidates lose it.
BD interviews look like sales interviews and score differently
The problem starts with the title. There is no business development manager page in the BLS Occupational Outlook Handbook, which tells you something useful: depending on the company, the job is quota-carrying new-logo sales, or partnerships and channel, or a research-and-outreach function that hands qualified meetings to somebody else.
I pulled two BLS pages on 6 September 2026 to see how wide that spread really is. Sales managers show a 2025 median wage of $148,270 with roughly 4% projected growth through 2035. Wholesale and manufacturing sales representatives sit at $72,080 for non-technical products and $104,920 for technical ones, with employment projected to stay roughly flat and about 123,400 openings a year from churn. BD titles get paid across that entire range. The same two words on a job board can mean a $70k outbound seat or a $150k number-carrying one.
Which is why the first thing to establish is which of those jobs is being hired. Ask in the recruiter screen: is this role carrying a new-business number, or is it partnership-led? The answer changes what you prepare, and asking early reads as commercial maturity rather than confusion.
The pipeline walkthrough, and what they’re listening for
The prompt is some version of: walk me through your pipeline. The follow-ups are all “and then what happened”.
Stages with definitions attached. “I’ve got 14 opportunities” says nothing. “Six at discovery, four with a business case in front of a buying committee, three in procurement, one verbal” says you run a process.
Deal size, stage, expected close, and what you did last week to move each one. That last part is where it comes apart for a lot of people. Movement is the evidence; the rest is a spreadsheet.
Honest attrition. If everything in your pipeline is progressing, you’re either lying or you aren’t prospecting hard enough, and an experienced interviewer will read it the second way and probe until it becomes the first.
A named next action per deal. Not “following up”. “Their CFO joins on the 12th, I’ve sent the security questionnaire ahead of that.”
If you can’t name accounts, say so and use descriptors. A 400-person logistics company in the Midwest is a perfectly good stand-in. Refusing to name customers is expected and fine. Being vague about the mechanics is not.
Business development manager interview questions about numbers you personally moved
This is the cluster that separates people, and it’s mostly arithmetic you should know cold.
What was your quota and what did you attain? Say both numbers. If you missed, say by how much, why, and what changed afterwards. A miss with a diagnosis attached lands better than an attainment figure with no context.
How much of that was inbound? They’re separating pipeline you generated from pipeline you were handed. Give a split even if it’s approximate. “Roughly 60/40 inbound to self-sourced” is an answer. “A mix” is not.
What was your average deal size and cycle length? If these aren’t in your head, that itself is the answer the panel receives. Work them out the night before.
Which of those deals would have closed without you? Occasionally asked, always revealing. The honest answer earns more than the flattering one, and there is usually at least one.
Partnerships versus direct sales
Two different jobs sharing a title, and interviewers test the boundary directly.
What’s the difference between a reseller, a referral partner and a technology partner? If you’re going for a partnership seat and can’t answer this cleanly, the loop ends in that room.
How do you know a partnership is working? Sourced pipeline and influenced revenue, with a date by which you’d expect the first sourced deal. Partnerships that produce a press release and nothing else are the standard failure, and any interviewer who has run partnerships has lived through two or three of them.
Would you rather sign one large partner or ten small ones? No correct answer. They’re checking whether you cost out enablement. Ten partners means ten sets of training, collateral and account mapping, and plenty of companies can’t service that with the headcount they have.
The cold-outreach exercise
Some loops set a take-home: here’s the ICP, write five emails. Others do it live. “I’m a VP of Operations at a logistics company. Call me.”
The live version is harder and more common than candidates expect. Four things get marked.
Whether you earn the next 20 seconds. The opener has to give a reason for this call, to this person, now.
Whether you ask before you pitch. Two questions before any product mention.
Whether you survive the brush-off. “Send me something” is the test. The good move is one qualifying question before you agree, so the thing you send is worth opening.
Whether you close on a specific next step with a day and a time in it.
For the written version: shorter than feels right, one idea, one ask, and no opening paragraph about how much you admire their recent funding round. Everyone writes that paragraph. It reads as a mail merge because it usually is one.
Over-claiming, and how interviewers catch it
The most common way BD candidates lose a loop they were qualified for is by claiming team results as personal ones.
It’s rarely deliberate. You say “we grew the region 40%” because that’s how the number got talked about internally. The interviewer hears an unattributed figure and starts probing. How big was the team. What was your territory. What was your individual number. Who else touched those accounts. Three questions in, the 40% turns out to be six people’s work, and now you look like you were inflating even though you weren’t trying to.
The fix is boring. Attribute first, then claim. “The region grew 40%. I carried the enterprise segment inside it, which was 11 of the 34 closed deals and about $1.2M of the $4.1M.” Nobody minds that the team did well. They mind not being able to work out what you did.
The second version of this is influence. “I built the partnership with X” where you actually attended the meetings and wrote the follow-ups. Interviewers who have done the job spot it in about two questions, and getting caught costs far more than the smaller honest claim would have.
I’d argue the whole attribution problem is a writing problem rather than an ethics one. People describe their work the way their old team described it, and their old team was describing a collective effort to itself. Rewrite your last two years in the first person singular before you interview and most of it fixes itself.
What to ask them, and how to spend the last week
Ask about the pipeline that already exists, because you’re inheriting it.
Where did last year’s closed revenue actually come from? Inbound, outbound, partners, expansion. If it’s 80% inbound and you’re being hired to build outbound, that’s a two-year project, not a quota year.
What’s the ramp, and what’s expected at day 90? Then ask what the last two hires actually hit.
Who owns the SDR function, and do I get support? Self-sourcing everything at an enterprise deal size is a different job to the one in the description.
What happened to the last person in this seat? Ask it plainly. The pause is informative.
For the week itself: rebuild your numbers from whatever system you had access to, write your pipeline out on one page in the format above, and pick three deals you can narrate for four minutes each, including one you lost. Then rehearse out loud, and get interrupted while you do it, because a hiring manager will cut into your pipeline walkthrough on the second deal and candidates who rehearsed uninterrupted lose their thread.
That’s the specific thing Craqly’s mock interview mode is built for. It runs on your desktop, asks questions out of order, cuts in when an answer runs long, pushes on the part you skipped, and gives you a transcript afterwards so you can see your own answer lengths and talk-to-listen ratio. The free Starter plan is 20 credits a month, one credit being one minute of live session, and credits reset every month. Paid plans start at $19 a month billed yearly, or $38 month to month, checked on 6 September 2026.
Worth reading alongside this: the sales representative questions for the quota and objection rounds, our cold calling notes for the live outreach exercise, and the STAR method guide for the behavioural half of the loop.
Bring one page with your real numbers on it and be willing to say the bad ones out loud. That single habit does more for a BD loop than any answer you can memorise.
