Skip to content
Writing Style Library

Resume

A structured, scannable record of a person’s professional experience, skills, and qualifications.

Resume

Section titled “Resume”

A resume is a structured, scannable record of a person’s professional experience, skills, and qualifications, organized for a recruiter to assess fit in seconds. Its defining quality is compression: it presents the candidate’s history in the most efficient form possible, organized into reverse-chronological roles, bulleted accomplishments, and labeled credential sections, so a screener can locate the signal without reading prose. The document exists to answer one question: does this person have the background this role requires?

What the resume does not do is argue. It presents evidence. The cover letter makes the case in prose; the resume is the record the case draws on. A candidate who embeds persuasive rhetoric inside a resume’s bullet structure has confused the two documents: the resume’s authority comes from its factual density, not from its rhetoric. Narrative connective tissue - transitions, explanations, hedges - dilutes that density and signals the candidate does not understand the format’s purpose.

The structural conventions of a resume are conventions for a reason: recruiters and applicant tracking systems process hundreds of documents with learned pattern expectations. Consistent date formatting, parallel bullet syntax, and standard section headers (Experience, Education, Skills) are not stylistic preferences but contracts with the reader. Departing from them forces the reader to slow down, which a resume cannot afford.

Canonical template

Section titled “Canonical template”
[Full Name]
[Email] | [Phone] | [LinkedIn or Portfolio URL] | [City, State]


## Experience


[Job Title] | [Company Name] | [Start Month Year - End Month Year or Present]
- [Action verb + what you did + measurable result]
- [Action verb + what you did + measurable result]


[Job Title] | [Company Name] | [Start Month Year - End Month Year]
- [Action verb + what you did + measurable result]
- [Action verb + what you did + measurable result]


## Education


[Degree], [Major] | [Institution] | [Graduation Year]


## Skills


[Category]: [Skill 1], [Skill 2], [Skill 3]

When to use

Section titled “When to use”

Applying for a job posting where a resume is requested or expected by the employer or recruiter; submitting qualifications to a recruiter for initial screening before any conversation; presenting credentials ahead of a networking meeting or informational interview when asked for background; populating a professional portfolio or profile with a formal credentials document; responding to any structured request for professional background that calls for a parseable, scannable form.

When not to use

Section titled “When not to use”

When a narrative framing of your work is needed - use a cover letter or bio instead; when initiating first contact with no posted opening and no shared context - the resume alone will not carry that ask; when the format requested is a CV, portfolio, or capability statement, which carry different structural conventions.

Pairs well with

Section titled “Pairs well with”

direct-communicator, executive, matter-of-fact, confident, executive-summary

Often confused with

Section titled “Often confused with”

cover-letter: A cover letter is a letter accompanying an application that makes the case for one specific person for one specific role. It connects the applicant’s experience to the posting’s stated needs, in the applicant’s own voice, and asks for the interview. Where a resume presents facts in parallel bullets organized for scanning, a cover letter argues from those facts in prose - mapping specific history onto specific job demands and closing with a direct request for the interview. The cover letter makes the case; the resume is the factual record the case draws on. The two documents work together: mixing persuasive argument into resume bullets, or listing credentials in a cover letter as though it were a second resume, weakens both.

Tells

Section titled “Tells”
  • Sections labeled with conventional headers: Experience, Education, Skills or close variants
  • Reverse-chronological order within Experience: most recent role listed first
  • Bullet points begin with past-tense action verbs; no subject pronoun (“I” or “We”) in the bullets
  • Dates formatted consistently, appearing on every role line alongside the company and title
  • No narrative transitions or connective prose between entries
  • Accomplishments quantified where possible: percentages, dollar amounts, headcount, time frames
  • Contact information block at the top; no salutation, no closing, no signature

Anti-patterns

Section titled “Anti-patterns”
  • Writing duty descriptions (“Responsible for managing the pipeline”) instead of accomplishment bullets (“Reduced pipeline cycle time 30% by restructuring the intake process”) - Duty descriptions tell the recruiter what the job was, not what the candidate did in it. Every applicant who held the same title had those duties; specific accomplishments are what differentiate this candidate from the field.
  • Replacing accomplishment bullets with narrative prose paragraphs in order to “stand out” - Narrative paragraphs break the scannability contract. A recruiter spending seconds on a resume cannot parse prose at speed; bullets beginning with action verbs let the eye find signal fast. Prose in a resume disrupts the format’s core function.
  • Padding bullets with advocacy or fit language - phrases like “passionate about innovation” or “eager to contribute to a collaborative culture” - The resume is a factual record, not a persuasive argument. The cover letter makes the case in prose, arguing from the resume’s evidence toward a specific ask. Mixing advocacy into the record muddies both documents: the resume loses credibility as evidence, and the argument loses force because it is not structured to carry one.
  • Using a functional or skills-first layout to obscure an employment gap or non-linear career path - Recruiters and applicant tracking systems recognize functional formats as a signal that something is being hidden, and many systems cannot parse non-chronological layouts at all. A brief, honest explanation in the cover letter handles gaps more credibly than a structural maneuver that raises the same question.

