Career guide
Sales engineer resume guide
Pre-sales resumes are scanned by an SE leader in about ninety seconds. Structure for that, and quote numbers you can defend.
Updated July 2026
What hiring managers actually look for
From the recruiter side of the table, SE leaders read a resume for four things, in this order: the motion you've sold (mid-market or enterprise, ACV, sales cycle), the stack and sector, evidence you owned proofs of concept rather than assisted on them, and whether the numbers look defensible. Everything else — tooling lists, courses, hobbies — is skimmed.
How to structure it
- Header: title, level, location and remote preference.
- Summary (3 lines): sector, deal size, motion, stack.
- Experience: for each role — the motion and ACV, then four outcome bullets with numbers.
- Technical stack: grouped, honest about depth.
- Education and certifications: last, kept short.
Quantifying your wins
The five numbers worth the space.
| Metric | How to calculate it | How it reads |
|---|---|---|
| Technical win rate | Technical wins ÷ evaluations you ran | 71% across 24 evaluations |
| PoC volume and cycle | PoCs owned end-to-end, median days to sign-off | 24 PoCs, 19-day median |
| Deals influenced | Count and average ACV of deals you supported | 18 deals, $340k average ACV |
| ARR touched | Total new ARR on deals you were technical lead on | $6.4M new ARR |
| Enablement | Assets or people you levelled up | Demo library used by 6 SEs; 3 hires ramped |
Bullets that work
Specific, measurable, defensible.
- Supported $6.4M ARR across 18 enterprise deals; technical win rate 71%.
- Owned 24 proofs of concept end-to-end; median 19 days from kickoff to sign-off.
- Built the demo environment now used by all six SEs on the team.
- Reduced security questionnaire turnaround from 9 days to 2.
Bullets that don't
Filler an SE leader skims past.
- Responsible for pre-sales activities.
- Excellent communication skills and team player.
- Assisted the sales team with technical questions.
- Familiar with cloud technologies.
Template outline
Copy this outline and fill it in.
NAME — Senior Sales Engineer City, State · Remote/hybrid preference · email · LinkedIn SUMMARY Enterprise pre-sales in [sector]. [ACV] average deal size, [cycle] sales cycle. Technical lead on [n] evaluations a year; [stack]. EXPERIENCE Company — Senior Sales Engineer 2023–present Motion: enterprise, $250k–$1M ACV, 4–7 month cycle, [sector] buyers. · Technical win rate [x]% across [n] evaluations. · Owned [n] PoCs end-to-end; median [n] days to sign-off. · [$X]M new ARR on deals where I was technical lead. · [Enablement or process win with a number.] TECHNICAL Cloud: … · Data: … · Security/identity: … · Languages: … EDUCATION & CERTIFICATIONS Degree, institution · [certs, one line]
Common mistakes
- Leading with responsibilities instead of outcomes.
- No ACV or motion, so the reader can't place your level.
- Numbers you can't reconstruct in the panel — assume every figure gets probed.
- A 40-item tool list that hides the three stacks you actually know.
- Three pages. Two is the ceiling; one is fine below senior.
- No pay expectation research — check the calculator before recruiter screens.
Based on our placement data
The one line most SEs leave off
Almost no pre-sales resume states technical win rate or PoC volume — the two figures an SE leader is actually looking for. Adding them near the top of each role puts you ahead of most of the pile, provided you can back them up in the panel.
Based on our placement data — illustrative placeholder figures.
For candidates
Looking for your next pre-sales role?
Join the network and we'll come to you when a role matches your stack, sector and number — confidential, no spam, and never shared without your say-so.
Methodology
Figures are medians drawn from placement records, offer letters and employer briefs across the last 12 months, expressed as 25th–75th percentile ranges. Base is fixed cash; OTE is base plus variable at 100% attainment, excluding equity. All numbers currently shown are illustrative placeholders. Read the full methodology.