Methodology · SDR

The Builder's Standard for SDR Hiring

A resume full of "booked 15 meetings/month" can hide the single most important fact: whether those meetings came from a raw ICP the SDR worked cold, or from a purchased list and inbound demo requests that would have converted no matter who answered the phone. Here's exactly how the Builder's Standard tells the difference.

Built Not Inherited · The Number Not the Story · Verified Fit Not Assumed Fit

Why SDR hiring hides the hardest signal to fake

SDR searches look easy from the outside: a large applicant pool, a lower seniority bar, an entry-level comp band. That's exactly why the signal-to-noise ratio is so bad. Almost every applicant can describe "a strong cold-calling process" in an interview. Very few can actually produce a working cold sequence on the spot, or hold up under a live objection instead of a rehearsed answer about one.

The three pillars below are the exact screen we run on every SDR search, with the specific test and the specific tells that separate a real prospector from someone who has only ever worked warm leads.

01

Built, Not Inherited

The core question: did this SDR build their own target list from a raw ICP and write their own outreach, or did they work a purchased list and a pre-qualified inbound queue where most of the hard part was already done? We hand every SDR candidate a real ICP and ask for a cold sequence, written live, with no help.

Inherited

An SDR who booked meetings almost entirely from inbound demo requests and a vendor-provided lead list, with little need to build a target list or write original outreach.

Built

An SDR who was handed a raw ICP, built their own target account list from scratch, and wrote and sent a cold sequence that generated a meeting with no inbound interest to start from.

Builders produce a specific, researched first line on the writing test: something that references the actual company, not a mail-merge token. Inheritors produce generic filler, "I wanted to reach out and see if you'd be open to a quick chat," because they've never had to earn a reply with no existing interest to work from.

David Berk · Founder, Beacon Talent
02

The Number, Not the Story

"I consistently hit my activity targets" tells us nothing on its own. The number is: exact meetings booked per month, show rate, SQL conversion rate, and what share of those meetings came from genuinely cold, self-sourced outreach versus inbound or a purchased list, with team-average context on all of it.

Question we askStory answer (fails)Number answer (passes)
Meetings booked"I consistently booked 15+ meetings a month.""12 meetings a month, 9 of them from cold outbound I sourced myself, team average on cold-sourced meetings was 4."
Show rate"Most of my meetings showed up.""78% show rate on booked meetings, versus a team average of 61%, over four consecutive quarters."
SQL conversion"A good chunk converted to real opportunities.""41% of my booked meetings converted to SQL, versus a team average of 29%, tracked in the same CRM view."

This standard also applies to how a candidate talks about a cold stretch. An SDR who can say "I had a six-week stretch with almost no replies, so I rebuilt my list criteria and rewrote my opener, and bookings recovered within two weeks" is more trustworthy than one who claims they've never had a slow month.

03

Verified Fit, Not Assumed Fit

A genuine cold-outbound builder can still be the wrong SDR for a specific role if their motion doesn't match what's being hired for. An SDR who has only ever qualified inbound demo requests is not automatically a fit for a pure cold-outbound seat at an early-stage startup with no inbound volume yet, and the reverse is just as true. We match explicitly on motion, outbound versus inbound-qualifying, then verify it by calling the manager who actually ran the candidate's day-to-day, not a reference they hand-picked.

The question on every reference call is the same, no matter the role: on a scale of 1 to 10, how likely would you be to hire them again, and why? Anything below a 9 is worth digging into. Then we ask the manager directly how much of the candidate's booked pipeline was genuinely cold versus inbound or purchased-list, because that answer is the one most likely to contradict what the candidate claimed.

David Berk · Founder, Beacon Talent
David Berk
Founder & CEO, Beacon Talent · developed the Builder's Standard, now run on every Beacon search
← Back to the full Builder's Standard methodology See the SDR hiring service page → Candidate side: the SDR to AE Promotion Guide →

The Builder's Standard for SDR: FAQ

How does the Builder's Standard apply to SDR candidates specifically?

Built Not Inherited asks whether the SDR wrote their own cold sequences and built their own target lists from a raw ICP, or whether they worked purchased lead lists and warm inbound hand-offs with the hard part already done. The Number Not the Story asks for exact meetings booked, show rate, and SQL conversion, with team-average context, not a vague claim of hitting activity targets. Verified Fit Not Assumed Fit matches their motion, outbound versus inbound-qualifying, to the role, then confirms coachability and resilience on a call with the manager who actually ran their day-to-day.

What's the single best test to run on an SDR candidate?

A writing test: hand the candidate a real ICP and ask for a 3-email cold sequence with no help. Most candidates fail this. A true builder produces a specific, well-researched first line and a clear value proposition with no coaching. Someone who has only ever worked a script or a purchased list struggles to produce anything beyond generic filler.

What's the biggest red flag the Builder's Standard catches in SDR interviews?

A meetings-booked number with no source breakdown. An SDR who says they booked 15 meetings a month sounds strong until you learn 12 of those came from inbound demo requests that would have converted regardless of who answered them. The number is meaningless without knowing how many meetings came from genuinely cold, self-sourced outreach.

Why does Beacon Talent run a live role-play instead of just asking about objection handling?

Describing how you'd handle an objection and actually handling one live are different skills, and only one of them predicts performance on the phone. We role-play a cold call with a real objection and watch the candidate react in real time, the hesitation, the recovery, the tone, none of which shows up when a candidate is simply narrating their process after the fact.

Read next: the Complete Guide to GTM Recruiting →

Want SDR candidates screened this way?

Get a free talent map for your SDR search: candidates who have already cleared the Builder's Standard, delivered in 48 hours.

Get your free talent map