Achievements vs duties

A duty is what your job required you to do; an achievement is what changed because you did it well. Duties describe the job description. Achievements describe you.

Compare:

• Duty: "Responsible for answering customer emails."
• Achievement: "Cleared a backlog of unanswered customer emails within my first month and kept replies within one working day after that."

Both lines are about the same work, but only the second shows a result, a standard you kept and some initiative. Anyone hired into the same role could claim the duty. Only the person who did the job well can claim the achievement.

Most strong resumes still mention the core duties briefly so the reader understands the role, then spend most of the space on results, improvements and recognition. If a bullet could be copied into the job advert unchanged, it is probably a duty.

Because achievements show how well you did the job, while responsibilities only show that the job existed. Two candidates with the same title usually had the same duties, so a list of tasks gives the reader nothing to compare.

Achievements help the reader answer the questions they actually care about:

• Did this person do the work to a good standard?
• Did they improve anything or solve a problem?
• Were they trusted with more over time?
• Would they bring similar results here?

A responsibility such as "Managed the store stock" leaves all of those open. An achievement such as "Reorganised the stockroom layout so weekly counts finished a day earlier" answers several at once. It also gives an interviewer something specific to ask you about, which is usually a good thing for you.

Ask yourself "so what?" about the duty until you reach a result, then write the result with the action that caused it.

A simple method:

• Write the duty plainly: "Processed supplier invoices."
• Ask how well, how much or what improved: Were there fewer errors? Was anything faster? Did you fix a problem?
• Add how you did it: a new checklist, a better system, extra checks.
• Rewrite with the action first and the outcome at the end.

Example: "Processed supplier invoices" becomes "Introduced a three-way match check on supplier invoices, catching duplicate bills before payment."

If you cannot find any result, describe the standard you kept, the scale you handled or who relied on your work. That is still more useful than the bare duty.

Then read it aloud and check it is true.

STAR stands for Situation, Task, Action, Result. It is a way to tell a short story about something you achieved, and on a resume you compress it into one bullet.

• Situation: the context or problem.
• Task: what you were asked or decided to do.
• Action: the specific steps you took.
• Result: what changed afterwards.

On a resume, the Situation and Task are usually folded into a few words, and most of the line goes to Action and Result.

Example: "When month-end reporting kept running late (S/T), built a shared tracker for every open item (A), so reports went to the finance director on time for the rest of the year (R)."

Written as a bullet: "Built a shared month-end tracker for open items, ending repeated late reporting to the finance director."

Keep the full STAR version in your notes; it is also your answer when an interviewer asks about that bullet.

CAR means Challenge, Action, Result. It is a shorter cousin of STAR and suits resume bullets well because it has only three parts.

• Challenge: the problem or goal.
• Action: what you did about it.
• Result: the outcome.

Example: "Customer complaints about late deliveries were rising (C); I set up a daily dispatch check with the warehouse team (A); late-delivery complaints dropped noticeably over the next quarter (R)."

As a resume bullet: "Set up a daily dispatch check with the warehouse team to tackle rising late-delivery complaints, which fell noticeably the following quarter."

Some writers also use PAR (Problem, Action, Result), which is the same idea with a different label. Pick whichever helps you think; the reader never sees the letters.

Neither is better; they lead to the same kind of bullet. CAR is often easier for resumes because it has fewer parts, while STAR is more useful when you prepare interview answers and need to explain the background.

A practical way to use both:

• Draft each achievement in full STAR form in your own notes.
• Cut it down to Action plus Result for the resume, keeping only enough context to make the result meaningful.
• Use the full STAR story in interviews when someone asks about that line.

What matters is that each bullet shows something you did and what happened because of it. If your bullet does that clearly, the framework you used to get there does not matter.

Show reliability, accuracy, volume or trust, because in a routine job doing the work consistently well is the achievement.

Questions that uncover achievements in steady roles:

• Did you keep a high standard over a long time, such as no missed deadlines or no audit findings?
• Did you handle a large amount of work, or more than others in the same role?
• Were you asked to train new staff, cover for a supervisor or handle difficult cases?
• Did you get positive feedback, a thank-you or an internal award?
• Did you fix even a small annoyance, such as a confusing form or a messy shared folder?

Example: "Trusted to open and close the branch alone after three months; trained four new cashiers on till procedures."

Small, true achievements are far better than invented big ones.

No. Aim for most bullets to show a result or a standard, but one or two short scope lines per role are fine and often helpful.

A balanced role entry often looks like this:

• One line that sets the scope: team size, region, products, systems or clients you handled.
• Two to four achievement bullets showing what you improved, delivered or were trusted with.

Example scope line: "Handled payroll for 3 sites and around 200 staff using Oracle HR."

That line is mostly a duty, but it gives the reader the context needed to judge the achievements that follow. The problem is not having any duties at all; it is having only duties, so the reader learns what the job was but not how you did it.

Yes. Here are sales duties rewritten to show results, using illustrative details:

• Duty: "Responsible for selling products to customers."

Achievement: "Exceeded quarterly sales target in 5 of 6 quarters, selling home appliances to walk-in and phone customers."

