How to Write a Resume, Section by Section
A resume is a short argument that you can do a specific job, built so a stranger can check it in under a minute. This guide goes section by section, in the order worth writing them, and shows what separates a bullet that earns an interview from one that fills space.
Start from the job, not from a blank page
Most weak resumes are weak because they were written inward-out: the writer listed what they have done and hoped an employer would notice the fit. The useful order is the reverse. Read two or three postings for the job you actually want, side by side, and mark the responsibilities that appear in all of them. That overlap is the argument your resume has to make, and every line on the page either supports it or competes with it.
Before writing a word, spend twenty minutes collecting raw material: employers, exact titles, start and end months, the projects you owned, and any number you can defend - volumes, budgets, headcounts, cycle times, error rates, revenue. Numbers are the hardest part to reconstruct later and the part that carries the most weight, so gather them while you still have old reviews, dashboards and sent mail to look at.
The header: name, title, and how to reach you
The top of the page needs five things and rarely more: your name, the job title you are applying for, an email address, a phone number, and the city and state you live in. A link to a professional profile or a portfolio earns its place when a reader would genuinely click it. A personal site with three posts from four years ago does not.
The title line under your name is the most undervalued element on a resume. It tells the reader in three words what to file you as, and it should match the language of the posting wherever that is honest. Our software engineer example leads with Senior Software Engineer and our nursing example with Registered Nurse (BSN, RN), because the credential belongs on the line where a reader goes looking for it.
Leave out the full street address
City and state answer the only question a reader has, which is whether you are local or relocating. A full mailing address is a small privacy cost with no upside, and it spends a line you can use better.
Use an email address you would read aloud
First name, last name, an ordinary provider, checked daily. A university address that expires in June or a shared household mailbox is how an interview invitation sits unanswered for a week.
Keep the contact block in the body of the page
Details placed inside a document header, a text box or a graphic can go missing when the file is read by anything other than your own word processor. Plain text on its own line is safer, and our guide to applicant tracking systems covers why.
The summary: three sentences, no adjective you cannot prove
A summary is not an objective statement. Nobody needs to be told that you are seeking a challenging role at a growing organization; that sentence is true of every applicant and therefore says nothing about you. What a reader wants at the top of the page is a compressed version of your case: what you are, how long you have done it, and two or three things you have done that a peer in the same job would consider difficult.
Our data analyst example opens with "Data analyst with 4 years of experience turning product and revenue data into decisions. Found the churn driver behind a 12% retention lift, built the metrics layer a 40-person company runs on, and treats data quality checks as the first step of every analysis." Three sentences, one specific outcome, and not a single phrase that could be pasted into a stranger's resume without changing its meaning.
Write the summary last. It is a distillation of the bullets underneath it, and writing it first tends to produce a promise the rest of the page never keeps. Three sentences is the working limit. Four is roughly where readers stop and skip down to your most recent job.
Experience: a verb, what you did, and what changed
This is the section the decision is made on, and its unit is the bullet. A bullet that works has three parts: a verb in the active voice, the thing you actually did, and the consequence of having done it. Drop the third part and you have written a job description - a list of duties anyone with that title could claim - rather than evidence that you were good at it.
From our software engineer example: "Led the migration of the billing pipeline from a nightly batch job to an event-driven architecture, cutting invoice processing time from 6 hours to under 10 minutes." Led is the verb, the migration is the work, and six hours falling to ten minutes is the consequence. Written as a duty instead - responsible for billing pipeline architecture - the same fact proves nothing, and you can see exactly what the third part was carrying.
The pattern is not an engineering trick. Our high school teacher example carries "Redesigned the curriculum around inquiry-based investigations; AP Biology enrollment has doubled and 78% of students earned a 3 or higher last year, up from 54%", and our entry-level example turns a campus job into "Trained 8 new hires on service standards and the register; handled daily cash reconciliation of roughly $2,000 with zero discrepancies." The stakes differ by an order of magnitude. The structure does not.
Weight the section the way it is read
Four or five bullets for the job you hold now, three for the one before it, one or two for anything older. Equal space for every job tells a reader you have not decided what matters.
Quantify what can honestly be quantified
Not every result has a number and inventing one is worse than leaving it out. Scale, frequency and comparison all count: three production services, 140 students a year, half the time it used to take, zero discrepancies over two years.
Open with the verb and drop the pronoun
Managed, built, negotiated, reduced, precepted, rebuilt. No I, no we, no responsible for, no successfully. The reader already knows the sentence is about you, because your name is at the top of the page.
Put the strongest bullet first inside each role
Bullets are read from the top down and abandoned partway through. The order within a job is an editorial decision rather than a chronology, so the result you would mention first in conversation belongs first on the page.
Education, skills, and the sections worth adding after them
Education is short, and its position depends only on how recently you left it. A graduate with no full-time history puts education above experience; anyone two or more years into a career puts it below, cut down to institution, degree and the year it ended. Grades belong there while they are recent and good, and coursework belongs there only when it is the closest thing to experience you have.
The skills section is an index, not an argument. Group it - languages, tools, clinical, methods - and keep every entry to something an interviewer could question you about for five minutes without embarrassing you. Character adjectives with nothing behind them do active harm: a line reading team player, hard worker, detail-oriented tells a reader you had nothing specific to put there.
After skills, add only what does work for this application. Licenses and certifications matter enormously in regulated fields and belong high on the page; our nursing example lists the RN license, BLS and ACLS because a hiring manager screens on exactly those before reading a bullet. Projects earn their place when paid history is thin. Languages, publications, volunteering and speaking are worth one line each when they are relevant to this employer, and nothing at all when they are not.
Build it in this order, then cut
Write in the order a reader does not read. Most recent job first, then the earlier ones, then education and skills, then the header, and the summary last of all. Each step supplies the material for the next, and a summary written at the end is the only one that ends up true of the page beneath it.
Then cut. Length is a symptom rather than a target: the reason two pages of a short career read badly is that half of it is padding, and the padding is precisely what makes the good half hard to find.
Apply the deletion test to every line
Read a bullet, delete it, and ask what a reader would no longer know about you. If the answer is nothing, or nothing that matters for this job, it stays deleted. Duties that the job title already implies are the usual casualties.
Compress the distant past into single lines
Older roles exist to show that a timeline is continuous, not to be argued in detail. Company, title and dates on one line does that job and buys back the space your recent work needs.
Read the finished page aloud, once
Reading aloud catches the two failures a spell checker cannot see: sentences no human being would say, and four consecutive bullets that all open with the same verb.
Questions people ask
How long should a resume be?
One page for most careers under about ten years, two when the second page carries real work rather than repetition. The mistake is treating length as the goal. A padded single page is worse than a dense second one, and a second page that repeats the first is worse than either, so cut for redundancy and count pages afterward.
Should I include an objective statement?
In almost every case, no. An objective describes what you want and a summary describes what you bring, and only one of those helps a stranger decide whether to call you. The exception is a genuine change of direction, where one honest line explaining the move stops the reader from inventing a worse explanation for it.
How far back should my work history go?
Roughly ten to fifteen years in detail, with older roles reduced to single lines and only if they establish something your recent history does not. Anything earlier can go entirely. Nobody is screening for a summer job from two decades ago, and dropping it removes the easiest way for a reader to start guessing your age.
Do I need a different resume for every application?
Not a different resume, a differently tuned one. Keep one strong base document per job family and change the top of the page each time: the title line, the summary, and the opening bullets of your most recent role. That puts the words this particular employer cares about where they will actually be read.
Is it acceptable to leave a job off my resume?
Yes. A resume is a professional summary you author, not a sworn statement of every job you have held, so a two-month role that confuses your story can go. Application forms and background checks are a separate matter: when a form asks for complete employment history, answer it completely and truthfully.
What should I do about a gap in my dates?
Show it and move on. Use one consistent date format so the gap is visible rather than disguised, and if it has a one-line explanation - caregiving, study, a layoff followed by contract work - a short entry for that period costs you nothing. Vague dates meant to hide a gap read worse than the gap ever did.
Keep going
Write it in the editor instead of a blank document.
Every section from this guide is already laid out, with the formatting handled and the export waiting at the end.