8 min read
Your PDF looks fine in Preview. iCIMS shows your MBA under your last employer or dumps every skill into one job. That's not a mystery rejection. It's a section boundary the importer couldn't see.
Check your resume for free on the same file you'll attach. If the checker flags columns or odd headers, the iCIMS preview will probably mash blocks the same way.
You're not here for a full upload tutorial. You're here because the preview lied about where your sections start and stop. We'll name the symptom, test each field line, and match fixes to the layout mistake that caused it.
And no, adding keywords won't un-merge a wall of text. Separators and boring headers do that work.
Quick Wins
- Label sections Professional Experience, Education, Skills, and Certifications on plain lines.
- Insert one blank line before and after every section header.
- Re-upload and confirm each preview field holds only that section's content.
What merged sections look like in the iCIMS preview
After upload, iCIMS maps your file into profile fields recruiters skim: employers, titles, schools, skills. When parsing fails at a section edge, content bleeds across fields. You might see degree lines inside an experience row, or certifications listed as job duties.
The preview is the truth test, not the Word thumbnail. If Education imported under Company B, recruiters sorting by school name won't find your credential where they expect it.
Symptom one: the last job block never ends. Bullets from a volunteer role or a bootcamp project attach to paid work because no header broke the stream.
Symptom two: Skills disappear as a list and reappear as comma soup inside one employer. That happens when a sidebar or table put tools beside jobs instead of below them.
Symptom three: contact details ride along with job one. Icons and text boxes in the margin often import before the first header, so your email becomes part of a title line.
Symptom four: Certifications vanish as their own field and show up as bullets under the wrong employer. That usually means the Certifications header used the same style as a job title line.
Before: You assume silence means weak fit.
After: You assume the preview mis-labeled a section until you prove each field boundary is clean.
Broader upload habits live in iCIMS resume upload issues for US formatting . This page stays on the merge symptom and the boundary checklist only.
Run the preview-field boundary test
Upload the resume to iCIMS or any parser preview you trust. Scroll field by field. For each block, ask whether the text belongs only there.
Experience boundary: The first line after Professional Experience should be an employer or title, not a school name or a skill keyword list. The section should end before Education or Skills headers appear in that field.
Education boundary: School names and degrees stay together. No job bullets should appear between them unless you intentionally listed a student job under Experience with its own dates.
Skills boundary: Tools and languages live in Skills or inside relevant job bullets, not both at once in the same preview row. If Skills is empty while Experience reads like a tag cloud, the parser merged layout columns.
Mark failures on paper: Experience swallowed Education, Skills merged into job two, contact info in title field. Each mark maps to a layout fix below.
Copy-paste header block (edit to your truth):
Professional Experience
[Employer] | [Title] | [Month Year] – Present
• [Bullet with tool the posting names]
Education
[University] | [Degree] | [Month Year]
Skills
[Tool], [Tool], [Tool]
Certifications
[Cert name] | [Issuer] | [Year]
Illustration lines above are fictional resume samples, not hiring outcome claims. Keep your real employers and dates honest.
Cause A, missing blank line: headers touch body text. Fix by inserting one empty line above and below each header, then re-export.
Cause B, two columns or tables: collapse to one column, move sidebar contact lines under your name at the top, and delete text boxes.
Cause C, decorative rules: horizontal lines from templates sometimes read as body text. Replace them with blank lines only.
Cause D, nonstandard headers: rename My Path to Education before you run the test again.
Cause E, scanned or image PDFs: if you cannot highlight a word in the file, iCIMS may dump everything into one text box. Rebuild from the DOCX source instead of printing to PDF.
I've opened iCIMS profiles where the preview showed one long Experience paragraph; I stopped reading because the degree was buried mid-block and I couldn't sort by school.
Before: You edit bullets while preview still merges headers.
After: You pass the boundary test, then tune bullets for the req.
iCIMS parsing: keep sections from merging (US) field checklist
Use this table after every template change. One font swap can break a boundary you fixed yesterday.
| Preview field | Pass | Fail sign |
|---|---|---|
| Experience | Jobs with dates, no degree lines | School or cert text inside a job row |
| Education | Schools grouped, no job bullets | Employer names under Education |
| Skills | List or short comma line in Skills only | Skills only appear inside one job block |
| Contact | Email and phone in contact area | Phone merged into first job title |
Layout habits that break boundaries include Canva exports, resume templates with shaded bands, and triple-column skill grids. Stick to 11-point Calibri or Arial on a single column when iCIMS is in the stack.
Before: You trust the PDF because it printed cleanly.
After: You trust only the preview fields that passed every row in the table.
When merges persist on a plain file, compare with resume formatting errors that break ATS parsing for export settings that strip hidden tables.
Check layout before you apply again
Run tools on the file the portal will ingest. Section merges are layout problems first; keyword tweaks come after boundaries pass.
Run the ATS check for column risk, header labels, and export issues that show up before iCIMS does.
Score your job match once Experience and Skills import into separate fields so tools from the posting land where recruiters search.
Stop applying on a merged preview
iCIMS parsing only keeps sections from merging when your file gives the importer clean edges. Standard headers, blank lines, and a single column are boring on purpose.
Run the boundary test, fix the cause that matches your symptom, and re-upload until each preview field holds the right content. Then tailor bullets for the req.
This won't fix applying to roles you're not qualified for. It stops a qualified file from looking like one messy job history.
Save a version named with the company after preview passes. You'll know which file cleared the merge check.
If you need a short note after layout is clean, generate a cover letter that explains a pivot the title row cannot show.
Read more
Frequently asked questions
The parser lost the boundary between sections because headers were styled like body text, columns split the page, or a decorative line sat where a blank line should be. Put Education on its own line, add a blank line above and below, switch to single column, then re-upload and confirm the preview lists school names under Education only.
Two columns often flatten left-to-right, so Skills beside Experience can import as one continuous block. A sidebar with contact icons can also pull phone numbers into the first job row. Collapse to one column before you treat the file as ready.
Custom titles like My Journey or Where I Grew replace the standard labels parsers hunt for. Without a recognizable Professional Experience or Education line, the importer guesses and often glues the next paragraph to the prior section. Rename headers to the four US defaults unless the posting asks for a CV with publications.
Fix the source file first. Hand-typing jobs into iCIMS fields helps one application but does not travel when you attach the same PDF elsewhere. When the preview is wrong, treat the resume as broken until export and headers pass the boundary test again.