By The advice is always the same. Quantify your bullets. Show impact. Use numbers. Then you look at your resume, which says member of the finance club and worked part time at a grocery store, and none of that advice applies to anything you have actually done.
It does apply. Nobody hands a student a metric. You still have plenty worth counting, and the gap between an invisible bullet and a strong one is usually one specific detail you left out because it felt too small to mention.
Twelve rewrites below. Find the one closest to yours and copy the structure.
What a strong bullet is actually made of
Three parts. Most student bullets stop after the first one.
- The action. What you did, in a specific verb. Built, rebuilt, ran, negotiated, trained, cut, automated.
- The mechanism.How, or with what. This is where your tools, methods, and the posting's keywords live.
- The result. What was different afterwards, with a number if one exists.
Missing the third part is why bullets feel flat. Compare:
- Managed social media for the club. Action only. Tells the reader you were assigned something.
- Managed the club Instagram, posting three times a week. Action plus mechanism. Better, still no outcome.
- Grew the club Instagram from 340 to 1,900 followers over two semesters with a three post per week schedule, which filled our two largest events to capacity for the first time. All three. Now the reader knows you were good at it.
A responsibility says what you were told to do. A result says whether you were any good at it. Only one of those gets you a call.
Where to find numbers when nobody gave you any
This is the actual blocker for most people, so be systematic about it. For any thing you did, run through these six questions. One of them almost always produces a number.
- How many people? Team size, members served, students taught, customers per shift, event attendees.
- How many things? Orders, tickets, files, pages, applications processed, items tracked.
- How often, for how long? Weekly for eight months. Three shifts a week across two summers.
- How much faster or cheaper? Before and after. Two days down to forty minutes. Twelve hours a week down to two.
- How much bigger? Growth in members, followers, signups, attendance, budget managed.
- How much less of something bad? Fewer errors, fewer no shows, fewer support questions, fewer manual steps.
A reasonable estimate of something that genuinely happened is fine. If you handled roughly sixty orders a shift, write sixty. What is not fine is inventing a percentage you never measured, because you will be asked about it and the answer will show.
Twelve rewrites, line by line
Part time and service work
Worked as a cashier at a grocery store. Responsible for handling transactions and customer service.
Handled roughly 60 transactions per shift across 3 shifts a week for 14 months, and trained 4 new cashiers on the POS system during back to school hiring.
Training people is a real responsibility and reads as trust. Almost nobody puts it on the resume.
Server at a restaurant. Duties included taking orders and helping customers.
Ran a 6 table section on Friday and Saturday peak, averaging 90 covers a night, while covering host duties during a 3 month staffing shortage.
Peak shift, section size, and covering a gap all signal reliability under pressure, which is what a hiring manager is actually screening for.
Worked at a summer camp with kids.
Led a group of 22 campers aged 8 to 11 for 7 weeks, planned the daily schedule, and handled parent communication for the group with zero escalations to the director.
Zero escalations is a number. Negative results count.
Clubs, societies, and volunteering
Member of the university finance club. Attended weekly meetings and helped with events.
Ran sponsorship outreach for the finance club, closing 4 new sponsors worth $6,200 and funding the first paid speaker event in the club's history.
If you were genuinely only a member, say what you did as a member. Attended is not a bullet, it is a line in an interests section.
Volunteer at a local food bank on weekends.
Coordinated weekend intake at a food bank for 9 months, reorganising the sorting process so a 5 person team cleared the same volume in about half the time.
Process improvements count everywhere. You do not need a job title to have fixed something that was slow.
Treasurer of the student engineering society.
Managed a $14,000 annual budget across 11 events as society treasurer, moving reporting from paper receipts to a shared spreadsheet and closing the year without a reconciliation gap for the first time in three years.
Budget size is the single most under used number on student resumes.
Projects and coursework
Built a personal website using HTML and CSS.
Built and deployed a portfolio site on Next.js and Vercel scoring 98 on Lighthouse performance, and wrote the deployment guide two classmates then used for their own sites.
A real deployment, a real score, and someone else using your work. All three raise it above a tutorial.
Group project for my database class where we built an inventory system.
Designed the PostgreSQL schema for a 4 person inventory system project, including the indexing that took our worst case query from 3.2s to under 200ms.
Name your specific contribution. Group project with no named role reads as having been carried.
Did a machine learning project on housing data.
Trained a gradient boosting model on 21,000 housing records in Python and scikit-learn, reaching 0.89 R squared, then wrote up why the two features I dropped were leaking target information.
Explaining what you got wrong and why is the strongest possible signal for a technical role. It reads as someone who actually understands the work.
Internships and co-op
Software engineering intern. Worked on the front end team and fixed bugs.
Shipped 14 pull requests to a React application used by about 30,000 monthly users, including a form validation rewrite that cut support tickets on that flow by roughly a third.
Ask your former manager for the numbers if you do not have them. Most will tell you and it is a normal thing to ask.
Marketing intern. Helped with social media and email campaigns.
Wrote and scheduled 26 email campaigns to a 12,000 person list, running subject line A/B tests that lifted average open rate from 19% to 27% over the term.
A/B testing is a keyword. Marketing recruiters search for it and most interns who did it never write it down.
Data analyst intern. Created reports for the team using Excel and SQL.
Automated a weekly reporting pack in SQL and Excel that a 9 person team had been building by hand, cutting it from about 6 hours a week to 20 minutes and removing three recurring copy paste errors.
Time you gave back to other people is the most legible form of impact there is.
Verbs that work and openers to delete
The first three words of a bullet are the highest value real estate on the line, because the left edge is where the eye lands on a scan. Do not spend them on nothing.
Delete these openers permanently: responsible for, helped with, worked on, assisted in, participated in, was tasked with, involved in, duties included.
Every one of them is replaceable by the verb that comes after it. Just start there.
| What you did | Verbs worth using |
|---|---|
| Made something new | Built, designed, launched, shipped, wrote, prototyped |
| Made something better | Rebuilt, cut, reduced, streamlined, automated, refactored |
| Ran something | Led, coordinated, managed, scheduled, ran, owned |
| Worked with people | Trained, negotiated, presented, onboarded, advised |
| Figured something out | Analysed, diagnosed, investigated, modelled, tested |
One caution. Do not reach for an inflated verb over an honest one. If you fixed a bug, say fixed. Spearheaded a bug fix is worse than fixed, because a reader can tell.
How many bullets, and in what order
- Three to five for your most recent and most relevant role.
- Two to three for older or less relevant roles.
- One is fine for something you are including only for continuity.
Within a role, strongest first. Not chronological, not by how much time it took. The first bullet of your top role is one of the four or five things that actually gets read on a first pass, so it should be the single best thing you did.
And cut ruthlessly. If a bullet has no number, no tool, and no outcome, it is taking up a line that a better version of another bullet could use. Six weak bullets do not add up to three strong ones. They subtract from them.
Once the bullets are solid, the next question is which of them to lead with for a specific posting. That is in how to tailor your resume to a job description, and if you want the terms to work into them, start with the ATS keywords guide.
Common questions
- What do I write if I have never had a real job?
- Write about coursework, projects, clubs, volunteering, and part time work as if they were jobs, because structurally they are. You made decisions, you used tools, and something changed as a result. That is all a bullet is. A class project with a real stack and real users is stronger than a summer role you cannot say anything specific about.
- How do I quantify a bullet when nobody gave me metrics?
- Count what you touched. How many people, how many items, how many hours, how often, over what period, how much faster than before. You do not need company revenue. Forty members, six events, three hours per week, twelve percent fewer errors are all legitimate and all verifiable by you.
- How many bullets should each role have?
- Three to five for a relevant recent role, two to three for older or less relevant ones. Six weak bullets are worse than three strong ones, because the reader is scanning and the weak ones dilute the strong ones.
- Is it lying to estimate a number I did not formally measure?
- No, as long as it is a reasonable estimate of something that actually happened and you could defend it in an interview. Saying you handled roughly sixty customer orders per shift when that is genuinely the scale is honest. Inventing a thirty percent revenue lift you never measured is not.
- Should every bullet start with an action verb?
- Start with the strongest specific word available, which is usually a verb. Avoid the filler openers: responsible for, helped with, worked on, assisted in. Those spend the most valuable part of the line, the left edge where the eye lands, on nothing.
Stop retyping the same application.
Save your answers once. ApplyAgents fills Workday, Greenhouse, Lever, and more.
Get 3 autofills freeNo credit card. You always click Submit.