How to write a resume in 2026 (the complete guide)

Most resume advice on the internet is written by people who haven't hired anyone in the past five years — or anyone, ever. The result is a recycled body of conventional wisdom that's either out of date, contradictory, or just wrong. This guide is different: it's built from what hiring managers, technical recruiters, and search committees actually do when they sit down with a stack of resumes and a coffee. We'll walk you through every part of the resume in order, explain what the reader is looking for in each section, and show you what to write — with worked examples for each common career path.

If you read this start to finish you'll have everything you need to write a resume that passes the applicant tracking system, earns the seven-second first scan, and survives the second-round read where the actual decisions get made. We'll also tell you which conventions to ignore (the objective statement, the references line, the obligatory list of soft skills) because they're holdovers from a hiring process that no longer exists.

What a resume actually has to do

A resume has three readers, and it has to work for all three. The first is the applicant tracking system, the software that parses your PDF before any human sees it. The ATS doesn't read your resume the way you do — it extracts structured fields (name, dates, titles, skills) and runs them against the criteria the recruiter set up for the role. Layouts that look beautiful on screen but use multi-column flow, decorative icons in place of headings, or images of text get filtered out silently.

The second reader is a recruiter or hiring manager doing a seven-second scan. They're looking for three things: a job title that matches the role, a company name they recognise or that suggests the right tier of experience, and a recent bullet that explains what you actually did and what changed as a result. If the answer to those three isn't immediately findable on the first half of page one, your resume goes into the no pile.

The third reader is whoever does the second pass — usually a slightly more senior person doing forty seconds to two minutes per resume. This is where decisions actually get made. They're reading for specificity, evidence, and signal. Generic phrases ("results-driven", "team player", "strong communicator") tell them nothing. Concrete facts ("shipped the migration that cut our cold-start latency from 1.8s to 220ms") tell them everything.

The structure: what goes on the page, in order

Every effective resume in 2026 follows the same skeleton. The order matters because the recruiter reads top-down and decides at every step whether to keep going. Here's the structure, with what each section is doing and how much space it should take.

• Header — name, target title, location, email, phone, LinkedIn, optional website. One line per field. Skip the home address; it's a privacy risk with zero upside.
• Summary — three lines that answer "who are you, what are you best at, what do you want." 50 words max. We've written a whole post on this one.
• Experience — your last three to five jobs, most recent first. This is the load-bearing section; 60-70% of the page should belong here.
• Skills — a tight, scannable list of the technologies, tools, frameworks, or competencies the role asks for. Group them; don't list 47 things in a wall of text.
• Education — degree, school, dates. Less prominent than experience unless you're a recent graduate.
• Optional sections — projects, certifications, awards, languages, publications, volunteer work. Add when relevant; cut when not.

Notice what's not there: an objective statement (replaced by the summary), a list of references (recruiters expect to ask separately if they want them), an "interests" section listing hiking and cooking (irrelevant to anyone hiring you), or a photograph (varies by country, but in the US/UK it makes the ATS choke and biases reviewers in ways that hurt you legally and practically).

The header: get the basics right

The header looks trivial but it's where most resumes lose the ATS. Your name needs to be the largest text on the page, formatted as plain text (not an image, not a logo, not a fancy SVG). Use the same name you use on LinkedIn, your government ID, and your published work — recruiters will cross-reference. Under your name, put your target title. This is the role you're applying to, not your current job title. If you're applying for a Senior Software Engineer role, your header says Senior Software Engineer, even if your current job title is "Software Engineer III" or "Tech Lead." The ATS is matching against the title in the job description, so make the match easy.

Below the title comes the contact line: city + state or city + country, a single email address (the one you check daily), a phone number with country code, and your LinkedIn URL. Optional: a portfolio or GitHub URL if you're in design or engineering. Skip postal addresses. Skip Twitter unless your account is professional and relevant. One clean line, separated by bullets or pipes.

The summary: three lines, 50 words

