A resume is not a career history. It is a short, targeted argument that you can do a specific job, supported by evidence. Most resumes fail because they describe duties instead of results, and because they are written once and sent everywhere. This guide walks through the whole document section by section, with the wording choices that actually change whether a recruiter reads past the first third of the page.
Before you write anything: read the job posting properly
Open the posting you want most and read it twice. The first read tells you what the job is. The second read tells you what the employer is worried about. A posting that repeats "cross-functional" four times is describing an organisation where projects stall between teams. A posting that lists a specific tool three times is telling you the screening filter.
Write down three things before you touch the document:
- The five to eight terms that appear in the posting and describe skills or tools, in the exact words used. If they say "stakeholder management", do not write "working with people".
- The seniority signal. "Support the team" and "own the roadmap" are different jobs with the same title.
- The one problem the role exists to solve. Nearly every posting has one, usually in the first paragraph.
Everything you write from here should be aimed at those three notes. This is what people mean by tailoring, and it is usually a thirty-minute edit rather than a rewrite.
Choosing a format
There are three structures in common use, and only one of them is a safe default.
- Reverse chronological. Most recent role first, working backwards. This is what recruiters expect and what parsing software handles best. Use it unless you have a strong reason not to.
- Functional. Groups achievements by skill and hides dates. Experienced recruiters read this as an attempt to conceal something, and it parses badly. Avoid it.
- Hybrid. A skills or projects block above a chronological history. Genuinely useful for career changers and for technical people whose projects matter more than employers.
On length: one page if you have under about ten years of experience, two pages beyond that. Academic and research roles have their own conventions and often expect longer documents. Three pages for a mid-career commercial role signals that you cannot edit.
Keep the layout single-column with real text. Columns, text boxes and graphics look considered on screen and frequently scramble when parsed. If you want a designed look without that risk, start from a tested layout in our collection of 28 resume templates rather than building one in a word processor.
The header
Name, city and region, phone, professional email, LinkedIn URL. That is the whole list.
Things to leave out: full street address, date of birth, marital status, photograph (outside countries where it is conventional), and the word "Resume" as a heading. Nobody is confused about what the document is.
If you are targeting roles in a different city, put that city in the header or add a line saying you are relocating. Recruiters filter on location early and a mismatch is a silent rejection.
The professional summary
Three to four lines at the top, replacing the old objective statement. An objective says what you want. A summary says what you offer. Employers care about the second.
A workable structure is: what you are, how long, the domain you know, and one concrete result.
Weak: "Hard-working marketing professional seeking a challenging role where I can utilise my skills and grow with a dynamic company."
Stronger: "B2B marketing manager with seven years in enterprise software, specialising in demand generation and lifecycle email. Built the nurture programme that became the largest single source of qualified pipeline at a 200-person SaaS company."
The second version tells a recruiter what to do with you. The first could be anyone. There are role-by-role summaries written this way in our resume examples by job title if you want more patterns to work from.
Experience: the part that decides the outcome
This is where most of the effort should go. The unit of work is the bullet point, and a good bullet has three parts: what you did, how you did it, and what changed as a result.
Duty: "Responsible for managing the company's social media accounts."
Achievement: "Rebuilt the LinkedIn content programme around customer case studies, growing followers from 4,000 to 19,000 in fourteen months and producing roughly 40 inbound demo requests per quarter."
Some practical rules that hold up across industries:
- Start with a verb, in the past tense for previous roles and present tense for the current one. Cut "Responsible for", "Tasked with" and "Helped to". They add length and remove ownership.
- Quantify where a number exists. Money, volume, time saved, percentage change, headcount, number of clients. If you genuinely have no numbers, use scale instead: "across eleven markets", "for a portfolio of 30 accounts".
- Do not invent numbers. Interviewers ask how you calculated them, and an estimate you cannot defend is worse than no number at all. "Reduced report preparation from two days to about four hours" is fine and honest.
- Three to six bullets per recent role, tapering to one or two for jobs more than ten years back.
- Lead with your strongest bullet. Nobody reads to the bottom of a block.
Turning a duty into an achievement
If you are stuck, ask three questions of every task you performed. Why did anyone want this done? What was it like before you arrived? What would break if you stopped? The answers usually contain the achievement.
| Duty version | Achievement version |
|---|---|
| Handled customer complaints | Resolved escalated complaints for a 60,000-customer base, cutting average case age from nine days to three by rewriting the triage rules |
| Assisted with monthly reporting | Automated the monthly management pack in Power BI, replacing a two-day manual process and removing a recurring source of version errors |
| Managed a team of five | Led a team of five analysts through a platform migration with no unplanned downtime and no attrition during the project |
If you want to see how the same principle looks in a finished document for your own job title, read the experience sections of published examples rather than admiring the layouts.
Skills
Keep this section short, specific and true. Two groupings work well: tools and technical skills, then domain knowledge. List things a hiring manager could reasonably test you on.
Cut the following: "Microsoft Office" unless the job is administrative, "team player", "excellent communication skills", and self-assessed proficiency bars. A bar chart claiming you are 85 per cent proficient in Python communicates nothing measurable.
If a posting names a tool you genuinely use, use their word for it. Software that screens applications is matching strings, and "GA4" and "Google Analytics 4" are not the same string.
Education and certifications
Institution, qualification, and year if it is recent. Move education below experience once you have two or three years of work behind you. Graduating year can be omitted if you are concerned about age screening, though gaps in dates elsewhere invite questions.
Include certifications that are current and relevant. A lapsed certification from 2014 in a tool nobody uses is clutter. Include a professional licence where the role requires one and put it near the top, since it is a hard filter.
Formatting that survives screening
Most mid-size and large employers run applications through an applicant tracking system before a person sees them. You do not need to game it, but you should avoid breaking it:
- Standard section headings: Experience, Education, Skills. Not "Where I've Made My Mark".
- A common font at 10 to 12 points, with real bullet characters rather than symbols from a decorative font.
- No critical information inside headers, footers, text boxes or images. Parsers routinely drop those regions.
- Submit as PDF unless the posting asks for a Word document. Name the file with your name and the role.
- Dates in a consistent format, month and year, in the same place on every entry.
Before submitting, run the finished document through our free ATS resume checker to confirm it parses cleanly and that the terms from the posting actually appear. It takes a minute and catches the failures you cannot see by looking at the page.
The final edit
Do these five checks before you send anything.
- The six-second test. Look at the top third of page one. Does it say what you are and what you are good at? That is all most first passes read.
- Cut ten per cent. Every resume has filler. Removing it makes the rest hit harder.
- Read it aloud. Awkward phrasing and stray tense changes are audible in a way they are not visible.
- Check the numbers. Be ready to explain how you arrived at each one.
- Check the company name. Sending a document that mentions the wrong employer ends the application immediately, and it happens constantly.
Then get one other person to read it, ideally someone who hires. Ask them one question: what job do you think I'm applying for? If they cannot answer in a sentence, the document is not focused enough yet.
Keep a master version
Maintain one long document containing every role, project and metric you have ever collected. Never send it. For each application, copy it, cut it to the relevant material, and reorder against the posting. This turns tailoring into an editing job that takes half an hour rather than an evening of writing from scratch.
You can build and store tailored versions in our free resume builder, which keeps the formatting consistent while you swap the content per application. The document is only the entry ticket, but a weak one stops the process before anyone hears what you can actually do.
