How to Write a Resume in 2026: Complete Guide

A resume is not a record of your career. It is a single argument, aimed at one job, that you should be the person interviewed for it. Almost every problem with a resume comes from forgetting that: the document becomes a list of everything that happened instead of the case for one thing that should happen next.

This guide goes section by section, and for each one answers the question that actually matters, which is not "what goes here" but "what is this section for". If a section is not doing a job, it should not be on the page.

Start by reading the posting properly

Before writing a line, read the job description twice: once for what the role does, once for what it is worried about. The second reading is the useful one. A posting that mentions "stakeholder communication" three times is describing a team that has been burned by someone who could not do it. A posting that lists a specific tool five times has a migration in progress.

Write down the four or five things the posting keeps returning to. Those are what your resume has to answer. Everything else on the page is supporting material.

The header: be contactable

Name, city, email, phone, and one link that is worth clicking. That is the whole section.

Two mistakes are common enough to be worth naming. The first is putting all of it in the document's header region, which many resume parsers discard entirely, so the record arrives with no way to contact you. Put it in the body of the document. The second is listing every profile you own; a LinkedIn URL and, if it is relevant to the work, a portfolio or repository. A dormant profile is worse than no profile.

City and country are enough for location. A full street address buys you nothing and is a privacy risk on a document you are about to email to strangers.

The summary: earn the next ten seconds

A summary is worth writing only if it says something the rest of the page cannot say quickly. Its job is to establish, in two or three lines, what kind of professional you are and at what scale you operate. That is it.

The first describes nobody. The second tells a hiring manager the domain, the seniority and the scale before they have read a single role. If you cannot write a specific version, leave the section out and let the experience speak.

Experience: outcomes, not duties

This is most of the resume and most of the opportunity. The distinction that matters is between a duty, which describes the job you were given, and an outcome, which describes what was different because you were the one doing it.

The second sentence is not longer because it is padded. It is longer because it contains information. It also survives the interview: a hiring manager can ask how you did it, and you have an answer.

Go through every bullet and ask what changed. If the honest answer is nothing, cut the bullet rather than dressing it up. Four sharp bullets beat eight vague ones, and a resume that lists every responsibility of the role reads as junior regardless of how many years it covers, because seniority shows in what you chose to leave out.

Numbers help but are not compulsory. Where you have them, use them and give them a denominator: "grew revenue 40%" means very different things on a $200k base and a $20m one. Where you do not have them, describe the change qualitatively rather than inventing a figure. A number you cannot defend in an interview is worse than no number.

Skills: a filter, not a wish list

The skills section exists so a reader scanning for a specific capability finds it in under a second. It is a filter, and it works best when it is short and true.

The weakest possible version is a long list of everything you have ever touched, unsupported by anything in the experience below it. A reader who sees a tool in your skills list and nowhere else concludes you used it once. Name the important ones in the role where you actually used them, and keep the list itself to what you would be comfortable being questioned on.

Education: it moves down the page over time

Early in a career, education is near the top and carries detail: the degree, relevant coursework, a project, a GPA if it is strong. After two or three years of real work, it becomes a line at the bottom with the institution, the qualification and the year, and it stays there. The exception is fields where the credential is the licence to practise, which is most of medicine, law, accounting and academia, where it stays prominent permanently.

Gaps, short stints and career changes

Three situations cause more anxiety than anything else on a resume, and all three are handled the same way: state the fact plainly and move on. Ambiguity is what invites suspicion. A reader who cannot tell what happened assumes the worst available explanation, and they are usually wrong in a direction that costs you.

Gaps. Use years rather than months on the roles either side and most short gaps disappear without anything being hidden. For a long one, give it a line of its own with a neutral label: caregiving, study, medical leave, redundancy followed by a search. You do not owe anyone the details, and a labelled gap reads as a life, whereas an unexplained hole reads as something being concealed.

Short stints. One is invisible. Three in a row is a pattern a reader will ask about, so answer it on the page: "contract", "fixed-term", "company acquired", "role eliminated". Four words removes the question entirely. Leaving a genuinely short role off the resume is defensible; leaving off the one immediately before your current job rarely is, because the gap it creates is more conspicuous than the stint.

Career changes. The instinct is to hide the old field. Do the opposite and translate it. A teacher moving into product management has run stakeholder communication, curriculum design and outcome measurement for years; those are the words to use, because they are true and they are what the new field calls the same work. What loses a career changer the interview is not the old field, it is a resume that describes the old field in the old field's vocabulary and leaves the reader to do the translation.

Length, and the one-page argument

One page is right for most people with under about ten years of experience. Beyond that, insisting on one page starts to read as an inability to prioritise rather than as concision, because the compression itself becomes visible: six-point type, no margins, three roles crushed into a line each.

Two pages is normal for a senior professional. Three is normal for academic and medical CVs, which are a different document with different conventions. The real rule is not a page count: every line must be doing work, and the page count is whatever falls out of that.

Format so it can actually be read

Most applications go through an applicant tracking system before a person sees them. That system is a database with a parser attached: it extracts text from your file and maps it into fields a recruiter later searches. Anything that carries meaning visually rather than textually can be lost on the way in.

• One column. Two-column layouts interleave into alternating fragments.
• No tables. A skills grid flattens into a run of words with no structure left.
• Conventional headings: Experience, Education, Skills. A parser matches against a vocabulary it already knows.
• One date format, everywhere. Three formats on one page produce a garbled employment history and invent gaps that do not exist.
• Links written out as text, because a hyperlink whose destination lives only in file metadata arrives as the word "portfolio".

The two-minute test: open your PDF, select all, copy, paste into a plain text editor. What you see is roughly what a parser sees. If it reads as a coherent document, you are fine.

Before you send it