Refolk
TeardownPositioning and materials

The One-Employer Title Stack Teardown, Five Titles to Four Verified Rows

Mark every title change at one employer stack, split, or fold, and ship an entry that parses as separate rows, groups on LinkedIn, and matches a record.

20 min readLast reviewed November 17, 2026Read as Markdown

Key takeaways

  • Employment verification through payroll feeds returns one job title plus hire dates and has no field for title history, so every older title on a resume needs its own offer letter, promotion letter, or HR letter.
  • LinkedIn groups positions at one employer only when each new start date falls within one month of the previous end date and both positions link to the same company page.
  • A parser founder's rule for stacked titles is that every title line needs its own dates, because dates are what the parser uses to recognise a new role.
  • A company-wide retitle with no change in scope should be folded into one line using the newest payroll title over the full date range, never shown as a promotion.
  • In Refolk's index there are 1,225 current US Interim Director profiles against 537 Acting Director profiles, and at least 9 of 25 sampled Acting Directors work at federal agencies, so the label carries meaning.
  • The only published data on title checks is a 2004 survey in which 53% of HR professionals said they always verify former job titles, so treat every title line as checkable.

This guide is for anyone who has held three or more titles at one employer, through promotions, team moves, or a company-wide retitle, and needs one experience entry that does three things: reads as progression, parses as separate roles in an application portal, and matches what HR will confirm. I take one eight-year, five-title tenure through every decision, wrong turns included. You end with a decision for each title change, a parse test you can repeat, and a record tied to every title on the page.

What reads a multi-title entry, and what each reader sees

Four readers see the same entry, and each keeps less of it. The portal parser builds rows from dated title lines. LinkedIn groups positions by a date window and a company page link. Employment verification returns one payroll title. On top of all three, a recruiter skims for progression.

Where each title survives

  1. The resume page
    Every title you write, with any wording you choose
  2. Portal parser rows
    Only title lines that carry their own dates become separate roles
  3. LinkedIn company block
    Positions linked to one company page, each starting within one month of the last
  4. Verification record
    One payroll job title, plus original and most recent hire dates
Each layer keeps less of your history than the one above it, and only the innermost layer is checked against payroll.

The portal parser

No ATS vendor has published documentation on stacked titles at one employer, so everything here comes from practitioners. They report that:

  • Stacking titles without repeating the company makes older parsers attach only the first role's dates to the company header and merge the remaining titles into the bullet text.
  • A parser founder says every title line needs its own dates, because dates are how the parser recognises a new role. The same founder says some parsers read a stack as three jobs at one company and others read it as one job with three titles.
  • One comparison table says stacked entries often split into two separate employer entries unless the company name appears on every title line. It also says a "formerly" title gets captured in the description, not as a separate role. That table doesn't say which ATS it tested.

The pattern is consistent even though the source isn't official: dates mark where a role starts, and the company name on each line keeps it attached to the right employer.

LinkedIn

LinkedIn's help page says positions are grouped when the start date of a new position falls within one month of the previous position's end date at the same company. LinkedIn's launch post for the feature adds that both positions must link to the same company page. Grouped positions get tenure that is calculated automatically. There is no documented manual switch to group or ungroup positions. If grouping is wrong, the help page says to check and update the company name.

LinkedIn publishes nothing on how grouping behaves after an acquisition or a company page rename. One practitioner says renames might update profiles but mergers and acquisitions will not. LinkedIn does say followers can't be migrated from an acquired organisation's page to the acquirer's page, though duplicate pages can be merged. If your employer was acquired during your tenure, check the profile by hand.

The recruiter's skim

Ladders reported a 7.4-second initial screen in its 2018 eye-tracking study, up from 6 seconds in 2012. Recruiters looked at the current title and company, then the previous one, then moved right to the dates to check for steady progression. The published report doesn't say how many recruiters took part, and no study compares stacked titles with repeated employer headers. Any claim that many titles in a short span reads as a negative is unsupported. Optimise for the parser and the record, both of which you can test.

The worked example: five titles, two team moves, one retitle

The example is a composite eight-year tenure built to hit every fork. The dates are relative (Y1 to Y8) so you can map your own months onto them. The parse results I describe are the outcomes the practitioners above report, not a benchmark of any named ATS. Here is the candidate's title ledger as they first wrote it, with the record found for each title.

