You won an internal award for the migration nobody else wanted, and the ATS stored it as a skill called "Spot". Awards and honors are the cheapest proof a resume can carry: someone other than you judged your work and wrote it down. They are also a section that parsers handle inconsistently, because there is no standard field for "recognition" in most applicant tracking systems. The fix is to write every award so it survives as plain, searchable text, with the reason attached.
I build Smart Resume Analyzer, an ATS resume checker, and I have spent nine years as a Principal Software Engineer in Karachi writing parsing and matching code in PHP, Laravel, Vue, Nuxt, Node and TypeScript. I wrote this with help from AI tools and checked every example and claim myself. This piece covers one problem: listing awards, honors, scholarships and internal recognition so ATS software keeps them and recruiters understand why they matter.
How should you list awards on a resume for ATS?
Direct answer: Put awards in a section headed "Awards" or "Honors and Awards", one award per line, in the pattern Award Name, Issuer, Month Year, followed by a short reason with a number. Use plain text, no icons or badge images. Mention a strong award again inside the relevant job bullet, because some parsers drop or flatten custom sections.
Why awards are awkward for parsers
Most ATS data models have firm fields for contact details, work history, education and skills. Awards rarely get their own structured field. What happens to them depends on where they sit and how they look.
| Where the award sits | What a parser usually does | Searchable? | Risk |
|---|---|---|---|
| Own section, headed "Awards" or "Honors" | Keeps it as a text block, sometimes under "Additional information" | Yes, as full text | Low |
| Inside a job bullet ("Won the 2024 Engineering Excellence Award for...") | Stored as part of that job's description | Yes, and tied to the right employer | Low |
| Under Education ("Dean's List, Gold Medal") | Often stored with the degree, sometimes dropped if the line looks like a course | Usually | Medium |
| Mixed into Skills ("Leadership, Spot Award, Python") | Treated as a skill token | Misleading | High |
| Badge images, logos or icons | Ignored; images carry no text for the parser | No | High |
| Sidebar or text box in a two-column design | Read out of order or skipped | Unreliable | High |
The two high-risk rows are the ones I see in designer templates: a row of badge icons in a sidebar, or a "Highlights" box that mixes awards with skills. Both look impressive to a human and leave very little behind for the parser.
How the major ATS products tend to treat awards
Treat these as working assumptions, not vendor guarantees. Each employer configures its own instance, and parsing engines change.
| ATS | What to expect | What to do |
|---|---|---|
| Workday | Structured rows for work, education, skills and certifications on the form; awards usually have no row of their own | Keep awards in the resume text and repeat the strongest one in a job bullet |
| Greenhouse | Parsed profile plus the original file, which stays searchable | Plain-text award lines are found by keyword search |
| Lever | Profile fields plus the attached resume | Use the full award name, not an internal nickname |
| iCIMS | Configurable fields; unrecognized sections often go into a general text area | Use a standard heading so the block is not merged into the section above |
| Taleo | Older parsing; custom sections may be flattened into the experience text | Keep each award on its own line so it does not merge with a bullet |
The common thread is simple. If the award exists only in a place the parser does not understand, it is invisible to search. If it exists as plain text under a standard heading, and again inside a job bullet, it survives almost any engine.
What the parser does with your lines
Here is a simplified version of how a section splitter works. Real engines are more forgiving, but the failure shape is the same.
KNOWN = {"experience", "education", "skills", "certifications",
"awards", "honors", "honors and awards", "projects"}
def split_sections(lines):
sections, current = {}, "header"
for line in lines:
key = line.strip().lower().rstrip(":")
if key in KNOWN:
current = key
sections[current] = []
else:
sections.setdefault(current, []).append(line)
return sections
If your heading is "Wins & Kudos" or "Hall of Fame", it is not in the known list, so every award line is appended to whatever section came before it, often Skills or the last job. That is how "Spot Award, Q3 2024" ends up looking like a skill. Use a heading the splitter recognizes. I covered the full list of safe headings in Resume Section Headings: What ATS Parsers Recognize.
AI-generated image.
Weak vs. ATS-optimized rewrites
1. The bare name
- Weak:
Spot Award - Optimized:
Spot Award, Acme Logistics, Mar 2024: Migrated 40 cron jobs to a monitored queue with zero missed runs in the first quarter
The weak version says nothing about who gave it or why. The optimized version names the issuer, a date and the work. The numbers must be your own, true numbers.
2. The internal nickname
- Weak:
Rockstar of the Quarter - Optimized:
Quarterly Engineering Recognition Award (company-wide), Acme Logistics, Q3 2023: Led incident response for a payment outage and wrote the postmortem adopted as the team template
Recruiters outside your company do not know what "Rockstar" means. Translate it into plain words and state the scope (team, department, company-wide) only if you know it.
3. The badge row
- Weak: three badge icons in a sidebar with no text
- Optimized: three plain lines under "Awards", each with name, issuer and date
4. The academic honor
- Weak:
Gold Medal - Optimized:
Gold Medal (first position in BS Computer Science cohort), NED University, 2017
Put academic honors under Education next to the degree, or in Awards if you have several. The way degrees themselves are parsed is in How ATS Parses Education and Certifications on Your Resume.
5. The hackathon
- Weak:
Hackathon winner - Optimized:
First Place, Karachi Fintech Hackathon (team of 4), Nov 2022: Built a fraud-flagging prototype in Laravel and Vue in 36 hours
The names in these examples are illustrations. Use your real award names, issuers and dates.
Awards vs. certifications vs. achievements
People mix these up, and parsers do too. Keeping them apart helps both.
| Item | What it proves | Where it goes | Example line |
|---|---|---|---|
| Award or honor | Someone judged your work as outstanding | Awards section, plus a job bullet for the strongest | Engineering Excellence Award, Acme, 2024 |
| Certification | You passed a defined exam or course | Certifications section, with issuer and ID if useful | AWS Certified Solutions Architect – Associate, 2025 |
| Achievement | A result you produced | Job bullets, with a number | Cut API p95 latency from 900 ms to 300 ms |
| Scholarship | Selection for funding, usually academic | Education, next to the degree | Merit Scholarship, NED University, 2014–2018 |
| Publication or talk | Your work was accepted by an editor or committee | Publications or Talks section | Covered in my earlier guide on publications |
The rule I use: if you did not get selected or judged by someone else, it is an achievement, not an award. Do not label a result you produced as an award, and do not list a course certificate as an honor.
Which awards to include, and which to cut
Not every award helps. Space is limited and a recruiter scans quickly.
Keep:
- Awards from the last five to seven years, unless an older one is unusually strong.
- Awards with a clear selection process: company-wide, competitive, external judges.
- Awards connected to the job you want: an engineering award for an engineering role.
- Academic honors if you graduated recently or the role values them.
Cut or merge:
- Attendance or participation certificates.
- Repeated identical awards: write "Spot Award (3 times), 2022–2024" instead of three lines.
- Awards that reveal information you would rather not share, such as religious or political affiliation. That is your call, but you are not required to list them.
A step-by-step diagnostic checklist
Run this before you submit:
- Heading: The section is called "Awards", "Honors" or "Honors and Awards", on its own line.
- One per line: Each award is its own line, not a comma-separated list.
- Pattern: Award Name, Issuer, Month Year (or Year), then a short reason.
- Plain text: No badge images, icons, logos or text boxes.
- Translated names: Internal nicknames are rewritten in words an outsider understands.
- Repeated where it counts: Your strongest award also appears inside the matching job bullet.
- Not in Skills: No award names inside the Skills section.
- Dates are consistent: Same date format as your work history.
- True and checkable: Every award, number and scope is real and could be confirmed by a reference.
- Parsed result checked: Run the file through a parser and confirm the award text appears in full and under the right section.
For step 10, paste your resume into an ATS parser preview such as the one I build and read the raw text output, not just the score. If the award line is missing, broken across two lines, or sitting under Skills, fix the layout and test again. I described a full pre-submit routine in The 15-Minute Pre-Submit Resume QA Pipeline.
A template you can copy
HONORS AND AWARDS
Engineering Excellence Award, Acme Logistics, Jan 2025
Selected company-wide for leading the queue migration that removed nightly batch failures.
Spot Award (3 times), Acme Logistics, 2022–2024
First Place, Karachi Fintech Hackathon (team of 4), Nov 2022
Gold Medal, BS Computer Science, NED University, 2017
Keep it short. Four strong lines beat ten weak ones.
FAQ
Should awards have their own section on a resume?
Yes, if you have two or more relevant ones. Use a standard heading like "Awards" or "Honors and Awards" so parsers recognize it. With only one award, put it inside the matching job bullet or under Education instead of creating a near-empty section.
Do ATS systems read badge images or icons?
No. Parsers read text. A badge image, logo or icon carries no text the parser can use, so it disappears. If an award matters, write its name, issuer and date as plain text.
How do I list an internal company award nobody outside knows?
Translate it. Write what it was for and its scope in plain words, for example "Quarterly Engineering Recognition Award (company-wide)". Then add one short reason with a real result. Keep the original name in brackets if a reference might mention it.
Can I list the same award won several times?
Yes, but merge it into one line, such as "Spot Award (3 times), 2022–2024". Three identical lines waste space and look padded to a human reader, and they add nothing for search.
Should I include academic honors years after graduating?
Include strong ones (a gold medal, a national scholarship) for about the first five years, or longer if the role is research-heavy. After that, move them to the Education line or drop them to make room for recent work recognition.
Are awards used as ATS keywords?
Only as full text. Most systems do not have a structured awards field, so awards are found through general keyword search of the resume. That is why the award name, the issuer and the skill it recognized should all be written out in words.
The short version
Awards are third-party proof, which is exactly why they are worth keeping. Give them a standard heading, one line each with name, issuer and date, a short true reason, and repeat the best one where the work happened. Then check the parsed text before you hit submit.
Follow & Connect
- YouTube: Resume Boost AI (@resume-boost-ai)
- TikTok: Resume Boost AI (@resumeboostai)
- X: Muhammad Ali Mughal (@AliMughal887)
- GitHub: Muhammad Ali Mughal (@ali111887)
- LinkedIn: Muhammad Ali Mughal
Top comments (0)