How to Write a Resume: A Complete Step-by-Step Guide

A resume has exactly one job: getting you invited to an interview. Not landing the job, not showcasing your entire portfolio — just making someone think "I need to talk to this person." Forgetting that is the biggest trap most resumes fall into: people try to cram their entire life story onto the page, when the person reading it usually has dozens of other resumes in hand and only a limited amount of time for each one.

This guide walks through how to write a resume from start to finish, section by section: which format suits you, what recruiters actually look for, and which mistakes to avoid.

1. Choose the Right Format

Resumes are written in three main formats:

• Chronological (reverse-chronological): The most widely used format, and the one recruiters are most familiar with. Experience is listed from most recent to oldest. This is the safest choice if you have a steady career history.
• Functional (skills-based): Skills are emphasized over a chronological work history. Intended for people early in their career or switching industries, but many recruiters read this format as a signal that "something is being hidden" — so use it carefully.
• Hybrid: A short skills/summary block at the top, followed by a chronological experience list. This combines the structure an ATS looks for with the skills you want to highlight.

In most cases, the hybrid format is the safest choice: it's readable for screening software (ATS) and familiar to the human eye.

2. Contact Information

This should sit at the top, simple and clear:

• Full name
• Phone number
• Email address (something that looks professional — not a nickname or an old school email)
• City (a full address isn't necessary)
• LinkedIn profile and a personal portfolio/GitHub link, if you have them

Don't dress this section up with a complex table or graphic — many ATS systems can't read that kind of structure correctly (we cover this in detail in What Is an ATS? How to Get Your Resume Past the Robots).

3. Professional Summary

Right below your contact information, add a short, 2-3 sentence summary section. This summarizes who you are, how many years of experience you have, and your strongest asset.

Weak example: "I'm a hard-working person who works well in teams, looking for new opportunities."

Strong example: "Backend Developer with 5 years of experience, specializing in performance optimization and API design for e-commerce platforms."

The difference: the second is concrete, measurable, and role-specific. The first could be copy-pasted onto almost any resume — which is exactly why it says nothing.

4. Experience Section

This is the section that deserves the most time on your resume. For each position:

1. Job title, company, date range — on a standard header line.
2. Bullets that open with an action verb — instead of passive phrasing like "was responsible for" or "helped with," use direct verbs like "developed," "led," "reduced," "increased."
3. A measurable result wherever possible — instead of "improved the customer support process," write something concrete like "built a ticket prioritization process that cut average response time from 24 hours to 6."

This simple formula works when building bullets: [Action verb] + [what you did] + [measurable/observable result]. You won't always be able to express the result as a percentage or a number — in that case, describing an observable impact with phrases like "faster," "with fewer errors," or "adopted team-wide" also works.

5. Education Section

If you're a recent graduate, this section goes near the top; if you're experienced, it goes below your experience section. School name, major, and graduation year are enough — no need to include high school details (if you're a university graduate) or your GPA (unless it's high).

6. Skills Section

Instead of listing skills randomly, split them into two groups:

• Technical/professional skills: the tools, software, languages, and methods you use.
• Languages and certifications: foreign language proficiency and professional certifications, if applicable.

Writing skills that appear in the posting — and that you genuinely have — using the exact same wording in this section increases your chances of matching for both a human reader and an ATS.

7. Length: One Page or Two?

• 0-7 years of experience: aim for one page.
• 7+ years of experience, or a large number of relevant projects/publications: two pages is acceptable.
• A resume that runs past three pages almost always contains unnecessary detail — summarize or cut anything from more than 10 years ago.

8. Common Mistakes

• Generic content that isn't role-specific. Sending the exact same resume to every posting doesn't go unnoticed by a recruiter.
• Visually heavy designs. Icons, progress bars, and multi-column layouts can look stylish to a human eye but may be misread — or not read at all — by an ATS.
• Spelling and consistency errors. Inconsistent date formats, verb tenses, or punctuation signal carelessness.
• A list of duties, not a list of achievements. "Was responsible for reporting" is a duty; "automated the weekly reporting process, eliminating 3 hours of manual work" is an achievement.
• False or exaggerated claims. Never write anything on your resume you can't defend in an interview.

Conclusion

A good resume chooses the right format, describes a concrete result in every bullet, is written in posting-specific language, and is easy to read. Once you've applied the steps in this guide, you can learn how to tailor your resume to a specific posting in What Is an ATS? How to Get Your Resume Past the Robots, or see a concrete profession-specific example in Software Engineer Resume Example and Writing Guide.