Draft titleDatesWhat changedRecord found
Operations AnalystJan Y1 - Dec Y2HireOffer letter
Senior Operations AnalystJan Y3 - Jun Y4New level, same teamPromotion letter
Platform Program CoordinatorJul Y4 - mid-Aug Y4Team move 1, 1.5 monthsTransfer notice
Senior Program Manager, Platformmid-Aug Y4 - Aug Y7Company retitle in Y6Retitle memo, no promotion letter
Acting Director, Customer OpsOct Y7 - Dec Y8Team move 2, acting dutiesActing memo; report shows Customer Operations Manager

Draft one stacked all five titles under one company line dated Jan Y1 - Dec Y8, with no dates on the title lines. That is the layout most sample templates show. Based on the practitioner reports, a parser would most likely return one row: Operations Analyst, with the full eight-year range, and the other four titles buried in the bullets. On screen it looked like a clean progression. In the portal it looked like one job.

Building the ledger exposed four more problems:

  • The 1.5-month coordinator title was a transitional label. The transfer paperwork had not caught up yet. On its own line it reads as a role, but it held no work worth a bullet.
  • "Senior Program Manager" came from the Y6 company-wide retitle. Payroll had renamed every Program Manager to "Program Lead." The candidate had read the new name as a step up and written the old title with "Senior" added. No promotion letter existed.
  • "Acting Director" sat on a title line by itself. The Employment Data Report (the consumer copy of the payroll-fed verification file) showed "Customer Operations Manager."
  • A gap of more than one month sat between the Platform end date (Aug Y7) and the Customer Operations start date (Oct Y7). On LinkedIn, that alone would split the company block in two.

Stack, split, or fold: how to call each title change

Stack a title when the scope stayed the same and the level rose. Split it when the team or the duties changed. Fold it when only the name changed, or when the title lasted too briefly to stand alone. Each call puts the title somewhere different: stacked and split titles get their own dated line, and folded titles end up in a parenthetical or a bullet.

  • Stack: a new level in the same scope. The title gets its own dated line under the employer.
  • Split: a new team or new duties. The title gets its own dated line with the employer name repeated, so the parser and the reader both see a distinct role.
  • Fold: a retitle with no change in scope, or a very short title. It merges into the neighbouring title, and the old name moves into a parenthetical or a bullet.

Calling each title change

New levelSame level
Stack
Own dated line, same employer, promotion letter on file
Split
Own dated line, employer repeated, transfer and promotion records on file
Fold
Merge into the neighbouring title; note the old name if references use it
Split (lateral transfer)
Own dated line, employer repeated, transfer notice on file
Same team and dutiesNew team or duties
Whether the level rose and whether the scope changed decide the call, and a change on neither axis is always a fold.

Where sources disagree: the retitle

The sources split on the company-wide retitle, so here they are side by side.

SourceAdvice on a retitle with no scope change
PrezumiNewest title over the full date range; note the old title if references use it
HR Bartender / Barrett-PoindexterA bullet saying same duties, retitled in a reorganization; never tweak upward
VisualCVStack the titles for an internal reclassification
Resume GeniusA restructuring is not a promotion; format it as one only if title and duties changed

I side with Prezumi and Barrett-Poindexter. A stacked line implies a step up that the payroll record won't show, and verification returns only the current payroll title. As Jacqui Barrett-Poindexter puts it, "don't give yourself a promotion."

The calls in the example

  1. Operations Analyst to Senior Operations Analyst: stack. Same team, new level, and the promotion letter is on file.
  2. Platform Program Coordinator: fold. No source sets a minimum length for a title to stand alone, so this is a judgement call. I folded it because the transfer notice dates the team move from Jul Y4, which lets the Platform role start in Jul Y4 with no loss of tenure.
  3. Senior Program Manager: drop the inflation, fold the retitle, split from the analyst roles. The team move makes it a split. The retitle makes it a fold within that role. The final line uses the newest payroll name over the full range: "Program Lead, Platform (titled Program Manager before a company-wide retitle)."
  4. Acting Director: split, and relabel. New team, so it gets its own line. The label itself needs its own decision, which the next section covers.

Five draft titles became four dated lines: two stacked and two split.

Acting and interim titles: what the label signals

"Acting" means a temporary assignment over a base title. Payroll returns the base title, so the base title goes on the title line and the acting role goes in parentheses or the first bullet. The label isn't decoration. Refolk's index shows it clusters in specific sectors.

