Work Experience on a Resume: What to Include and How to Write It

The work experience section is usually the most important part of a resume because it shows whether you have done work similar to the job you want. It should be easy to scan, recent enough to matter, and specific enough to prove your skills.

A strong work experience section is not a list of responsibilities. It is a selected record of relevant proof.

Work experience format

Use this structure for each role:

Company Name - Job Title - Location or Remote - Dates

Then add 3-6 bullets for the most relevant roles.

Example:

Brightline Software - Customer Success Manager - Remote - Mar 2022 - Present

• Managed onboarding for 38 mid-market accounts, coordinating kickoff plans, training sessions, and renewal handoffs.
• Built weekly account health reports in Salesforce to identify usage gaps before renewal conversations.

What to include in each role

How far back should work experience go?

For most resumes, focus on the last 10-15 years. Older experience can be shortened if it is still relevant. Remove old roles that distract from the target job.

Exceptions include academic, medical, federal, executive, and specialized roles where older experience may still matter.

How to write bullets for recent roles

Recent roles deserve the most detail. Use 4-6 bullets for the current or most relevant job. Include the skills, tools, and outcomes that match the target role.

Older roles can use fewer bullets. The resume should get more specific as it gets closer to the present.

Handling promotions

If you were promoted at the same company, show progression clearly:

Company Name

• Senior Analyst, 2024-Present
• Analyst, 2021-2024

Then group bullets under each title if the roles were meaningfully different.

FAQ

Should I include unrelated work experience?

Include it only if it helps explain your timeline or shows transferable skills. Keep it brief.

Should work experience come before education?

For experienced candidates, yes. Students and recent graduates may put Education first.

Can I combine similar roles?

Yes, if older roles are less important. You can summarize them under Additional Experience.

Work experience should prove the target role

The work experience section is not a job history archive. It is the main proof that you can do the target job. Recent roles deserve the most space when they support the target. Older or unrelated roles should get shorter.

Use this structure for each role:

1. Title, company, location, dates.
2. One context line if the company or role is not obvious.
3. 3-6 bullets for recent relevant roles.
4. 1-3 bullets for older or less relevant roles.

Bullet order inside each role

Put the strongest relevant proof first. Do not start with a routine duty if the second bullet proves the target role better.

Weak order:

1. Attended meetings.
2. Helped with reports.
3. Built renewal-risk dashboard for account managers.

Better order:

1. Built renewal-risk dashboard for account managers.
2. Created weekly reporting notes.
3. Coordinated follow-up meetings.

The reader may only skim the first bullet.

Work experience example

Weak:

• Responsible for customer onboarding and reporting.

Better:

• Guided 42 SMB customers through onboarding, documented launch blockers, and built weekly Salesforce reports for account managers.

The better bullet shows scope, responsibility, tool, and audience.

What to cut

Cut old duties that do not support the target. Keep promotions, scope, and transferable proof. If a role is older than 10 years and not relevant, it may need only title, company, and dates.

Work experience examples by situation

Same role family:

• Lead with recent outcomes, tools, and scope.
• Keep older similar roles shorter.
• Show progression when titles changed.

Career changer:

• Translate old work into target-role language without changing facts.
• Add transferable bullets before routine old duties.
• Use projects or certifications when they prove the new direction.

Entry-level:

• Include internships, campus work, volunteer work, and projects when paid experience is limited.
• Show tools, audience, and scope.

Older role example

If an older job does not support the target, compress it:

• Earlier experience: Retail associate, Office assistant, Campus coordinator. Built customer communication, scheduling, and documentation habits across part-time roles.

That is enough. Do not spend six bullets on old work if the target role depends on recent proof.

Work experience final check

Read only the first bullet under each recent role. If those bullets do not prove the target role, reorder or rewrite them. First bullets carry more weight than most candidates realize.

How many bullets to include per job

Use more bullets where the job is recent and relevant. Use fewer bullets where the job is old or unrelated.

Work experience rewrite examples

Weak:

• Responsible for customer onboarding.

Better:

• Guided 38 SMB customers through onboarding, tracked setup blockers in Salesforce, and escalated unresolved product issues before launch deadlines.

Weak:

• Helped with reports.

Better:

• Built weekly Excel reports comparing inventory delays, vendor response times, and fulfillment exceptions for operations managers.

Weak:

• Worked on website updates.

Better:

• Updated product landing pages in Webflow, coordinated QA fixes with design, and documented release notes for marketing handoff.

Each better bullet names work, tool or process, audience, and outcome context.

Work experience final gate

For each recent job, underline the nouns and numbers in the bullets. If a bullet has no tool, audience, scope, metric, process, or deliverable, it is probably too vague. Rewrite before adding more bullets.

Context lines can make experience clearer

Some roles need one short context line before the bullets. Use it when the company, team, or job scope is not obvious.

Example:

• B2B SaaS support team handling onboarding, account setup, billing questions, and product escalation for SMB customers.

Then write bullets that prove the work:

Weak:

• Handled customer issues.

Better:

• Resolved 45-60 weekly onboarding and billing tickets, tagged repeated product issues, and escalated release blockers to support leadership.

Use context lines sparingly. They should make the bullets easier to understand, not replace the bullets.

Experience section review order

Review the section in this order:

1. Are dates and titles clear?
2. Does the first bullet prove the target role?
3. Are the strongest tools visible?
4. Are older roles compressed?
5. Is every bullet defensible in an interview?

Work experience mini case study

A candidate applying for project coordinator roles has three years of office assistant experience. The old resume lists phones, email, filing, calendars, and office support. That reads like general admin work.

Better framing:

• Coordinated calendars for six managers, tracked appointment changes, and sent daily schedule updates before office opening.
• Maintained vendor follow-up tracker, flagged missing responses, and summarized open items for weekly operations meeting.
• Documented client intake details and updated records before handoff to service team.

The facts did not change. The bullets now show coordination, tracking, documentation, and handoff ownership.

How to handle promotions

If you were promoted, show it clearly. Promotions are evidence of trust.

Example:

• Customer Support Associate, 2023-2024
• Senior Customer Support Associate, 2024-2026

Then use bullets under the combined role to show what changed: ticket scope, mentoring, escalations, process notes, reporting, or team ownership.

Experience proof map

Every recent role should prove at least one target skill.

Experience rewrite example

Weak:

• Worked with team members on projects.

Better:

• Maintained launch task tracker for design, support, and product, documenting unresolved blockers before weekly release review.

If a bullet cannot connect to a target skill, cut it or move it lower.

Final work experience check

Read the first bullet under each recent role. It should be the strongest role-relevant proof, not the most routine duty.

Weak:

• Attended meetings and supported team needs.

Better:

• Maintained launch tracker for design, support, and product, documenting unresolved blockers before release review.

The first bullet sets the frame for the whole role.

Last-mile experience review

For each role, mark bullets as target proof, context, or filler. Keep target proof. Keep only necessary context. Cut filler.

Weak:

• Six bullets that all describe routine duties.

Better:

• Three bullets showing scope, tool, audience, and result, plus one context bullet if needed.

The section gets stronger when weaker bullets leave.

Sources

• USAJOBS resume guidance
• NIST resume tips
• O*NET, U.S. Department of Labor