How to Write Every Section of Your Resume (With Copy-Paste Examples)

Every section of a resume follows one rule: give each section a single job to do, then write it with the formula that job demands. The header routes you; the summary sells your fit in three lines; the skills section feeds the ATS its keywords; the experience bullets prove impact with numbers; education and certifications close credibility gaps. Below is the complete formula for every resume section — what goes in, what stays out, the exact order, and copy-paste examples for each.

This guide is the hub for everything section-related on this site. Each part of your resume gets one deep-dive linked below; this page gives you the working formulas so you can build or rebuild a complete resume today. Whether you're starting from a blank page or fixing a document that isn't getting callbacks, work through the sections in the order presented — that's also the order parsers and recruiters read them.

If you're rebuilding from scratch, start by understanding why section order affects ATS parsing — the sequence below isn't stylistic preference; it's what parsing algorithms map against.

Resume Section Order: What Comes First?

The canonical order that works for 90% of job seekers:

1. Header — name, contact details, links
2. Professional summary — 2–3 lines positioning you for the target role
3. Skills — keyword-loaded, grouped, scannable
4. Work experience — reverse chronological, achievement bullets
5. Education — degrees, dates, honours
6. Certifications & extras — credentials, languages, volunteer work

Two legitimate exceptions: students and recent graduates move Education above Experience, because their degree is their strongest credential; career changers sometimes lead with a Skills or "Relevant Experience" block because their chronology undersells them. Everyone else follows the standard order.

Why does order matter so much?

Two audiences, two scanning behaviours. ATS parsers extract content in reading order and map it to profile fields using heading recognition — nonstandard headings and shuffled sections cause fields to populate wrongly (your skills landing under education, for instance). Human reviewers scan top-down in seconds, spending most attention on the first third of page one. Standard order satisfies both: machines parse cleanly, humans hit your summary and top achievements immediately. Our breakdown of the seven-second recruiter scan details exactly where eyes land first.

Section 1: The Header — Contact Details Done Right

The header's only job is being findable. Include:

• Name — largest text on the page, no titles like "Mr" or credentials cluttering it
• Phone — a number you actually answer
• Email — professional address based on your name; retire the novelty account
• Location — city and state/region only
• LinkedIn URL — customised, not the default string of characters
• Portfolio link — for any role where work samples matter

What kills resumes at the header stage

Placing contact details inside a document header or footer — many ATS platforms skip these zones entirely, silently deleting your phone number. Two-column headers can also scramble parsing order. Keep everything in the body, single column, plain text labels. Full street addresses are unnecessary in 2026 and create privacy exposure; city-level location is enough for commute and right-to-work screening.

Section 2: The Professional Summary — Your Three-Line Pitch

The summary replaces the dead "objective" format for almost everyone. Its job: tell a skimming recruiter who you are, what you're strongest at, and why you fit this specific role — in two to three lines containing the posting's key vocabulary.

The formula:

[Adjective] [job title] with [X] years of experience in [relevant domain]. Proven record of [top achievement with metric]. Skilled in [2–3 keywords from the target posting].

Example output: Data analyst with 4 years of experience turning messy retail datasets into pricing decisions. Cut stock-out rates 22% across 40 stores by rebuilding demand forecasts in Python and Power BI. Skilled in SQL, stakeholder reporting, and A/B testing.

Tailor the final clause per application — swap in whatever the posting emphasises. For level-specific templates ranging from freshers to directors, our library of resume summary examples by career level has 40+ ready-to-adapt versions. If you're early-career and genuinely have nothing to summarise yet, the objective format still has narrow legitimate uses — our comparison of resume objectives versus professional summaries gives the decision rule.

Section 3: Skills — Feed the Machine Without Starving the Human

The skills section exists primarily for keyword matching, secondarily for quick human verification. Structure it as grouped lists — never a paragraph, never a rating-scale graphic ("★★★★☆ Excel") which parsers can't read and recruiters mock.

Structure:

• Technical: SQL (advanced), Python (pandas, NumPy), Power BI, Tableau
• Analytical: forecasting, cohort analysis, statistical modelling, dashboard design
• Collaboration: cross-functional project delivery, stakeholder management, documentation

