Blog · 19 August 2026 · 10 min read

How to Write a Resume: The Complete Guide

The whole arc in one place — what goes on the page, how to write bullets that prove impact, how to format for the first scan, and how to tailor per job.

By Amit Kumar

Most resume advice is either too abstract to act on — "show impact!" — or so granular you lose the thread. This guide is the whole arc in order: what a resume is actually for, what goes on the page, how to write a line that proves something, how to lay it out, and how to change it per job.

Each section below is the short version. Where there is genuinely more to say, it links to the full treatment rather than half-explaining it here.

What a resume is actually for

A resume is not a career history. It is an argument that you can do a specific job, supported by evidence.

That reframing settles most of the questions people agonize over. Should you include the job from nine years ago? Only if it argues for this role. Should you list every tool you have touched? Only the ones this posting cares about. Is one page or two correct? Whichever makes the argument without padding.

It also explains the single most common failure. A resume full of duties — "responsible for", "managed", "involved in" — is a description of a job that existed. It is not an argument that you were good at it.

What goes on the page

In order, for almost everyone:

  1. Name and contact — in the body of the document, not the header or footer, where some parsers cannot read it. Location, email, phone, LinkedIn. No photo, no date of birth, no marital status.
  2. Summary — two to three lines, and only if it is doing work. A summary that says "results-driven professional with a passion for excellence" is worse than no summary. One that says what you do, at what scale, with one proof point, earns its space.
  3. Skills — concrete tools, languages and methods. Not "communication" and "leadership", which nobody searches for and nobody believes.
  4. Experience — reverse chronological, three to six bullets on recent roles, fewer as you go back.
  5. Education — near the top as a new graduate, near the bottom once you have several years behind you.
  6. Anything that genuinely differentiates — publications, patents, talks, significant open-source work, certifications that a recruiter in your field would recognize.

What to leave off: references available on request, objective statements, skill-rating bars, hobbies that reveal nothing, and any table or column that a parser might scramble.

How to write a bullet

This is where resumes are won and lost, and where most of the acronyms come in — CAR, STAR, PAR, BAR, XYZ. They are not competing systems. They are different ways of getting the facts out of your memory.

The written order, though, is settled. Princeton teaches ACE — Action verb, Context, End result. MIT teaches PAR. Yale teaches action verb, project, quantified result. All of them start with the verb, which is why the honest summary is: interrogate however you remember, write verb-first.

Responsible for improving the loan application process.

Redesigned the loan review workflow and automated validation, cutting processing time 37% and enabling same-day approval for 60% of applications.

Why it works: The first names a responsibility. The second names a decision, its scale, and what moved because of it — in the same number of lines.

Full comparison of every framework, which to use when, and the two acronyms worth ignoring: CAR vs STAR vs PAR vs XYZ.

Where the evidence comes from

Here is the thing almost nobody says out loud: if your bullets are weak, the problem is usually not your writing. It is that the evidence is not in front of you. You have forgotten the number, the baseline, the size of the team.

The fix is interrogation, not better adjectives. For every role, answer: how many people were affected, what was the baseline before you arrived, what was it after, how long did it take, what did it cost or save, what broke less often.

And impact is not only revenue. Cost, time, scale, quality, efficiency, customer behaviour, risk, reliability and scope are all measurable, and most roles have two or three of them even when they have no revenue figure at all.

The full excavation process, ten categories of impact with examples, and what to write when you genuinely have no number: how to turn work experience into achievements. For expressing a number once you have one, and estimating honestly when you are unsure: how to quantify your achievements.

How to lay it out

Before anyone reads your resume, they scan it. Ladders' 2018 eye-tracking study measured an average first screen of 7.4 seconds; MIT's career team puts it at six to ten. Nobody is claiming that is a full read — that is the pass that decides whether a full read happens.

So: single column, always. Dates right-aligned into a scannable timeline. Job title bold and separated from the company. Standard section headings. No icons, no skill bars, no two-column layouts that both human eyes and parsers stumble over.

And use bold as a budget, not for emphasis — at most two short spans per bullet, never on the first word, spent on the quantified outcome and one hard skill.

The full treatment, including the fold test and how to order sections by career stage: how to format a resume recruiters can scan.

How to tailor it per job

Sending one resume to every posting is the most common avoidable mistake. Writing a new one from scratch each time is the second.

