How to Write a Resume (2026 Guide)

Most resumes lose the reader in the first seven seconds.

That’s roughly how long a recruiter spends on the initial scan before deciding whether to keep reading (TheLadders eye-tracking research). A resume isn’t your career autobiography. It’s an argument for one specific job, and anything that doesn’t support that argument is working against you.

Start with the job, not your history

Before you write a line, read the job description twice and pull out the exact phrases that matter: job titles, tools, qualifications. Those words aren’t decoration. Most companies run applications through an applicant tracking system (ATS) first, and a recruiter searches that database using terms straight from the posting. Jobscan found that candidates whose resume job title matches the listing get interviews about 10 times more often than those with a mismatched one.

So mirror the language of the role wherever it’s honest. Don’t claim skills you can’t defend in an interview, but do use the employer’s vocabulary instead of your own clever synonyms.

Open with a summary that says something

The top third of the page gets around 80% of a recruiter’s attention, so don’t waste it on filler. Skip the objective (“Seeking a challenging role where I can grow”) and write three or four lines stating your specialism, years of experience, and one concrete result. “Operations lead, 8 years, cut fulfilment costs 22% across two warehouses” tells a hiring manager more than a paragraph of adjectives ever will.

Make experience about results, not duties

This is where most resumes fall apart. Cultivated Culture analysed over 125,000 resumes and found 36% contained zero measurable metrics, just lists of responsibilities. Yet resumes with quantified achievements are roughly 40% more likely to make the shortlist (TalentWorks).

Use one pattern for every bullet: action verb, what you did, the result with a number.

• Weak: “Responsible for managing social media.”
• Strong: “Grew Instagram engagement 40% in six months by testing weekly content formats.”

If you don’t have exact figures, estimate honestly. “Reduced processing time by roughly 30%” beats “improved efficiency” every time. Numbers signal scale and proof; vague duties signal nothing.

Keep the formatting boring on purpose

The resume that wins isn’t the prettiest one. Stick to a single-column layout, standard headings (Experience, Education, Skills), reverse-chronological order, and a common font at 10–12 points. Two-column “designer” templates routinely scramble the reading order when software parses them. Put your contact details in the body, never in the header or footer, where many systems can’t read them. Export a text-based PDF so your layout holds. ResumeMay’s templates are built around this structure.

Order it for your career stage

There’s no single correct section order. Mid-career professionals should lead with experience. Recent graduates and career changers should move education, projects, or a skills summary up top, because that’s their strongest evidence. The rule is simple: put your best proof where the eye lands first.

Cut the lines that say nothing

Some phrases are pure filler, and recruiters skim straight past them. Drop “references available upon request,” generic objective statements, and soft-skill stacks like “hardworking, detail-oriented team player.” None of those are claims you can prove on the page. If a line doesn’t help answer “why this person, for this job,” it’s spending space your achievements should own instead.

You don’t need to fit one page

The one-page rule is the most repeated myth in resume advice. It holds for early-career candidates with under five years of experience. Beyond that, two pages is standard, and about 90% of recruiters say a two-page resume is fine (Reed survey). Cutting relevant, recent achievements just to hit one page does more harm than good. Don’t pad, but don’t amputate either.

Once the structure is solid, write a fresh version for each role you actually want, adjusting the summary, the keywords, and which bullets you lead with. That’s about 15 minutes per application, and it returns roughly three times the callbacks of a generic send. Spend it on the handful of jobs you’d genuinely take.