Resume
Resume bullet points: examples, action verbs and writing tips
Turn responsibilities into clear resume bullet points. See three before-and-after examples, evidence prompts and ways to write honestly without metrics.
By Resume Home · Updated . Illustrative examples are fictional: replace sample identities and experience with your own facts before applying.
In short
A useful resume bullet tells the reader what you did, where or how you did it and what changed when you know the result. Start with the action you actually performed. Add tools, scope or outcomes only when you can support them. A specific, accurate description is useful even when you do not have a numerical metric.
Key takeaways
- Start with the action you actually performed, then add context, tools or outcomes you can support.
- Use a number only when you know its source and what it measures.
- Read each bullet aloud: could you explain the verb, the subject and the outcome in an interview?
Start with a record of the work
Before rewriting, jot down the task, your part in it, the tools used and any observable outcome. Useful prompts include: what did a colleague ask you to do, what did you deliver, what problem did you resolve and what would a teammate say you owned? These notes give a rewrite something concrete to work with.
Separate an individual contribution from a department-wide result. If the team shipped a feature and you tested the registration flow, say that you tested the flow. You can mention the shared project without claiming that you led it.
- Action: resolved, built, reviewed, scheduled, tested or documented, when that verb fits the work.
- Context: the feature, customer need, document or process you worked on.
- Evidence: a deliverable, verified scope, recorded result or clear description of how the task was completed.
Action verbs by type of work
Pick the verb that names what you actually did, not the strongest-sounding one. These are starting points; use one only when it fits your own work.
- Building: built, implemented, set up, configured, developed.
- Fixing and improving: resolved, fixed, simplified, streamlined, reduced.
- Organising: coordinated, scheduled, planned, prepared, tracked.
- Communicating: explained, presented, documented, trained, answered.
- Checking: tested, reviewed, verified, audited, reconciled.
Three rewrites that add clarity rather than facts
These examples assume the details in the revised wording are already known. They are fictional writing exercises, not claims about customer outcomes. If a detail is not true of your work, leave it out.
Before
Responsible for customer support tickets and help articles.
After
Resolved customer support tickets and maintained help articles explaining account setup.
Why it works: The action replaces a vague responsibility label. The article topic makes the work more concrete, if account setup was genuinely the topic.
Before
Worked on testing the app.
After
Tested the registration flow and documented steps to reproduce validation errors.
Why it works: The revised wording names the flow and the deliverable. It does not claim improved reliability without evidence.
Before
Helped with monthly reporting.
After
Compiled monthly expense records and flagged missing receipts for the finance lead.
Why it works: The reader can see the contribution without inferring ownership of the entire reporting process.
Use metrics when you know what they mean
A number should have a source and a clear definition. A ticket count, recorded processing time or documented project scope may be useful. Ask what was measured, over which period and whether the outcome can fairly be attributed to your work. Avoid turning a rough impression into an exact percentage.
If records are unavailable, describe the action and deliverable. 'Documented the onboarding checklist for new volunteers' is a useful statement without a claim that onboarding became faster. Do not insert a placeholder metric into a resume you are about to send.
Choose bullets for the application, then verify them
A resume is not a complete task diary. Choose examples that help a reader assess the role you are applying for. If the posting asks for customer communication, a well-described support task may be more useful than an unrelated administrative task.
Read each bullet aloud and ask whether you could explain it in an interview. Check the verb, the subject and the outcome separately. AI can make a sentence sound stronger while quietly changing 'helped' into 'led' or 'tested' into 'designed'; keep the accurate level of ownership.
- Does the verb match the work you personally performed?
- Are tools, numbers and outcomes supported by your records?
- Does the bullet add useful information beyond the job title?
Put these ideas into practice
Explore the AI resume builder
Start from scratch or upload your resume, refine the wording and choose a layout.
Try itEntry-level software engineer resume: example and writing guide
Write an entry-level software engineer resume using projects, coursework and transferable experience. Includes a fictional example and a review checklist.
Read moreHow to tailor your resume to a job description
Tailor your resume with a requirement-to-evidence checklist. Learn what to reorder, what to rewrite and how to handle requirements you cannot support.
Read moreHow to turn your resume into a tailored cover letter
Turn resume facts into a cover letter that explains fit for one job. Includes a fact-to-paragraph example, a complete fictional letter and a final checklist.
Read moreResume summary examples: how to write a professional summary
Write a resume summary that fits the job: a simple formula, fictional examples for experienced, entry-level and career-change resumes, and what to leave out.
Read more
Further reading
Independent career resources for further reading. Listing a source does not imply an endorsement of Resume Home.