The summary is the most expensive 50 words on your resume — the seven-second scan starts here, and recruiters decide in those seconds whether to keep reading. Three lines is plenty. We've written a separate guide on the exact formula, but the short version is: line one says who you are and how long you've been doing this; line two says what you're best at, with a specific outcome that makes it credible; line three says what role you're targeting next.

Example, before: "Results-driven product manager with a proven track record of delivering successful products. Passionate about user experience and seeking a challenging opportunity at a forward-thinking company." That paragraph could describe anyone applying for any role at any company. The recruiter learns nothing.

Example, after: "Senior PM with 6 years owning subscription products at consumer SaaS companies. Best at running pricing experiments — most recently raised ARPU 24% on a flagship product without dropping conversion. Looking to lead a 0-to-1 PM team building infrastructure for SMB owners." Same person, same length, completely different signal. The recruiter knows what kind of role you've held, what you're best at, what you're targeting, and that you can quote a real outcome to back it up.

The experience section: where most resumes lose

Your experience section is what the second-pass reviewer actually reads. The structure is mechanical: company name, your title, location, dates, then three to six bullet points per role. The bullets are the entire point — and they're where most resumes are weakest. The two failure modes are responsibility-statement bullets ("Responsible for managing the customer support team") and vague achievement bullets ("Improved customer satisfaction significantly"). Both tell the reader nothing useful.

Strong bullets follow a simple pattern: action verb → what you did → what changed because of it. "Rebuilt the checkout payment flow from scratch, cutting cart abandonment 18% in Q2." "Led the migration from REST to GraphQL across 12 services, reducing average page load by 340ms." "Onboarded 23 new enterprise customers in 9 months, generating $1.4M in net-new ARR." Notice the structure: an action you took (not a responsibility you held), a specific scope (not a vague claim), and an outcome that's quantified where possible.

If you don't have numbers, use the closest concrete substitute. "Authored the team's API style guide; cut review cycles on new endpoints by ~40%" is fine. "Owned the migration from Heroku to AWS, completed without downtime" is fine. What's not fine is a bullet that could describe anyone: "Worked on various projects" tells the reader nothing about you. The implicit question for every bullet is: would this bullet still make sense if I removed your name from the resume? If yes, it's a generic bullet; rewrite it.

Bullets: action verbs that pull weight

Start every bullet with an action verb. Avoid "helped," "assisted," "contributed to," and "was responsible for" — they're hedging language that makes you sound junior. If you genuinely only contributed to something, that's fine, but say it specifically: "Contributed three bug fixes that landed in the v3.0 release" beats "Helped with the v3.0 release." Specific contribution > vague involvement.

Strong verbs you can rotate through: shipped, led, owned, authored, architected, migrated, rebuilt, scaled, reduced, increased, accelerated, automated, designed, drafted, negotiated, closed, recruited, mentored, presented, published, launched, decommissioned. Pick the one that's literally true. "Shipped" is overused in tech; use it when you actually delivered something to production. "Led" implies you ran the project end-to-end; don't claim it if you didn't. The credibility of your resume depends on the precision of these verbs.

Skills: tight, grouped, parsed correctly

The skills section's job is to give the ATS a clean list to match against the role's requirements, and to give the human reader a quick scan of your technical surface area. Both goals are best served by short, grouped lists rather than a wall of text. For an engineer: Languages — TypeScript, Go, Python. Frameworks — React, Next.js, FastAPI. Infrastructure — AWS, Docker, Kubernetes, Terraform. Databases — Postgres, Redis, Elasticsearch. For a designer: Design — Figma, Sketch. Prototyping — Framer, ProtoPie. Research — UserTesting, Lookback. Code — HTML/CSS, basic Tailwind, light React for prototyping.

Three rules: list things you'd be comfortable having a hour-long technical conversation about. Don't pad with technologies you used once at a hackathon — recruiters ask, and you'll get caught. Don't list everything; list the things the role needs. Three groups of four to six items reads cleaner than one block of twenty.

Education: how much space depends on where you are

