Skip to content
launchcv

How to write a resume: step by step, with real examples.

Eight steps from a blank page to a resume you can send: what goes in each section, how to turn duties into results, and how to tailor it for each job in the US.

By · Updated · 8 min read

The eight steps at a glance

  1. Contact details

    Name, city and state, phone, email and one link, as plain text.

  2. Summary

    Two or three lines: your level, your focus and one result.

  3. Experience

    Most recent job first, with bullets that show results.

  4. Skills

    The tools and skills the job asks for, named the same way.

  5. Education

    Degree, school and year, plus licenses and certifications.

  6. Tailor it

    Match your wording and order to each job post.

  7. Format for ATS

    One column, standard headings, a text-based file.

  8. Proofread

    Read it slowly, out loud, and check every date and link.

Before you start

A resume has one job: get you to an interview for a specific role. Everything below follows from that. Before you write a word, gather three things: the job post you're applying to, a list of your past jobs with start and end dates, and any results you can back up — sales closed, time saved, people trained, projects shipped.

Then pick the layout. For almost everyone in the US that's a reverse-chronological resume: one column, your most recent job first, standard headings. The resume format guide explains why and covers the exceptions. The eight steps below fill that layout in, top to bottom.

THE SHORT VERSION

One column, most recent job first, results in every bullet.

  • Start from a reverse-chronological, one-column layout
  • Write bullets as action + what you did + what changed
  • Use numbers you can explain in an interview
  • Name skills the way the job post names them
  • Tailor the summary and bullet order for every application
  • Send a text-based PDF unless the posting asks for Word

Step 1: Contact details

Put your name at the top, larger than anything else, followed by one line with your city and state, phone number, professional email and, if you have one, a LinkedIn or portfolio link. A full street address isn't needed.

Type these as plain text in the body of the page — not in the document's header area, which some applicant tracking systems skip, and not behind icons. Leave off a photo, date of birth, marital status and Social Security number; none of them belong on a US resume.

Daniel Kim

Data Analyst

Chicago, IL · daniel.kim@email.com · linkedin.com/in/danielkim

The contact block from our data analyst resume example: name, target title, then location, email and one link on a single line. Names and details are illustrative.

Step 2: A short summary

A summary is two or three lines that tell the reader who you are and what you're best at: your level, your focus and one result. It replaces the old "objective statement", which talked about what you wanted rather than what you offer.

Skip adjectives a reader can't check — "hard-working", "detail-oriented", "results-driven". A number or a named area of work does more. Here is how the same kind of summary changes with experience, from our data analyst resume example:

  • Entry level

    Statistics graduate with SQL, Python and Tableau experience from two internships. Built a sales dashboard now used weekly by a 12-person team.

  • Mid level

    Data analyst with 4 years in retail. My forecasting and pricing work has cut stockouts by 17% and added $1.2M in annual margin.

  • Senior

    Analytics lead who has built BI functions from scratch at two companies, owning metrics, data quality and experimentation for teams of 200+.

Summaries from the data analyst resume example. Figures are illustrative.

Stuck on yours? The free resume summary generator drafts one from your title, experience and strongest result, and you edit it from there.

Step 3: Experience, with achievement bullets

This is the section that gets read. List your jobs most recent first. For each one, give your job title, the employer, the city and state (or "Remote"), and start and end dates as month and year. Under each job, write three to six bullets — more for your current role, fewer for older ones.

Each bullet should show what changed because you were there, not what your job description said. A reliable pattern is:

Action verb + what you did + the result. A duty says what you were supposed to do; an achievement says what happened because you did it.

  • Start with a strong verb — led, built, cut, launched, negotiated — not "responsible for" or "helped with". The resume action verbs list has alternatives by skill.
  • Add a number when you have one — money, time, volume, people, percentages — and only numbers you could explain in an interview.
  • No number? Show scope instead: how many people used it, how often, for whom, or what it replaced.
  • Keep each bullet to one or two lines. If it wraps to a third, split it or cut the least useful words.

