11 min read
Listing duties doesn't work anymore because parsers and recruiters read the same file for different jobs. Your duty bullets can still hit ATS keywords from the posting. They fail the human pass when bullet one names a task with no outcome a recruiter can't ask about in thirty seconds. That's the split you're losing on, not keyword count.
Check your resume for free after you rewrite bullet one. You'll see whether keywords sit inside dated lines in Workday and Greenhouse, and whether bullet one gives a recruiter a real question instead of a job-description echo.
Below you'll get why duty lines still show up in qualified files, the small exceptions, before/after pairs across roles, and a rewrite you can run tonight. Job searching is hard. This page isn't a lecture about bad templates. It's about changing bullet one with your hands.
Quick Wins
- Rewrite bullet one under your current role before you touch bullet two.
- Replace responsible for with verb plus scope plus change plus tool.
- Move posting keywords from Skills into the new dated bullet.
- Paste your export into Notepad to confirm employer order parses.
Why listing duties fails after the parser pass
Corporate stacks run two filters. Applicant tracking systems match keywords inside experience text. Recruiters scan for proof they can defend to a hiring manager. Duty bullets like managed client relationships or assisted with reporting often satisfy the first filter when the posting used the same nouns. They die on the second because there's no scope number and no change.
What recruiters actually do in thirty seconds: read headline, current employer, dates, then bullet one under the latest role. If bullet one is responsible for vendor management, the next question should be how many vendors, what spend, what broke. Duty language doesn't invite that question. It ends the scan.
A composite operations coordinator whose file lists coordinated shipments, updated trackers, and filed paperwork in three bullets gets parsed. A peer whose bullet one says reconciled 120+ inbound shipments weekly in NetSuite; cut mis-route tickets from 18 to 7 per month across Q2 2025 gets the callback. Same employer. Different first eight words.
And duty stacks create a second problem: they read like you pasted the internal job description. Hiring managers assume you don't know what changed because of your work. Outcome bullets signal you can explain impact on a call. Duty bullets signal you'll read the req back to them.
The parser pass vs the human pass on the same bullets
ATS does not reward responsible for. It rewards keyword presence in readable layout. Single-column PDF or DOCX, Month Year dates, employer headers parsers can sort. A duty bullet that names Salesforce, SQL, or HIPAA inside a dated line can score fine while still failing you on the phone screen.
That's why listing duties doesn't work anymore even when your match tool looks green. Match tools count terms. Recruiters count proof. If your highest-scoring lines live in Skills and your Experience section is duty paste, you're optimized for the wrong reader.
Before: Skills holds 18 tools; Experience bullets say handled requests, supported teams, maintained records.
After: Two tools move into bullet one with scope; Skills shrinks to a one-line echo; Experience carries keywords inside outcomes.
Paste your export into Notepad before you trust a green match score. If Skills paragraphs appear before Experience in plain text, parsers may overweight keywords that never sit next to a date. Fix column order first. Then rewrite bullet one so the same keywords appear inside Month Year lines recruiters trust.
Read monitoring resume bullets that show outcomes when your role is metrics-heavy and you need more than one rewrite pattern for proof lines.
Why duty templates still look safe on paper
Old resume templates were built for HR file cabinets, not Greenhouse queues. They rewarded completeness: every task you ever touched got a line so no manager felt omitted. That logic still feels responsible when you're unemployed and anxious. More lines look like more effort.
Template trap one: five equal bullets per role. Recruiters read top-down. Bullet five never gets read if bullet one is assisted with projects. Collapse to three bullets max per role and put your only scoped outcome first.
Template trap two: summary paragraphs that repeat duties in prose. Managed teams, drove results, and communicated with stakeholders is three duty clauses with adjectives. Delete the summary or replace it with one line echoing bullet one's metric.
Template trap three: copying the posting into Experience. Parsers may love the keyword overlap. Humans spot paste instantly because tenses and tools don't match your employer's stack. Translate each duty into your scope instead of mirroring the req.
A composite project manager whose file lists ran status meetings, tracked milestones, and updated RAID logs in four bullets gets filtered after the keyword pass. One bullet that says cut release slip from 11 to 4 per quarter across 6 squads using Jira dashboards in 2024 carries the same keywords with proof attached.
When a duty line still belongs on the page
Rare postings treat the duty itself as the credential. Clinical roles sometimes need procedure names. Compliance roles need control language. Even then, pair the duty with volume, error rate, or time window in the same bullet. Pure task lists without scope stay off bullet one.
Exception 1: regulated task is the skill. Audited SOX control samples weekly in Workiva; closed 32 findings with zero repeat exceptions in FY2024. The duty is auditing. The proof is count and clean close.
Exception 2: brand-new role with no metrics yet. You can name scope without inventing impact: onboarded as sole payroll specialist for 140 employee records in Paylocity during Jan 2025 migration. That's defensible. assisted with payroll is not.
Exception 3: internal promotion same month. One duty line is fine on bullet three. Bullet one still needs the strongest outcome from the prior six months in the same seat. Do not lead the role with updated spreadsheets.
Outside those cases, treat duty language as raw material. Extract the verb, add object, scope, tool, and change. Delete the rest.
Before and after: listing duties vs outcomes by role
Customer success (mid-level)
Before: Managed customer accounts. Responded to tickets. Escalated issues as needed.
After: Owned 42 enterprise accounts in Zendesk and Gainsight; raised CSAT from 88 to 94 across H1 2025 while cutting avg first response to 2.1 hours.
Marketing coordinator
Before: Assisted with email campaigns. Updated CRM lists. Coordinated with sales.
After: Built weekly nurture flows in HubSpot for 28K contacts; added 340 SQLs in Q3 2024 for a 6-rep SMB SaaS team.
Software engineer
Before: Worked on backend services. Participated in code reviews. Fixed bugs.
After: Shipped rate-limit service in Go on AWS; cut p99 latency 120ms for 2M daily API calls across Mar to Aug 2024.
HR generalist
Before: Processed onboarding paperwork. Scheduled interviews. Maintained employee files.
After: Ran onboarding for 65 hires in 2024 in BambooHR; cut day-one missing-doc cases from 11 to 2 per quarter.
Financial analyst
Before: Prepared monthly reports. Supported budget process. Updated Excel models.
After: Built rolling 13-week cash forecast in Excel for $42M division; flagged $1.2M variance two weeks before close in Q4 2024.
Numbers inside bullets are illustrations of shape, not market claims. Swap in your real scope. Keep Month Year headers on every role block.
What to do tonight: rewrite bullet one first
Open the posting you care about most. Highlight three must-have skills or tools. Open your resume to the current role. Delete responsible for, assisted with, and handled from bullet one only. Rebuild that bullet as verb plus object plus scope plus change plus tool plus date range.
The line worth remembering: if a recruiter can't ask a follow-up from bullet one, it's still a duty bullet with better verbs.
Copy-paste rewrite prompt: "Under [Role, Employer, Month Year to Month Year], write one bullet that names [posting keyword], [scope number: team size, volume, budget, or geography], [change metric or before/after], and [tool from posting] in the first eight words."
Export PDF or DOCX. Paste into Notepad. Employer names and dates should read top to bottom. Fix layout before you rewrite bullet two. Bullet one carries most of the human pass.
Then move posting keywords from Skills into the rewritten bullet if they still miss. Shrink Skills to a one-line echo. Parsers read Experience first. Recruiters never read bullet six if bullet one is empty.
Work role by role, newest first. You don't need twelve perfect bullets tonight. You need one bullet a recruiter can interview against. After bullet one is fixed, rewrite bullet two only if it still reads like a duty clone of bullet one with a different verb.
If you're stuck on metrics, use scope proxies hiring managers accept: volume per week, accounts owned, budget managed, geography covered, tickets closed, or time saved for a named team. A defensible proxy beats a fake percentage every time on a reference call.
See how to write a job description for a resume when you're tempted to paste the employer's req verbatim instead of translating duties into outcomes.
Verify parsing and match after bullet one
Run a free ATS check with the description pasted after bullet one is rebuilt. If keywords still miss, add them inside the new bullet, not as five more duty lines. When the file parses cleanly but feels thin, you have a proof problem, not a keyword problem.
Generate a cover letter that repeats the same outcome from bullet one in plain sentences. Letters that re-list duties double the job-description smell.
Duty patterns to delete on sight
Responsible for plus noun. Swap the frame entirely. Responsible for social media becomes grew LinkedIn followers 4K to 19K in nine months with three posts weekly for a B2B SaaS brand.
Participated in or involved with. Name the deliverable and your slice. Participated in ERP migration becomes mapped 240 vendor SKUs into NetSuite during Aug to Nov 2024 cutover.
Duties included. That's a heading, not a bullet. Delete the line and start with the strongest outcome from that role.
Various or multiple without a number. Various clients means nothing. 28 mid-market clients in Salesforce means something.
Keyword rows with no employer date. If Python only lives in Skills, move one posting use into a dated bullet or drop the claim.
I've screened duty-heavy files where the parser passed and bullet one still read responsible for weekly reports. Promote one scoped outcome to bullet one before you add another duty line with the same keyword.
Stop optimizing duty lines for the wrong reader
Listing duties doesn't work anymore because the human pass needs a question, not a task list. Parsers still move duty-heavy files forward when keywords match. Recruiters stop when bullet one has no scope and no change. Fix bullet one under your current role tonight. Then check parsing and match with the posting pasted in.
This won't fix applying to roles you're not qualified for. It does stop qualified candidates from losing screens because responsible for weekly reports was the strongest line on the page.
And if your match score looks great while screens stay quiet, read bullet one out loud. If you wouldn't ask yourself a follow-up, rewrite it before you add a fourth duty line with the same keyword.
Read more
Frequently asked questions
Parsers in Workday, Greenhouse, Lever, and iCIMS score keyword presence inside experience lines. A duty bullet that says managed customer accounts and used Salesforce can still match the posting. The human screen runs next and bullet one gives nothing to ask about in thirty seconds. Recruiters need scope and change: how many accounts, what moved, which tool inside a dated line. Duty language passes the file forward and stops the conversation.
Yes, when the duty itself is the rare skill the posting demands and you pair it with scope in the same bullet. Example: processed 40+ vendor invoices weekly in NetSuite with zero missed payment deadlines across 2024. The duty is invoice processing. The outcome is volume, tool, and error rate. Pure duty lines with no number and no change belong in your delete pile, not bullet one.
Replace it with verb plus object plus scope plus change inside the first eight words. Instead of responsible for weekly reports, write built weekly pipeline dashboards in Excel and Looker for a 9-person SMB sales team; cut manager prep 4 hours per week across Jan to Dec 2024. The posting keyword still lands. The recruiter gets a question to ask.
They want proof you did the work that produced results they care about. Daily tasks buried in five duty bullets read like a job description paste. One outcome bullet that names the task, tool, and metric covers the same ground. Save task lists for the interview when they ask how your week runs.
Rewrite bullet one under your current role first. Open the posting, highlight three must-haves, and rebuild that bullet with one scope number and one change metric. Paste the export into Notepad to confirm dates and employer order parse. Run a free ATS check with the description pasted. One strong bullet often fixes the screen problem before you touch the rest of the role.