The Complete Resume Writing Guide

A recruiter filling a mid-level role will see somewhere between 200 and 500 applications. They are not reading them. They are looking for a reason to move a small number into a "maybe" pile and get through the rest before lunch. The first pass is closer to six seconds than six minutes, and it is spent on three things: your most recent job title, the company next to it, and whether the dates line up.

That is not cynicism. It is the constraint the document has to survive.

Everything below follows from one idea: a resume has exactly one job, which is to get you a conversation. It is not a career history, not a confessional, and not a place to be comprehensive. Anything on the page that does not move a stranger toward "let's talk to this person" is costing you the attention you needed for something else.

What your resume is actually competing against

Before a human sees it, most resumes pass through an applicant tracking system. There is a lot of folklore about this and most of it is wrong. The ATS is not scoring you out of a hundred and rejecting you at 74. In the overwhelming majority of deployments it is a database with a search box. A recruiter types in the two or three things they cannot compromise on — a certification, a language, a tool — and reads what comes back.

What that means practically: the system's failure mode is not judgment, it is extraction. If your job titles end up in a field labelled "Skills" because you built the layout in two columns, you are not scored badly. You are invisible. That distinction matters, because it tells you what to fix — structure, not vocabulary.

Run your own file through an ATS check before you send it anywhere. Read what comes back as plain text. If you cannot tell which job each bullet belongs to, neither can the parser.

Choosing a format, in one decision

There are three formats and roughly one situation each.

Reverse-chronological lists jobs newest first. Use it. This is the default for something like nine out of ten candidates, and every recruiter can read it without effort.

Functional groups everything under skill headings and pushes employment history to a footnote. It exists to hide something, every experienced recruiter knows it exists to hide something, and its main effect is to make people look for what you are hiding. Avoid it, including — especially — when you have gaps.

Hybrid opens with a short block of relevant capability, then runs a normal reverse-chronological history underneath. This is the one honest use of a non-standard shape: when your last job title does not describe the job you are applying for. A teacher moving into customer success, an analyst moving into product. The opening block does the translating; the history stays legible.

If you are unsure, you want reverse-chronological. The times you don't will be obvious.

The header

Name, city, one phone number, one email address, one link. That is the whole thing.

Cut the full street address — it is a relocation-bias liability and no one is mailing you. City and state or country is enough, and if you are open to remote, say so in parentheses rather than leaving people to guess. Cut the photo unless you are applying somewhere it is genuinely conventional. Cut date of birth, marital status, and nationality for the same reason.

The link should be the one that is actually worth clicking. For most people that is LinkedIn. For engineers, designers, and writers it is a portfolio or repository, and it should go directly to work — not to a landing page that requires another click to find any.

Summary or objective

A summary is three lines describing what you do, at what level, with what evidence. It is worth writing when you are continuing in your field, because it lets a reader place you before they start reading dates.

Operations manager, eight years in third-party logistics. Took a 40-person warehouse from 91% to 98.6% on-time dispatch inside a year. Now looking for a site with a harder problem.

An objective states what you want. That is only useful when the resume needs explaining — you are changing industries, returning after time out, or deliberately stepping down a level. In every other case you are spending your best three lines telling a company what you would like from them, on a page whose entire purpose is telling them what they get.

Whichever you write, write it last. You cannot summarise a document you have not finished.

Work experience, which is the resume

Everything else is context. This is the part that decides.

Each role gets a title, a company, dates to the month, and a short line of orientation if the company is not a household name — "Series B fintech, 60 staff" saves a reader from guessing at your scope.

Then bullets. Not paragraphs, not a job description copied from the offer letter. The failure mode here is describing duties, and it is nearly universal:

The pattern underneath is: what was the situation, what did you do, what changed. You do not need to name the framework or force every bullet through it. You do need the third part, because that is the part almost nobody writes.

When you genuinely have no numbers

Not every job produces metrics, and inventing them is worse than not having them. Reach for scale, frequency, or duration instead — they are all real, all verifiable, and all more concrete than an adjective.

"Sole", "across two offices", "roughly 40 a week" — none of those are metrics in the finance sense. All of them tell a reader something true about the size of the job.

How many bullets

Three to six for your current role and the one before it. Two or three for anything older than about eight years. One line, or nothing at all, for the summer job from a decade ago.

Treat bullets as a fixed budget rather than a form. If your most recent role is the least relevant one, it does not automatically get the most space. Spend the lines where the work looks most like the work you are applying for.

Verbs

Start each bullet with something that describes a decision. "Led", "rebuilt", "negotiated", "cut", "shipped", "consolidated", "recovered". Avoid "responsible for" and "helped with", which describe proximity to work rather than the work. Avoid "spearheaded", "leveraged", and "synergised", which have been used so heavily in resume templates that they now read as filler.

Do not use the same verb twice in one role.

Skills, education, and the rest

The skills section should be scannable and specific. Tools, languages, systems, certifications. Not "communication", not "team player", not a five-star rating of your own Excel ability — self-assessed proficiency bars tell a reader nothing and consume a third of a page.

Anything in that section should appear again inside a bullet, doing something. A skill listed but never demonstrated reads as aspirational.

Education goes at the bottom once you have two or three years of work behind you, and at the top before that. Degree, institution, year. Drop your GPA after your first job unless it was exceptional and recent. Drop high school entirely once you have a degree.

References do not belong on a resume. Neither does "References available on request" — it takes a line to announce the industry default. Keep a separate sheet, ask your referees before you list them, and hand it over when someone asks.

Length

One page under ten years of experience. Two beyond that. Three only for academic CVs, senior medical roles, and a handful of government applications that ask for it explicitly.

The page count is a symptom. If you cannot fill a second page with material that would change a hiring decision, you do not have a two-page resume — you have a one-page resume with padding. Equally, do not compress a genuinely long career into one page by shrinking the type to 9pt and the margins to nothing. A dense unreadable page is worse than a clean second one. Our guide to margins, fonts and spacing covers where the real floor is.

Tailoring, and what keywords actually means

Sending the same document to forty companies is the single biggest reason good candidates get no replies.

Tailoring does not mean rewriting from scratch. It means reading the posting properly and adjusting three things: the summary, the order of your bullets, and the vocabulary.

The vocabulary point is where "keywords" gets misunderstood. It is not about density, and there is no threshold to hit. It is about matching the words the company actually uses. If the posting says "client onboarding" and your resume says "customer implementation", a recruiter searching their database for the first phrase will not find you — not because an algorithm penalised you, but because you and they are describing the same work with different nouns.

So: pull the six or eight terms that appear repeatedly in the posting. Check each one against your resume. Where you have done that work under a different name, change the name. Where you have not done it at all, leave it alone. Stuffing terms you cannot back up gets you into a conversation you will lose in the first ten minutes.

If you want a starting point for your specific job title, our resume examples by role show the vocabulary that actually appears in postings for over a thousand roles.

Before you send it

• Every bullet has an outcome, not just an activity.
• No duty descriptions copied from a job posting — yours or theirs.
• Dates run to the month and account for every year.
• One column. No text inside images, headers, or footers.
• Saved as PDF, unless the posting explicitly asks for .docx.
• Filename is Firstname-Lastname-Resume.pdf, not resume-final-v4.pdf.
• Read aloud once. Anything you stumble over, a stranger will too.

That last one catches more than any checklist. A resume is read by people, and people notice when a sentence was assembled rather than written.