Failure modes

Section titled “Failure modes”
  • Over-compresses until bullets become telegraphic fragments - “Led initiative, +18%” - with no recoverable context about what was led, what 18% measured, or why the result mattered - Each bullet should carry three elements: the action, the context, and the result. A number without a story cannot be evaluated. Expand the bullet until a reader who does not know the candidate can place the achievement.
  • Quantification overdrive - every bullet forces a metric even where none is meaningful, producing noise like “Attended 12 team meetings” or “Responded to 100% of emails within 24 hours” - Quantify accomplishments where the number is evidence of scale or impact. A metric that does not distinguish a strong performer from a weak one adds noise rather than signal. Remove manufactured metrics; replace with qualitative specificity or a stronger accomplishment.
  • Structure dominance - the resume becomes a rigid taxonomy of labeled sections and sub-sections that fragments a coherent career into unconnected atoms, losing any sense of progression or throughline - Structure is a service to the reader, not an end in itself. If a significant result or a non-obvious career move disappears inside perfect parallel formatting, a brief parenthetical or a reordered bullet can restore the throughline without breaking scannability.

Instruction

Section titled “Instruction”
Write as a resume. The output is a structured, scannable credentials document organized for a
recruiter to assess fit in seconds. Use conventional section headers: Experience, Education,
Skills (or close variants). In the Experience section, list roles in reverse-chronological order,
most recent first. Write each accomplishment as a bullet beginning with a past-tense action verb;
do not use a subject pronoun. Quantify results where the number is meaningful evidence of scale
or impact; do not manufacture metrics. Write no narrative prose, no transitions, no rhetorical
advocacy. The resume presents evidence; it does not argue. Persuasive claims and fit language
belong in a cover letter, not here. Place contact information at the top. Hold to one page for
early-career candidates, two pages for ten or more years of relevant history.

Template

Section titled “Template”

See the Resume template.

Section titled “Related”

Pairs well with

Section titled “Pairs well with”

Direct Communicator, Executive, Matter of Fact, Confident, Executive Summary

Avoid with

Section titled “Avoid with”

Confessional, Reverent, Playful

Often confused with

Section titled “Often confused with”

Cover Letter

Examples

Section titled “Examples”

Jordan Ellis

Section titled “Jordan Ellis”

jordan.ellis@example.com | (555) 555-0142 | linkedin.com/in/jordanellis | Seattle, WA

Experience

Section titled “Experience”

Engineering Manager | Fernbridge Software | March 2021 - Present

  • Hired and onboarded 5 engineers over 18 months, growing a distributed engineering team from 6 to 11 across four time zones: US Pacific, US Eastern, UK, and India.
  • Redesigned the team’s daily status process, replacing a synchronous 9am Pacific standup that produced roughly 4 minutes of substantive content out of every 14 minutes and left India-based engineers attending an average of 3.2 of 5 weekly sessions versus 4.6 for US-based engineers.
  • Shipped a three-field async template (Shipped, In progress, Blocked or at risk) posted to #team-standup by 10am local time, with a single 60-minute weekly working session on Thursdays reserved for discussion that needed real-time exchange.
  • Raised on-time daily posting from 78% to 85.5% week over week during the first two weeks of a 30-day trial, tracked across 55 expected posts per week from an 11-engineer team.
  • Cut blocker response time to a median of 18 minutes and a 90th percentile of 2 hours 40 minutes, replacing a process where blockers raised at 9am often went unaddressed until the afternoon.
  • Brought India-based engineers to full weekday participation for the first time in the team’s history and recovered approximately 70 minutes per engineer per week previously spent in synchronous status reporting.
  • Documented the decision and rollout in an ADR, a process README, and a 30-day trial retro plan, making the rationale and template discoverable to new hires joining the distributed team.

Senior Software Engineer | Warrenton Analytics | June 2016 - February 2021

  • Led migration of the primary billing service from a monolithic deployment to independently deployable components, reducing release coordination overhead across three dependent teams.
  • Mentored two junior engineers through promotion to mid-level roles and served as on-call lead for the payments pipeline, the team’s highest-incident service.

Software Engineer | Cobalt Freight Systems | July 2013 - May 2016

  • Built internal tooling for shipment tracking that replaced a spreadsheet-based process for the warehouse operations team.
  • Rotated through the checkout and inventory systems teams during a period of rapid company headcount growth.

Education

Section titled “Education”

B.S., Computer Science | Redwood State University | 2013

Skills

Section titled “Skills”

Engineering leadership: distributed team management, async-first process design, hiring and onboarding, cross-timezone coordination Technical: Python, Go, PostgreSQL, CI/CD pipelines Tools: Slack, Jira, Linear, Notion