Here are duty-style bullets rewritten as achievements, taken from our resume examples:

  • Software Engineer · Performance

    Instead of: Improved API speed

    Write: Cut p95 API latency from 900ms to 180ms by adding caching and query indexes

  • Registered Nurse · Patient education

    Instead of: Educated patients before discharge

    Write: Introduced teach-back discharge teaching that cut follow-up calls about medications by 30%

  • Sales Representative · Sales process

    Instead of: Improved the sales process

    Write: Cut the average sales cycle from 62 to 45 days with structured discovery and tailored demos

  • Customer Service Representative · Resolution

    Instead of: Solved customer problems

    Write: Raised first-contact resolution from 71% to 86% with a shared troubleshooting guide

  • Teacher · Student growth

    Instead of: Helped students improve their scores

    Write: Raised the share of students meeting grade-level benchmarks from 58% to 71% in two years

  • Administrative Assistant · Events

    Instead of: Planned events

    Write: Organized a 60-person leadership offsite, delivered 8% under budget

Before-and-after pairs from our resume examples; each role name links to the full example. Figures are illustrative.

If you have a bullet that still reads like a duty, paste it into the free resume bullet point generator and it suggests achievement-style rewrites you can edit with your real numbers.

Step 4: Skills

List the hard skills, tools and certifications the job calls for and that you'd be comfortable being asked about: software, programming languages, methods, equipment, languages you speak. One or two lines of comma-separated terms is easier to scan than a grid.

Name each skill the way the job post names it. If the posting says "Salesforce" and "forecasting", write those words, not "CRM tools" and "planning". The resume keywords pages list the terms that come up for each role.

Leave out rating bars, stars and percentages next to skills — a parser can't read them and a recruiter can't interpret "80% Excel". Soft skills such as communication or leadership are better shown in an experience bullet than claimed in a list.

Step 5: Education and certifications

