What this role’s resume is actually judged on — the language postings use, what a reviewer looks for in the first ten seconds, and the specific way Sales Development Rep resumes go wrong.
A first pass takes seconds and is looking for three things. If they are not near the top, the rest of the page rarely gets read.
Most resumes fail one bullet at a time. The difference is almost always specificity — a number, a constraint, or a consequence.
Made outbound calls and emails to generate new business leads.
Booked 41 qualified meetings a quarter from 1,800 touches, a 2.3% cold-to-meeting rate against a 1.4% team average, sourcing $2.1m of pipeline.
Terms that recur in real postings for this role. They belong in the bullet that proves them, not in a list at the bottom — our own checker weights requirement coverage at 40% and raw keyword matching at 20%, and most serious systems make a similar trade.
A keyword you cannot defend in an interview is worse than a missing one. How the format checks work.
'Made 100 calls a day' measures effort, and effort is the easy half. What a manager buys is efficiency — meetings per touch, meetings that became opportunities. Give them the ratio, not just the numerator.
SDR loops test resilience and process more than polish. Expect a cold-open roleplay, questions about volume and rejection, and whether you can qualify out quickly rather than chasing everything.
A sales resume with no numbers on it
Being invisible in the deal
Relationship language with no retention number
Listing technologies you have touched once
A resume that reads identically to a mid-level one
Abstraction with no anchor
Generic resume advice only goes so far — what matters is whether this resume covers this posting. Paste both and get requirement-by-requirement coverage, the keywords you are missing, and the format problems a parser will hit. The first check is free.