Most resumes fail for the same reason: they read like a job description of what the candidate was supposed to do, not evidence of what they actually accomplished. A recruiter or hiring manager spends seconds, not minutes, on a first pass — long enough to notice whether a resume shows impact or just lists duties. This guide covers how to write one that survives that first pass, for any field, at any stage of your job search after graduation.
Structure That Works Across Most Fields and Levels
| Section | What Goes In It | Notes |
|---|---|---|
| Header | Name, phone, email, LinkedIn URL, location (city/region is usually enough) | No photo, age, or marital status for US/UK/Canada applications — norms differ elsewhere, check locally |
| Summary (optional) | 2–3 lines positioning your background and target role | Skip it if it's generic filler; include it only if it adds information a recruiter can't get from skimming the rest |
| Work experience | Reverse-chronological, most recent first | Company, title, dates, location, then 3–5 quantified bullets per role |
| Education | Degree, institution, graduation date, GPA if strong and recent | Push further down the page once you have 2+ years of work experience |
| Skills | Technical skills, tools, languages — relevant to the role you're applying for | Keep this to genuinely relevant, verifiable skills, not a keyword dump |
| Projects / certifications (optional) | Relevant independent projects, certifications, or portfolio links | Especially useful for entry-level candidates without much work history yet |
For most early-career job applications (as opposed to academic or research-focused roles), one page is the right length. Two pages becomes defensible once you have roughly a decade or more of relevant experience — not before.
Quantified Achievements Beat Responsibilities, Every Time
This is the single biggest quality gap between resumes that get interviews and resumes that don't. A responsibility describes what your job was. An achievement describes what you did with it.
Template: Action verb + what you did + quantified result (and, where useful, how you did it)
| Weak (Responsibility-Based) | Strong (Quantified, Achievement-Based) |
|---|---|
| "Responsible for managing social media accounts" | "Grew Instagram following from 2,000 to 18,000 in 9 months by shifting posting cadence and content mix, driving a 3x increase in link-click traffic" |
| "Helped with customer support" | "Resolved an average of 45 customer tickets per day with a 96% satisfaction rating, reducing average response time from 6 hours to 90 minutes" |
| "Worked on a team project" | "Coordinated a 5-person team to deliver a client project two weeks ahead of schedule, resulting in a repeat contract worth $40,000" |
| "Assisted with data analysis" | "Built a dashboard automating a weekly report that previously took 6 hours manually, saving the team roughly 300 hours annually" |
Not every bullet will have a clean number, and that's fine — but aim for a clear majority to include one. If a role genuinely doesn't have quantifiable output, use scope instead: team size, budget managed, number of stakeholders, geographic reach, or scale of what you touched.
Tailor Per Role, Not Just Per Industry
A resume that's identical across every application is a resume optimized for no application in particular. Tailoring doesn't mean rewriting from scratch each time — it means:
- Reordering bullets within a role to lead with the most relevant achievement for that specific job posting.
- Matching language to the posting where it's genuinely accurate — many employers use applicant tracking systems (ATS) that scan for keywords from the job description, and a resume with zero overlap in terminology can get filtered before a human ever sees it.
- Cutting or shrinking irrelevant experience for a specific application, even if it stays prominent on your "master" version for other applications.
- Adjusting the summary line (if you use one) to speak directly to the specific role rather than a generic version of your background.
Keep a comprehensive "master resume" with everything you've ever wanted to include, and trim a tailored version from it for each application — don't try to write each one from a blank page.
Common Mistakes
- Listing duties instead of achievements. "Responsible for X" tells a reader what your job was, not what you accomplished in it.
- No quantification anywhere. Vague impact language ("significantly improved," "helped grow") reads as unverifiable and gets discounted by an experienced reader.
- A one-size-fits-all resume sent to every job. Even small tailoring — reordered bullets, matched keywords — measurably improves response rates.
- Generic action verbs. "Worked on," "helped with," and "involved in" say nothing about your actual role. Use verbs that show ownership: led, built, launched, negotiated, redesigned, automated.
- Inconsistent formatting. Mismatched date formats, bullet styles, or fonts read as carelessness on a document meant to demonstrate attention to detail.
- Burying the most relevant experience. If your most impressive, most relevant achievement is three bullets down under a less relevant one, move it up — resumes get skimmed top-down.
- Typos and inconsistent tense. Past roles in past tense, current role in present tense — small, but noticed.
- Objective statements that talk about what you want, not what you offer. "Seeking a challenging role where I can grow" tells the reader nothing about your value to them.
Regional Format Differences Worth Knowing
If you're applying across countries, one terminology mismatch trips up more candidates than almost anything else: in the US, "resume" and "CV" mean different things — a resume is the short, tailored document, and a CV is the long-form academic document. In the UK (and much of the Commonwealth), "CV" is the standard word for what an American would call a resume, used even outside academia.
A UK employer asking for a "CV" for a marketing or business role wants a short, tailored, achievement-focused document — functionally identical to a US resume, just called something else. Don't send a multi-page academic-style document because the word "CV" appeared in the posting; look at what the application actually asks for (length guidance, emphasis on "concise" or "relevant experience") rather than relying on the label alone.
This is a job-market-specific version of a broader confusion — see Gabble's guide on CV vs. resume for graduate school applications if you're navigating this same terminology trap for an academic or graduate-program application rather than a job search; the underlying distinction is the same, but the stakes and expected format differ by context.
Beyond the US/UK naming issue, other regional norms worth checking before you apply internationally: some countries still expect a photo or date of birth on a CV (common in parts of continental Europe), while others consider that inappropriate or even illegal to request (common in the US, UK, and Canada). When in doubt, follow the norm of the country and employer you're applying to, not your home country's convention.
A Quick Self-Check Before You Submit
- Does every bullet answer "so what?" — does it show a result, not just an activity?
- Could someone who has never met you describe what you actually accomplished after a 20-second skim?
- Have you tailored at least the top third of the resume to this specific role?
- Is the formatting consistent — same date format, same bullet style, same tense conventions throughout?
- If applying across countries, have you checked whether "resume" or "CV" is the expected term and format for that specific market?
A resume's job isn't to document your career — it's to get you an interview. Every bullet, every section, and every word of tailoring should serve that one purpose: giving the person reading it, in the few seconds they'll actually spend, a clear reason to keep going.