Resume sections
Achievements: change the line only where you have a real result
Replace duty lines with achievements only where you have a real result: a number, a time change, a volume, or a named deliverable. Workday and Greenhouse store that text under Experience — they do not have a magic Achievements field. Do not invent percentages. Scope is honest when a metric is secret.
Written by EnhanceCV Editorial Team·Editorial review: CPRW
Published August 27, 2026·Last updated August 27, 2026
Key takeaways
- · An achievement is a duty plus a result you can defend in a screen: volume, time, money, quality, or a shipped artifact.
- · Workday maps Experience, not a heading called “Wins.” Put the number in the job block Greenhouse will search.
- · If you lack a clean metric, write scope: caseload, team size, budget band, sites, shift — not “improved performance.”
- · Never invent a percent. Recruiters in Lever ask for the baseline in the first five minutes.
- · Rewrite three lines, then check the parse so the nouns still sit in selectable text inside the builder.
Achievements are not a separate section — they replace duty lines
Key takeaway: A heading called Accomplishments does not impress a parser. A verb, a noun, and a number inside Work Experience does.
People add an Achievements block because templates leave a hole at the top. Workday does not map that heading to a field that recruiters filter. Greenhouse search still runs on employer, title, dates, and the text under those jobs. If the only place you wrote “cut cycle time from 9 days to 4” is a floating list under your name, some extracts attach it to the wrong role or drop it. Put the line under the job where it happened.
A duty describes the job that already existed when you arrived: “responsible for onboarding,” “handled invoices,” “supported the sales team.” Anyone with the same badge can paste that. An achievement describes a change, a volume you held, or a thing that shipped: “onboarded 14 retail hires in Q3 using Greenhouse onboarding,” “closed 120 invoices a week in NetSuite with a 2-day average,” “built the Q4 forecast tab the AE team still uses.” The job ad’s nouns should appear in those lines when they are true. That is tailoring, not stuffing.
You do not need a “STAR story” label on the page. You need enough of the story for a human to ask a follow-up: situation in a clause, action as the verb, result as the number or deliverable. The rest belongs in the interview. Dumping a full STAR paragraph per bullet is how a two-page file never gets finished on a phone. Line craft lives next to resume bullet points and resume action verbs.
What counts as a result you already have
- Volume you can name without a dashboard login: tickets per shift, patients per day, stores on a route, invoices per week.
- Time you watched change: days to close, minutes of wait, weeks to hire, hours of downtime.
- Quality the team already tracked: CSAT, error rate, audit findings, on-time percent — only if you saw the report.
- A named artifact: playbook, dashboard, SOP, SKU set, training deck, cutover weekend.
If your employer forbids publishing internal metrics, write the frame you can swear to: “weekly forecast for eight sites in Excel, reviewed with regional managers.” That is an achievement of ownership. “Grew revenue 40%” without a year, a baseline, and a team size is a claim you will regret in Greenhouse notes.
Where Workday and Greenhouse store a number — and where they ignore it
Key takeaway: The metric has to live in extractable text under a mapped heading. Charts, skill bars, and header slogans do not count.
Workday’s experience widget stores employer, title, start/end, location, and a description blob. That blob is where your number must sit. A summary line at the top may be searchable in some tenants and ignored in others. Do not hide the only proof in the summary. Repeat the strongest proof once under the relevant job even if the summary already mentions it.
Greenhouse indexes the uploaded file and the parsed fields. Recruiters type tool names and outcome words. “Reduced” plus a noun they care about (churn, AHT, defects) can surface you — if those words are real text, not a screenshot of a dashboard. Taleo is worse at text boxes. If you put “+27% NPS” in a colored callout shape, assume it is gone. Put “NPS 27 points on the Q2 tracker the CX lead ran” in a bullet under the job.
There is no official Achievements field in Workday HCM recruiting that hiring managers sort on. There is Skills if you used a Skills heading — and Skills should be tools and methods, not “results-oriented.” Keep metrics in Experience. Keep tools in Skills and again in the bullet that used them. See resume skills and resume keywords.
What to delete before you add a number
- “Successfully,” “various,” “multiple,” “cross-functional stakeholders” with no names of functions or dates.
- Percentages you reverse-engineered from a feeling. If you cannot name the report, cut the percent.
- Awards without a year or a scope (“Employee of the Month” with no team size reads as filler).
- Duty stacks: six lines that all start with “Responsible for.” Keep one context line, rewrite the rest.
File still has to parse. A beautiful infographic of your “impact” is a two-column problem in disguise. Flatten first using the same rules as an ATS resume. Then rewrite. Order of operations matters: a metric in a text box is a metric Workday never stored.
Rewrite weak lines: three before-and-after transforms
Key takeaway: Duties describe the seat. Achievements describe you. If the line could sit on any resume with that title, it is not finished.
Three rewrites we use constantly in edits — operations, people ops adjacent, and a shared credit case. Steal the pattern. Do not steal the numbers.
Before
Responsible for processing customer orders and handling issues as they came up.
After
Processed 45–60 Shopify orders per shift and cut same-day WISMO tickets from ~12 to 4 by adding tracking macros in Gorgias.
Before
Worked with stakeholders to improve the onboarding process across the board.
After
Shipped a 9-page Greenhouse onboarding checklist with People Ops (Jan–Mar 2025); new-hire laptop requests dropped from 8 days to 3.
Before
Led a project that increased sales and exceeded team goals.
After
Owned the Q4 add-on attach tracker in Excel for a 6-person floor team; attach rate moved from 11% to 16% on the weekly ops report (numbers from my manager’s pack, used with permission).
Shared credit is allowed when you say so. “With finance, closed month-end two days faster after we rebuilt the Accruals tab” is stronger than “I closed the books.” Lying about solo ownership is how a Workday reference check later hurts you.
Older roles get two bullets, not six achievements from 2014. Recruiters skim recent proof. Mid-career editing notes sit in resume for mid-career. Examples you can adapt without copying metrics: resume examples.
A 12-step playbook for mining numbers you already have
Key takeaway: You are not inventing a dashboard. You are recovering facts from email, calendars, and old reviews.
Block 90 minutes. Have the job ad, your last review, and sent mail. Type inside a known-good layout if you want: Enhance CV builder.
- Highlight nouns in the posting: tools, volumes, outcomes they name (quota, CSAT, uptime, census).
- Open last year’s review or self-assessment. Copy any number your manager already signed. Those are the safest metrics.
- Search your inbox for “attached,” “tracker,” “QBR,” “CSAT,” “closed.” Write a list of report names, not percentages yet.
- For each recent job, write eight messy duty lines. Do not polish. This is the raw list.
- Match each duty to a noun from step 1. Delete duties that help a different career.
- For remaining lines, add one of: volume, time, money band, quality, or named artifact. If none exist, add scope only.
- Read the line out loud. If you cannot say where the number came from in one sentence, delete the number.
- Put tools in the bullet and again under Skills. No star ratings.
- Cap recent roles at three to five bullets. Older roles: one or two proof lines, then dates only if needed for the graph.
- Remove an Achievements heading if it duplicates Experience. Merge the best lines down into jobs.
- Export selectable text. Confirm numbers are highlightable, not in a chart image.
- Paste resume and ad into the ATS checker. Then upload to Workday or Greenhouse and read the description fields.
Step 7 is the ethics gate. A number without a source is marketing. Enhance CV will not know you invented it; the interviewer will. If Legal owns the only dashboard, ask what you may publish, then use scope until you have an answer.
If you stall, you are probably writing the summary first. Write proof under jobs, then a 3-line summary that repeats one number. Structure (not sentences) from professional summary examples is fair. Pasting someone else’s 40% is not.
Do this, skip that
Key takeaway: Most “quantify your resume” advice skips the part where the metric has to be true and parseable.
Desk filter while you edit. If the case is not in the table: would you repeat this number to a hiring manager who can call your last boss?
True, mapped achievements vs. resume fiction
| Topic | Do | Don’t |
|---|---|---|
| Where it lives | Under the job in Work Experience as a bullet. | A floating Achievements cloud above the jobs. |
| Numbers | Volume, time, $ band, or a named report you can cite. | A percent with no baseline, year, or source. |
| Scope fallback | Team size, sites, caseload, budget range, shift. | “Improved KPIs” with no KPI named. |
| Tools | In the bullet and under Skills. | Only as a logo row the parser skips. |
| Credit | “With X team” when it was shared. | Solo verbs on a committee deliverable. |
| ATS | Selectable text in one column. | Charts, badges, and text boxes for the only proof. |
Functional resumes that hide dates under skill clouds still show up in “achievements-first” templates. Greenhouse can parse them; humans distrust the timeline. Keep chronology and put proof in the job blocks — see chronological vs functional.
Edge cases: no metrics, regulated work, and first jobs
Key takeaway: The method stays. You only change which kind of proof is legal and available.
No dashboard access. Use scope and artifacts: “night coverage for a 32-bed unit,” “owned the returns SOP in Confluence,” “trained 6 seasonal cashiers on POS v3.” That is enough for many Workday screens.
Healthcare, finance, defense. Do not publish patient names, account numbers, or classified program titles. Use counts and systems: “Epic inbasket of 40–50 messages per shift,” “SOX evidence pack for two control owners.” The noun the posting uses (Epic, SOX) still belongs in text.
New graduates. Class projects count when they shipped: “SQL queries on a 50k-row class dataset, dashboard used in the final critique.” Coursework lists are weak. Pair with resume with no experience and student resume.
Career change. Keep true titles and dates. Reframe the result in the language of the new posting without inventing a title. Career change resume covers the hybrid block. Do not dump old duties that scream the previous field.
A number you can source in one breath beats a yearly “efficiency” percent reverse-engineered from a feeling. Name the pack: weekly WFM export, QA sampler, POS close, signed review. If Legal owns the only dashboard, ask for a publishable band and ship scope until they answer. Workday stores whatever you typed; the interviewer still asks where it came from. That is the whole game: true text under a mapped job, not a floating wins cloud.
What to do today: pick one job, rewrite three bullets with sources, flatten if needed, score the file. If the checker flags a heading Workday will not map, rename it before you add another adjective. Enhance CV returns you to builder and checker.
FAQ
Should achievements be a separate section on a resume?
Almost never for Workday or Greenhouse. Put the result under the job where it happened so dates and employer stay attached. A separate Wins heading is easy for a parser to detach or drop.
What if I am not allowed to share company metrics?
Write scope and artifacts: team size, sites, systems, documents you shipped. Ask your manager what is public. Do not invent a percent to look quantitative. Interviewers ask for the source.
How many achievement bullets per job?
Three to five for the most relevant recent role. Two for older roles. A wall of ten “wins” from one job is how the line that would have gotten you the screen never gets read.
Do ATS systems score achievements?
They store text and match nouns. They do not grade “impact.” Workday maps Experience fields. Greenhouse search hits words in the extract. Make the number real text under a standard heading.
Is STAR required on the resume?
No. Use a short clause for context, a verb for what you did, and a result. Save the full story for the interview. Long STAR paragraphs waste space and still need to parse as text.
Can I use team metrics if I was not the only owner?
Yes if you say it was shared: function, date range, your part. Solo verbs on a committee number are a common reason reference checks go cold.
Where do I put awards?
Under the job, with year and what was measured, or in a short Awards line if the posting cares. “Employee of the Month” with no scope reads as filler in a Workday blob.
How do I check that my metrics still parse?
Select-all in the PDF. If the number does not highlight, it is a picture. Then run the Enhance CV ATS checker and read the Workday description field after upload.
Rewrite the next duty line in a layout parsers already map
Open the Enhance CV builder, keep your true numbers, and cut lines that still read like a job description. Then score the file against the posting.