Three rules govern this section. First, every listed skill must be evidenced somewhere else — a bullet, a project, a certification. Listing proves nothing; contextual proof convinces both algorithms and people. Second, use the posting's exact phrasing: if the ad says "stakeholder management", don't write "relationship building". Third, keep it to 8–14 skills; exhaustive lists dilute signal.

For the full menu organised by role and seniority, see our list of 150+ skills to put on a resume. Understanding the difference between hard and soft skills placement matters here too: hard skills belong in your dedicated skills section where ATS filters verify them; soft skills earn their place woven into achievement bullets, not claimed in isolation.

Section 4: Work Experience — Where Resumes Win or Lose

This section carries 60–70% of your persuasive weight. Format each role consistently:

Job title — Company, Location — Month Year to Month Year, followed by 3–6 bullet points.

The bullet formula that works everywhere

Each bullet: Action verb + what you did + measurable result. This is the X-Y-Z structure popularised in Google's recruiting guidance — "Accomplished [X], measured by [Y], by doing [Z]" — and it transforms duty statements into evidence.

• Duty version: Responsible for managing the company's social media accounts.
• Achievement version: Grew Instagram following 140% in eight months by launching a weekly customer-story series, lifting referral traffic 31%.

Choosing the right opening word matters more than most applicants realise — "responsible for" signals duty while "grew", "cut", and "rebuilt" signal ownership. Our grouped list of 250+ action verbs with before/after rewrites fixes weak openers fast. Then put numbers behind those verbs: our formulas for quantifying achievements without obvious metrics cover volume, frequency, percentage, time saved, and scale — including approaches for support, HR, and teaching roles where revenue numbers don't exist.

How far back should experience go?

Ten years is the norm; fifteen maximum for senior roles. Older roles compress to a single line (title, company, dates) without bullets. Exceptions exist for continuous tenure in one profession or legally required detail. When trimming creates gaps, handle them honestly rather than hiding them — our guide to explaining employment gaps provides framing language for caregiving, study, and redundancy periods.

What about job titles that don't match the target?

ATS matching weighs your current title heavily against the posting's title. You can't invent titles, but you can add honest clarification: "Customer Success Associate (account management focus)" or a parenthetical mapping like "(equivalent to operations coordinator)". Our guide to mirroring a job title without lying covers exactly where honesty's line sits and how parenthetical retitling passes both ATS checks and reference checks.

Section 5: Education — More Than a Degree Name

List degrees in full formal form: BSc (Hons) Computer Science, University of Manchester — 2024. Add graduation year unless you graduated over a decade ago. Include honours classifications (UK) or GPA (US/India contexts) when strong; omit when unremarkable rather than drawing attention.

Students and freshers can expand this section strategically: relevant coursework lines, final-year projects, and academic awards all substitute for thin work history. As experience accumulates, shrink education accordingly — five-plus years into your career, it needs three lines total.

Certifications deserve their own subsection beneath education when they're role-relevant: AWS, PRINCE2, PMP, Google Analytics, NMC registration — formatted as Name, Issuing Body, Year, with credential IDs for verifiable ones. Expired or irrelevant certificates come out; our guide to listing certifications recruiters actually value explains what earns space and what quietly undermines credibility.

