12 min read
Your resume looks perfect in Word. You upload to Workday or Greenhouse. The preview shows job titles glued to end dates, or two roles collapsed into one row. You're not imagining it, and you don't need a new template pack. The importer stored a mashup because it read columns out of order.
Recruiters search Experience by title and date range. When those fields merge, keyword hits land on the wrong employer and timeline filters skip you. It's frustrating, but it's usually fixable in an afternoon if you'll flatten layout instead of tweaking fonts.
Before you rewrite bullets, check your resume for free on the same export you'll upload. You're hunting layout warnings, not a vanity score.
This page walks the symptom, two root causes that cover most merged-line previews, how to tell which one is yours, and the flatten fix for each. You don't need a new career story. You need a single-column timeline parsers can read.
After dates sit on clean rows, generate a cover letter that repeats the same Month Year strings so the attachment and profile never disagree.
Quick Wins
- Paste the export into Notepad and read title and date order.
- Open the employer preview pane when the portal offers one.
- Move dates out of right columns into the employer line.
- Type the same date strings into split portal date boxes.
The symptom: titles and dates become one unreadable string
The preview is the truth test. PDF viewers lie because they preserve your design. Applicant tracking previews show what the database stored. When you see Senior Product Manager January 2019 December 2021 on one line, the parser treated title text and date text as a single field.
Recruiters sorting by recent title may never open your attachment. They read the row. Merged lines make it look like you held one vague role for a decade or jumped employers without dates. Neither story helps you.
Why ATS merges job titles and dates feels random until you map layout. Importers are dumb readers. They do not understand that your Canva sidebar is dates. They read cells in file order and write whatever string results.
Silence after upload sometimes traces back here. Not because keywords failed. Because Experience imported with scrambled timelines and recruiter date filters excluded your row.
Design tools and resume builders love side columns because they look modern on screen. Parsers do not share that taste. They read the file like a teletype. When your eye sees a tidy grid, the database sees one long string with dates in the middle of a title.
International candidates using CV layouts with narrow date gutters hit the same bug in US portals. The fix is the same: one column, employer block, title with dates on one line, bullets underneath. Save the creative layout for a human-only networking PDF if you still want one.
For broader parser failures beyond merged lines, read why ATS filters out most applicants . Import health comes before keyword tuning.
Two causes, how to tell which is yours, and the flatten fix
Cause 1: Column or table layout splits title from dates
How to tell: plain-text paste shows dates in a block on the right while titles stack on the left, or dates appear before employer names. The preview mirrors the same glue.
Before: Two-column Word template. Title in column one, Month Year range in column two. Employer name centered above a table row.
After: Single column. Line one: Employer Name, City. Line two: Job Title, January 2019 to December 2021. Bullets below on plain rows.
The fix: remove layout tables from Experience. Use bold employer lines and regular title lines if you need visual hierarchy. Parsers read paragraphs more predictably than invisible grids.
Sidebar skills tables cause the same reorder when they sit beside Experience. Move skills into bullets or a simple list below jobs, not beside them in a shared table row.
Canva and similar exports often wrap each job in a nested table. Word may not show gridlines, but the XML still marks columns. Convert to plain paragraphs before you upload to Taleo or iCIMS. If you must keep a visual line under the employer name, use a bottom border on a paragraph, not a table row.
Text boxes floating over the margin are another hidden column. They parse after body text or merge with the nearest cell. Pull floating objects into the main flow or delete them.
Cause 2: Split date fields inside the document or form
How to tell: you used separate cells or tabs for start month, start year, end month, and end year. Plain text shows fragmented numbers with title words inserted between them.
Before: Tabbed columns: Jan | 2019 | Dec | 2021 beside Analyst on the same row.
After: One string on the title line: Business Analyst, January 2019 to December 2021. Portal work history forms get the same string typed into start and end boxes when split fields are required.
The fix: never rely on micro-columns for dates in the file. Consolidate to Month Year to Month Year on the employer block. Then mirror exactly in Greenhouse or Workday manual fields so attachment and profile agree.
Some templates put start date on the line above the title and end date below the bullets. Parsers attach both dates to the title field or drop the lower date entirely. Keep the full range on the title line every time.
When the portal offers separate start and end pickers, type the same Month Year strings you used in the file. Do not switch to numeric-only formats in the form if the resume says January 2019. Mismatches trigger audits and slow approvals.
How to tell which cause is yours in five minutes
Run a plain-text paste. If titles and dates alternate line by line from two columns, you have Cause 1. If you see broken month and year fragments around a title, you have Cause 2. Some files show both; fix column layout first, then merge date strings.
I've reviewed Greenhouse previews where the PDF looked crisp and the stored title field read Director of Operations March 2020 because dates lived in a right-aligned table. Flattening fixed search visibility faster than keyword edits.
Copy-paste block: merged title and date diagnostic
1. Export the upload file (PDF or DOCX)
2. Paste into Notepad: titles before dates on each job? Y / N
3. Any right-column or table layout in Experience? Y / N
4. Split month/year micro-columns in the file? Y / N
5. Portal preview: title and date on separate stored fields? Y / N
6. Form start/end boxes match resume strings? Y / N
Cause 1 (column/table): flatten to single column
Cause 2 (split dates): one Month Year to Month Year string per role
Edge case: multiple roles at one employer. Use repeated employer headers with distinct title lines and date ranges. Do not stack two titles on one line to save space. Parsers merge them the same way they merge titles with dates.
Edge case: current role with Present or Current. Spell it the same way in the file and in portal end-date fields. Some systems treat an empty end date as error and attach the next job's title to your current line.
Edge case: contract roles listed beside full-time jobs. Label contract or consulting in the employer line so parsers do not merge adjacent date ranges from two engagements at one client.
After you flatten, rerun the plain-text paste and screenshot the preview. Store both in a folder per req. If a recruiter questions timeline later, you have evidence of what you submitted on day one.
Bullets should stay under the correct employer block after flattening. If a bullet imports above the title line, add a blank line between jobs or remove extra paragraph spacing tricks that confuse reading order.
Google Docs exports sometimes insert soft breaks that look like new lines but parse as spaces. Turn on show formatting marks, delete stray breaks at the end of title lines, and export again.
For month formatting rules recruiters expect, see month-year vs year-only on resume dates . Consistent Month Year strings reduce merge risk in form imports.
Related merge patterns on specific ATS builds are covered in why ATS merges your job titles and dates into one line . Same mechanics, more employer-specific examples.
Fixes that make merged lines worse
Panic edits after a bad preview often create duplicate timelines. Slow down and fix the source file once.
Mistake: Hiding dates in a header or footer. Many importers skip headers entirely. Dates vanish or attach to the wrong section. Keep dates on the employer line in the body.
Mistake: Shrinking font in a side column to fit dates. Smaller text still parses in column order. The merge remains. Widen to one column instead.
Mistake: Editing only the preview without re-exporting. Recruiters may open the attachment later and see a different timeline than the stored row. Fix the file, upload once, verify again.
Before: Five re-uploads of the same two-column template with tweaked margins.
After: One single-column export, preview confirmed, single submission per req.
Mistake: Using icons or pipes as date separators. Decorative separators become part of the stored title string. Use commas and the word to between Month Year values.
Mistake: Bolding only the title while dates stay light gray. Color and weight do not guide parsers. Position on the page guides them. Put dates next to the title in the same paragraph style.
Mistake: Assuming the recruiter will read the PDF. Many teams disposition from the profile row during first pass. If the row is wrong, the PDF never opens.
This will not fix applying with a scanned image PDF. Camera uploads fail parsing entirely. Use a text-based export from Word or Google Docs saved properly.
And if your file parses but scores low on keywords after flattening, read why your resume looks fine but ATS scores it low . Layout and wording are separate passes.
Verify layout before the next upload
Run your export through HireFlow's free ATS resume checker and fix column warnings before you touch keywords. Merged title and date lines show up as out-of-order Experience in the readout.
Match the posting language with score your job match after dates sit on clean rows so must-have terms attach to the right employer in search.
Do this now: Plain-text paste, identify Cause 1 or 2, flatten, mirror dates in portal fields, upload once.
What to do now
Why ATS merges job titles and dates comes down to column layout or split date fields. Diagnose with plain text, flatten the file, align portal forms, and upload a single clean export per req.
- Paste tonight and label Cause 1 or 2.
- Rebuild Experience as single-column rows.
- Put Month Year ranges on the title line.
- Mirror strings in split date form boxes.
- Confirm the preview before you submit.
Open the application again. Run a free ATS check , fix merged lines, and send one verified upload.
Merged titles and dates are boring problems with boring fixes. That is good news. You do not need a paid template. You need one column, honest Month Year strings, and a preview that matches your source file before you hit Submit again.
If a friend shares a designer resume that imports cleanly, ask what export settings they used. Often the answer is a plain Word file with no tables, not a secret ATS hack.
Track which cause you fixed in a one-line note on your phone: column layout or split dates. The next time a preview glues fields, you will know which flatten pass to run first instead of guessing.
Set a calendar reminder to recheck the preview if the req stays open for weeks. Some portals re-parse attachments after profile edits, and a late merge is easier to catch when you still have the source file open.
Read more
Frequently asked questions
Importers read left to right, then top to bottom. When your title sits in a left column and dates sit in a right column, the parser often concatenates both cells into one Experience field. The preview then shows something like Senior Analyst March 2021 instead of separate title and date rows. Flatten to one column with dates on the same line as the employer, not in a side column.
Portal forms with separate start month, start year, end month, and end year boxes are safer for storage when you type them manually. On the resume file itself, split micro-columns for month and year still scramble in many parsers. Use one Month Year to Month Year string on the employer line in the document, then mirror the same strings in form fields.
Tables are a common trigger, not a guaranteed failure. A single invisible table wrapping the whole page may parse fine while a two-column experience table will not. Test with a plain-text paste. If dates appear before titles or titles from two jobs glue together, rebuild without layout tables.
Fix the source file, export again, and upload once on a fresh application when the portal allows it. Editing only the preview boxes without fixing the attachment leaves two conflicting timelines in the database. Recruiters searching by date range miss you when stored dates attach to the wrong title string.
Format matters less than layout. A designed PDF from a two-column template fails the same way a DOCX table fails. Follow the posting format, then flatten columns. Export from Word as a simple single-column file before you convert to PDF if the portal wants PDF.