How to Make a Resume: Build It in the Right Order

You open a blank document, or a template with "Professional Summary" sitting at the very top, cursor blinking inside it. And you freeze, because you are being asked to summarize a resume you have not written yet. That is the moment most people either quit for the night or paste in three sentences of "results-driven professional" filler they will never edit again.

The blank page is not really the problem. The order is. Almost every guide walks you down the page from the top, which means you write the parts that make promises before you have written the parts that keep them.

The takeaways

• Five sections cover it: contact details, summary, work experience, skills, education. Everything else is optional and goes near the bottom.
• Build order is not read order. Draft your work experience first; write the summary last, once you can see what the page actually says.
• A resume can only report what you have done. The honest version is faster to write than the inflated one, because you are describing, not inventing.

What sections does a resume actually need?

Five, for almost everyone: contact details, a resume summary, work experience, skills, and education. That is the whole spine, and a clean one-column layout of those five reads better than a design with sidebars and star ratings.

Contact details are your name, phone, email, city, and a link (LinkedIn or a portfolio) if it adds something. The resume summary is two or three lines at the top. Work experience is your roles in reverse order, most recent first. Skills is a short, honest index of what you can do. Education is your degrees or training.

Optional sections (certifications, volunteer work, languages, projects, awards) earn a spot only when they match the job, and they sit below the core five. Use plain headings an applicant tracking system (ATS) recognizes: "Work Experience," not "Where I've Been." The software that first reads your resume looks for standard labels, and a clever heading is where parsing quietly breaks.

You can read the rest of our resume and CV guides for the section-by-section detail; this post is about the sequence you build them in.

What order should you build a resume in?

Not the order you read it in. A recruiter reads top to bottom: summary, then experience. You should build bottom-up, because each section is raw material for the one above it. Here is the sequence I use:

1. Dump your work history first, unpolished. Every role, dates, and a rough list of what you actually did. No formatting, no verbs chosen yet.
2. Turn each duty into a bullet point with a result. "Managed the email list" becomes "Ran a 12,000-contact email list and lifted open rates from 18% to 26% over six months." A strong bullet point shows a change you caused, measured wherever you can measure it.
3. Read your own bullets back and pull out the skills. Your skills section should be the words that already appear, earned, in your experience rather than a wish list.
4. Now write the summary, because now you know what it is summarizing.
5. Add education, then contact details, then the optional sections that survive the "does this match the job" test.

Doing it this way, the top of your resume is a promise the bottom can keep. Do it the other way and you write a summary claiming "data-driven marketer," then spend the next hour trying to make your bullets prove a phrase you picked first.

Should you write the resume summary first or last?

Last. A resume summary is the two or three lines under your name that tell a recruiter, in one glance, who they are looking at. It is the highest-value real estate on the page, and it is the section people most often fake, because writing it from a blank start invites you to describe the candidate you wish you were.

Write it after the body exists and the job gets easier: you lift your two strongest, already-written bullets and compress them into a claim, then add the role you are targeting. That is it. If you have almost no history to summarize yet, an objective (the role you want plus what you bring) can replace it. We go deeper on this in the guide to writing a resume summary that earns a read.

How long should it be, and what do you cut?

One page if you have under ten years of experience, two if you have more. The cut is not about deleting your oldest job to hit a number. It is about relevance: anything that does not help you get this specific job is taking up space a matching bullet could use.

A widely cited Ladders eye-tracking study put a recruiter's first scan at roughly seven seconds. You do not beat that with more content. You beat it by making the top third of page one carry your strongest, most relevant proof, so the seven seconds land somewhere that matters.

Who should skip this and just tailor?

If you already keep a solid master resume, you do not need to build from scratch again. Your job is tailoring: reshaping that base for one posting rather than starting over. This is where a tool earns its place. JobScalr keeps a master CV and rewrites it toward one specific posting, weighting each section by what that posting rewards, and it will not add a skill you did not list, it asks you first. That guardrail matters, because the fastest way to ruin an honest resume is to let anything, human or AI, write a claim the body cannot back. The next step after building your base is tailoring it to the job description.

Common questions about making a resume

Should a resume be a PDF or a Word file?

A PDF, unless the posting asks for Word. A PDF holds your layout on any device. Make sure it is a text-based PDF (one you exported rather than a scan or an image), because an applicant tracking system needs to read the text, and a scanned image reads as blank.

Do I need a summary and an objective, or just one?

Just one. Use a summary when you have relevant experience to compress. Use an objective when you are entry-level or changing fields and need to state the target directly. Never stack both.

What order do the sections go in for a recent graduate?

Move education above work experience. When your degree or coursework is your strongest recent thing, it belongs where the seven-second scan lands. Once you have a year or two of relevant work, flip it back so experience leads.

How many skills should I list?

Enough to cover the role's core requirements, usually six to twelve, and every one should be something you could be asked about in an interview. A skills section works as a searchable index of what you can actually do; treat it that way rather than as a personality quiz.

How often should I rewrite my resume?

Rewrite the base rarely; re-tailor it every time you apply. Keep one master version current, then adjust the emphasis for each posting. That is far less work than starting over, and it is what keeps each application relevant instead of generic.