How to write a résumé: a readable structure and 7 achievement rules

Experience and evidence the reader can find quickly

A résumé should hold experience related to the role you’re applying for, not phrases that dress you up. Write it so the reader can confirm what you were responsible for, how you acted, and what changed in that experience.

Reading order and evaluation criteria vary by hiring process and role. So before fitting your résumé to rules like “always one page” or “you have a few seconds,” check these three things.

Is the role you’re applying for clear on the first screen?
Is every claim backed by experience that can be checked?
Does the content related to the skills in the posting get read first?

1. Placing the experience closest to the role

Listing your work and experience in reverse chronological order usually makes the flow easy to follow. But you don’t need to write every experience with the same detail. Describe projects that connect directly to the role down to your role and results, and shorten less relevant experience.

Start by marking the following in the posting.

Tasks that come up repeatedly
Required skills or qualifications
Who you’d work with and the scope of responsibility
Expected results or metrics

Then move the evidence from your experience that actually shows these to the front. If you borrowed words from the posting, also show when and how you used that skill.

2. Describing your role, actions, and results

In charge of service operations alone tells the reader neither the scope of your responsibility nor how you work. Make the sentence concrete in this order.

Problem to solve or role you held → what you did → a result that can be checked

The examples below were written to explain the structure.

Before: Was in charge of order service operations.
After: Categorized the causes of recurring missed orders and added a verification step, reducing the monthly number of reprocessed orders.

If you have exact numbers, include the period and the baseline. If you don’t, don’t invent them or use vague estimates; look for these kinds of evidence instead.

Before and after: automated manual work, merged inquiry channels into one
Scale: the range of customers, projects, data, or budget you handled
Frequency and speed: from monthly to weekly, from five approval steps to three
Quality: fewer error types, prevented omissions, set review criteria
Decisions: what you chose and what you based the decision on

Whether a number is true and the situation it came from matter more than its size. It’s safer to leave out any number you couldn’t explain again in an interview.

3. Connecting the posting’s language to real experience

If a posting asks for data-driven decision-making, adding that phrase to your skills list one more time isn’t enough. Attach something you actually did after it.

Weak: Performed data analysis
Concrete: Defined weekly conversion metrics and analyzed drop-off points, used as the basis for decisions in feature prioritization meetings

Don’t add work you didn’t do or technologies you didn’t use just to match keywords. Rewrite in the posting’s job terms only when you have the experience and only the wording differs.

Experience to put first, by role

When the role changes, the actions and results a recruiter wants to see change too. These are fictional examples, not real accepted cases or correct answers, showing which evidence to put first by role. Keep only the scope you actually worked on and results that can be checked.

Engineering

Weak: Backend API development and operations
Shows evidence: Reproduced the slow parts of the order API from logs and adjusted queries and the cache policy, then compared response times and error rates before and after deployment.

How you reproduced the problem, what you chose, and how you confirmed the change matter more than the names of technologies.

Product planning and PM

Weak: New feature planning and project management
Shows evidence: Analyzed sign-up drop-off together with customer inquiries to set the scope of improvements, agreed on priorities with design and engineering, and launched an identity verification recovery flow.

The data you used to define the problem, the scope you adjusted, and the change you confirmed after launch matter more than the number of features.

Marketing and sales

Weak: Campaign operations and customer management
Shows evidence: Split campaign messages by differences in conversion across incoming search terms, and adjusted budget allocation by comparing consultation requests and follow-up responses each week.

Rather than claiming total revenue as your personal result, separate the channels and customer groups you owned, the experiments, and the stages you directly contributed to.

Operations and customer support

Weak: Customer inquiry handling and service operations
Shows evidence: Categorized recurring inquiries by cause and unified guidance text and escalation criteria, standardizing how the team responds.

Even without a headline number, the scope you handled, recurring problems, the process before and after, and criteria others reused can all serve as evidence of results. If you need to explain the whole project in more detail, also see career history examples by role.

4. Your current role and direction on the first screen

If your experience points in several directions or you’re changing roles, a short summary under your name and contact details can help. Try condensing these three things into two or three lines.

Your current or target role
The scope of your most relevant experience
A representative strength or result

Not everyone needs a summary. If, like many entry-level applicants, your experience is short and the sections below already make your direction clear, you don’t have to force one. If you include a summary, the experience below should actually back it up.

5. The submission format set in the posting

File format, length, photos, and required sections differ by company and hiring system. Check the posting and the application screen first.

With no other instructions, PDF is convenient when the layout needs to be preserved, but if the posting asks for a Word file, follow that. When submitting a PDF, check the following.

Can the body text be selected and copied with a mouse?
Is key information inside tables, two-column layouts, and icons also available as text?
Do fonts and line breaks hold up on other devices?
Is your contact information not only in the header or footer?
Does the file name identify you and the role?

How ATS and other hiring systems parse résumés varies by product and settings. Favor standard headings and a simple reading order over elaborate decoration, but don’t assume it will pass any particular system.

6. Length and white space for relevant experience

Neither one page nor two is the right answer for every applicant. A short career may fit on one page, and an experienced applicant with a lot of relevant work may be easier to read on two.

When cutting length, don’t start by shrinking the font size and margins; remove things in this order.

Older experience unrelated to the role
Sentences that repeat the same meaning
Lists of technology names that don’t explain your role
Self-evaluating adjectives the body already demonstrates

White space makes the boundaries between pieces of information visible. Keep the spacing between sections, date formats, and font size levels consistent.

7. Checking facts, consistency, and personal information before submitting

In the final review, removing errors matters more than making sentences sound better.

Do the company name and job title match this application?
Do employment periods and project dates match LinkedIn and your career history?
Did you avoid writing team results as if you achieved them alone?
Can you explain the baseline and period of every number?
Are your email and phone number correct?
If it’s blind hiring, did you remove prohibited information such as school name, hometown, and family details?
After the spell check, did you reopen the PDF to check the layout?

When getting feedback from someone else, first cover personal information that isn’t needed for the review, such as your name, contact details, and address.

A ‘first-screen test’ that isn’t tied to 10 seconds

This test doesn’t time how long someone reads. It checks whether a person who sees only the first screen can answer the following questions.

What role is this person aiming for?
What is their most relevant experience?
What role did they have in that experience?
Is there evidence that makes you want to read more?

If the role and experience they name differ from what you meant to show, revisit the order and headings before adding more sentences.

Frequently asked questions

How do I write class projects on an entry-level résumé?

Separate class assignments, personal work, and internships, and write the period, the problem, your role, what you produced, and the result you confirmed. It’s better to show what you decided and did than the result of the whole team. If you can’t think of material, also see how to find evidence in ordinary experience.

Can I send the same résumé to several companies?

Keep the source facts for company names, dates, roles, and results the same, but adjust the order and descriptions of relevant experience for each posting. Rather than rewriting all your experience each time, use a table that connects the posting to your experience to pick the evidence to show for this application.

What to reread in the file you submit

Put the experience closest to the role first, and read whether your role, actions, and results connect as facts. Use numbers only when you have them, and use them precisely; when you don’t, make things concrete with evidence such as before-and-after changes, scale, frequency, and quality. Match the submission format to the posting, and finally check the content and personal information together.

How this was written and references

This article is a guide for making application documents more accurate and easier to read, not a scorecard that guarantees an offer from any company. If practices for a company, role, or country, or a posting’s submission instructions, differ from this article, follow those instructions first.