Business Development Representative interview questions

An outbound BDR creates qualified sales opportunities by starting conversations with prospects who have not asked to be contacted.

• I identify accounts and people that match the ideal customer profile instead of contacting everyone.
• I use calls, email, and social touches to learn whether there is a relevant problem and enough interest for a meeting.
• I pass qualified context to an Account Executive and track conversion to accepted opportunities, not just activity volume.

An ICP describes the type of company most likely to get value from the product and become a good customer.

• It usually includes firmographic criteria such as industry, company size, geography, revenue, and technology used.
• It also includes business conditions, such as a problem the product solves or a team mature enough to adopt it.
• I use the ICP to choose accounts, while a buyer persona helps me choose the right people inside those accounts.

A buyer persona describes a relevant person inside an ICP-fit company, including their goals, problems, and role in a purchase.

• The ICP tells me which companies to target; the persona tells me whom to contact and what message may matter to them.
• A Head of Sales may own the business outcome, while Sales Operations may evaluate workflow and integrations.
• I adapt the value proposition and proof point to the persona instead of sending the same pitch to every title.

An account is the company I may sell to, while a contact is an individual associated with that company.

• Account data includes industry, employee count, location, and current technology.
• Contact data includes title, seniority, responsibilities, email, phone, and LinkedIn profile.
• Salesforce links several contacts to one account so the team can see the full buying group and avoid duplicate outreach.

I look for evidence that the company matches our firmographic criteria and has a problem our product can solve.

• Firmographic fit might mean a SaaS company with 100 to 1,000 employees in a supported market.
• Operational fit could be a growing sales team, a named technology in its stack, or a process our product replaces.
• I record the evidence behind the fit so another rep can understand why the account was prioritized.

I exclude an account when reliable data shows it cannot buy, use, or legally receive the offer.

• Clear exclusions include unsupported geography, company size outside the product range, or a direct competitor.
• A missing need or incompatible technology can make the account a poor fit even when the industry looks right.
• I mark the reason in the CRM rather than deleting the record, which prevents another rep from repeating the research.

The total addressable market is the broad universe that could buy, while a prospecting list is a filtered set I can work now.

• A TAM estimate may include thousands of possible companies based on market size and product scope.
• A working list applies ICP filters, territory rules, data quality checks, and current priorities.
• I keep the list narrow enough to research and contact well instead of treating the entire market as this week's queue.

I gather enough evidence to explain why this company and this person may care, without spending so long that outreach stops scaling.

• I confirm ICP basics such as size, industry, location, product, and the prospect's current role.
• I look for one useful business signal, such as a hiring plan, funding round, expansion, leadership change, or relevant technology.
• I turn that signal into a message angle tied to our value, not a generic compliment about the company.

I combine first-party company sources with reliable sales data tools and verify important facts across sources.

• The company website, careers page, press releases, and annual reports explain products, priorities, and hiring.
• LinkedIn helps confirm current roles, team structure, and recent job changes.
• Salesforce and Apollo show existing ownership, prior activity, contact data, and enrichment, but I do not assume every field is current.

A trigger event is a recent change that gives me a timely, evidence-based reason to contact an account.

• Examples include new funding, rapid hiring, a product launch, entry into a new market, or a new executive.
• The event matters only if I can connect it to a problem our product addresses.
• I mention that connection briefly, such as hiring 20 support agents creating a need for faster onboarding, rather than merely congratulating the prospect.

I prioritize accounts by fit, evidence of a current need, and my team's territory or campaign rules.

• Strong ICP fit comes first because intent from a company that cannot buy is not useful.
• A relevant trigger, prior engagement, or known technology can move a good-fit account higher.
• I use the agreed score or tier in Salesforce and revisit stale priorities when the underlying data changes.

I start with ICP and territory rules, find matching accounts, add relevant contacts, then validate and deduplicate the data.

• I apply company filters first so I do not enrich contacts at accounts the team cannot pursue.
• I select titles and seniority based on the buyer personas, then add verified business contact details.
• Before enrollment, I check CRM ownership, suppression rules, duplicates, missing fields, and recently contacted records.

A good list has strong ICP fit, the right people, usable contact data, and no ownership or compliance conflicts.

• I sample records to confirm company size, title relevance, and whether the contact still works there.
• I monitor invalid email and wrong-number rates because high failure rates expose poor enrichment.
• I also compare list-to-reply and list-to-meeting conversion by source, since a large list is not automatically a valuable one.

I choose contacts whose responsibilities connect directly to the problem, the evaluation, or the purchase decision.

• I map likely users, operational evaluators, budget owners, and executives instead of relying on one exact job title.
• I check the person's current role and seniority on LinkedIn or the company site before adding them.
• For a junior campaign, two or three relevant contacts per account usually give coverage without spamming the whole company.

Multi-threading means contacting several relevant people at one account instead of depending on a single contact.

• Different stakeholders may care about business outcomes, technical fit, or daily workflow, so each needs a relevant message.
• I stagger touches and check CRM activity to avoid sending identical emails to colleagues at the same time.
• I keep the account view connected so a reply from one person informs outreach to the others.

Data enrichment adds missing or updated company and contact information to an existing record.

• Apollo can add fields such as title, employee count, business email, phone number, and technology used.
• I keep the source and last-updated date where possible because people change jobs and companies grow.
• Enrichment supports research and routing, but I still verify high-value fields before using them in personalization.

Email verification reduces hard bounces and protects the sender reputation used by the whole team.

• A verifier checks whether the domain and mailbox are likely able to receive mail without sending the campaign itself.
• I avoid addresses marked invalid and follow team policy for risky or catch-all results.
• I watch hard-bounce rate after launch because even previously valid data can become stale.

Good data hygiene keeps records accurate, uniquely owned, current, and usable by the next person in the sales process.

• I standardize fields such as country, company name, phone format, and lead status instead of hiding facts in free-text notes.
• I merge or flag duplicates and check account ownership before creating a new Salesforce record.
• I log outcomes like wrong person, left company, or do not contact so bad data does not return to another sequence.

A cold email should quickly establish relevance, connect a real problem to value, and ask for one simple next step.

• The opening uses a specific account or persona signal rather than a generic introduction about my company.
• The body names one likely problem and one credible outcome or proof point in plain language.
• The close uses a low-friction call to action, such as asking whether a 15-minute conversation is worth exploring.

A useful subject line is short, accurate, and relevant to the reason for the email without pretending to be an internal reply.

• I use the business topic or trigger, such as onboarding new support hires, rather than vague words like opportunity.
• I avoid all caps, false urgency, clickbait, and prefixes such as Re: when there was no earlier conversation.
• I judge the subject together with reply and meeting rates because a high open rate alone can reward curiosity without intent.