How to Format a Resume With Multiple Jobs at the Same Company (2026 Guide)

Getting promoted or changing teams internally is a major career achievement — but formatting it on a resume confuses a lot of job seekers. List each role separately and waste space? Combine them and hide the progression?

Here are three proven approaches, with ATS compatibility notes for each.

The Challenge: Why Multiple Roles at One Company Is Tricky

When you've held multiple positions at the same employer, you face three competing goals:

1. Show career progression (employers love internal promotions)

2. Save space (most resumes should be 1–2 pages)

3. Pass ATS parsing (some ATS systems struggle with stacked roles)

There's no single right answer — the best format depends on how different the roles were and how long you held each.

Method 1: Stacked Format (Best for Promotions in Same Function)

Use when: You were promoted or changed titles but stayed in the same team/function.

~~~

ACME Corporation — San Francisco, CA Jan 2020 – Present

Senior Software Engineer Mar 2023 – Present

• Led architecture of microservices migration reducing latency by 45%

• Mentored team of 4 junior engineers, improving team velocity by 30%

Software Engineer II Jul 2021 – Mar 2023

• Built core API layer handling 5M+ daily requests with 99.9% uptime

• Reduced infrastructure costs by $80K/year via AWS optimization

Software Engineer I Jan 2020 – Jul 2021

• Developed 12 new product features shipped to 200K+ users

• Reduced bug backlog by 60% through systematic test coverage improvements

~~~

Why this works:

• Company name appears once (no repetition, saves space)
• Progression is visually clear (dates + titles stacked)
• ATS reads it correctly — each title is a separate entry under the same employer
• Bullet points under each title keep responsibilities distinct

Method 2: Merged Format (Best for Similar Roles, Emphasizing Scope Growth)

Use when: The roles were very similar, and you want to emphasize cumulative impact rather than individual role boundaries.

~~~

ACME Corporation — San Francisco, CA Jan 2020 – Present

Software Engineer → Senior Software Engineer

• Progressed from Engineer I to Senior in 3.5 years based on performance

• Built and maintained API infrastructure serving 5M+ daily requests

• Led microservices migration (Senior role) reducing system latency by 45%

• Mentored 4 junior engineers; reduced infrastructure costs by $80K/year

• Shipped 12 product features used by 200K+ customers

~~~

Why this works:

• Maximally space-efficient
• The "→" in the title signals progression without requiring multiple entries
• Good when the responsibilities genuinely overlapped heavily

Warning: Some ATS systems may only capture the most recent title. If exact title matching matters (e.g., you're applying for "Senior Software Engineer" roles), the Stacked Format is safer.

Method 3: Separate Entries (Best for Very Different Roles or Departments)

Use when: You changed departments, moved from technical to management, or the roles are genuinely distinct (e.g., IC to manager, or engineering to product).

~~~

ACME Corporation — San Francisco, CA

Engineering Manager Jul 2023 – Present

• Managed team of 8 engineers across 3 product squads

• Delivered $2M product roadmap on time and under budget

• Hired and onboarded 4 engineers, improving team throughput by 35%

ACME Corporation — San Francisco, CA

Senior Software Engineer Jan 2020 – Jul 2023

• Architected event-driven microservices system handling 8M+ daily events

• Reduced system latency by 45%; improved test coverage from 40% to 88%

• Mentored 3 junior engineers, 2 of whom were promoted within 18 months

~~~

Why this works:

• Clearly differentiates IC vs. management roles
• Each entry is unambiguous for ATS parsing
• Allows tailored keyword sets per role

Downside: Uses more space. Only worth it if the role transition is significant enough to justify.

Which Format to Use: Decision Guide

ATS Tips for Multiple Roles

Always include dates for each role. ATS systems calculate tenure by reading start/end dates. Missing dates on individual roles can confuse parsers and undercount your experience.

Use the exact job title you held. Don't inflate ("Principal Engineer" when your title was "Senior Engineer"). ATS systems sometimes cross-reference LinkedIn for title verification.

Keep the company name consistent. If the company rebranded (e.g., "Facebook" → "Meta"), use the current name but note the former in parentheses: "Meta (formerly Facebook)."

Quantify progression. Numbers make promotions tangible. "Promoted to Senior Engineer after leading 3-person team to deliver project 2 weeks early" is stronger than just listing the title change.

Contract and Freelance Work at the Same Company

If you did contract work followed by a full-time hire:

~~~

ACME Corporation — San Francisco, CA

Full-Time Software Engineer Jul 2022 – Present

Contract Software Engineer Jan 2022 – Jul 2022

• Contract-to-hire; converted full-time based on performance

~~~

This makes the conversion explicit and prevents ATS from treating the gap as unexplained unemployment.

A well-formatted resume is the foundation. Once it's polished, ResumeToJobs handles the volume — applying to relevant positions with your tailored resume and delivering screenshot proof of every submission.