The formula before the examples
Every strong bullet does three things: what you did, how you did it, and what happened because of it, with a number. "Improved performance" tells a recruiter nothing. "Cut page load time from 2.1s to 640ms by lazy-loading images, reducing bounce rate 18%" tells them you can be trusted with a real problem. If you're missing the number, that's the thing to go dig up before you're missing the interview.
Technical / data
- Built a Python script to deduplicate 40,000+ rows of customer records using fuzzy matching, cutting manual cleanup time from 3 days to 20 minutes
- Migrated a 12-table MySQL schema to PostgreSQL with zero downtime, writing the rollback plan the team still uses
- Trained a logistic regression model on 6 months of support-ticket data to flag likely churn, catching 31% more at-risk accounts than the existing rule-based system
- Automated a weekly sales report with a SQL + Sheets pipeline, saving the analytics team roughly 5 hours a week
- Debugged a memory leak in a Node.js service causing daily restarts, tracing it to an unclosed event listener and cutting restarts to zero
Leadership / campus orgs
- Recruited and onboarded 14 new members for a student org, redesigning the intake process to cut ghosting from 40% to 12%
- Managed a $3,200 event budget for a spring conference, coming in 9% under budget while doubling attendance from the year before
- Ran weekly 1:1s with 5 first-year mentees, three of whom landed their first internship the following summer
- Resolved a funding dispute between two committees by proposing a shared-cost model both sides adopted for the rest of the year
Ops / process
- Rebuilt the intake form for a campus tutoring program, cutting average signup-to-first-session time from 9 days to 2
- Standardized onboarding docs for a 6-person team, cutting new-member questions in Slack by roughly half
- Audited 200+ inventory records for a campus makerspace and caught $1,100 in unaccounted equipment
Customer / client-facing
- Handled 30+ support tickets a week as a part-time rep, maintaining a 4.8/5 satisfaction score across two semesters
- Ran user interviews with 15 students to inform a class project's feature list, presenting findings that changed the team's top priority
No experience yet? Use what you actually did
You don't need a job title to have done real work. A class project where you built something, a hackathon, a research assistantship, even a personal project you shipped, all of it counts if you can describe the decision you made and what happened. "Built a scheduling app for my dorm's laundry room used by 40 residents" is a real bullet. Don't wait for an internship to start writing bullets; start with what you're doing right now.
Where do the numbers come from if you never tracked them?
Estimate conservatively and say so honestly if asked in an interview. "Roughly 20 hours a week" or "about a dozen teammates" is fine. Recruiters aren't fact-checking your club's Slack, they're checking whether you think in outcomes instead of tasks.