If you graduated within the last five years and your degree is relevant, give education a fuller treatment — school, degree, dates, GPA if it's above 3.5, relevant coursework if it's a fresh grad role. If you graduated more than five years ago, education shrinks to one or two lines: school, degree, year. Your work history is doing the heavy lifting by then; the degree is a check-box. If you didn't finish a degree, that's increasingly fine in most fields; just don't list it as if you did. "Coursework toward MS in Computer Science, MIT" is honest; "MS in Computer Science, MIT (in progress, dropped out)" is unnecessary.

The ATS test: what to check before you export

Before you send your PDF anywhere, run the ATS test: save it, then open it in a plain text editor (or copy-paste it into a blank Google Doc). If the result is unreadable — column text scrambled, dates in the wrong order, decorative icons turning into garbage characters — your layout isn't ATS-safe. The fix is usually to switch to a single-column template or to drop the decorative elements. Resumeely's templates all pass this test by construction; if you're using a builder where they don't, that's the moment to switch.

The other ATS pitfall is fonts. Stick to common, web-safe fonts: Inter, Geist, Roboto, Open Sans, Helvetica, Arial, Georgia, Garamond, Times New Roman. Avoid free fonts you downloaded from a free-fonts site; they often don't embed correctly in PDFs and the ATS sees garbled glyphs. If a template lets you pick a font, pick a boring one. Your resume isn't the place to express your typographic personality.

Length: one page or two?

The answer almost no one gives you straight: one page for the first ten years of your career, two pages once you've genuinely earned the space. If you're an entry-level or mid-career candidate stretching three roles across two pages with generous whitespace, that's worse than the same three roles on one tight page. The reader treats density as a proxy for substance. If you're a director or VP with fifteen years of experience and you cram it all onto one page, you'll cut content the reader wanted.

Don't pad. Don't shrink the font below 10pt to make it fit. Don't widen the margins to make it fit. If your content is too long, the first cut is your oldest roles (truncate to one line each), then your bullets per role (cap at four for older roles), then sections you can remove entirely (interests, volunteer work, anything not load-bearing). The resume is a hiring document, not a complete history of your professional life.

Tailoring: the single highest-leverage thing you can do

