Resume Writing · 20 min read
How to Write a Resume in 2026: Step-by-Step Guide and Examples
A complete, no-fluff guide to writing a resume that actually gets read in 2026. Format, sections, ATS rules, tailoring, and a full example you can copy.
Short answer: a modern resume is one page (two if you have 10+ years), single-column, in reverse-chronological order, with a clear headline, a 2–3 line summary, achievement-focused bullets under each job, and a skills section that mirrors the exact wording of the jobs you're applying to. That's 90% of it. The rest of this guide is the details, plus a full worked example.
If you'd rather skip the writing, the free AI resume builder drafts a first version from your LinkedIn or an existing resume in about 30 seconds. Then edit.
Table of contents
- Step 1: Pick a resume format
- Step 2: Contact information
- Step 3: Headline
- Step 4: Professional summary
- Step 5: Work experience
- Step 6: Achievement bullet points
- Step 7: Skills
- Step 8: Education
- Step 9: Optional sections
- Step 10: ATS formatting rules
- Step 11: Tailor to the job description
- Full example resume
- Examples for different career stages
- Final resume checklist
- FAQs
Step 1: Pick the right resume format
Three exist. Only one is safe to use in 2026:
- Reverse-chronological (recommended). Most recent job first. Every recruiter and every ATS expects this. Use it unless you have an unusual reason.
- Functional (avoid). Groups content by skill instead of by job. Recruiters read this as "trying to hide something."
- Hybrid. Only useful for career changers with a specific reason to lead with skills. Rare.
For the full breakdown see the ATS resume format guide.
Step 2: Contact information (10 seconds)
Top of the page. Single line if possible:
Alex Morgan · alex.morgan@email.com · +1 415 555 0142 · San Francisco, CA · linkedin.com/in/alexmorgan · github.com/amorgan
Rules: real email, real phone, city + state/country only (no full address), one URL that adds context (LinkedIn is default; add GitHub or portfolio if relevant). Skip the photo unless you're applying in a country where it's expected — the photo-or-not guide covers regional norms.
Step 3: Headline
One line under your contact info. Not "Resume." Your role and specialism.
Senior Product Manager · Growth & Activation · B2B SaaS
If you're job-hunting for a different level or specialism than your current title, the headline is where you signal it.
Step 4: Professional summary (2–3 sentences)
Skip the "objective." A summary is more useful for anyone with more than one year of experience.
Formula: [level + specialism] with [years] in [domain]. Known for [specific strength backed by a metric]. Looking for [role type] at [company shape].
Example:
Senior product manager with 7 years across B2B SaaS growth teams. Led the activation redesign at Segment that lifted paid conversion from 3.1% to 5.4%. Looking for a Head of Growth role at a Series B–C SaaS.
Full library of samples in the resume summary examples guide. If you're early in your career, use a resume objective instead — a summary with no experience underneath reads thin.
Step 5: Work experience
For each role:
- Company, city, dates (Month YYYY – Month YYYY).
- Title — the one on your contract or paycheck. Don't inflate.
- One sentence of context (optional) — "Series B fintech, 60 engineers, $28M ARR." Recruiters need this if the company isn't famous.
- 3–6 achievement bullets — most recent role gets more; older roles get fewer.
Reverse chronological. Group internships and part-time roles under a single "Early experience" heading if they crowd the page.
Step 6: Achievement bullet points
Every bullet follows one of two shapes:
- Verb + what you did + measurable outcome. "Cut checkout drop-off from 41% to 26% by simplifying the guest flow."
- Verb + what you did + concrete detail if no metric exists. "Rewrote the on-call runbook across 14 services; adopted by three sibling teams within a quarter."
Aim for 60% of bullets to have a number. If you're stuck, the performance metrics guide has 40 metric templates you can steal, and the 200 resume action verbs list handles the verb problem.
Don't write duties. "Responsible for managing a team of five" is a duty. "Grew the team from 5 to 12 while keeping quarterly OKR completion above 80%" is an achievement.
Step 7: Skills
One clean block, near the top or bottom depending on the role. Group them:
- Technical: Python, SQL, dbt, Snowflake, Looker
- Product: A/B testing, activation funnels, PLG motion
- Leadership: cross-functional planning, hiring, mentorship
Rules:
- Only list what you've actually used within the last 3 years.
- Mirror the exact wording of the JD (if they say "GCP" don't write "Google Cloud").
- Skip skill bars. ATS can't read them and recruiters don't trust them.
Full breakdown: how to list skills on a resume. To find the right words for your target role, run your resume through the resume keywords guide or the CV keyword optimizer.
Step 8: Education
- School, degree, graduation year (or expected year).
- Add GPA only if you're within 3 years of graduation and it's ≥3.5.
- Add relevant coursework only in your first job hunt.
- Move education below experience the moment you have any full-time job.
Step 9: Optional sections (only if they earn their space)
- Certifications. Only current, only relevant. (AWS SA, PMP, CFA, etc.)
- Projects. Great for early-career, engineers, designers. Link to the artifact.
- Publications / talks. Great for research, dev-rel, senior IC roles.
- Affiliations. See the professional affiliations guide.
- Languages. With honest level (B2, Native, etc.).
Don't add "Interests" unless one is genuinely rare and interesting.
Step 10: ATS formatting rules
Non-negotiable:
- Single column. No sidebar.
- Standard section headings: Experience, Skills, Education. Not "Where I've Made Magic Happen."
- No text in images, no icons for skill levels, no tables.
- Standard font — Inter, Calibri, Helvetica, Arial. Size 10–11 body, 12–14 headings.
- Save as PDF from a real text source. Not a scanned image.
- File name: FirstLast-Role-2026.pdf.
For the deeper technical breakdown, read how ATS systems actually work.
Step 11: Tailor to the job description
Every role needs a slightly different resume. Not a rewrite — a re-emphasis.
- Copy the JD.
- Highlight the top 5 requirements.
- For each requirement, find the strongest matching bullet in your resume and move it up.
- Mirror the JD's vocabulary (their words, not synonyms) — but only where it's honestly true.
The tailor-resume-to-job tool does this automatically against a pasted JD. If you'd rather see what's missing first, run it through the ATS resume checker.
Full example resume (mid-level PM)
Alex Morgan Senior Product Manager · Growth & Activation · B2B SaaS alex.morgan@email.com · +1 415 555 0142 · San Francisco, CA · linkedin.com/in/alexmorgan
Summary Senior PM with 7 years in B2B SaaS growth. Owned activation and paid-conversion at Segment through the CDP category peak. Known for shipping small, measurable changes over big-bang launches.
Experience
Segment (Twilio) — Senior Product Manager, Growth · Jan 2023 – Present · San Francisco · Led the free-to-paid activation redesign; paid conversion 3.1% → 5.4% over four quarters (+$4.2M ARR). · Introduced weekly activation review with data, growth, and product. Cut experiment cycle time from 6 weeks to 2. · Shipped 27 A/B tests in 2024; 9 winners, 12 nulls, 6 losers. Winners consolidated into a new default onboarding.
Segment — Product Manager · Jul 2021 – Dec 2022 · Owned the SDK version-check prompt that reduced churn on the developer plan by 11%. · Ran the first pricing test on the workspace plan; validated a $20 price increase with no measurable churn impact.
Intercom — Associate PM · Mar 2019 – Jun 2021 · Shipped the "resolution bot" onboarding sequence; adoption rose from 14% to 41% in six months.
Skills Product: activation, PLG, A/B testing, funnel analysis, pricing Data: SQL, Amplitude, Mixpanel, Snowflake, dbt basics Craft: written specs, weekly reviews, hiring, cross-functional facilitation
Education B.S. Computer Science, UC Berkeley, 2018
That's a full resume in ~250 words. No filler.
Examples for different career stages
- First job / no experience. Follow the resume with no experience guide. Lead with projects, coursework, and a clear objective.
- Career changer. Follow the career change CV guide. Lead with transferable outcomes, then a short "why this switch" line in the summary.
- Executive. Lead with scope (team size, budget, revenue) in every role. See executive resume tips.
Final resume checklist
- One page (or two if 10+ years).
- Contact block on one line.
- Headline under contact block.
- Summary is 2–3 sentences with a metric.
- Every job has 3–6 bullets; most recent has the most.
- 60%+ of bullets contain a number.
- No duty language ("responsible for").
- Skills mirror the JD's exact vocabulary.
- Single column, standard headings, PDF from text source.
- File named FirstLast-Role-2026.pdf.
- Read out loud, sentence by sentence. Cut anything that made you cringe.
Related reading
- 50+ Cover Letter Examples for Every Career Level
- 500+ Resume Keywords by Industry
- 70+ Resume Objective Examples
- What Is a Good ATS Score?
- Resume Summary Examples for 2026
- How to Write Better CV Bullet Points
FAQs
How long should a resume be in 2026? One page for anyone under 10 years of experience. Two for senior/executive. See the full length guide.
Chronological or functional? Chronological. Functional resumes look like you're hiding something.
Do I need a summary? If you have >1 year of experience, yes. Otherwise use an objective.
PDF or Word? PDF, exported from a text source. Word only if the JD explicitly asks.
How many jobs should I include? Last 10–15 years or last 4–5 roles, whichever is more relevant. Anything older, consolidate under "Earlier experience."
Should I use ChatGPT to write it? For a first draft, sure. For the final version, use a tool that has your real experience in front of it — ResumAI's free builder reads your existing CV or LinkedIn and rewrites it to match a specific JD without inventing facts.
Last updated: 2026-08-11 · ResumAI editorial team. Methodology.