How to make a resume: a working order that does not waste the evening

"How to make a resume" is usually answered with a list of sections and a plea to keep it to one page. That advice is not wrong, but it is the wrong place to start. People who open a blank template and invent content to fill the boxes produce vague resumes, because the template is asking questions they have not answered yet.

The working order below is the one that wastes the least time. It is also the order that produces a document an applicant tracking system can parse and a human can skim in under a minute.

Step 1 — Inventory, not design

Before you open a builder, open a plain text file and list every role, project, course, certification, and piece of volunteer work from the last ten years that you can still describe honestly. Under each item, write three things you did and one number if you can find one — volume, time saved, money, people, tickets, patients, students, dollars.

Do not write resume language yet. "Helped with onboarding" is fine at this stage. The point is to surface material that will otherwise stay in your head until you are staring at a blank Experience section at eleven at night.

If you have almost no paid work, put projects, coursework with a real deliverable, and volunteer roles on the same list. An empty inventory is rarer than people think; an inventory they dismissed as "not real experience" is common.

Step 2 — Pick the posting you are writing toward

A resume without a target becomes a biography. Pick one concrete posting — or, if you are not applying yet, one job title and industry — and keep it visible while you write. You will use it twice: once to decide which items from the inventory belong on the page, and once to pull keywords into the bullets and skills section.

You are allowed to keep a master inventory and derive shorter versions per application. You are not served by writing one generic resume and sending it everywhere unchanged.

Step 3 — Choose a format that ATS and humans both survive

For almost everyone currently employed in a conventional career path, that format is reverse-chronological: contact, optional summary, experience, education, skills. Single column. Standard section headings. No text boxes, no icons for contact details, no skill bars.

Functional resumes that hide dates and group work under skill headings still get rejected by many ATS parsers and by recruiters who assume you are hiding a gap. Career changers sometimes need heavier reframing, but even then chronological with a clear summary usually beats a skills-only layout. There is a separate guide on chronological versus functional if you are deciding.

Step 4 — Write the experience section first

This is the load-bearing part of the document. For each role you keep:

• Job title as the market would recognise it, employer, location, dates
• Three to six bullets that start with a verb and end with a result or a scope
• Numbers where you have them; honest scope where you do not ("supported a 12-person team" beats "provided excellent support")

Cut anything that is true of every coworker in the same job. Keep the decisions, the ownership, and the outcomes. If a bullet only restates your job title, delete it.

People who start with the summary usually write adjectives. People who start with experience have facts to summarise later — or discover they do not need a summary at all.

Step 5 — Education, skills, and only then the summary

Education: school, degree, graduation year (or expected year). Add coursework only if you are early-career and the courses map to the posting. Drop GPA unless it helps and you are recent.

Skills: tools and methods the posting actually names, plus a short list of things you can defend in an interview. Not soft-skill adjectives. Not a bar chart.

Summary: three or four lines at the top, only if they route the reader faster than the first job entry would. First job, linear career, or nothing specific to say — skip it and reclaim the space.

Step 6 — Contact block and a pass for machines

Name, city and region (or "Remote"), phone, email, LinkedIn or portfolio URL if it helps. No photo for US applications. No full street address. No headshot icon.

Then paste the whole text into a plain-text view or run it through an ATS-oriented check: can every heading and bullet be selected as text? Are section titles the ordinary words Experience and Education? Did a two-column layout scramble the reading order? If the PDF is a picture of a resume, start over with a format that exports real text.

Step 7 — Stop

A finished resume is short, specific, and slightly uncomfortable to read because it commits to claims. An unfinished one keeps growing soft language and extra pages. When the inventory is represented, the posting's important terms appear in context, and a stranger can say what kind of role you fit, export the PDF and apply.

You will tailor later — usually a summary clause and a few bullets, not a rewrite. That is a different evening's work, and it is faster when the base document is already honest.

Common ways this goes wrong

Starting in Canva. Design-first tools produce layouts that look finished and parse badly. Content first, type second.

Writing for every possible job. The inventory can be broad; the resume on the page cannot. Specificity to one posting beats coverage of five.

Padding with duties. "Responsible for managing…" is a job description, not evidence. Switch to what you did and what changed.

Treating the first draft as sacred. The first pass is for material. The second pass is for cutting. Most good resumes lose a third of their first draft.

Where builders fit (and where they do not)

A builder saves you from fighting margins and fonts. It does not invent your achievements. Spend your evening on the inventory and the bullets; let software handle layout and PDF. If a tool will not let you download without paying, or exports a picture instead of text, switch tools — that is a product failure, not a personal one.

Related

• How long should a resume be?
• How to write resume bullet points that survive a seven-second scan
• ATS-friendly resume format: what actually breaks the parse
• Chronological vs functional resumes