How to Write Resume Accomplishments With STAR
Need to turn a list of job duties into resume accomplishments? Start by comparing the job description’s requirements and ATS keywords with evidence from your actual experience. Then rewrite the relevant bullets to show what you did, what you owned, and what changed.
Quick answer: Use STAR to organize your experience, compress it into an action-and-result bullet, and include numbers only when your records support them.
At refresh.cv, we help you extract requirements and ATS keywords from a job description, compare them with your resume wording and experience evidence, and identify revision priorities. The same sequence works here: find relevant experience that your resume does not yet communicate, then describe it accurately.
Match job requirements to experience evidence
Suppose a hypothetical job posting calls for “customer inquiry analysis and operational improvement.” Break that into distinct requirements: identifying inquiry patterns and using that analysis to change an operating process.
MIT’s career center recommends starting with action verbs relevant to the posting and connecting the task with its result. Use MIT’s guidance on writing about skills and accomplishments to review your experience in these categories:
- Both the keyword and supporting experience are present: Clarify your method, responsibilities, and the result of the work.
- Relevant experience is present, but the keyword is missing: If you have records of categorizing inquiries, describe that action in job-relevant language such as “analyzed customer inquiry types.”
- Neither the keyword nor supporting experience is present: Do not copy the phrase into your resume. Look for other relevant work you actually performed.
We distinguish these same evidence states in our comparison workflow. Start with important requirements for which you have evidence but lack clear wording. Strengthen existing matches with specific actions, scope, and results. Do not add keywords for experience you do not have.
Build a factual draft before polishing the bullets
Check the employer’s required format and file type first. If no template is specified, choose one with clear sections, consistent dates, and enough room for readable accomplishment statements.
Start with these facts:
| Section | What to include first |
|---|---|
| Contact information | Name, reachable phone number and email, and a relevant portfolio when appropriate |
| Experience | Organization, role, employment dates, and relevant responsibilities or projects |
| Education | School, field of study, attendance or graduation status, and dates |
| Skills | Tools and technologies you have actually used, with the work or projects where you applied them |
If you are submitting separate documents, give each a distinct purpose. Use the resume for a concise summary of experience and key accomplishments, a detailed experience document for project context and execution, and a cover letter or application statement for your motivation and the significance of selected experiences. This is an editing approach, not a requirement to submit extra documents. Follow the employer’s requested questions and structure first.
Use STAR for notes, then compress the action and result
Harvard’s career center presents STAR as a structure for interview answers: Situation, Task, Action, and Result. Here, use Harvard’s STAR framework to organize your experience notes. Do not paste an entire interview response into a resume bullet.
- Situation: What problem existed?
- Task: What responsibility did you personally hold?
- Action: What did you analyze, create, or coordinate?
- Result: What was completed or implemented, and what change was confirmed?
For the customer inquiry example, your notes might read: repeated inquiries → assigned to categorize them → reviewed records and drafted standard responses → the team reviewed and adopted those responses.
Compress those notes into your action + the subject and scope + a confirmed result.
Check your contribution separately from the team’s outcome. Writing a document, reviewing it, and deciding to implement it are different responsibilities. Changing “participated in” to “led” is not a writing improvement unless you actually led the work.
Separate workload from improvement when adding numbers
Look through work reports, processing logs, and project documents for time periods, volumes, scope, and before-and-after metrics. For each number, note what it measures, the period it covers, and whether it reflects your own responsibilities or the team’s work.
The number of inquiries handled describes workload. A reduction in average handling time describes a change. Handling a large volume does not, by itself, demonstrate improved efficiency.
Before reporting an improvement rate, check that the comparison periods and metric definitions are consistent. Do not turn a team-wide result into an individual accomplishment.
MIT’s career center advises clearly describing your role and positive results when exact numbers are unavailable. Following MIT’s guidance on crafting an effective resume, describe a completed deliverable and where it was actually used instead of adding an unverified improvement percentage. Keep intended effects separate from confirmed outcomes.
Before and after: rewrite a customer support duty
The experiences and numbers below are hypothetical writing examples, not an actual applicant’s accomplishments. Assume the posting asks for customer inquiry analysis and operational improvement.
When before-and-after measurements are available
Suppose the records show that you categorized recurring inquiries and drafted standard responses, which the team adopted. During the month before adoption and the month after, average handling time for the same inquiry type was recorded as 20 minutes and 15 minutes, respectively.
Before: “Responsible for responding to customer inquiries.”
After:
Categorized recurring customer inquiries and drafted standard responses adopted by the team. Average handling time for that inquiry type fell from 20 to 15 minutes across the one-month periods before and after adoption.
The rewrite separates your action, the team’s adoption, and the observed change. It also identifies the customer support context, the recurring-inquiry problem, your responsibilities, and the comparison scope.
If other operational changes occurred during that period, these records alone do not establish that your work was the sole cause of the reduction.
When adoption is confirmed but no improvement metric is available
Before: “Responsible for responding to customer inquiries.”
After:
Categorized recurring customer inquiry records and drafted standard responses incorporated into the team’s customer support documentation after review.
If a reduction in handling time has not been confirmed, do not add “improved support efficiency.” The categorization work and adoption into documentation are concrete results on their own.
You can apply the same questions to coursework or student organization projects if you do not have professional experience. For example, replace “Helped run events” with “Categorized event inquiries and revised the information sheet for inclusion in the next event announcement,” but only if you actually performed those actions and the revision was used.
Put the most relevant evidence first
If you have relevant professional experience, consider leading with that experience and its key accomplishments. If not, consider placing relevant projects and learning experiences earlier.
Harvard’s career center recommends ordering sections by importance, listing the most recent experience first within each section, and checking formatting after converting to PDF. Harvard’s resume structure and formatting guidance also notes differences between countries. Follow the requirements of the employer receiving your application rather than treating one format as universal.
Set the length according to the employer’s limits and the amount of relevant experience you need to communicate. Do not give every duty equal space. Keep key actions and results in the resume, and reserve detailed project explanations for a separate document if one is requested.
Open the final file and check that line breaks do not split sentences awkwardly or separate an action from its result.
Check accuracy before submitting
- Replace vague duties: Add your actual action and a confirmed result to bullets that stop at “responsible for.”
- Verify numbers: Remove or replace figures whose records, definitions, or comparison periods you cannot explain.
- Separate contributions: Distinguish your responsibilities from team results. Leave out job-posting keywords that do not reflect your experience.
- Inspect the final file: Check contact information, employment dates, spelling, and formatting in the version you will submit.
Put the job posting beside your experience records and revise one accomplishment bullet now. To use our workflow, enter the job description in refresh.cv and compare its requirements with your resume evidence. Prioritize truthful revisions that make relevant experience easier to see.
Our resume quality assessment, covering specificity, accomplishments, wording, and grammar, is separate from job-specific keyword fit. Neither represents your hiring probability or an employer’s actual ATS screening result.
0
Get new posts by email
Subscribe to get new articles on resumes, interviews, career moves, and career growth.