Business Development Representative interview questions

I want the strategy to state where pipeline should come from, why those accounts should care, and what we will stop doing.

• I define the ICP, priority segments, buying triggers, and the business problem each persona owns.
• I translate the revenue target into accepted opportunities, account coverage, and realistic BDR capacity.
• I set channel roles and clear exit criteria so a weak motion does not survive because the team is busy.

I choose the motion from deal economics and how the buyer actually evaluates change, not from the team's favorite channel.

• High-ACV enterprise accounts justify research, multi-threading, and close BDR-AE collaboration across a smaller account set.
• A transactional segment needs broader coverage, stronger automation, and a short path from response to qualification.
• I pilot one narrow segment first and compare accepted pipeline per hour before scaling headcount or tooling.

The ICP should be jointly governed by sales, marketing, RevOps, and customer evidence, with one named decision owner.

• I use closed-won, closed-lost, retention, and sales-cycle data to separate attractive logos from customers we can win and keep.
• Proposed changes include the affected segment, evidence, routing impact, and what current work will be deprioritized.
• I review the model on a regular cadence, but I allow an urgent change when product or regulatory conditions invalidate an assumption.

I refresh the ICP when downstream quality changes, not just when top-of-funnel response softens.

• A falling sales-accepted rate, longer sales cycle, or poor retention in one cohort says the fit assumption may be wrong.
• Repeated objections can reveal a missing buying trigger or a persona that feels the pain but cannot fund the solution.
• I compare those signals with product and market changes before rewriting scoring rules or account lists.

I keep tiering simple enough to drive a different action for each tier.

• Fit covers durable facts such as industry, company size, geography, and technical environment.
• Timing covers change signals such as hiring, funding, leadership moves, or a relevant compliance deadline.
• Tier one earns manual research and multi-threading, while lower tiers use lighter personalization and broader coverage.
• I audit conversion by tier so the score is judged by accepted pipeline, not by how sophisticated the model looks.

I vary the cost of pursuit and depth of coordination to match expected deal value and buying complexity.

• SMB needs fast qualification, standardized messaging, and tight limits on research time per account.
• Mid-market supports some account research and persona branching, but still needs repeatable sequences to preserve coverage.
• Enterprise requires named-account planning, multiple stakeholders, executive context, and an AE engaged before the first meeting.

A useful territory balances opportunity potential and workload, not just the number of accounts.

• I model reachable accounts by ICP tier, expected conversion, deal value, language, and time-zone constraints.
• I keep named-account ownership stable long enough for multi-threading to work, with explicit rules for dormant accounts and transfers.
• I review attainment and coverage by territory to find structural imbalance before blaming individual performance.

I prevent conflicts with one CRM ownership model and rules that reflect the buyer journey.

• Named accounts, active opportunities, recycling windows, and event follow-up each need an explicit owner and expiration rule.
• Routing logic should be visible in Salesforce and exceptions should go through RevOps, not private spreadsheets.
• I track duplicate touches and reassignment disputes because both reveal where the operating model is unclear.

I size the reachable market against the rate at which the team can work accounts without exhausting them.

• I remove customers, active opportunities, poor-fit firms, restricted contacts, and accounts with no usable buying trigger from the headline TAM.
• I estimate accounts consumed per rep from cadence length, recycle policy, and the depth required by each tier.
• If the same accounts must be recycled too often to support quota, I change the segment, target, or team size before hiring.

I give each channel a specific job in the conversation rather than repeating the same pitch everywhere.

• Email carries a concise business case and creates a durable reference the prospect can forward.
• Phone tests urgency and objections quickly, while LinkedIn helps establish context and reach contacts who ignore email.
• Async video is reserved for high-value accounts where visual proof or tailored research justifies the production time.
• I compare incremental accepted opportunities by channel, not vanity engagement such as views or likes.

Cold calling remains valuable when it is targeted and used to learn, not treated as a volume ritual.

• It gives fast feedback on whether the problem, persona, and timing signal are credible.
• I prioritize direct dials for accounts with strong fit or intent instead of forcing equal call volume across every list.
• Connect-to-conversation and conversation-to-meeting matter more than raw dials because they expose data quality and message quality separately.

Deliverability is a design constraint, so I protect domain reputation before trying to maximize send volume.

• I use verified business contacts, controlled sending patterns, clear identity, and simple messages without unnecessary tracking or heavy assets.
• I separate genuine negative replies from bounces and spam complaints because they point to different fixes.
• If reputation falls, I reduce volume and repair list quality rather than hiding the problem with more domains.

I use async video when showing specific insight is more persuasive than describing it in another email.

• It fits strategic accounts where a tailored workflow, product gap, or account observation can be demonstrated in under a minute.
• I template the structure but not the evidence, so the video remains personal without taking twenty minutes to produce.
• I judge it by meetings and accepted opportunities from the target cohort, not by video plays.

I organize sequences around stable combinations of segment, persona, and buying trigger instead of letting every rep create a private cadence.

• A core sequence carries the proven message for a common use case and gives the team a comparable baseline.
• Triggered and strategic-account sequences allow deeper context where timing or deal value supports it.
• Each sequence has an owner, intended audience, version history, and retirement rule so the portfolio stays governable.

I retire a sequence when its downstream yield no longer justifies the accounts and rep time it consumes.

• I require enough volume to separate a weak message from random variation, then inspect positive replies and sales acceptance by cohort.
• A sequence can also be retired because the trigger expired, the product changed, or the same audience has been overworked.
• The team records the reason and preserves the learning so a failed idea is not relaunched under a new name next quarter.

I change one meaningful element for a comparable audience and choose the decision metric before launching.

• The test might compare two problem frames or calls to action, not five simultaneous changes across different lists.
• I keep sender mix, segment, and timing balanced so rep quality or account quality does not decide the winner.
• Positive reply and accepted-opportunity conversion beat open rate, which is noisy and often distorted by privacy features.

I spend personalization time where better context has enough expected pipeline value to repay it.

• Deal value, ICP fit, a credible trigger, and access to multiple stakeholders raise the case for manual research.
• Lower-value accounts get relevant segment and persona language, but not fake personal details copied from a profile.
• I compare accepted pipeline per rep hour across tiers, because reply rate alone can reward expensive work that does not convert.

I split sequence standards only when buyer behavior or sales economics differ enough to justify separate operating rules.

• I compare reply quality, accepted-opportunity rate, cycle length, and unsubscribe risk by segment rather than relying on activity volume.
• Enterprise accounts may need slower, researched multi-threading, while a high-volume SMB motion can support more automation and faster tests.
• I keep shared compliance and CRM rules across every segment so customization does not create an ungoverned sequence library.

Good multi-threading builds a relevant case with several people without making the account feel spammed.

• I map the likely problem owner, operational user, economic buyer, and blocker, then give each a message tied to their role.
• Touches are coordinated in the CRM so contacts receive complementary context rather than duplicate copy on the same day.
• A response from one stakeholder changes the plan for the others, especially when they name the real owner or an active initiative.

I work backward from required revenue using observed funnel conversion and expected opportunity value.

• The model moves from pipeline target to accepted opportunities, held meetings, positive conversations, and reachable accounts.
• I use segment-specific conversion because enterprise and SMB cannot share one productivity assumption.
• I include ramp, leave, AE acceptance capacity, and list supply before turning the result into headcount or quota.