Title, countryCurrent profilesExact-title share of 25 sampledNotable employers
Acting Director, US53772%US Dept of Veterans Affairs (5), CISA, IRS, CBP
Interim Director, US1,22576%Coppin State Univ., TMC Health, Saint Leo Univ., Alstom
Acting Director, UK6348%UK Ministry of Defence, Goldsmiths, DN Colleges Group
2.28x
US "Interim Director" profiles per "Acting Director" profile in Refolk's index
1,225 against 537, and at least 9 of 25 sampled US Acting Directors work at federal agencies.

In Refolk's index of professional profiles, 5 of the 25 sampled US Acting Directors are at the U.S. Department of Veterans Affairs, and federal agencies account for at least 9 of the 25. The Interim sample leans towards universities and health systems. In the US, "Acting" reads mostly as a government label, and "Interim" is the more common term elsewhere.

The fork in the example. I considered relabelling the role "Interim Director," since that is the more common US convention in the private sector. I rejected it, because the assignment memo says "acting" and no record anywhere says "interim." Changing the word would replace one unsupported label with another. If your own memo says interim, use interim. The final line reads: "Customer Operations Manager (Acting Director, Customer Operations)." The payroll title comes first and the acting role sits in parentheses, with the memo on file.

A limit on these numbers: the exact-title share is only 48% to 76% of each sample. The UK Acting Director sample includes theatre titles, and the US sample includes at least one junk title. Treat the raw counts as directional.

What employment verification returns, and which record covers each title

Payroll-fed verification returns one job title and hire dates, not your title history. Every title on the page except the current payroll title therefore needs its own paper record. The table shows what each output from The Work Number contains, based on its product sheet, employment letter FAQ, and data dispute form.

OutputTitleStart date fieldsTitle history
Select Gold reportOne job titleMost recent start dateNot shown
Employment LetterJob titleNot listedNot shown
Data dispute formJob titleOriginal and most recent hire dateNot a field

The University of Northern Iowa describes the data as coming from payroll files sent weekly to The Work Number. No source shows a field for title history, so whether title history ever appears is not established publicly. Plan as if the verifier sees one title.

53%
HR professionals in a 2004 survey who said they always verify former job titles
66% always verified dates. This is the only published figure, and it is old; current rates are not established.

The date trap

The record keeps the original hire date separate from the most recent hire date. If the HR system coded a transfer as a rehire, or an acquisition re-entered staff, the visible start date can reset. In one Blind case, an employee's record started at the acquisition date and carried the real start as a continuous service date, and the screener flagged the dates. In the example, both hire dates on the Employment Data Report showed Jan Y1, so neither team move had reset anything. Check yours.

Which records count

A practitioner blog lists these as proof of a title:

  • The original offer letter showing the starting title
  • A promotion letter or an internal email confirming a title change
  • A signed letter from a former manager on company letterhead
  • Pay stubs that show the role

Don't count on any single one being accepted. In one Blind case, HireRight rejected the documents and asked for a W-2 or IRS transcript, neither of which shows a job title. In another, The Work Number returned "Not Applicable" in the title field and the screener flagged it as a discrepancy. A 2013 HireRight guideline, reproduced second-hand, lists a title that is "not equivalent to what was provided by the applicant" as a minor discrepancy.

To check your own record, view your Employment Data Report through The Work Number's employee portal, where you can also freeze or dispute your data. A secondary source says the report is free at least once every 12 months under 15 U.S.C. § 1681j. The report also shows who requested your data in the past 24 months. Turnaround time is not established, so request it before you need it.

The page can show five titles. The report shows one. Every other title needs its own paper.

The procedure: from records to a clean parse and a matched record

Follow these seven steps in order. Each one has a test for when it is done, and the parse test and the LinkedIn check are the two that catch most problems. Expect about a day to gather the records and under two hours for the rest.

One-employer title stack, records to submission

  1. Pull the records
    Request your Employment Data Report and gather every offer letter, promotion letter, transfer notice, and retitle memo. Done when each title has a record next to it, or a gap marked "none".
  2. Build a title ledger
    Write one row per title with the working title, payroll title, start and end month, and whether scope changed. Done when every date boundary is accounted for.
  3. Mark each change stack, split, or fold
    Stack a new level in the same scope, split a new team or new duties, and fold a no-scope retitle or a very short title. Done when every row has exactly one call.
  4. Write the entry
    Put the employer and overall range on the company line, then each surviving title on its own line with its own dates and the employer name repeated. Done when no title line lacks dates.
  5. Run a parse test
    Upload to a test portal or a text-extraction checker and compare the extracted rows with the ledger. Done when the row count equals your stacked plus split titles and every row has dates and an employer.
  6. Update LinkedIn
    Link every position to the same company page and keep each gap at one month or less. Done when one company block shows with tenure calculated automatically.
  7. Disclose before the check runs
    Tell the recruiter in writing about any gap between working title and payroll title, and upload records to the screening portal early. Done when the note is sent and the documents are on file.