The approach that works is a master list plus selection. Keep every achievement you have — far more than fits on a page — and select per application. Selecting is three decisions: reorder so the achievements that prove this job's core requirement sit near the top, mirror the posting's terminology where it is genuinely true of you, and cut the ones that dilute this particular story.

The filter is relevance, not impressiveness. Your most impressive achievement may be irrelevant to this role, and a smaller one that maps directly onto the job description will do more work.

Getting past the software

Applicant Tracking Systems are less frightening than their reputation. Most do not assign a secret score that rejects you. They parse your file into fields, store it, and let a recruiter search — so the real failure is not being rejected, it is never being retrieved because your resume does not contain the words being searched for.

That means: use the posting's exact terms where they are true of you, pair abbreviations with their full form at least once, use standard job titles, and submit a text-based PDF rather than a scan or an image. What an ATS does and does not do, and where resumes actually break: what is an ATS.

The mistakes worth naming

  • Duties instead of outcomes. The single biggest one. If a line would be true of anyone who held your job, it is not doing anything for you.
  • Invented numbers. A metric you cannot defend in an interview is a liability, not an advantage. A modest provable figure beats an impressive vague one.
  • Weak openers. Worked on, helped with, responsible for, assisted, participated in — each spends the strongest word in the line on something other than what you did.
  • Jargon that does not travel. Within your industry it signals expertise. Moving industries, it is a wall — translate it into outcomes anyone can follow.
  • Padding. Every line either earns its place or comes out. A tight one-pager beats a padded two-pager every time.
  • Hidden keyword tricks. White text and keyword blocks are visible to anyone who selects the text, recruiters know them, and they cost you credibility rather than gaining you a score.

A checklist before you send

  • Every bullet starts with a verb, not with setup.
  • The strongest one or two bullets per role carry hard evidence.
  • Nothing on the page is a number you could not explain out loud.
  • Single column, standard headings, contact details in the body.
  • Dates consistent and right-aligned; titles bold and separated from companies.
  • The top half alone communicates your role, your strongest skills, and one signal of impact.
  • The posting's two or three core requirements appear in your words, naturally.
  • The most relevant content is at the top — not simply the most recent.
  • A text-based PDF whose text you can select and copy.

Where nxtleap fits

Most of this guide is work you can do with a blank document and an afternoon. The part that does not scale is doing it again for every application.

nxtleap's Achievement Bank is built for that. You brain-dump raw experience with no structure, it splits into individual achievements, and Power-ups ask the targeted questions that surface the evidence — each showing the points it adds before you answer. Every achievement carries an Impact Score: Elite at 75 and above, Strong at 60–74, Task below.

Then, per job, score & tailor ranks the whole bank against that specific posting and rewrites the top achievements to lead on what it asks for. The ATS Audit reports keyword coverage by exact matching, and the Recruiter Audit scores the assembled page the way a six-second skim would. You approve every line — you are just not starting from a blank page each time.

Start with the resume builder, check something you already have with the ATS resume checker, or see worked examples by role.

Frequently asked questions

How long should a resume be?

One page for most people, because the constraint forces you to prioritize — which is the actual skill being tested. Two pages are reasonable past roughly ten years of substantial experience, as long as everything that matters is on page one. No reader is promised to reach page two.

What should a resume include in 2026?

Contact details in the document body, an optional two-to-three-line summary that says something concrete, a skills section of real tools and methods, reverse-chronological experience written as achievements rather than duties, education, and anything that genuinely differentiates you. Leave off photos, objectives, skill-rating bars and "references available on request".

Should I use a resume template?

Use one that is single column with standard section headings and real text — no tables, no sidebars, no graphics. Most visually elaborate templates trade parseability and scan speed for looks, which is the wrong trade when the first pass is a few seconds long.

How do I write a resume with no experience?

Argue from whatever real work you have: internships, freelance, coursework with genuine scope, open-source contributions, volunteering, student leadership. The rules do not change — lead with a verb, describe what changed, and be specific about scale. "Coordinated a 40-person event on a ₹60,000 budget" is evidence regardless of whether anyone paid you.

Do I need a different resume for every job?

Not a different resume — a different selection. Keep one master list of every achievement, then per application reorder so the most relevant sit at the top, mirror the posting's terminology where it is genuinely true of you, and cut what dilutes that particular story.

Keep reading

Put this into practice

Start building your career memory today.

Free while in early access. No credit card required.

Get started