What to Name Your Resume Sections

Use the plain, expected name for every standard section: Summary, Experience, Education, Skills. A section heading is navigation, not writing — its only job is to tell a reader where they are on the page in about half a second. Save invented names for sections that genuinely have no standard name, and even then, describe the contents rather than perform.

The default names

These are understood by everyone, everywhere, without a pause:

  • Summary — the short paragraph at the top.
  • Experience — your dated jobs.
  • Education — degrees, schools, years.
  • Skills — the grouped list.
  • Certifications — credentials an outside body assessed.
  • Projects — work you can point to.
  • Volunteer Experience — unpaid work.

There is a second reason to keep these boring. Applicant tracking systems — the software employers use to receive and search applications — recognize standard headings and use them to decide which block of text is your work history. A heading the software doesn’t recognize can leave a whole section unfiled. How ATS works and how to be machine-readable covers what that does to your application.

The naming decisions that change something

“Experience” vs “Work Experience” vs “Professional Experience.” All three are fine. Shorter is better, and consistency matters more than the choice: pick one and don’t use a second variant elsewhere on the page. “Professional Work Experience History” is four words doing one word’s job.

Splitting experience into two named buckets. “Relevant Experience” followed by “Additional Experience” lets you put the roles that match this job first without pretending the others don’t exist. Two rules if you do it: keep every date exactly as it is, so no reader thinks time is missing, and make sure the second heading doesn’t read as an apology. “Additional Experience” is neutral. “Other Jobs” is not.

“Summary” vs “Objective” vs “Profile.” Use Summary. An objective describes what you want, which is not what the reader is scanning for, and Profile is vague enough that some readers skip it. How to write a resume summary that earns its space covers what goes under the heading.

“Skills” vs “Core Competencies” vs “Areas of Expertise.” Use Skills. The longer alternatives are template language, and they set up an expectation of depth that a comma-separated list can’t meet. If you need to split the list, split it by kind — “Skills” with labelled groups inside — as described in build a skills section worth reading.

Anything you want to call “Accomplishments.” Be careful here. A separate accomplishments section usually means your bullets under each job are weak, and the fix is to move the accomplishments into the jobs where they happened rather than to build them a room of their own.

Names that cost you something

Creative headings. “Where I’ve Made a Dent,” “My Journey,” “The Work.” A reader who has to decode a heading has stopped reading your content, and software may not file the section at all. Creativity belongs in the sentences, not the signposts.

First-person headings. “My Experience,” “My Skills.” The whole document is about you. The pronoun is wasted space and it reads slightly younger than you want.

Headings that promise more than the section delivers. “Awards & Publications” above one line disappoints twice. If you have one item, name the section for what you actually have — or better, fold the item into the job where you earned it, as in awards and recognition on a resume.

Two headings a reader can’t tell apart. “Professional Experience” and “Professional Background” on the same page. If you can’t explain the difference in one sentence, neither can your reader.

Labels on obvious things. A heading that says “Contact Information” above your name and email is telling the reader something they already know from looking at it. The same logic applies to “Email:” before an address — see what to cut from your resume first.

When you need a name that isn’t standard

Sometimes you have a genuine block of content with no conventional heading: a run of conference talks, board service, languages, published work, a portfolio. The recipe is a plain noun phrase that names the contents:

Two words, no adjectives, no verbs. “Selected Projects” tells a reader they are about to read a curated few, which is a small and useful piece of information. “Cool Stuff I’ve Built” tells them about your tone instead.

Keep the headings consistent with each other

Every heading on the page should look and read like a member of the same set:

  • Same capitalization. Title Case throughout or Sentence case throughout, never a mix.
  • Same grammatical shape. All nouns — not “Education” next to “What I’ve Learned.”
  • No trailing punctuation. Headings don’t take colons or periods.
  • Same visual weight, spacing, and alignment, so the eye can find them without hunting. Tense, person, and punctuation covers the mechanical consistency pass.

Singular or plural is your call, but be consistent: “Certification” and “Skills” together looks like an oversight.

The outline test

Cover everything on the page except the headings, then read them from top to bottom.

Summary. Experience. Education. Skills. Certifications.

That should read as a short, sensible outline of a working life — one that a stranger could use to find any fact on your resume without reading a full line. If your headings instead read like chapter titles, or if two of them mean the same thing, or if one of them makes you explain yourself, rename it. It takes two minutes and it is the cheapest readability improvement on the whole document.