Resume Sections Explained, in the Order Recruiters Read Them

A resume is not a form to be filled in. It is a document with a reading order, and that order has changed substantially over the last twenty years as hiring shifted from CV databases to applicant tracking systems. The most common structural mistake is arranging sections by convention rather than by what the reader needs first.

The sections, and what each is for

Header

Name, location, email, and a phone number you answer. A link to a LinkedIn profile or portfolio if you have one. Nothing else. No date of birth, no nationality, no marital status, no photograph, and no street address beyond city and country — those fields are largely obsolete and several are actively problematic in some countries.

Summary

Three or four lines at most. What you do, the domain you do it in, the scale you have operated at, and what you are looking for. It exists to save the reader fifteen seconds, so it must be specific. "Results-driven professional with proven track record" is a category error: it says nothing and occupies the most valuable real estate on the page.

A summary is worth including when you are changing field, returning to work after a gap, or targeting a niche role. For a straightforward internal move, a strong recent experience section can do the job without one, and the space is better spent on evidence.

Experience

The core. Reverse chronological, three to five bullets per role, each one a claim followed by evidence. The single most common failure is describing duties rather than outcomes: "responsible for the accounts process" tells the reader what your job title already said. "Consolidated three separate billing systems into one, cutting month-end close from nine days to four" is worth three bullet points on its own.

The structure that works is: what the situation was, what you specifically did, and what measurably changed. Most of the third part is missing from most resumes, and it is the part a hiring manager is actually scanning for.

Skills

Tools, methods, technologies and domain knowledge, grouped and ordered by relevance to the role. Two things to avoid: a bar chart of self-assessed proficiency, which is noise; and an undifferentiated list of thirty items, which tells the reader nothing about what you would actually choose. Ten skills you would be happy to be interviewed on beat thirty you have seen mentioned.

Education

Institution, qualification, dates. For early-career candidates this is important; for anyone with five or more years of relevant experience it belongs below experience, and often compresses to a line or two. Include grades only where they are strong or the field expects them — a first-class degree is worth stating, a predicted grade is not.

Optional sections

• Projects — for early career, self-taught or portfolio-based candidates, where a project demonstrates the skill better than a job title can.
• Certifications — only where they are recognised in the field or required by the role. A wall of unrelated certificates reads as padding.
• Languages — where genuinely relevant, and especially in multilingual markets.
• Volunteer work — genuinely, when it demonstrates transferable skill or commitment. It is not a substitute for experience in the same way, but it is not nothing either.
• Awards — real ones only, and only where they are meaningful to somebody in the field.

Order by seniority

The master document

Build one complete document that is too long for any single application, and derive from it every time. The master holds everything: every role, every project, every skill, in full. Each application takes the relevant parts, reorders the summary, cuts the bullets that do not serve the target role, and moves on.

The alternative — writing a fresh document each time — feels thorough and produces four slightly different versions with four slightly different claims, which is a liability rather than an asset. One document, many targets, no contradictions.

Common questions

Frequently asked questions

Should I include a photo or my date of birth?

No, in most markets, and yes in a minority. Germany, Austria, Switzerland, parts of the EU and some Asian markets expect a photo, and in a few places omitting it can make an application feel incomplete. Include it where it is conventional; do not include it where it is not, because it introduces bias into a process that should be evidence-based and can be seen as an unlawful disclosure in some jurisdictions.

How long should each bullet point be?

One to two lines. Long bullets get skimmed, and a reader who skims has already decided. If an achievement needs four lines, it is usually two achievements.

Should I show gaps in employment?

Yes, do not hide them — the dates are visible whether you annotate them or not. A short note explaining a career break, a course, caring responsibilities or health reasons is enough. Extended unexplained gaps invite the reader to fill in the worst version, and they always will.

Is a separate skills section even needed?

For a career changer or someone moving between tools, yes — it is how the reader connects your history to the job's requirements. For someone clearly inside a field for years, the experience bullets usually demonstrate the skills adequately, and the section can be a short line near the bottom instead of a block.

Where to go next

These are the services referenced above. Compare them on your own terms before you sign up for anything.

• Resume Lab →
• Teal →

Related reading

• Resume vs CV: Which One to Send 3 min read
• How to Write a Professional Resume That Reads as Evidence 3 min read
• How to Make a Resume ATS-Friendly Without Making It Ugly 4 min read
• Common Resume Mistakes and What Each One Costs You 4 min read