Resume
A resume has one job: to make a stranger confident enough to spend thirty minutes with you.
A resume is not a record of your career. It is an argument, made to a specific stranger, that a conversation with you is worth thirty minutes of their week. Everything that does not advance that argument is taking up space, and the most common problem with a resume is not that it is badly written but that it is a complete and faithful list of things you have done.
The two failure modes are separate and need separate fixes. A resume can fail on format — unreadable in the first ten seconds, or mangled by the software it was uploaded into — and it can fail on content, where a reader gets through it and finds nothing that distinguishes you from six other applicants with the same job title. Formatting problems are cheap to fix. Content problems take an afternoon and are worth it.
The guides in this topic assume you are applying to real roles at real employers rather than optimising a document in the abstract. Where advice here conflicts with something you have read elsewhere, the difference is usually that the other version is optimising for a machine that does not work the way people think it does — which is worth understanding before you act on it.
Key terms
- Reverse chronological
- Listing roles most recent first. It is the format every reader expects and every parser handles correctly, and any deviation from it — a functional or skills-based resume — is read as an attempt to obscure a gap or a lack of relevant recent work, whether or not that is why you chose it.
- Evidence bullet
- A line describing something that happened because you were there, with enough specificity that a reader can picture it. Distinguished from a duty bullet, which describes the boundaries of the job and would be identical for anyone who held it.
- Master resume
- A working document holding every bullet you have ever written about your work, far longer than any resume you would send. Applications are produced by cutting from it rather than composing from scratch, which is the only version of tailoring that survives more than a handful of applications.
- Tailoring
- Adjusting a resume for a specific role — typically the summary line, the order of bullets and the leading skills. It does not mean rewriting the document, and it does not mean inserting keywords into sentences where they do not belong.
Frequently asked questions
How long should a resume be?
One page for anyone with under roughly eight years of experience, two beyond that. The rule is about how much genuinely relevant material exists, not about seniority as such — a specialist with fifteen years in one function may still have a strong one-page resume. What does not work is three pages, because the third page is not read and its existence tells a reader you could not decide what mattered.
Should I write a different resume for every application?
No — you should keep one master document with more evidence than fits, and cut a version from it per application. Rewriting from scratch each time is unsustainable and people abandon it within a week. Cutting takes ten minutes and produces a better result, because you are choosing among things you already wrote carefully rather than composing under deadline pressure.
Do resume templates with columns and graphics hurt me?
Sometimes, and the reason is parsing rather than taste. Multi-column layouts, text inside images and content in headers or footers are the layouts most likely to be read out of order or dropped entirely by the software that ingests your file. A clean single-column document is not a stylistic preference; it is the format most likely to survive intact.
Should I include a cover letter if it is optional?
It depends on the application type, and the honest answer is that it is often not read. Where it counts is a smaller employer, a role you are reaching for, or an application where you have a specific reason for approaching this employer that the resume cannot carry. Where it does not is a high-volume graduate scheme with a structured form.