Showing several roles at the same employer
Promotion inside one organisation is good evidence badly served by most layouts. Here are the two that work, and how each one parses.
— show the progression, not the repetition.
Several roles at one employer is good evidence: somebody watched you work for years and kept giving you more. Most layouts hide it, either by collapsing the whole run into one block or by repeating the employer four times until it looks like four jobs.
The stacked layout
One employer heading with the full span of years, then each title underneath with its own date range and its own lines. It reads as one relationship with a shape, and the progression is visible in three seconds. Use it when the work was continuous and the title changed as you grew into it.
The separate-entry layout
Each role as its own entry, employer repeated, in reverse chronological order. Use it when the roles were genuinely different work: a move from support into engineering, from a regional patch to a national one, from delivery into management. The reader needs both entries because they are two different sets of evidence.
Put each achievement under the role that produced it
Resist restating the same three lines at each level. The earlier role keeps what you did then, at the scope you had then, and the later role carries what changed once you had more. That contrast is the argument for your promotion, and repetition destroys it.
Dates do the talking
Four-digit years, one format, consecutive ranges with no gaps between the titles. Nobody has to write the word "promoted": 2019 to 2021 followed by 2021 to present says it, and says it without a claim a reader has to take on trust.
How it parses
The ATS résumé checker reads the experience section as lines of text and looks for role words, dates and achievement lines. A stacked layout is safe as long as each title sits on its own line with its dates beside it, in a single text flow.
What breaks it is a two-column or table arrangement of titles and dates. A detected table or multi-column pattern costs twenty-two points of parseability here, and in an employer's system the same pattern can interleave your titles with somebody else's dates. The format guide covers why.
Long runs at one employer
Ten years and four titles does not need four full entries. Give the last two roles their lines, compress the first two to a title and a date range each, and keep the employer heading spanning all of it. The guide to how far back to go applies inside a single employer exactly as it does across several.
Doing it in the builder
In the résumé builder, each role is its own entry with a title, employer, place and dates, so either layout is a matter of how you fill them in rather than of formatting by hand. Enter the employer once per role, keep the dates consecutive, and the design will lay the run out consistently. The rail counts the roles, so a title you meant to add and forgot is visible from the left.
When the employer changed name or owner
Acquisitions, mergers and rebrands leave people with a history that looks like two jobs. Write it as one: the current name, then the former name in brackets, with the date of the change if it matters. "Northwind Pay (formerly Leitmotiv Payments), 2018 to present" is one line and it answers the question before it is asked.
The same applies to an agency placement or an employer of record, where the organisation you worked for and the one that paid you differ. Name the one you worked for and note the arrangement, which is the version a reader can verify.
Internal moves that were sideways or down
Not every move is a promotion, and a page that presents every one as such invites the question. A move into a specialism, a reduction in scope during a reorganisation, a step back to a role you preferred: each is a fact with a date, and each can be stated plainly without explanation on the page. Where the reason matters to this application, it belongs in the letter, where you can answer the follow-up. The career-change guide covers the framing when the move is the point of the application.
Seven years, one employer
A long run at one organisation is evidence of trust, and it can read as a lack of range if the page shows no change inside it. The remedy is the titles and the widening scope: each entry naming what got bigger, not each entry repeating the same duties at a higher grade.
Lay out the progression
Each role is its own entry with its own dates, so a run of promotions reads as a sequence rather than one long block.
Open the résumé builderRead the experience guideQuestions
- Should I list each role separately
- List them separately when the roles were genuinely different work. Stack them under one employer heading when the work was continuous and the title changed.
- How do I show the promotion
- By the dates. Two titles with consecutive date ranges under one employer say promoted without using the word.
- Do I repeat the achievements
- No. Put each achievement under the role that produced it, and let the earlier role keep the ones a reader would expect from that level.
- Does a stacked layout parse safely
- Yes, as long as each title line carries its own dates and sits on its own line. Problems come from putting the titles in a table or a two-column block.
- What about a sideways move
- Treat it as two roles. A change of function at the same level is a change of work, and the reader needs both.
Conxfolio is a free set of four career tools: a résumé builder with 37 rendered layouts, an ATS résumé checker that prints its own arithmetic, a cover letter builder that traces every proof paragraph back to the line it came from, and a portfolio builder with 20 authored designs. There is no account to create, nothing is held back for a paid plan, and no language model is used anywhere in the product, so the readers, the score and the letter are deterministic code you can check.