Business Development Representative interview questions

A useful ICP tells me which accounts are both likely to buy and worth the cost of pursuing.

• It names observable firmographic limits such as industry, employee band, geography, and revenue.
• It includes operational signals, such as the relevant technology, sales motion, or compliance burden, that connect to our product's value.
• It also defines exclusions, because a clear reason not to prospect prevents wasted activity.
• I validate it against accepted opportunities and wins rather than treating the sales team's intuition as proof.

I separate fit from timing so a fashionable trigger cannot make a poor-fit account look qualified.

• Fit points cover stable attributes such as segment, geography, use case, and required technology.
• Timing points cover recent signals such as hiring, funding, leadership change, or a relevant product launch.
• I weight criteria using conversion history and cap correlated signals so company size and revenue do not count the same fact twice.
• The output should create simple tiers with a visible reason code, not a mysterious score that reps cannot use.

The right firmographics are the ones that change need, buying capacity, or sales complexity for the product.

• Employee count or revenue usually provides a size band, but I use the measure that best predicts contract value in our history.
• Industry and geography can expose regulatory needs, language constraints, and whether we can legally or operationally serve the account.
• Business model and growth stage often explain workflows better than a generic industry label.
• I avoid adding criteria merely because ZoomInfo provides them; each field needs a link to conversion or disqualification.

Technographics help me infer a compatible environment, a replacement opportunity, or a specific integration need.

• A complementary tool can prove the prospect has the workflow and technical maturity our product requires.
• A competitor can support a displacement message, but only if we know the switching pain and contract timing.
• Job posts and public documentation often provide fresher evidence than a vendor's technology-detection field.
• I verify important signals before personalizing because stale technology data quickly makes an email look careless.

I compare score bands with downstream conversion, not just email engagement.

• I look at positive replies, held meetings, sales acceptance, and opportunities by tier over a meaningful period.
• A useful model should show a clear lift from lower to higher bands after controlling for territory and rep coverage.
• I review false positives and false negatives with AEs to find criteria that are overweighted or missing.
• RevOps should version changes so we can compare the new model with the old one instead of rewriting history.

Segmentation lets the message reflect a shared problem without forcing one-to-one research on every account.

• I split where pain, proof, persona, or buying process materially changes, such as SMB self-service versus enterprise procurement.
• Each segment needs enough accounts to measure, so I do not create tiny groups for cosmetic differences.
• The sequence can then use the segment's language, customer evidence, and call-to-action.
• I compare segment conversion to confirm the extra operational complexity earns better pipeline.

I tier accounts by expected value and likelihood to convert, then match effort to the tier.

• Tier 1 receives deeper research, account mapping, and coordinated touches because the potential contract justifies the time.
• Tier 2 gets segment-level personalization with selected account signals.
• Tier 3 uses a lighter, scalable motion and serves as a place to test broad messaging.
• I set capacity limits per tier so the plan reflects the number of accounts a BDR can genuinely work, not the size of the database.

Account segmentation decides which companies deserve attention, while persona segmentation decides whom to contact and what each person values.

• An economic buyer may care about risk and return, while an operator cares about workflow and adoption.
• The same title can play different roles by company size, so I map responsibilities rather than relying only on job titles.
• I adjust proof and calls-to-action by persona but keep one coherent account-level problem.
• Persona results are measured by positive replies and progression, not opens alone.

I prioritize a territory from account potential, current timing, and coverage capacity.

• ICP fit and estimated value establish the base account rank.
• Trigger events and intent signals can move a good-fit account forward, but they do not rescue a bad fit.
• Existing ownership, open opportunities, customer relationships, and suppression rules prevent conflicting outreach.
• I keep a next-best-account view in the CRM so daily execution follows the territory plan rather than whichever list is newest.

A trigger event is a recent change that creates a plausible reason for the account to revisit a problem now.

• Examples include a new executive, funding, rapid hiring, expansion, a product launch, or a regulatory deadline.
• The event is useful only when I can connect it to a likely business consequence our product addresses.
• I cite the consequence rather than congratulating the prospect and immediately pitching.
• Triggers decay, so the source date and outreach window belong in the workflow.