The same resume applied to twenty different jobs gets generic results. The same resume, lightly tailored to each role, gets dramatically better callback rates — not because the recruiter is doing keyword matching (they're often not), but because the gap between what the role asks for and what your resume emphasises is what makes you forgettable. Tailoring isn't faking experience; it's reordering your bullets to put the ones the role cares about first, and rewriting your summary to mirror the role's vocabulary.

Most of the work in tailoring is in the summary and the experience bullets. If the role emphasises team leadership, lead with your leadership bullets. If it emphasises individual technical contribution, lead with your technical bullets. The skills section should also reorder to match — putting the most relevant stack first signals fit at a glance. We built an AI Tailor feature into Resumeely's editor that does this in under thirty seconds per application; pasted JD goes in, tailored bullets come out, you accept the ones that ring true.

Mistakes that get resumes rejected

Some failure modes show up over and over. Putting non-essential information at the top of page one (objective statements, generic summaries, soft-skill self-assessments) wastes the highest-value real estate on the page. Listing more than six bullets per role makes the reader skim; cap at four for older roles, six for current. Saying "team player" or "strong communicator" or "detail-oriented" wastes lines without conveying anything — anyone applying for any white-collar role would claim those things. Using a different font or layout for each section makes the resume look unfinished. Putting the date next to each bullet ("In Q2 2023…") is something the reader doesn't need; the role dates at the top of each job cover the time range.

The most common single mistake: typos in the company name of the company you're applying to. The recruiter spends three seconds on the cover letter or summary, sees a typo, and the application goes into the no pile. Always re-read with the company's name in mind right before you click submit. Auto-fill on browser forms regularly inserts the previous company you applied to in the new application's cover-letter field; check it.

Worked example: software engineer

Maya is applying for a Senior Frontend Engineer role at a SaaS company. Her resume opens with a header — name, target title ("Senior Frontend Engineer"), location, email, phone, LinkedIn, GitHub. The summary reads: "Senior frontend engineer with 7 years building user-facing products at consumer-scale companies. Best at turning ambiguous PM specs into shipped React features that move retention metrics. Looking to lead front-end on a product surface where the design bar is genuinely high." Three lines, 47 words, every word does work.

Her experience section leads with her current role: Senior Engineer at Driftline, four years. Bullets: "Rebuilt our checkout form layer with a typed schema-first approach; product engineers ship new fields without touching internals." "Led migration from REST to GraphQL across our six largest services; cut average page load 340ms." "Drove the front-end half of the 2024 redesign, A/B tested into a 12% lift in DAU on the dashboard surface." Each bullet starts with an action verb, names a specific scope, and quantifies an outcome. Then a previous role (Engineer at Brightline, three years) with similar treatment. Skills section grouped by language, framework, tooling. Education in one line. One page, dense but legible.

Worked example: product designer

Hana is applying for Senior Product Designer at a fintech company. Her header includes her portfolio URL (designers are expected to have one — the resume's job is to make the recruiter click through, not to show every project). Summary: "Senior product designer with 6 years shipping consumer SaaS products. Best at distilling ambiguous PM briefs into calm interfaces — most recently shipped a checkout redesign that cut abandonment 18% in Q2. Looking to lead design on a 0-to-1 product team where the craft bar is owned end-to-end."

Experience leads with the redesign role. Bullets emphasise outcomes that designers and engineering managers both care about: shipped surfaces with measurable lift, design-system work that scaled to other teams, prototypes that drove a re-prioritisation. Skills are tight (Figma, light Framer for prototyping, basic Tailwind for working in code with the engineering team). The portfolio URL is the load-bearing reference; the resume is the credibility check.

Worked example: career change

Career-change resumes are the hardest because the reader is checking for relevance, and most of your experience won't be obviously relevant. The trick is to lean on transferable skills in the summary, and to translate your past experience into the language of the new role. If you're moving from teaching to UX research, your summary leads with "7 years designing and running curriculum, including formal pre/post assessments and stakeholder interviews — looking to move into UX research roles where that experience translates directly." Your experience bullets emphasise the parts of teaching that are also research: needs assessments, qualitative interviews, written reports, stakeholder management.

Don't hide the career change — recruiters see through it instantly and it looks worse. Lead with what you're moving to and why, and let your translated past experience do the credibility work.

Cover letters, LinkedIn, and the rest of the application stack

The resume isn't the whole application. The cover letter (when there is one) is your chance to control narrative — to say what role you're applying to, why the company in particular, and the one specific thing about your background that makes you a fit. We've written a complete cover letter guide and a 50-examples library that show what good looks like; the short version is: three or four paragraphs, no clichés, names the role and the company specifically, leads with one concrete fact from your experience, ends with a clean ask.

Your LinkedIn should mirror your resume — same titles, same dates, same company names. Inconsistencies between resume and LinkedIn raise flags during reference checks. Your headline and About section can be slightly longer than your resume summary; treat them as the extended version, not a different version. Once the resume is dialled in, mirror it on LinkedIn that same day.

The submit checklist

• Read top-to-bottom once, out loud. Words you stumble on are words to rewrite.
• Search the document for every adjective. Replace the lazy ones (results-driven, dynamic, passionate, proven) with a specific fact.
• Verify every date and every company name spelling.
• Verify the target job title matches the role you're applying to.
• Save as PDF. Open the PDF in a plain text editor. If it's garbled, the layout isn't ATS-safe.
• Read once more with the role's job description open beside you. Anything in the JD that's also true of you should appear, in the role's vocabulary, somewhere on the resume.
• Submit. Apply the lessons to the next one.

What to do next

If you've made it this far, the highest-leverage next move is to actually rewrite your resume. Open the resume you currently use, open Resumeely in another tab, and rewrite section by section as you read back through this guide. Pick a profession-specific template that matches your role, use the AI Checker to flag generic phrasing, and use the AI Tailor on every application.

If you'd rather start from scratch, our editor walks you through it section by section so you never stare at a blank page. The free plan covers everything in this guide: every section, PDF export, all the AI feedback. Whatever you do, write the resume you'd want to read — recruiters are looking for a person, not a document.