Give your degree, school and graduation year (or "Expected May 2027" if you're still studying). Add honors, a relevant minor or a strong GPA only while you're a student or recent graduate; after a few years of work, the degree line is enough.

If you graduated recently and have little work history, move Education above Experience and add relevant coursework, projects or internships. Otherwise it sits below Experience.

Licenses and certifications that the job requires — RN, CPA, PMP, a teaching license — deserve their own short section or a clear line under Education, with the issuing body and the year.

Step 6: Tailor it to the job post

One resume sent to every opening reads like one. Keep a full master version with everything you've done, then make a copy for each application and adjust it:

  1. Read the post twice. Mark the job title, the required skills and tools, and the two or three outcomes the role is clearly hired to deliver.
  2. Mirror the wording where it's true. If you've done the thing, use the posting's term for it — in a bullet, and in your skills line.
  3. Reorder. Put the bullets that match the posting first under each job, and move the most relevant job details up.
  4. Rewrite the summary so its first line answers the posting's headline need.
  5. Cut what doesn't help for this role, to keep the length in check.

Here is what that looks like in practice. In our data analyst resume example, the bullets themselves carry the skills recruiters search for — highlighted below — rather than leaving them in a list at the bottom:

  • Built a demand forecast in Python that reduced stockouts by 17% across 120 stores (keywords: Python)
  • Replaced 30 weekly spreadsheets with a Tableau dashboard used by 85 managers (keywords: Tableau)
  • Automated SQL data checks that cut reporting errors by 70% (keywords: SQL)
  • Wrote 200+ SQL queries for product, finance and marketing requests (keywords: SQL)
Bullets from the data analyst resume example, with terms from the data analyst keyword list highlighted.

Never add a skill or a result you don't have to match a post. Interviews test the resume, and a mismatch costs more than a missing keyword.

Step 7: Format it for ATS and for people

Many employers read applications through an applicant tracking system (ATS), which turns your file into text and sorts it into fields. Formatting that confuses the parser can leave your job history empty even when the page looks fine. Keep it simple:

  • One column, with nothing side by side.
  • Standard headings: Summary, Experience, Education, Skills.
  • No tables, text boxes, icons or images in place of words.
  • A common font at a readable size, with consistent dates and spacing.
  • A text-based PDF — exported, not scanned — unless the posting asks for Word. Name it plainly, like Firstname-Lastname-Resume.pdf.

Length is part of formatting too: one page early in your career, two once your relevant experience fills them. The resume length guide covers each experience level, what to cut and the federal two-page rule.

To see how a parser reads your file, run it through the free ATS check. It flags columns, tables, missing contact details and inconsistent dates, and needs no account.

Step 8: Proofread before you send

Typos are the easiest reason to be passed over, and the easiest to fix. Proofread on a different day from the one you wrote it if you can, and check it against this list:

  • Your name, phone number and email are correct, and every link opens
  • Job titles, employers and dates match your LinkedIn profile
  • Every date uses the same format, and nothing overlaps by mistake
  • Bullets in past jobs use the past tense; your current job uses the present
  • Each bullet starts with a verb, and no two start with the same one in a row
  • Company names, tools and certifications are spelled the way their owners spell them
  • You've read it out loud once, slowly, start to finish
  • The file opens as expected, and you can select the text in the PDF

Then ask someone who knows your field to skim it once and tell you what they remember. If it isn't your strongest result, move that result higher.

Put it together: a full example

Here is a complete resume that follows every step above, rendered in one of LaunchCV's templates. Compare its bullets with your own: each starts with a verb and ends with what changed.

Maria Lopez

Senior Product Manager

Austin, TX · maria.lopez@email.com · linkedin.com/in/marialopez

Summary

Product manager with 6 years in B2B SaaS and healthcare. I turn customer research into shipped features that move retention and revenue.

Experience

Product Manager, Brightpath Health · Mar 2022 – Present

  • • Launched patient self-scheduling, cutting no-shows by 23% across 41 clinics
  • • Led a cross-functional team of 9 engineers and 2 designers through 3 major releases
  • • Ran 30+ customer interviews that shaped the 2024 roadmap and 2 new revenue features
  • • Managed stakeholders across clinical, legal and sales to ship HIPAA-compliant messaging

Associate Product Manager, Fieldnote · Jun 2019 – Feb 2022

  • • Owned onboarding for a B2B app; raised week-1 activation from 38% to 57%
  • • Introduced an A/B testing practice later adopted by 4 product teams
  • • Defined OKRs and pricing tests that lifted trial-to-paid conversion by 11%

Education

B.B.A. Business Analytics, University of Texas at Austin, 2019

Skills

Product strategy · Roadmapping · Stakeholder management · Go-to-market · SQL · Amplitude · A/B testing · User research · Jira · Figma

REAL EXAMPLEOur product manager resume example in the Classic template: contact line, a two-line summary, experience with the latest job first and verb-led bullets, then education and skills.

There are written examples for more roles — from registered nurse and teacher to software engineer and accountant — on the resume examples page, each with summaries and bullets you can adapt.

Next: the cover letter

Many applications still ask for a cover letter, and a short, specific one helps when you're changing careers or writing to a hiring manager directly. Start from the copyable cover letter template, which explains each paragraph and includes a filled-in example.

Keep "References available upon request" off the resume itself. Prepare a separate references page instead, and send it only when it's asked for.

Frequently asked questions

How do I write a resume for the first time?

Start with a one-column, reverse-chronological layout. Add your contact details, a two-line summary, then your experience — including internships, part-time jobs, volunteering or projects — with bullets that show what you achieved. Finish with education and skills, and keep it to one page.

What should a resume include?

Contact details, a short summary, work experience with dates and achievement bullets, education, and a skills section. Add certifications, licenses or relevant projects when they matter for the job.

How many bullet points should each job have?

Three to six for your current or most relevant job, and fewer for older or less relevant ones. Each bullet should show a result, not repeat a duty.

Should I write a different resume for every job?

Keep one master resume, then tailor a copy for each application: adjust the summary, reorder bullets so the most relevant come first, and use the job post's wording for skills you actually have.

Do I need a summary or an objective?

A short summary is more useful than an objective, because it says what you offer instead of what you want. Make it two or three lines with your level, your focus and one result.

What should I leave off my resume?

A photo, date of birth, marital status, Social Security number, a full street address, "References available upon request", and jobs from long ago that have nothing to do with the role.

Should I use a resume template?

Yes, if it's a simple one-column template with standard headings. Avoid designs with sidebars, tables, icons or skill bars, which applicant tracking systems often read incorrectly.

/ Keep going

/ Read next

Finished your resume? Check it.

The free ATS check flags columns, tables, missing contact details and inconsistent dates.

Check my resume — free