iCIMS Resume Parsing: Eliminating Table Drops, Header Blindness & Profile Mapping Errors

How iCIMS builds your candidate profile

iCIMS is one of the most widely used applicant tracking platforms in North America, common at mid-size and large employers in healthcare, retail, financial services, manufacturing and staffing. Its career portals usually start by asking for your email address, then offer to upload a resume. The parser reads the file and fills a candidate profile: name, phone, email, address, a list of work history entries with titles, employers and dates, education, and in some configurations skills.

You are then asked to review the parsed information and answer job-specific questions. Recruiters see the structured profile in search results and lists, and can open the attached resume. A profile with a blank phone field, a job title sitting in the employer field, or two roles merged into one makes a weak first impression before anyone reads your actual file.

Because iCIMS profiles are kept and reused, a mapping error does not just affect one application. It can sit in the employer's talent pool and show up every time a recruiter searches for candidates like you.

Table drops: why grid layouts lose content

Tables are popular in resume templates because they line things up neatly: skills in three columns, dates in a right-hand column, a two-column header with contact details on one side and a summary on the other. Parsers do not see that alignment. They read cell content in a fixed order, often row by row, sometimes column by column, and some skip tables altogether. Tables and text boxes are a common source of dropped or reordered content across many parsing engines.

The typical damage:

• Dates in a separate column get detached from their roles, so work history entries arrive with no dates or with the wrong ones.
• Skills grids come through as a jumble, or not at all, so a skills search for "Epic" or "Salesforce" misses you.
• Two-column headers split your name from your contact details, or merge your summary into the address field.
• Nested tables inside a template, often invisible because the borders are hidden, can drop whole sections.

To check for hidden tables in Word, turn on gridlines from the Table Layout menu. If dashed lines appear around your content, the template is built on a table. Rebuild those sections as plain paragraphs, using tab stops if you want dates aligned to the right margin.

For skills, a simple pattern works on every parser: a heading, then two to four lines that each start with a short label and a colon, followed by comma-separated terms. For example, "Clinical systems: Epic, Pyxis, Omnicell" on one line and "Certifications: BLS, ACLS, PALS" on the next. It reads cleanly to a recruiter scanning the page, extracts in order, and keeps related terms together so a keyword search finds them.

Header blindness: the contact details nobody sees

Many resume templates put your name, phone and email in the Word header, the area at the top of the page that repeats on every page. It looks clean, and it saves space. The problem is that some parsers skip headers and footers entirely, reading only the body of the document.

When that happens on iCIMS, the profile may still have your email because you typed it to start the application, but your phone number, city and LinkedIn URL can be missing. In some cases the parser then grabs the first name-like text it finds in the body, which might be a former employer or a school, and puts it in the name field. Recruiters calling down a list skip profiles with no phone number.

The fix is simple: put your name and contact lines as the first lines of the document body. You can style them to look like a header, with a larger name and a rule beneath. Keep page numbers or a short name line in the footer of page two if you like; nothing a parser needs should live there.

The same applies to icons. Template phone, envelope and pin icons are images or symbol-font characters. They carry no meaning for a parser and can arrive as stray characters next to your number. Plain labels, or no labels at all, work better: a phone number and an email address are recognizable on their own.

Profile mapping errors and what causes them

Mapping errors happen when the parser finds the right text but puts it in the wrong field. The most common examples recruiters report on iCIMS profiles:

• Title and employer swapped. Usually caused by mixing orders: some roles listed title first, others employer first.
• Company description read as a title. A line such as "Regional home health agency, 14 locations" under the employer name gets mapped as the job title.
• Two roles merged. A promotion written as "Charge Nurse / Staff Nurse, 2018 - 2024" becomes one entry with one title.
• Locations in the title field. "Operations Manager - Dallas" can come through as the full title, which then fails a title search for "Operations Manager".
• Current role not marked current. End dates written as "Now" or "Ongoing" may not be recognized.

Every one of these comes from inconsistency or extra text on the role line. Choose a pattern, such as Title on line one and Employer, City, State, MM/YYYY - Present on line two, and use it for every role without exception. Put company descriptions in the first bullet or in italics on a separate line below the dates, and spell current roles as "Present".

Search and rediscovery in the iCIMS talent pool

Employers using iCIMS keep a searchable pool of past applicants. Recruiters search that pool by keyword, title, location and other profile fields, and iCIMS sells AI-assisted matching features that some employers enable to suggest candidates for open roles. How those features weigh your profile is configured by the employer and not visible to you.

What you control is whether the profile says what you want it to say. Accurate titles in the title field, accurate dates, and the right terms in your work history all make it more likely that you surface for the next role, not just the one you applied for. For roles where recruiters search by license or certification, such as registered nurses, write the credential, its state where relevant, and its full name: "Registered Nurse (RN), Texas", "Basic Life Support (BLS)". For client-facing roles such as customer success managers and sales executives, name the CRM and the segment you sold or served into.

Building a parse-safe master resume

Use this checklist on your master resume before applying through any iCIMS portal:

1. Name and contact details in the first lines of the body, not the header.
2. No tables, text boxes or columns anywhere, including hidden ones in the template.
3. Standard headings: Summary, Experience, Education, Certifications, Skills.
4. One role pattern used for every entry, with each title on its own line and its own month/year dates.
5. Company descriptions moved out of the role line.
6. Simple bullets and a standard font.
7. Saved as .docx or exported as a text-selectable PDF.

Then check it with the ATS compatibility calculator. If you also apply through Workday, the same structure fixes the date and history problems covered in our Workday parsing guide.

Reviewing the profile before you submit

Even with a clean resume, give the parsed profile a careful pass. Check that your phone number, city and state are filled in. Count the work history entries against your resume. Confirm each title is in the title field and each employer in the employer field. Check that your current role shows as current. Then read the job-specific questions slowly; employers can configure questions that screen applicants out, such as license status, shift availability or work authorization, and your answers should line up with what the resume shows.

If you have applied to the same employer before, your earlier profile may load automatically. Replace the old resume with your current one and re-check the fields; an outdated title or missing recent role in a reused profile is easy to miss and costly when a recruiter compares you with other candidates.

When to get the structure rebuilt

If your current resume came from a template with tables, header contact blocks or columns, fixing it piece by piece often takes longer than rebuilding it. Our writers build every resume single-column with consistent role entries and body-text contact details, and the Complete Career Arsenal includes an ATS-checked .docx and a text-selectable PDF. See Professional resume writing, or browse sample resumes to see the structure.

Key takeaways

• iCIMS parses your resume into a stored profile that recruiters search and reuse, so mapping errors follow you into future searches.
• Tables, including hidden ones in templates, are a common cause of dropped dates, skills and sections.
• Put your name and contact details in the body of the page; many parsers skip the Word header.
• Use one role pattern for every entry and keep company descriptions off the title line to prevent field swaps.

Frequently asked questions