Use action, scope, and evidence as a writing prompt
Ask three questions: What did I do? What makes the work specific? What changed, got completed, or became useful? Draft the full answer first, then remove words that repeat your job title or add no information.
Choose a verb that matches your responsibility. 'Led' means something different from 'supported' or 'contributed.' A modest, accurate statement gives you a stronger interview story than a claim you cannot explain.
[Action] [task or deliverable] across [scope], using [method] to achieve [supported outcome].
Without a measured outcome: [Action] [specific task] for [people or purpose], with [frequency, complexity, or responsibility].
IT support: show troubleshooting and follow-through
'Fixed computer problems' hides the issue types, users, and process. Specify the systems you actually supported and how you checked the fix. If you name a ticketing tool or identity platform, be ready to describe your work in it.
Before: Helped users with IT issues.
With a verified metric: Resolved an average of 30 Windows and account-access tickets each week, recording troubleshooting steps and confirming the fix with users.
Without a metric: Diagnosed Windows sign-in and printer issues through remote support, documented attempted fixes, and escalated unresolved access problems with clear case notes.
Customer service: describe the request and your response
Replace 'excellent customer service' with the channels, issues, and decisions involved. Show how you explained options, followed policy, or coordinated a resolution. Do not claim you retained a customer unless you have evidence of that outcome.
Before: Handled customer complaints.
With a verified metric: Handled approximately 40 phone and email inquiries per shift, explaining return options and recording agreed next steps in the CRM.
Without a metric: Reviewed order histories to resolve billing questions, explained available options, and coordinated unresolved cases with the fulfillment team.
Project work: make your ownership clear
Describe the deliverable, the constraint, and the piece you owned. Organizing status meetings is more useful context when the reader understands what those meetings helped the team decide. Keep shared results attributed to the team.
Before: Managed projects and attended meetings.
With verified scope: Coordinated a six-month portal rollout across three teams, tracking dependencies and preparing sponsor decisions on schedule changes.
Without a metric: Maintained the project risk register, flagged a vendor dependency, and helped the team resequence testing before handover.
What to write when you do not have numbers
Look for concrete details instead of estimating a percentage. Useful evidence includes the type of problem, an unusually complex request, a document someone could use, a responsibility you were trusted with, or a process you made repeatable.
For example, 'Created a password-reset guide used during new-hire onboarding' is specific without claiming the guide reduced tickets by an invented amount. If you only drafted the guide and it was not adopted, say 'Drafted' and describe its purpose.
- Scope: users, locations, systems, workstreams, or issue types.
- Frequency: daily reconciliation, weekly reporting, or seasonal onboarding, if accurate.
- Complexity: multiple stakeholders, an unusual fault, or a time-sensitive request.
- Deliverable: a checklist, resolved case, training session, report, or completed handover.
Check each bullet before adding it to your resume
All examples on this page are fictional. Use their structure, then substitute your own actions and evidence. Remove confidential details and distinguish individual work from group results.
Read the bullets together. If several say the same thing, keep the clearest one and use the space for a different skill. Put the examples most relevant to the target job near the top of each role. Keep tense and punctuation consistent, and check wrapping in the actual exported file.
- Is the first verb accurate for my role?
- Does the line explain something beyond my job title?
- Can I trace every number or outcome to evidence?
- Would I be comfortable discussing this example in an interview?
Written with AI assistance. Examples are fictional and are not customer resumes. Review facts and follow the specific employer's application instructions.