How to Write a Resume, Step by Step (With Examples)

Your resume has one job: to get you an interview. A recruiter often spends only a few seconds on the first pass, scanning to answer one question. Does this person match what the role needs? Everything you write should make that answer obvious and fast. A resume is not your autobiography. It is a focused argument that you can do this specific job.

That is good news if you are a student or new graduate without years of experience. You are not expected to have a long career yet, and you do not need one to write a strong resume. Coursework, class projects, part-time jobs, campus roles, volunteering, and internships all count when you describe them well. This guide walks through the writing itself: what to include, how to phrase it, and how to stay readable by both software and people.

The sections to include, and the order that works

Most strong resumes use the same handful of sections in a familiar order. That order makes your resume easy to skim and easy for software to parse. Here is the standard structure.

• Contact details: your name, city and region, phone, a professional email, and a link to LinkedIn or a portfolio if you have one. No full street address needed.
• Summary (optional): two or three lines, and only if they add something a recruiter cannot get elsewhere. If it would just repeat your bullets, leave it out.
• Experience: paid jobs, internships, and substantial projects, most recent first, each with your title, organization, location, and dates.
• Education: your degree, school, and expected or actual graduation date, plus relevant coursework, honors, or a strong GPA if it helps.
• Skills: the concrete tools, languages, and methods you can genuinely use, grouped to scan quickly.

For students, one small change often helps. If your degree is your strongest asset and your work history is short, put education above experience. Once you have internships or a job tied to your target role, move experience back to the top.

Write bullets that show results, not duties

Your bullet points are where a resume is won or lost. Most people list responsibilities, which tells a reader what the job was, not what you achieved in it. Strong bullets follow a simple formula: an action verb, the task or context, and the result. Open with a specific verb (built, led, analyzed, organized), say what you did, then show what happened because of it.

In the strong version, the verb is grew, the task is the content calendar and events, and the result is the follower growth. That order does the persuading for you, and it reads in about two seconds.

Quantify honestly, and never invent a number

Numbers make results concrete, so use them wherever you genuinely have them: how many people, how much money, how often, how much faster. But one hard rule sits underneath. Never invent a figure. A made-up metric is easy to expose in an interview, and one question you cannot answer can end the conversation.

When you do not have a clean number, describe the scope in plain words instead. Honest detail beats an invented statistic every time.

Tailor every resume to the job description

A tailored resume beats a generic one every time. Before you apply, read the job description closely and treat it as a checklist. It tells you, in the employer’s own words, exactly what they want.

Mirror the real language of that posting. If it asks for data analysis, customer service, or project coordination, and you have honestly done those things, use those same terms. Two readers look for them: the software that screens resumes matches keywords, and the person who reads next is reassured to see their own priorities reflected back. Claim only what is true, then move your most relevant bullets near the top.

Format it so software and people can both read it

Many employers run resumes through applicant tracking software before a person ever sees them, and these parsers are not clever. They read plain, structured text and stumble on anything decorative. Design for the parser, and the human version takes care of itself.

• Use standard section headings (experience, education, skills) so the software knows what each block is.
• Stick to one clean, common font at a readable size. Save your creativity for what you say, not the typeface.
• Avoid tables, text boxes, columns, images, and icons for anything important. Parsers often drop or scramble text trapped inside them.
• Export as a PDF unless the posting asks for a Word file, so your layout survives on every screen.
• Keep it to one page. For students and early-career applicants, one focused page is the expectation, not a limit to apologize for.

One page forces good decisions. If a line does not support your case for this role, cut it. A tight, relevant page always beats two padded ones.

Proofread like your application depends on it

It does. A typo signals carelessness, and the wrong company name reads as an instant rejection. When the writing is done, slow down and check the details that quietly sink strong applications.

• Read the whole thing aloud once. Your ear catches clumsy phrasing and missing words that your eye slides past.
• Check every name: the company, the role, and anyone you mention. Names carried over from a previous application are a common, costly slip.
• Confirm that dates, titles, and numbers are accurate and consistent throughout.
• Keep verb tense consistent: past tense for finished roles, present tense for what you are doing now.
• Ask one other person to read it. A fresh set of eyes catches what you have stopped seeing.

Writing a strong resume is not about clever tricks. It is about making a clear, honest, specific case that you fit the role, then formatting it so nothing blocks that message. Build one solid version, then tailor it for each job you want.