1. LandOffer
  2. Blog
  3. All articles
  4. Promotions on a Resume: Show Multiple Roles at One Company Without Losing the Timeline

Job search

Promotions on a Resume: Show Multiple Roles at One Company Without Losing the Timeline

Show promotions and internal moves on a tech resume with accurate role dates, employer tenure, and achievements tied to the right position.

10 min readLandOffer team

When you have held more than one role at the same company, show the employer once and give every meaningful title its own dates. Stack related roles under the employer when their work forms a clear progression; give changed functions separate accomplishment blocks when readers need context. If you left and later returned, show the two employment periods separately. In every format, keep the senior title inside the dates when you actually held it.

This guide compares those layouts and works through three fictional examples: a software-engineering promotion, a move from engineering into management, and expanded responsibility without a formal title change. Use the titles and dates supported by your records, then follow any employer-specific application instructions. You can also browse recent roles on LandOffer.ai as you prepare your next search. The names, dates, projects, and outcomes below are invented examples, not candidate histories.

A resume editor shows an employer timeline above three dated role titles, with accomplishment bullets aligned to the right position.

Keep employer tenure and title tenure separate

The employer line shows where and how long you worked. Each position line shows the role and when you held that title. Those dates describe different facts: your company tenure might span six years while your current title covers only the last eighteen months.

The Department of Labor’s VETS resume workshop presents both a stacked format and separate listings for multiple positions at one organization. In its stacked example, the organization has an overall range, each title has its own dates, and achievements sit under the relevant position. CareerOneStop likewise advises making the title, organization, location, employment dates, and relevant contributions easy to find. Together, these sources support a simple standard: the reader should be able to reconstruct the sequence without guessing.

For example, a clean timeline might look like this:

Northstar Analytics — Austin, TX | May 2020–Present
Senior Software Engineer | Jan 2025–Present
Software Engineer II | Jul 2022–Dec 2024
Software Engineer I | May 2020–Jun 2022

The employer range shows continuous company tenure. The title dates show when each role began and ended. If you instead put “Senior Software Engineer | May 2020–Present,” a reader could reasonably conclude you held that title for the entire period. Do not rely on a promotion bullet to repair dates that say something else.

Use the date precision the employer or form requests. If you present month and year, use one style and a consistent transition boundary. Verify uncertain dates before sending; do not make the timeline look more precise than your records support.

Choose stacked titles or separate role blocks

Use a stacked format when the positions are related and the progression is easy to follow. This fits, for example, a software engineer who moved from Engineer I to Engineer II to Senior Engineer on one product area. Put the employer once, order positions newest first, and give every title a date range. Readers can then see both continuity and the actual length of time in each role.

Bullets can sit directly under each title when accomplishments clearly belong to one period. A shared group of bullets can work when the title changed but day-to-day work remained substantially similar; if you do this, do not attach a single role’s dates to the whole group. A short first bullet can explain the progression if it adds context: “Promoted to Senior Software Engineer in Jan 2025 after taking ownership of release coordination.” Use a reason only if you can substantiate it and it helps the reader understand the change.

Choose separate role blocks when the work changed enough that one shared bullet set would blur ownership. An engineer who became a people manager may need distinct evidence: architecture or delivery work under the engineering title, then hiring, coaching, team health, and planning under the manager title. A move from technical support into product engineering may also need separate blocks because the functions and relevant skills differ. You can still keep the company name and total tenure in one heading; “separate” means the roles have their own dated descriptions, not that the resume has to repeat the company name at every line.

Repeat the employer as a separate chronological stint when you left and returned, when another employer sits between two periods, or when separate entries make the sequence substantially clearer. Show the actual gap between stints. A return to the same company is not the same as an uninterrupted six-year tenure, even if the company header would look neater that way. If a merger or legal-name change altered the organization, use the name that best identifies the employer during the work and add a brief parenthetical only when it prevents confusion.

The DOL guide offers two formats, and Indeed’s career guidance also distinguishes similar positions from roles with different duties. Treat them as options, then choose the one that makes employer, dates, titles, and evidence easiest to read. These sources do not establish universal applicant-tracking-system compatibility.

Three worked formats for a technology career

These examples are fictional. Replace every company, title, date, project, and accomplishment with details you can support. The bullets show how to connect work to a role; they are not achievements to copy.

Example 1: A related engineering promotion

Cedar Peak Systems — Portland, OR | Feb 2021–Present
Senior Backend Engineer | Apr 2025–Present

  • Set the service-boundary review for a billing migration and documented rollback checks used by three product teams.
  • Mentored two engineers through design reviews and incident follow-ups; the fictional example does not assert a measured team outcome.

Backend Engineer | Feb 2021–Mar 2025

  • Built a retry-safe event consumer and added replay tests for duplicate webhook deliveries.
  • Rotated through service on-call and wrote the handoff guide used by the next owner.

The dates and bullets keep each scope with its title. The newer role shows broader review responsibility without rewriting earlier work as senior-level ownership.

Example 2: A move into engineering management

