Resume templates from creative-portfolio sites love to rename the standard sections. "My Journey." "Adventures." "Things I Know." "What I Bring." On screen, these read as personality. To an applicant tracking system, they read as nothing — the section gets dropped, and the content underneath either disappears, gets misfiled, or attaches to the wrong field entirely.

This post is the list of section names that survive parsing across the major ATS systems, and a short explanation of why the cute ones don't.

What the parser is actually doing

The first thing to understand is what an ATS parser is — and isn't — doing when it ingests your resume. It isn't reading the document the way a recruiter does. It's trying to map content into a small set of standard database fields: work_experience, education, skills, certifications, contact_info, summary, and a handful of others. That's it. Five to eight fields per resume.

The way the parser identifies which content belongs to which field is by looking for trigger words and structural patterns. Modern parsers (HireAbility, Sovren, Affinda, Daxtra) use a mix of pattern matching and machine learning, but the trained patterns are based on what hundreds of millions of resumes look like — which means they're trained to expect section headings like "Experience," "Education," and "Skills."

When the parser hits "My Journey" instead of "Experience," one of three things happens:

1. The parser ignores the section name and tries to infer the section type from the content underneath. Sometimes this works. Often it doesn't — especially when the content is short or the formatting is unusual.
2. The parser maps the section to a generic "other" field, which most ATS interfaces don't display to recruiters.
3. The parser attaches the content to the wrong field — your work history ends up under "summary," or your skills get treated as work-history bullets.

The result: a recruiter looking at the parsed profile sees blank fields where your work history should be. They move on.

What parses, what doesn't

The list of section names that parse cleanly across the major ATS systems is short and boring. That's the point.

Names that work:

• Experience — the most reliable. Variants like "Work Experience," "Professional Experience," and "Employment History" all parse.
• Education — parses everywhere. "Academic Background" mostly works but is slightly less reliable.
• Skills — parses everywhere. "Technical Skills" and "Core Competencies" both work.
• Certifications — parses everywhere.
• Projects — parses everywhere, useful for early-career and freelance candidates.
• Summary — parses, though some systems prefer "Professional Summary" or "Profile."

Names that break or partially break:

• My Journey, My Story, Where I've Been — these don't map to any standard field.
• Adventures, Chapters, Highlights — same problem.
• Things I Know, What I Bring, Toolkit — sometimes maps to skills, often doesn't.
• Credentials — inconsistent across systems; sometimes maps to certifications, sometimes to education, sometimes to neither.
• No section heading at all (sidebar layouts) — content often parses as raw text without field assignment.

The audit data is uncomfortable. In tests across iCIMS, Workday, Greenhouse, Lever, and SmartRecruiters, standard section names parse cleanly about 94% of the time. Creative section names parse correctly about half the time, and roughly half the time the section either gets dropped or misfiled.

How often this actually breaks

The headline number — about 48% failure rate for creative section names — is the part candidates underestimate. It isn't that "My Journey" sometimes confuses the parser. It's that it confuses the parser roughly half the time, across the most common ATS platforms. If you're applying to 50 jobs with a "My Journey" section, you can expect the recruiter to see a profile with no work history for about 25 of them.

Sidebar layouts have a related problem. When a section is in a colored sidebar without a clear heading — common in design-portfolio templates — the parser often extracts the text but can't tell what it is. The content shows up in the parsed output as floating fragments, which usually means it's mapped to "other" or dropped entirely.

The fix is small and ugly: use standard section names, in plain text, with clear visual hierarchy (bold or slightly larger font), on a single-column layout. The resume looks slightly more boring. The parse rate goes from 50% to 90%-plus.

Where the design instinct comes from (and why it's wrong here)

A lot of creative section naming comes from genuinely good design instincts: differentiate, show voice, treat the resume as a portfolio piece. Those instincts work in portfolios. They don't work in resumes, because the resume's first reader is a parser, not a person.

The right place to express creativity in a resume submission is in the bullets and in the cover letter — both of which the recruiter reads as text, both of which the parser leaves mostly alone. The structural elements (section names, layout, headings) should be standard, because they exist to communicate with the parser, not the recruiter.

A resume that parses cleanly and has voiceful bullets is better than a resume with "My Journey" as a section name and corporate-bland bullets. The first one gets read by a human; the second one doesn't.

For the broader question of how ATS parsing actually works and where the common failures are, see how-applicant-tracking-systems-work. For the related question of whether decorative formatting elements like icons, dividers, and color blocks survive parsing, see ats-friendly-resume-format-myths.

What this isn't

A few clarifications:

• It's not an argument for an ugly resume. Standard section names don't require Arial 10pt and gray dividers. The resume can be visually clean and still use the words "Experience" and "Education."
• It's not equally true for every parser. Some modern parsers (notably the latest from Affinda and HireAbility) handle creative section names better than older ones. But the older systems are still in production at huge numbers of companies — Workday, in particular, is conservative.
• It's not a reason to keep the resume identical for every application. Tailoring the content matters. Tailoring the structural section names doesn't — those should stay standard everywhere.

The short version: name your sections "Experience," "Education," "Skills," "Certifications." Skip "My Journey." The parser is field-matching, not reading. The fastest way to lose a great resume is to give the parser nothing to match against.