Some sources repeat the company name on every title line and some don't. I repeat it on every line, stacked titles included. It costs a few words and protects against the parser that would otherwise create a second, nameless employer. Here is the example's final entry.

Final entry, five titles carried to four dated lines
[EMPLOYER] | [City] | Jan Y1 - Dec Y8

Customer Operations Manager (Acting Director, Customer Operations) | [EMPLOYER] | Oct Y7 - Dec Y8
- [Result from the acting period, with the scope you held]

Program Lead, Platform (titled Program Manager before a company-wide retitle) | [EMPLOYER] | Jul Y4 - Sep Y7
- [Result from the Platform team]

Senior Operations Analyst | [EMPLOYER] | Jan Y3 - Jun Y4
- [Result that shows the new level]

Operations Analyst | [EMPLOYER] | Jan Y1 - Dec Y2
- [Result from the starting role]

Replace the bracketed parts and the Y-dates with your own; keep a date range and the employer name on every title line.

The parse test in the example. With draft one, the extraction came back as one row. With the final entry, it should come back as four rows, each with a date range and the employer, matching the two stacked and two split lines in the ledger. If a row comes back without an employer, the company name is missing from that line. If two titles merge, a date range is missing or in a format the parser doesn't read. Fix the line and run the test again. A clean result in one portal doesn't guarantee a clean result in all of them, because parsers differ. The test proves the structure, not every ATS.

LinkedIn in the example. The Platform position had been entered with the company typed as free text, so it showed no logo and broke off as a separate employer. Relinking it to the company page fixed that. The Aug Y7 end date became Sep Y7 to match the transfer notice, which closed the gap to one month. The profile then showed one company block with four positions.

If you build resumes with Refolk, give it the ledger rather than the old draft. Every version it tailors to a posting then starts from the same four title lines and dates, and the only thing that changes between applications is the bullets.

How this goes wrong: failure modes and false positives

Most failures come from one of two mismatches: the page says one thing and a machine reads another, or the page says one thing and the record says another. Each failure below includes what it looks like and the check that catches it.

  1. Stacked titles with no dates on the title lines. The parser returns one row and the later titles become bullet text. A person reading it sees a clean stack, but the portal pre-fills a single role. Check: the extracted row count matches the ledger.
  2. Company typed as free text on LinkedIn. The positions show as separate employers, so a promotion looks like a job change. Check: every position shows the same logo and links to the same page.
  3. A gap of more than one month at a team move. For example, a transfer that ends in March and starts in May. LinkedIn splits the block, and nothing about the roles themselves has changed. Check: line the dates up against the transfer notice.
  4. Working title on the screening form. The verifier returns the payroll title, and the screener matches it against the form, not the resume. Check: compare the job title on your Employment Data Report with the form before you submit.
  5. Offering only an offer letter as proof. It can be rejected in favour of W-2s, which carry no title at all. Check: also have pay stubs showing the role, or an HR letter on letterhead.
  6. A retitle listed as a promotion. This breaks the never-tweak-upward rule, and the inflated title won't match payroll. Check: is there a promotion letter? If not, fold the title.
  7. An acting role listed as a permanent title. "Acting" is concentrated in federal agencies, and the US index holds 2.28x as many Interim titles, so readers know what the label means. Check: does the payroll record show the base title? If so, it goes first.
  8. Trusting raw counts, including mine. The Refolk index counts above include off-target titles, with an exact-title share of 48% to 76% per sample. Check: read them as direction, not precision.

There are also two false alarms. A verification report showing only your current title is not an error. The report has no title-history field, so a missing history tells you nothing. And a parser reading your stack as separate jobs at the same company isn't a failure as long as each row has the right employer and dates. The founder's own description says parsers vary on this.

Keeping the entry current