Section 6: Extras That Earn Their Space (and Ones That Don't)

Special Case: The Projects Section (For Freshers and Career Changers)

When work history is thin or off-target, a projects section substitutes persuasively. It works because projects demonstrate the same evidence as jobs: scope, tools used, decisions made, results produced.

Format each project as:

• Project name — one-line context (personal, academic, freelance, volunteer)
• Tech stack or methods — matching the posting's vocabulary exactly
• Two bullets: what you built/did, and the outcome (users, grade, adoption, time saved)

Example: Retail Demand Forecasting Dashboard — final-year project. Python, Power BI, SQL. Built a forecasting model on 3 years of synthetic transaction data; achieved 88% directional accuracy against holdout data and presented methodology to an industry panel.

Two to three strong projects beat five padded ones. For IT freshers specifically, our guide to writing the projects section for IT fresher resumes covers which college projects impress recruiters and which quietly waste space.

Special Case: The Volunteer and Extracurricular Block

Volunteer work earns its place when it evidences role-relevant capabilities: treasurer of a society proves financial handling; organising a 200-person event proves logistics and leadership; helpline volunteering proves composure under pressure. Format it like experience — organisation, role, dates, one or two outcome bullets — but keep it honest in scale. Recruiters discount inflated volunteer titles instantly during reference conversations.

UK applicants note: community involvement carries more screening weight there than in most markets, particularly for public sector and healthcare roles where values-based recruitment is explicit. Indian applicants targeting mass recruiters can use extracurriculars similarly for "leadership potential" criteria that campus screens apply.

Worked Example: Rewriting a Full Experience Block

Watch the formulas apply to a real transformation. Here's a typical weak submission for a customer support role:

Customer Service Executive — RetailCo — 2023 to 2025

• Responsible for handling customer queries and complaints
• Helped customers with orders and returns
• Worked with the team to improve service

Three duties, zero evidence, no keywords beyond the generic — this resume loses to every competitor who quantified anything. The rewritten version:

Customer Service Executive — RetailCo, Birmingham — Jun 2023 to Feb 2025

• Resolved 60+ daily customer queries across email, chat, and phone while maintaining a 94% satisfaction score, top quartile of a 40-person team
• Cut average refund-processing time from 5 days to 36 hours by drafting a new returns macro adopted team-wide
• Escalation point for VIP accounts, personally recovering £80K in annual at-risk revenue through proactive outreach

Same job, same person, same facts — different framing discipline. Every bullet now carries a verb of ownership, a number, and a keyword cluster ("customer queries", "escalation", "VIP accounts") that ATS filters for support roles scan for. This rewrite took fifteen minutes using the formulas above; it typically doubles interview conversion on its own.

Adapting depth by career stage

The same block changes shape across a career:

• Fresher: internship bullets follow identical structure but draw numbers from projects and volume handled ("processed 200+ tickets during a three-month placement")
• Mid-level: mix execution metrics with one process-improvement bullet per role — recruiters screen mid-level candidates for leverage, not just output
• Senior: shift from personal metrics to team outcomes and scope ("led a team of 9 across two sites; retained 100% of staff through a restructuring year") — individual-contributor achievements read as failure to delegate at this level

Our library of annotated resume examples by role shows this progression applied across sectors if you want full documents to model against.

Tailoring Every Section to the Job Description

The section formulas above produce a strong master resume. Winning applications then tailor three specific touchpoints per posting:

1. Summary's final clause — name the target role and swap emphasis keywords
2. Skills ordering and phrasing — lead with what the ad leads with; adopt its exact terms
3. Bullet emphasis — reorder bullets within roles so the most relevant achievement appears first; you rarely need to rewrite them entirely

This takes ten minutes once your master document is solid. Doing it manually is fine; automating it is faster — paste the job description into JD2CV and the tool identifies which keywords are missing from every section simultaneously. Our walkthrough of tailoring a resume to any job description details both routes.

How do ATS keyword checks interact with each section?

Different sections carry different keyword weight. Hard requirements (tools, certifications, methodologies) must appear in your skills section and be evidenced in a bullet — parsers increasingly cross-check context, and recruiters always do. Job-title keywords matter most in your current title line and summary. Soft-skill keywords ("stakeholder management", "cross-functional") score best inside achievement bullets rather than listed bare. Our industry-level breakdown of ATS keywords by sector shows which vocabulary each employer type rewards.

How many bullets should older roles get?

Apply a tapering rule: your current role gets five to six bullets, each prior role gets one fewer than the last, and anything past ten years compresses to a single line with no bullets. This mirrors how recruiters actually read — attention concentrates on the most recent two roles, and bullet counts should reflect that gradient rather than treating a decade of history uniformly.

Frequently Asked Questions About Resume Sections

Should I include every section on my resume?

No. Sections earn space through relevance. A career changer with twenty years of experience may skip a separate skills section because their bullets carry keywords already. A fresher may skip certifications they don't have. The mandatory core is four sections: header, summary, experience (or projects for new grads), education. Everything else justifies itself by strengthening your case for the specific role.

Can AI write my resume sections for me?

AI drafts well and finalises poorly. Generated summaries and bullets arrive grammatically clean but generically worded — and hiring managers increasingly recognise the register instantly. The reliable workflow: draft with AI assistance, then inject specifics only you know — actual percentages, project names, tool versions. Our analysis of whether ATS systems flag ChatGPT-written resumes explains where the real risk lies (it's generic phrasing, not detection software). Tools like JD2CV anchor generation to your target job description specifically, which keeps output concrete rather than boilerplate.

How long should each section be?

• Summary: 2–3 lines, always
• Skills: 8–14 entries, grouped
• Experience: 3–6 bullets per recent role, tapering for older roles
• Education: 1–3 lines after your first job; fuller for graduates
• Total length: one page under ~10 years' experience, two pages beyond — our one-page versus two-page breakdown settles the debate with parsing data

Should the skills section go before or after work experience?

Before, for technical and data roles where recruiters verify tool fit first. After, for people-facing and senior roles where narrative achievements should hit first and a keyword block interrupts them. When in doubt, before — ATS parsers read it earlier, and recruiter attention concentrates on page one where it sits.

How do I write resume sections with no experience at all?

Reallocate weight: education expands (projects, coursework, awards), a projects section substitutes for experience, and your summary leans on demonstrated capability rather than tenure. Never pad with a long objective or generic soft-skill claims — our fresher-specific guidance in the summary examples by level covers entry-level variants directly.

Do section headings need to be exact?

Standard variants parse reliably: "Work Experience" or "Professional Experience", "Education", "Skills" or "Core Skills". Avoid creative labels entirely — parsing maps run on known heading vocabularies, and every nonstandard heading risks misfiled content that never reaches the recruiter's view of your profile.

Can I use the same resume for every application?

A master document, yes; an identical submission, no. Untailored applications rank lower in ATS relevance scoring and read as low-effort to recruiters who see your exact document repeatedly across roles. The ten-minute tailoring routine above — summary clause, skills phrasing, bullet order — is the minimum viable customisation that separates you from the pile.

What's the biggest mistake people make in each section?

Summary: writing about themselves instead of the target role. Skills: listing tools they can't defend in an interview. Experience: duties without outcomes. Education: burying strong honours under outdated GCSE/A-level detail. Header: contact info trapped in a Word header field where parsers can't reach it. Fix these five and you're ahead of most applications any given posting receives.

How do I know if my finished resume actually works?

Test it against a real posting before applying. Paste the ad's requirements next to your resume and check: does every hard requirement appear verbatim somewhere? Does your summary name the role? Do half your bullets contain numbers? Better yet, automate the check — match-scoring tools quantify the overlap and highlight missing keywords precisely. For context on interpreting scores, our benchmarks guide covers what match score ranges mean by employer type.

A Complete Example Skeleton (Copy This Shape)

JAMES OKAFOR
Manchester, UK · 07xxx xxxxxx · james.okafor@email.com · linkedin.com/in/jamesokafor

Project coordinator with 3 years of experience delivering digital transformation projects in public-sector consultancy. Coordinated 12 concurrent workstreams worth £2.1M, hitting 95% of milestones. Skilled in PRINCE2, stakeholder reporting, and Jira workflow design — targeting complex programme environments.

Core skills: PRINCE2 (Foundation) · MS Project · Jira · Confluence · stakeholder management · risk registers · budget tracking (£500K+) · Gantt planning

Experience

Project Coordinator — Brightpath Consulting, Manchester — Mar 2023 to Present

• Coordinate 12 concurrent workstreams across a £2.1M government digital programme, maintaining 95% on-time milestone delivery
• Cut weekly status-reporting effort 40% by automating data collection in Power BI dashboards
• Onboarded and mentored 4 junior coordinators, reducing team ramp-up time from six weeks to three

Graduate Analyst — Brightpath Consulting, Manchester — Sep 2021 to Feb 2023

• Built risk-register tracking adopted across three client programmes, flagged 17 issues before escalation

Education
BA (Hons) Business Management, University of Leeds — First Class, 2021
PRINCE2 Foundation, AXELOS — 2022

Note what the skeleton does: summary names the target direction, skills mirror typical postings in that field, every visible bullet carries a number, and education stays compact because experience leads. Adapt the shape, replace the specifics, keep the discipline.

Key Takeaways

One job per section: summary pitches fit in 3 lines, skills feed keyword matching, experience proves impact with action-verb-plus-metric bullets, education closes credibility gaps. Follow canonical order for clean parsing, use the posting's exact vocabulary throughout, and cut anything that doesn't strengthen your case for the specific role. Every section above links to a deeper guide when you need it.

Want each section written and optimised against your actual target job? Try JD2CV's AI Resume Optimizer free — paste your resume and a job description, get section-by-section rewrites matched to what the employer asked for.