How to Write Professional Experience

Your professional experience section is the heart of your resume. It is where a hiring manager decides whether you have actually done the work the job requires, and it is where an applicant tracking system (ATS) finds most of the keywords it searches for. How you write it matters more than any template or design choice.

This guide covers what each entry needs, simple formulas for writing strong bullets, before-and-after examples, and the mistakes that weaken this section. For the rest of the resume, see our full guide on how to build a professional resume that gets you noticed.

What Each Experience Entry Needs

List your roles in reverse chronological order, most recent first. Each entry should include:

• Job title: your actual title. If it was unusual, you can add a common equivalent in parentheses, such as "Customer Champion (Account Manager)."
• Employer and location: company name, city and state, or "Remote."
• Dates: month and year for start and end, in one consistent format, such as "Jun 2021 – Present."
• Three to six bullets: what you achieved in the role, strongest and most relevant first.

If you held several titles at one employer, list the company once and stack each title with its own dates underneath. It shows progression and saves space.

Duties vs. Achievements

The most common problem in this section is describing a job description instead of a performance. "Responsible for customer onboarding" tells the reader what you were supposed to do. It says nothing about whether you did it well.

An achievement bullet answers three questions:

1. What did you do?
2. How big or complex was it?
3. What changed because of it?

Not every bullet will have a number, and that is fine. A clear description of scope or outcome ("so the team could close the books two days earlier," "adopted by all three regional offices") is often as persuasive as a percentage. What you must never do is invent a figure. If an interviewer asks how you arrived at a number, you need to be able to explain it.

Bullet Formulas That Work

You do not need to be a strong writer to produce good bullets. These patterns cover most situations.

Action + scope + result

Start with a strong verb, say what you worked on and how big it was, then give the outcome.

Pattern: [Verb] [what] for/across [scope], [result].

Example shape: Rebuilt the monthly reporting process for a five-person finance team, cutting close time from X days to Y.

Accomplished X, measured by Y, by doing Z

This is a widely used formula that forces you to include the result and the method.

Pattern: [Result], measured by [metric], by [what you did].

Problem + action + result

Useful when the context makes the achievement impressive.

Pattern: [Faced problem], [took action], [result].

Example shape: Inherited a backlog of overdue vendor invoices; set up a weekly triage with purchasing and cleared the backlog within one quarter.

Choosing verbs

Pick verbs that show your actual role. "Led," "owned" and "managed" imply responsibility. "Built," "designed" and "launched" imply creation. "Reduced," "improved" and "grew" imply results. "Supported" and "assisted" are honest when you contributed to someone else's work, so use them when they are true rather than overstating.

Use past tense for previous roles and present tense for your current one.

Before and After Examples

The examples below are illustrative. The rewrites show the structure to aim for; the bracketed parts are where your own real figures go. Do not copy numbers you cannot back up.

Customer service

• Before: Answered customer calls and emails.
• After: Resolved [number] customer calls and emails a day across billing and technical issues, and wrote the team's first FAQ for recurring billing questions, reducing repeat contacts.

Project coordination

• Before: Responsible for coordinating projects.
• After: Coordinated [number] concurrent construction projects with budgets up to [amount], keeping subcontractor schedules aligned through a shared weekly tracker.

Software engineering

• Before: Worked on the checkout page.
• After: Rebuilt the checkout page's payment form in React, reducing page load time by [your measured figure] and removing a legacy dependency that blocked upgrades.

Retail management

• Before: Managed store staff.
• After: Hired, trained and scheduled a team of [number] associates; introduced cross-training so the store could cover every shift without overtime.

Notice what changed in each: a stronger verb, a clear sense of scale, and an outcome the reader can picture.

Tailoring and Keywords

The same job can be described many ways, so describe it in the language of the role you want.

• Read the job description and note the skills and tools it repeats.
• Where those skills truthfully describe your work, use the employer's exact words in your bullets. If they say "stakeholder management," use that phrase rather than only "worked with other teams."
• Reorder bullets so the ones most relevant to the posting come first.
• Put keywords in real sentences about real work. A term that appears in context reads better to a person than one dropped into a list, and keyword stuffing is obvious to anyone reading.

To see which of a job's requirements your experience section already covers, ATS scoring shows the match requirement by requirement, with the evidence behind each one.

How Much to Include

• Recent and relevant roles: full detail, three to six bullets.
• Older roles (roughly ten to fifteen years back): one or two bullets, or just title, employer and dates.
• Gaps: you can note them in one line ("Career break: family caregiving") rather than leaving the reader to guess.

Common Mistakes

• Listing duties without results.
• Vague bullets such as "helped with various projects."
• Too many bullets per role, which buries the best ones.
• Inconsistent date formats or tenses.
• Invented or inflated numbers.
• Leaving irrelevant, outdated experience in full detail.
• Skipping the proofread.

Getting It Done Faster

HireCurve is AI software that helps with this step: you upload your resume once, it builds a profile of facts from your history with the source quote for each one, and when you paste in a job description it tailors your experience section to that job using only your own experience. Every line cites where it came from, and it does not invent experience, skills, metrics or outcomes. There is a free plan with two applications a month, and you can see how it works.

Frequently Asked Questions

How many bullet points should each job have?

Three to six for recent, relevant roles, and one or two (or none) for older ones.

What if I do not have numbers to show?

Describe scope and outcome in words: who used what you built, what became easier or faster, what problem went away. Specific description beats an invented metric.