Harborline Health — Remote | Jun 2019–Present
Engineering Manager | Oct 2024–Present

  • Set quarterly service goals with product and reliability partners; made staffing and delivery risks visible before planning commitments.
  • Hired and coached a four-person platform team, with hiring and headcount figures included only where the candidate’s records support them.

Software Engineer | Jun 2019–Sep 2024

  • Designed an audit-log service in Go and worked with security to define retention and access controls.
  • Improved deployment checks so operators could identify incomplete rollouts before routing traffic.

Separate blocks fit because the evidence changed from individual contribution to team leadership. Add a promotion note only when it is factual and relevant; show what changed instead of claiming “high performance” without support.

Example 3: More responsibility, same official title

Fernwell Data — Chicago, IL | Mar 2022–Present
Data Engineer | Mar 2022–Present

  • Expanded ownership in Sep 2025 to include data-contract reviews and the release checklist for two pipelines; title unchanged.
  • Built schema validation and a quarantine report for late vendor files, then documented the escalation path for the analytics team.

If the employer did not issue a new title, do not invent one such as “Senior Data Engineer” simply because you gained scope or a raise. Keep the official title and use a dated bullet to describe the added responsibility. The wording “expanded ownership” is only suitable if that accurately captures the change and the date can be verified. If the resume’s space is tight, one short clause can mark the change without adding a new role entry.

Run a chronology audit before you polish the bullets

The most common timeline error is easier to spot in a small audit than in a polished resume. Before formatting, compare your records in a private table:

An audit sheet keeps one employer-wide span separate from three role-specific date ranges and marks an incorrect full-tenure title span for correction.
Record check Fictional timeline Resume decision
Employer service Northstar Analytics, May 2020–Present Company header uses May 2020–Present.
First title Software Engineer I, May 2020–Jun 2022 Keep its own dates; use bullets from this period only.
Second title Software Engineer II, Jul 2022–Dec 2024 Show the transition month consistently and attach the relevant work to this title.
Current title Senior Software Engineer, Jan 2025–Present Do not give this title the full May 2020 company span.
Role evidence Release coordination began in 2025 Describe it under the current role, unless it began earlier and the dates are stated accurately.

Check transitions against employer records: effective month, interim titles, team changes, and conflicting dates in a promotion notice or internal profile. Keep a note of the source. If a date remains uncertain, don't guess; use supported precision and prepare a plain explanation. A clean design cannot compensate for a timeline you cannot explain.

After a reorganization, distinguish a new team or reporting line from a new title. Use the official title held at the time. If it is opaque outside the company, add a short accurate explanation, but do not substitute a seniority level you did not hold.

Date a leave or employment gap according to the real work periods and employer relationship. Do not extend role dates to hide a break or create a second stint if employment continued. For a rehire after separation, list distinct stints in reverse chronological order. Whether to explain a leave depends on the resume’s purpose and employer instructions; this guide does not determine legal or benefit status.

Match achievements to the period when they happened

Divide accomplishments by the time and scope in which you performed them. If you launched a service before a promotion and later became its technical lead, write one bullet for the launch and another for the later leadership only if both are true. A result that spans roles can be assigned to the period in which the work occurred, or described with dates that clarify the sequence. Avoid giving the newest title credit for a project that began under an earlier role without explaining that history.

Use an action, context, and outcome when you have evidence. Describe the system or team affected and what changed. Add metrics only when you can explain how they were measured and what your contribution was. CareerOneStop encourages specific accomplishments, not invented numbers.

If the promotion itself matters, name it in a concise bullet or transition phrase: “Promoted from Engineer II to Senior Engineer in Jan 2025; assumed design review for the ingestion platform.” Check that the date agrees with the title line. If there was no formal promotion, describe the new scope without using the word “promoted.” Titles, compensation changes, expanded duties, and formal promotions are related but not interchangeable facts.

Trim repeated bullets before removing role dates. Older positions may need only one relevant accomplishment; keep the title dates accurate. A master career record can preserve more detail than a tailored resume.

Reconcile the resume with an application form

An application may allow one employer entry, several roles, or a full work history. Follow its instructions. If separate entries are allowed, give each real title its dates. If there is only one title field, use the most accurate supported title and include earlier roles in an attachment or supplemental field if permitted. Do not pair the newest title with the oldest start date just to fit the form.

For federal roles, use the current job announcement and the official application instructions. OPM’s applicant guidance, for example, specifies a job title and employer, month/year start and end dates, and hours per week for relevant work experience in that federal resume context. Those requirements are specific to federal hiring materials and should not be presented as a universal private-sector rule. Save a copy of what you submit so you can answer consistently if a recruiter asks about the timeline.

Check the exported document, not just the editor. Confirm each title still sits beside its dates, employer names remain attached to roles, and bullets have not shifted. A simple single-column layout is easier to inspect, but no design guarantees identical parsing by every system. Follow employer format instructions and verify the PDF or DOCX you upload.

Before sending, read only the employer and role lines from top to bottom. Can you reconstruct every start, transition, and end date? Does the newest title begin when you actually took it? Do the accomplishments fit those dates? Check the same sequence in the exported file and any application fields. If those details line up, a reader can see the progression without having to infer it. For your next search, browse recent roles on LandOffer.ai.

Sources and Further Reading