By Peter Miller · Published September 20, 2026 · Last updated: September 20, 2026
9 min read
The portal asks for a resume. Your brain hears "describe yourself" and reaches for adjectives. That's how you end up with "motivated self-starter with excellent communication skills" where a recruiter wanted job title, years, and one number they can repeat in a hiring meeting. The gap isn't confidence. It's format, and you can fix it tonight.
Before you rewrite tonight, check your resume for free against the posting you want. You're checking whether your summary field imported cleanly and whether must-have terms from the req appear above the fold, not whether the block sounds inspirational.
Below: what belongs in a resume self-description versus an interview answer, four before-and-after teardowns by career stage, copy-paste templates for both formats, and the wording that gets files skipped in Workday and Greenhouse. You won't fix this with a thesaurus. You'll fix it with role, scope, and proof instead.
When the application still asks for a letter, generate a cover letter that adds one new proof point. The summary carries facts. The letter can carry motivation without repeating the same metric twice.
Quick Wins
- Delete every trait that isn't attached to a number, tool, or outcome.
- Rewrite sentence one as title + years + domain before you touch bullets.
- Swap line two keywords to mirror the posting without rewriting your whole career.
How can you describe yourself on a resume without sounding generic?
A resume self-description answers "what do you do, at what level, with what proof?" in under fifteen seconds. That's title, years, domain, and one outcome. Not your personality type. Not what you're passionate about.
US convention puts this block in Summary or Profile at the top. Third person or no pronouns. "Marketing coordinator with 4 years in B2B SaaS" works. "I am a creative marketer who loves storytelling" does not survive a six-second skim on mobile.
Interview "tell me about yourself" is different packaging for the same facts. First person. Spoken. Present-past-future in about 45 seconds. The resume is the compressed version; the interview is the expanded one. Paste one into the other and both sound wrong.
Parsers in Workday and Greenhouse often import summary text into a headline or profile field. Keywords here help matching, but dated Experience bullets still carry the proof. If the summary claims "managed $2M budget" and no bullet supports it, the file reads inflated.
For how the top third gets scanned before Experience, read what recruiters look at first on a resume . Fix the summary first; bullets second.
Four before-and-after self-description teardowns
Stage 1: Recent graduate (first full-time role)
Before: "Enthusiastic recent graduate eager to learn and contribute to a dynamic team environment."
After: "Business administration graduate (May 2026) with internship experience in accounts payable; processed 180+ vendor invoices monthly in QuickBooks with 99.2% accuracy; seeking entry-level finance analyst roles."
The after version names degree, tool, volume, and target role. No adjective survives without a number attached.
Stage 2: Mid-career operations manager
Before: "Results-driven operations leader with a proven track record of success and strong leadership skills."
After: "Operations manager with 9 years in e-commerce fulfillment; leads 3 shift supervisors across a 120,000 sq ft warehouse; cut mis-pick rate 17% in 2025 through barcode workflow redesign in NetSuite."
"Proven track record" tells the recruiter nothing. Square footage, team count, and a named system do.
Stage 3: Career changer (teacher to instructional design)
Before: "Dedicated educator looking to transition into corporate training and bring passion for learning to a new industry."
After: "High school science teacher pivoting to instructional design; 7 years building Canvas modules for 140 students per term; completed Articulate 360 certification 2025; shipped 4 SCORM courses adopted district-wide."
Name the target field, keep honest years, and pair with a credential line. Vague intent loses to candidates who mirrored the posting's LMS keywords.
Stage 4: Specialist (registered nurse, acute care)
Before: "Compassionate RN committed to excellent patient care and lifelong learning."
After: "Registered nurse (RN, BSN) with 6 years in med-surg; precepted 8 new hires on a 32-bed unit; maintained 96% medication administration accuracy while supporting Joint Commission readiness audits."
Regulated roles want credentials plus operational proof in the same block. Soft traits can live in the cover letter if the portal asks for one.
I've screened stacks of these in Greenhouse where the summary read like a personality quiz and the Experience section had the real story buried three bullets down. The top block never gave me a reason to scroll.
Copy-paste block: resume summary template
[Job title] with [X years] in [industry/domain]; [scope: team size,
volume, geography, or book size]; [one outcome with number or system name].
Line 2 (swap per posting): [keyword from posting] | [second keyword from posting]
Keep 40-70 words. Third person or no pronouns. Read aloud in under 15 seconds.
Copy-paste block: interview tell-me-about-yourself script
{`Present (10 sec): "I'm a [title] focused on [domain the role needs]."
Past (25 sec): "For the last [X years] at [employer type], I [one scope line]
and [one outcome with number]. Before that, I [one earlier proof point]."
Future (10 sec): "In this role I'd bring [skill from posting] to [team or
problem named in the job description]."
Total: about 45 seconds. First person. Do not read your resume summary aloud.`}
Edge case: no metrics yet
Before: "Hardworking customer service rep with great people skills."
After: "Customer service representative with 2 years in SaaS support; handled 45 to 55 tickets daily in Zendesk across billing and onboarding queues; trained on Salesforce case routing and WFM adherence reporting."
Volume and system names count as proof when you don't have a percentage win yet. Honest ranges beat invented percentages you'll choke on in round two.
Edge case: freelance or contract-heavy history
Lead with function, not employment type: "UX designer with 5 years across 12 client projects in fintech and health tech; shipped 3 design systems adopted by engineering teams of 8+; Figma, FigJam, and WCAG 2.1 AA audits." Contract count signals breadth without hiding the non-W-2 pattern.
For more summary patterns that don't read like filler, see resume summary examples that don't sound generic . Same structure works when you're describing yourself for any role family.
Wording that gets self-description skipped
Trait lists without proof. Hardworking, passionate, team player, detail-oriented. Each one needs a number, system, or outcome attached or it gets cut.
First person on the resume. "I am a…" belongs in the interview script, not the PDF. Parsers and recruiters both expect third-person headline style in the Summary field.
Objective statements about what you want. "Seeking a challenging role where I can grow" tells the recruiter nothing about what you've already done. State past proof, not future hopes.
Repeating the same line in summary and bullet one. Summary carries scope. Bullets carry variety. Wasting both slots on the same revenue number leaves no reason to keep reading.
Before: Summary is a mini cover letter praising the company's mission. Bullets start four lines down on mobile.
After: Summary is role plus one metric. Company praise stays in the letter if the portal asks for one.
This won't fix applying to roles where your experience genuinely doesn't match. It stops a qualified file from dying because the top block read like a dating profile instead of a professional headline.
Match your summary to the posting before you apply
Upload your PDF to HireFlow's free ATS resume checker with the job description pasted in. Confirm must-have terms appear in your summary and Experience. If the parser drops your profile into a garbled field, fix layout before you tailor wording.
When you're ready to rebuild the file from scratch, use the free resume builder to keep a single-column Summary section that imports cleanly. Then paste the template above and swap line two per posting.
What to paste tonight
How can you describe yourself in a way that survives both the parser and the six-second skim? Lead with title, years, and domain. Attach one proof point with a number or system name. Keep the resume third-person and the interview first-person. Swap line two keywords per posting without rewriting your entire file.
- Open your summary and delete every trait not tied to proof.
- Paste the resume template, fill the brackets, read it aloud in under fifteen seconds.
- Practice the interview script once so you don't recite the summary word for word.
Stop sending files with empty top blocks. Run a free ATS check and make your self-description earn the rest of the read.
Read more
Frequently asked questions
Use third person or drop pronouns entirely. US resume convention treats the summary as a professional headline, not a cover letter. First person belongs in your interview answer, not the PDF you upload to Workday.
Two to four sentences, roughly 40 to 70 words. Long enough to name your role, domain, and one proof point. Short enough that a recruiter reads the whole block on mobile before scrolling to Experience.
Same facts, different packaging. The resume summary is third-person, keyword-aware, and under 70 words. The interview answer is first-person, spoken, and follows present-past-future in about 45 seconds. Do not paste one into the other.
Standalone traits without proof: hardworking, passionate, team player, detail-oriented. Replace each with a number, system, or outcome from a real role. If you cannot attach proof, cut the word.
Under Summary, Profile, or About at the top, above Experience. Parsers in Greenhouse and Lever map this block into a headline field. Keep it single-column plain text so the import does not garble your name line.