Treat the ledger as the source and the resume as its output. Every new title, transfer, or reorganization goes into the ledger first, gets a stack, split, or fold call, and then flows to the page, the profile, and your disclosure note. Pull your Employment Data Report again before any final-stage process, and check which employers have requested it in the past 24 months.

Send this note at the offer stage, before the screening form goes out, whenever a working title differs from payroll.

Title disclosure note to the recruiter
Hi [Name],

Before the background check runs, one note on titles at [EMPLOYER].

My payroll title is [payroll title]. My resume shows [working title] from [start] to [end] because [I served as acting director under a written assignment / a company-wide retitle renamed the role].

I've attached [the assignment memo / HR letter / pay stub showing the role] and uploaded the same documents to the screening portal. On the screening form I've used the payroll title so it matches the employer's record.

Happy to walk through any of it.

[Your name]

Send in writing before the screening form goes out; attach the same records you upload to the screening portal.

When you score a posting against your history in Refolk, use the ledger version of your history. A fit score built on an inflated title will mislead you too.

Before you send the entry anywhere

  • Every title in the ledger has a record beside it, or a gap marked "none" with a plan to close it
  • Every change is marked stack, split, or fold, and no retitle is shown as a promotion
  • Every title line on the resume has its own date range and repeats the employer name
  • The test upload returned one row per stacked or split title, each with dates and the employer
  • On LinkedIn, every position links to the same company page and each gap is one month or less
  • The original and most recent hire dates on the Employment Data Report match your first start date
  • The screening form shows the payroll title, and the disclosure note and records are sent

Questions job seekers ask

How do I list promotions at the same company on a resume so the ATS reads them?

Give every title its own line with its own start and end dates, and repeat the employer name on each line. Practitioners report that older parsers attach only the first role's dates to the company header and merge later titles into the bullet text when title lines have no dates. No ATS vendor documents this behaviour, so upload the file to a test portal and count the rows that come back before you send it anywhere real.

My resume title is different from my HR title. Will the background check flag it?

It can. Payroll-fed verification returns the payroll title, and one reproduced screening guideline counts a title that is not equivalent to the applicant's as a minor discrepancy. Put the payroll title on the screening form, show the working title on the resume only where a record supports it, and tell the recruiter in writing before the check runs. Have pay stubs or an HR letter ready, because offer letters alone have been rejected.

How do I show an internal transfer on a resume?

Treat a move to a new team or new duties as a split: a separate title line under the same employer, with its own dates and the employer name repeated. Line the dates up against the transfer notice so the old role ends the month before the new one starts. That keeps the parser reading two roles and keeps LinkedIn grouping them, since LinkedIn only groups positions that start within one month of the previous end.

How should I list a company-wide title change on my resume?

Fold it. Use the newest title over the full date range and note the old title in parentheses or one bullet, especially if your references know you by it. Don't present a reorganization rename as a promotion. One master resume writer's rule is 'don't give yourself a promotion', and the inflated title won't match payroll. If you have no promotion letter for the change, it wasn't a promotion.

Why won't LinkedIn group my positions under one company?

There are two usual reasons. One position is linked to free text or a different company page instead of the same page, or the gap between one end date and the next start date is more than one month. LinkedIn has no manual group or ungroup switch, so you fix it by changing the company link or the dates. How grouping behaves after an acquisition is not documented.

Should I put 'Acting Director' as my job title?

Only in parentheses next to your base title. 'Acting' means temporary, and verification will return the base payroll title, so a title line that reads 'Acting Director' alone looks like a permanent title the record won't support. Write the payroll title first, then the acting role and its months, and keep the memo that assigned it with your records.

Put this to work

Paste your career in once. Every application after that is written for you.

Drop a resume or a LinkedIn URL. I rank the live openings against it, rewrite the resume and write a cover letter for the best of them, and fill in the employer's form when you press the button. You read, you decide what goes out.

  1. 01Drop your resume

    A PDF or a LinkedIn URL. About a minute, once.

  2. 02I rank the openings

    Every weekday morning, the live catalog scored against your history. Up to 20 worth your time, not two hundred links.

  3. 03Each one is written up

    Resume rewritten for the posting, a cover letter, a fit score. Press send, or let me fill in the form.

  • New matches ranked and written before you are up.
  • Every bullet stays inside what your history supports. Nothing invented.
  • Queued, submitted, interviewing, offer: one screen, not a spreadsheet.

Free, no card. Up to 25 applications sent a week, and nothing is sent until you say so.

Read next