Resume guides

How to write a Résumé that gets interviews

Most Résumés are rejected in the first screen not because the candidate is weak, but because the document makes the reader work too hard. This guide walks through the structure recruiters expect and the details that decide whether you get a call.

The structure recruiters expect

A hiring manager spends well under a minute on a first pass. Use the order below so the most decision-relevant information appears where the eye already goes.

1. Header: name, job title you are targeting, city, phone, email, LinkedIn.
2. Professional summary: three to four lines that state your role, years of experience, domain and one measurable achievement.
3. Work experience: reverse-chronological, most recent first.
4. Education: degree, institution, year. Move above experience only if you graduated within the last year.
5. Skills: tools, methods and languages that appear in the job posting.
6. Optional: certifications, publications, volunteering, projects.

Write bullet points that carry evidence

Replace duty descriptions with outcomes. A duty says what you were assigned; an outcome says what changed because you were there. The simplest reliable pattern is action verb + what you did + measurable result.

If you have no hard numbers, quantify scope instead: team size, budget, number of clients, volume handled, geography covered.

How long should a Résumé be?

• 0–5 years of experience: one page.
• 5–15 years: two pages, with the first page carrying your strongest material.
• Academic or research Résumés: length follows publication record, not a page rule.

What to cut

• Objective statements about what you want — the summary should say what you offer.
• "References available on request" — assumed.
• Full home address; city and country are enough.
• Skill rating bars; they communicate nothing verifiable.
• Jobs older than ~15 years, unless directly relevant. Compress them into one 'Earlier career' line.

Tailor before you send

Read the posting and mark the five requirements that appear first or repeat. Those five should be visible in your summary and your top three bullet points, in the employer's wording. This single step raises reply rates more than any design change.

A worked example: rebuilding one weak entry

Take a real, common starting point: someone who managed a small retail team and wrote "In charge of staff and daily store operations." That line tells a reader nothing about scale, difficulty or result, so it gets skimmed past. Rebuilding it starts with three questions: how many people, what changed while you were responsible, and what number would prove it.

Before: In charge of staff and daily store operations. After: Managed a 12-person retail team across two shifts, cutting staff turnover from 41% to 22% in one year through a revised scheduling and onboarding process.

Notice what changed: team size replaces "staff," a named process replaces "operations," and a before/after number replaces the vague claim of being in charge. The same rebuild works for almost any generic bullet — find the scale, find the change, find the number, and put them in that order.

Common mistakes that quietly sink a Résumé

• Burying the strongest bullet third or fourth instead of first — recruiters often stop reading a block after two lines.
• Listing responsibilities in the order your employer listed them internally, rather than the order relevant to the job you want now.
• Using the same summary for every application, which reads as generic even when the experience underneath is strong.
• Mixing tenses within the same role description, which forces the reader to re-read a sentence to understand timing.
• Writing bullets that describe a team's result without ever saying what you personally did inside it.

How your first job title after graduation should read

Early-career Résumés often list an internship or first job with the exact, narrow title the company used internally, such as 'Junior Associate II', which means nothing to an outside reader. Pair the internal title with a plain-language clarifier in brackets if the original title is unusual, and lead each bullet with what you contributed rather than what you observed or shadowed.

Final checks

1. Read every bullet aloud — anything you stumble over gets rewritten.
2. Check tense: present for the current role, past for everything else.
3. Confirm dates have no unexplained gaps.
4. Export as PDF and name the file Firstname-Lastname-Résumé.pdf.
5. Have one person outside your field read it and tell you what you do for a living.

Handling a résumé with more than one career track

Some careers do not move in a straight line — a person might have five years in accounting followed by three years in product management, with no obvious thread between them. Trying to blend both into one summary usually produces a vague line that undersells both halves. Instead, decide which track you are applying against for this specific job, and let the other track become supporting evidence rather than a competing headline.

If you are applying to a product role, the accounting years should show up as one or two bullets under a heading like 'Additional experience' rather than being fully detailed. The summary should read as if the accounting years were preparation for product work — budgeting discipline, stakeholder reporting, forecasting — not as two unrelated jobs stapled together.

A second worked example: an over-stuffed bullet

The opposite problem from vagueness is a bullet trying to say too much at once. A common version reads: 'Responsible for managing the customer support team, handling escalations, training new hires, updating the knowledge base, and reporting metrics to leadership on a monthly basis.' It is accurate, but a reader cannot tell which part mattered most, so none of it lands.

Before: Responsible for managing the customer support team, handling escalations, training new hires, updating the knowledge base, and reporting metrics to leadership on a monthly basis. After: Led an 8-person support team; cut average escalation resolution time from 3 days to 1 by rewriting the knowledge base and retraining agents on tier-1 triage.

The rewrite drops training, reporting and monthly cadence — not because they never happened, but because they were not the strongest evidence available. One overstuffed bullet becomes one sharp bullet, and the dropped detail can move into a second, shorter bullet if it is still worth keeping.

Checklist before you call a draft finished

• Every bullet in your most recent role contains a number, a scale, or a named outcome — not just a task.
• The top third of the first page could stand alone and still convince someone to read the rest.
• No two bullets across the whole document make the same point in different words.
• Every acronym is either standard in the field or spelled out once on first use.
• The file opens correctly on a phone, since a growing share of first reviews happen there.