I rank triggers by relevance to our use case, evidence strength, and how quickly the buying window may close.

• A mandatory compliance deadline usually has more urgency than a generic hiring post.
• First-party actions such as a pricing-page visit may show interest, while public events explain the business context.
• I combine the trigger with ICP fit and persona access before increasing outreach effort.
• I track accepted opportunities by trigger type so the ranking improves from observed results.

Every trigger should carry a source date, confidence level, and expiration rule.

• I use the event's natural window: leadership changes may stay relevant for weeks, while event attendance becomes stale much faster.
• Automation can queue accounts, but a BDR should verify the source before using the detail in a message.
• Expired signals should lower priority or be removed so old news does not keep recycling through sequences.
• I feed incorrect sources back to RevOps or the data vendor rather than silently fixing only my record.

A strong sequence coordinates a clear hypothesis, several channels, and a deliberate progression of messages.

• The opening touch connects a relevant account or persona signal to one business problem.
• Later touches add new proof, a different angle, or a useful question instead of repeating the first email.
• Calls, voicemail, email, and LinkedIn each have a defined role rather than appearing as an activity quota.
• Exit rules stop the sequence after a response, disqualification, opt-out, or ownership change.

I use channels for their different strengths instead of copying the same pitch everywhere.

• Email carries a concise, easy-to-forward business case and relevant proof.
• A call tests the hypothesis quickly, uncovers context, and handles an objection in real time.
• LinkedIn helps verify role changes, build familiarity, and engage with relevant public activity without pitching in every interaction.
• Voicemail can give the next email context, but only when the message is short and specific.

I set cadence from the segment's urgency, channel mix, and normal buying rhythm rather than using one universal template.

• A time-sensitive trigger supports tighter early touches, while strategic enterprise accounts need more space for research and internal forwarding.
• I avoid stacking several automated touches on the same day because it feels mechanical and can hurt deliverability.
• The sequence should be long enough to test multiple angles but have a clear stop date.
• I review reply timing and unsubscribe patterns to adjust spacing with evidence.

An effective opening earns permission to continue by being relevant and brief.

• I identify myself, state the specific reason for calling, and connect it to the prospect's role or account signal.
• I avoid pretending the call is warm or hiding behind vague phrases such as checking in.
• A focused question tests whether the problem exists before I explain the product.
• I log the objection or context in structured CRM fields so the call improves later touches and segment learning.

LinkedIn should add context and familiarity, not become a second inbox for the same automated pitch.

• I use profiles and activity to confirm responsibilities, tenure, priorities, and changes in the buying group.
• A connection note stays short and relevant; I do not force the full value proposition into it.
• Thoughtful engagement with a prospect's public post can create a natural opening when the topic relates to our problem.
• I record material interactions in the CRM so the rest of the account team sees the complete cadence.

I match personalization effort to account value, signal strength, and the repeatability of the insight.

• Tier 1 accounts may justify manual research into initiatives, leadership priorities, and the buying committee.
• Mid-tier accounts work well with a verified trigger plus persona-specific proof.
• Scaled accounts should use segment relevance, not fake one-to-one lines generated from weak data.
• I judge personalization by positive replies and opportunity creation per hour, because relevance that cannot scale has a real cost.

Account mapping is a working view of the people, relationships, and decision roles around a target problem.

• I capture likely users, technical evaluators, champions, economic buyers, procurement, and blockers when relevant.
• For each contact I note role, influence, current stance, source, and the next useful action.
• Reporting lines, recent moves, and prior company relationships help identify warm paths and missing coverage.
• The map lives in shared CRM data or an agreed account plan, not only in a BDR's private notes.

I start from the problem and trace who feels it, evaluates a solution, controls budget, and can block change.

• Similar won deals provide a role pattern, but I adjust it for the account's size and operating model.
• Job descriptions, org charts, earnings calls, and LinkedIn tenure help test who owns the relevant outcome.
• Discovery with one contact should confirm who else is affected and how decisions are made.
• I mark role confidence instead of presenting guessed titles as facts.