How to Screen Sales Development Representative Resumes: An Evidence-First Kit

Sales development resumes often lead with numbers: calls made, emails sent, meetings booked and percentage of quota. Those numbers can be useful. They can also hide important differences in territory, lead quality, product, sales cycle, targets and how the employer counted a qualified meeting.

Do not solve that problem by ignoring numbers. Record the number, the context the resume gives and the question you still need to ask.

This kit is for sales development or business development representatives whose main job is finding and qualifying potential customers before a later sales stage. It is not a complete rubric for an account executive who owns negotiation and closing.

Define the job before reading resumes

For a typical SDR, four outcomes are a useful starting point:

1. Find plausible prospects that match the agreed customer profile.
2. Start relevant conversations across the channels the team actually uses.
3. Qualify interest and pass useful context to the next sales step.
4. Keep records, follow up and improve the approach from results and feedback.

The broader O*NET occupation for sales representatives of services includes contacting prospective customers, answering questions, explaining how services meet customer needs, maintaining customer records and identifying prospects. An SDR role is usually narrower, so use this source as a prompt and define your real handoff point.

Write down whether the job is inbound, outbound or mixed; which market and product it covers; the expected channels; and what counts as a qualified conversation. If you cannot define the outcome, a resume number will not fix it.

Evidence to look for

Useful numbers may include accepted meetings, show rate, opportunity conversion, response rate or pipeline created. Activity counts such as calls and emails explain effort, but effort is not the same as a useful result. Quota attainment is stronger when the resume also states the period, target and what was counted.

Keep the must-haves short

A genuine must-have may be:

• ability to work the advertised schedule or market hours;
• fluency in a language the role actually uses with prospects;
• experience with a regulated sales process the person must handle without training;
• enough knowledge of a technical market when the first conversation requires it.

A degree, an exact former title, experience with your particular CRM or an arbitrary number of years often belongs in the preference column. O*NET describes a broad service-sales occupation, not your exact SDR job; it also shows how varied the work can be. Name the work you require instead of borrowing a generic credential rule.

Do not miss transferable experience

Relevant evidence may appear in:

• fundraising, membership or donor outreach;
• recruitment sourcing;
• appointment setting or inside sales;
• customer support with renewals or expansion work;
• events, partnerships or community outreach;
• retail or hospitality roles with deliberate lead follow-up;
• founder-led sales or small-business business development.

Do not reward a nearby title by itself. Look for the same cycle: select a plausible person, start a relevant conversation, learn enough to choose the next step and leave a useful record.

What a resume cannot answer

A resume cannot reliably show whether someone:

• researched before contacting people or sent the same message to everyone;
• used an honest and respectful approach;
• listened well enough to qualify a real need;
• inflated team pipeline or accepted meetings as personal results;
• kept accurate records when activity was high;
• learned from rejection without becoming careless or pushy.

Use the same short exercise for each finalist. Give them a fictional product, a short customer profile and three possible accounts. Ask which account they would contact first, why, what they would say and what they would record after the reply. Score relevance, reasoning, clarity and whether they invent facts. Do not ask applicants to build a live prospect list or do outreach for your business.

Copy these criteria into your review

Adjust the weights before reading the first resume.

SALES DEVELOPMENT REPRESENTATIVE RESUME REVIEW

1. Prospect selection and research — 20%
Look for evidence of choosing accounts or contacts against a stated market,
territory or customer profile. Do not infer research from activity volume.

2. Relevant outreach — 25%
Look for calls, emails, social outreach or sequences adapted to a defined
audience. Record channel and context when stated.

3. Qualification and handoff — 30%
Look for discovery, agreed qualification rules, accepted meetings, useful
notes or progression to a named next stage. Record how the result was defined.

4. Records and follow-through — 15%
Look for pipeline updates, follow-up discipline and customer records. Treat
similar CRM systems as transferable unless day-one use is truly necessary.

5. Learning and adjustment — 10%
Look for messages, targeting or process changed in response to results,
feedback or repeated objections.

For every criterion, return: rating 0–3, exact resume evidence, and a question
to verify. Keep activity, outcome and context separate. Write “not stated”
instead of guessing. Do not automatically reject or hire anyone.

If the job owns negotiation, proposals or closing, add criteria for those outcomes or use a different role rubric. Do not make an SDR scorecard carry an account executive job.

Calibrate before the full batch

Have two reviewers score the same five varied resumes. Fix the rubric when:

• one reviewer treats calls or emails sent as results;
• a quota percentage receives credit without a period or definition;
• a famous sales employer replaces evidence of the applicant's work;
• inbound and outbound results are compared as if the starting conditions were equal;
• “not stated” becomes a rejection instead of a question.

Then review the whole batch and keep the shortlist decision with a person. The general resume-screening rubric gives fuller scoring anchors. If a broad applicant pool feels uncomfortable, why you should want 1,000 resumes explains how written criteria can help you review widely without treating software as the decision-maker.

The short version

• Define the market, channels, handoff and qualified outcome.
• Separate activity counts from accepted progress.
• Look for research, relevant outreach, qualification, records and learning.
• Count transferable outreach work when the evidence matches.
• Verify approach and reasoning with the same fictional exercise for every finalist.

Resume Ranker can apply your written job description and criteria across a folder of PDF resumes. Use the ranked reviews to find evidence and questions, then have a person inspect the source and choose who moves forward.