• Duty: "Managed key accounts."

Achievement: "Retained all 12 assigned key accounts through a supplier price rise by offering early renewal terms."

• Duty: "Generated leads."

Achievement: "Built a referral routine with existing clients that became my main source of new meetings."

• Duty: "Attended trade shows."

Achievement: "Ran the company stand at two regional trade shows and followed up every lead within a week."

Use your own real figures or describe the outcome honestly if you do not have exact numbers.

Good admin achievements show that things ran more smoothly, faster or with fewer mistakes because of you. Illustrative examples:

• "Reorganised the shared drive folder structure so the team could find contracts without asking me."
• "Coordinated travel and visas for a 15-person delegation to a regional conference with no missed connections."
• "Created a meeting-room booking sheet that ended double bookings on the busy floor."
• "Took over minute-taking for the monthly board meeting and circulated drafts within 24 hours."
• "Trained two new receptionists on the phone system and visitor log."

Notice that none of these need big numbers. They show organisation, trust and problems solved, which is exactly what admin roles are judged on. Replace the details with your own and keep every line true.

Focus on problems you solved, standards you kept and feedback you earned, rather than "answered calls" or "handled complaints".

Ideas to look for:

• Customer feedback or quality scores you consistently met.
• Difficult cases you were trusted with or escalations you resolved.
• Fixes you suggested, such as a clearer reply template or FAQ.
• Training or mentoring new agents.
• Recognition, such as employee of the month.

Illustrative examples:

• "Rewrote three standard reply templates, cutting repeat contacts about delivery dates."
• "Handled escalated billing complaints for the team, resolving most without manager involvement."
• "Named Agent of the Month twice for customer feedback ratings."

If your employer tracked metrics and you know yours, use them. If you do not, describe the outcome in words.

Healthcare achievements usually show safety, quality of care, teamwork and initiative, not sales-style numbers.

Illustrative examples:

• "Introduced a bedside handover checklist on a 28-bed medical ward, adopted by the whole unit."
• "Precepted five newly qualified nurses through their first three months."
• "Served as infection-control link nurse, leading monthly hand-hygiene audits."
• "Recognised in a patient letter of thanks forwarded by the hospital director."
• "Covered as charge nurse on night shifts when the senior nurse was absent."

Keep patient information confidential: never include names or details that could identify a patient. Also keep clinical claims accurate and within your scope of practice. If your role or country requires a licence, list it in your licences or certifications section with the details your regulator expects.

Developer achievements show what your code made possible: faster systems, fewer bugs, shipped features, saved effort or better user experience.

Illustrative examples:

• "Rebuilt the checkout API in Node.js, cutting average response time from 900 ms to 250 ms."
• "Added automated tests to the billing service, ending a run of production bugs after releases."
• "Led the migration of three internal apps from on-premise servers to AWS."
• "Built an internal tool that replaced a weekly manual data export for the support team."
• "Mentored two junior developers through code reviews and pair programming."

Avoid lines like "Wrote code in Java" or "Worked on the backend". They describe your job title, not your contribution. Name the system, what you changed and why it mattered to users or the business.

Show what changed for your students, your department or your school because of your work, not just that you "planned lessons" and "marked homework".

Illustrative examples:

• "Introduced weekly reading circles for Year 7, raising library borrowing across the year group."
• "Led the Grade 10 science fair, with two student projects selected for the regional competition."
• "Redesigned the Year 9 maths scheme of work to match the new curriculum, adopted by the department."
• "Ran after-school revision clinics that became a regular part of the exam timetable."
• "Mentored a trainee teacher through their placement."

Share student results only if they are fair to use and you can explain them; avoid naming individual students. Group or class improvements, new programmes and responsibilities you were given are all strong achievements.

Warehouse and logistics achievements show accuracy, safety, speed and reliability. Hiring managers in these roles want to know you kept goods moving correctly and safely.

Illustrative examples:

• "Kept picking accuracy above the site target for 18 consecutive months."
• "Completed forklift certification and became the shift's go-to driver for high racking."
• "Suggested a new labelling system for returns that reduced misplaced stock."
• "Worked through the peak season with zero safety incidents."
• "Trained six seasonal staff on the scanner system and safe lifting."

If you do not know exact figures, write the outcome honestly: "Consistently met daily pick rates" is fine. Licences and certifications, such as forklift training, belong in their own section with any expiry date.

Show accuracy, speed, control and savings rather than listing the accounting tasks every accountant does.

Illustrative examples:

• "Cut month-end close from eight working days to five by automating bank reconciliations in Excel."
• "Recovered duplicate supplier payments found during a vendor master clean-up."
• "Prepared VAT returns for three entities with no penalties or corrections from the tax authority."
• "Supported the external audit with complete schedules, closing with no management-letter points on payables."
• "Trained the accounts payable team on the new ERP approval flow."

Duties such as "Prepared journal entries" or "Handled reconciliations" can appear in a short scope line, but most of your bullets should show what improved or how well you did it.

Good hospitality achievements show guest satisfaction, teamwork under pressure, upselling and standards you kept.

Illustrative examples:

• "Named in guest reviews by name several times for attentive service."
• "Trained new waiters on the POS system and menu allergens."
• "Suggested a wine pairing card that increased dessert-wine orders."
• "Handled 60-cover evening services on a short-staffed team without complaints."
• "Passed every food-safety inspection during my time as section lead."

For front desk roles, think about check-in speed, handling complaints, upselling room upgrades and accuracy with bookings. For kitchens, think about consistency, hygiene audits, menu contributions and training. Keep it specific and true; one real compliment from a guest is worth more than a vague claim of "excellent service".

Show delivery: what you shipped, on what scope, and how you managed time, budget, risk and people. "Managed projects" is a duty; the outcome is the achievement.

Illustrative examples:

• "Delivered a 9-month ERP rollout across four sites on schedule and within the approved budget."
• "Recovered a delayed client fit-out by re-planning the critical path and adding weekend shifts, handing over two weeks late instead of the forecast eight."
• "Set up a weekly risk review that caught a supplier delay early enough to source an alternative."
• "Coordinated a cross-functional team of 14 across engineering, procurement and finance."

If you hold PMP, PRINCE2 or a similar certification, put it in your certifications section rather than repeating it in each bullet.

Look at your studies, projects, internships, part-time jobs, volunteering and student activities. Achievements do not have to come from full-time work.

Places to look:

• Final-year project or thesis: what you built, tested or found.
• Internships: anything you completed, improved or were praised for.
• Part-time jobs: reliability, customer feedback, trust with cash or keys.
• Clubs and societies: events you organised, members you recruited, money you raised.
• Competitions, hackathons or awards.

Illustrative example: "Organised the university careers fair as events lead, bringing 25 employers to campus."

Write them the same way as work achievements: what you did and what happened. Put the strongest ones near the top, even if they came from a project rather than a job.

Employers hiring graduates know you are early in your career, so modest, real achievements are exactly what they expect to see.

Yes, as long as you describe your own part honestly. Most real work is done in teams, and employers know that.

How to write it fairly:

• Use wording that shows your role: "led", "contributed to", "built the reporting part of", "one of three analysts who".
• Name the specific piece you did.
• Mention the team result as context.

Example: "Designed the data model for a team-built customer dashboard now used by all regional managers."

What you should avoid is claiming the whole result as yours, such as "Increased revenue across the region", when you were one of many people involved. An interviewer will ask what you personally did, and your answer needs to match the bullet.

Words that describe change or outcome, such as "so that", "which led to", "resulting in", "reducing", "improving", "ending" or "allowing".

Task-style phrases to watch for:

• "Responsible for…"
• "Duties included…"
• "In charge of…"
• "Tasked with…"
• "Worked on…"

These phrases put the job first and you second. A result-focused bullet usually has an action and then a consequence.

Example:

• Task style: "Responsible for the monthly newsletter."
• Result style: "Relaunched the monthly newsletter with a shorter format, so more staff opened and read it."

A quick test: if you can add "…and as a result…" to the end of your line and nothing follows, it is still a duty.

Describe it plainly and specifically. A small improvement written precisely is more believable and more useful than an exaggerated one.

Tips:

• Say exactly what changed: a form, a process, a habit, a file.
• Say who benefited: your team, customers, a manager.
• Do not inflate the impact. "Saved the company time" is vague; "saved the team re-entering the same data twice" is real.

Illustrative examples:

• "Created a one-page checklist for new-joiner IT setup, used by the whole office."
• "Started labelling returned items on arrival, so they were easier to restock."

Employers value people who notice small problems and fix them. Several modest, true improvements across a resume tell a clear story about how you work.

Yes. A promotion shows that someone who saw your work every day trusted you with more. It is one of the clearest achievements you can show.

Ways to present it:

• List each title separately under the same employer, with its own dates.
• Or add a line such as "Promoted from Sales Associate to Assistant Store Manager within 18 months."
• If you were promoted early or ahead of peers, you can say so if it is accurate.

Then show what you achieved in the new level, not just that you got there. A promotion plus results in the bigger role is a much stronger story than the promotion alone.

Being given extra responsibility without a title change, such as covering a manager's role, also counts. Describe it honestly.

Put the recognition inside the relevant job if it was given for that work, and say briefly why you received it.

Example: "Named Employee of the Quarter (Q2 2025) for clearing the customer refund backlog."

The reason matters more than the award name, because internal awards mean little to outsiders on their own. "Star Award" says nothing; "Star Award for leading the branch through a system migration" says a lot.

If you have several major awards, scholarships or external honours, you can also create a separate Awards section. Keep the strongest work-related ones in your experience section, where they support the role, and avoid repeating the same award in two places.

Then describe what you did during that period rather than claiming the whole result. Reasonable readers know that sales in a booming market or savings from a price fall are not all down to one person.

Better approaches:

• Focus on your actions: "Expanded the client list to meet rising demand by setting up weekend viewings."
• Describe your share: "Handled the largest share of new enquiries on a team of four."
• Compare fairly if you can: "Ranked first of six agents in viewings booked."

If an interviewer asks about it, explain the context openly. Honest framing builds trust and protects you if a reference or later employer checks the story.