Writing Effective Bullet Points
Bullet points are the core of your resume. Each one needs to convey impact clearly and concisely. This guide teaches you how to write bullets that get noticed.
The STAR Format for Bullets
STAR (Situation, Task, Action, Result) isn’t just for interviews — it’s the framework for writing powerful resume bullets.
For resume bullets, the format is condensed:
Action + Context/Task + Result/Impact
You don’t need all three in every bullet, but aim for at least two.
The Formula
[Action Verb] + [What You Did] + [Technology/Method] + [Quantified Result]
Examples
Weak: “Worked on the backend API” Strong: “Designed and implemented RESTful API endpoints using Node.js and Express, serving 10K+ daily active users with 99.9% uptime”
Weak: “Helped with testing” Strong: “Automated regression testing suite using pytest and GitHub Actions, reducing QA time by 60% and catching 15+ bugs before production”
Weak: “Made the website faster” Strong: “Optimized database queries and implemented Redis caching, reducing average page load time from 3.2s to 0.8s”
Action Verbs
Start every bullet with a strong action verb. Avoid weak verbs like “helped,” “worked on,” “was responsible for.”
Technical Verbs
| Category | Verbs |
|---|---|
| Building | Built, Developed, Created, Implemented, Designed, Architected, Engineered |
| Improving | Optimized, Refactored, Improved, Enhanced, Streamlined, Accelerated |
| Leading | Led, Directed, Spearheaded, Drove, Owned, Managed, Coordinated |
| Analyzing | Analyzed, Investigated, Diagnosed, Evaluated, Assessed, Researched |
| Scaling | Scaled, Migrated, Transitioned, Expanded, Distributed, Parallelized |
| Collaborating | Collaborated, Partnered, Coordinated, Aligned, Integrated, Unified |
| Reducing | Reduced, Eliminated, Minimized, Consolidated, Simplified, Automated |
| Delivering | Delivered, Shipped, Launched, Deployed, Released, Published |
Verbs to Avoid
- ❌ “Helped” → ✅ “Contributed to,” “Supported,” “Enabled”
- ❌ “Worked on” → ✅ “Developed,” “Built,” “Implemented”
- ❌ “Was responsible for” → ✅ “Owned,” “Led,” “Managed”
- ❌ “Assisted” → ✅ “Collaborated on,” “Co-developed”
- ❌ “Participated in” → ✅ “Contributed to,” “Drove”
Quantified Impact
Numbers make your bullets concrete and memorable. Always quantify when possible.
What to Quantify
| Metric | Example |
|---|---|
| Scale | Users, requests, data volume, team size |
| Performance | Latency reduction, speed improvement, throughput |
| Efficiency | Time saved, cost reduced, process improvement |
| Quality | Bug reduction, uptime, test coverage |
| Scope | Number of features, services, APIs, endpoints |
| Business | Revenue impact, conversion rate, user growth |
Before/After Examples
Without numbers: “Improved application performance by caching frequently accessed data”
With numbers: “Reduced API response time by 45% (from 800ms to 440ms) by implementing Redis caching for 50+ frequently accessed database queries”
Without numbers: “Built a notification system for the mobile app”
With numbers: “Designed and built a push notification system using Firebase Cloud Messaging, delivering 100K+ daily notifications to 25K+ mobile users with 99.8% delivery rate”
Without numbers: “Led the migration to a new database”
With numbers: “Led migration of 500GB PostgreSQL database to AWS RDS, coordinating across 3 teams and completing the zero-downtime cutover 2 weeks ahead of schedule”
When You Don’t Have Exact Numbers
Estimate conservatively and use qualifiers:
- “Processing ~10K requests/day” (approximate)
- “Reduced build time from ~10 minutes to ~2 minutes” (approximate)
- “Serving the team of 8 engineers” (exact team size)
- “Reducing manual testing effort by approximately 50%” (estimated)
Never fabricate numbers. Estimates are fine; lies are not.
Bullet Point Structure Patterns
Pattern 1: Action + What + How + Result
[Verb] [what you built/did] using [technology/method], resulting in [quantified outcome]
Example: “Built a real-time analytics dashboard using React and D3.js, enabling the marketing team to track 15+ KPIs and reducing report generation time from 2 hours to 5 minutes”
Pattern 2: Problem + Action + Result
[Identified/Addressed problem] by [action taken], [quantified result]
Example: “Addressed high memory usage in production servers by profiling with pprof and optimizing Go goroutine management, reducing memory consumption by 35% and eliminating OOM crashes”
Pattern 3: Scope + Action + Impact
[Verb] [scope/Scale] [what you did] across [context], [result]
Example: “Standardized API response formats across 12 microservices, reducing client-side error handling complexity and decreasing integration bugs by 40%”
Pattern 4: Collaboration + Action + Result
Collaborated with [team/stakeholders] to [action], [result]
Example: “Collaborated with product and design teams to define and implement a new onboarding flow, increasing user activation rate by 22% within the first month”
Before/After Makeover Gallery
Internship Bullet
Before: “Worked on the company website using React”
After: “Developed 5 responsive React components for the customer portal, improving mobile usability scores from 62 to 94 (Lighthouse) and reducing bounce rate by 18%”
Project Bullet
Before: “Made a to-do list app with a database”
After: “Built a full-stack task management application with React, Node.js, and PostgreSQL featuring real-time sync, drag-and-drop UI, and JWT authentication — deployed on Vercel with 500+ users”
Research Bullet
Before: “Helped professor with machine learning research”
After: “Implemented transformer-based sentiment analysis model in PyTorch achieving 92% accuracy on IMDB dataset, contributing to published research paper at ACL 2026 Workshop”
Leadership Bullet
Before: “Was president of computer science club”
After: “Led 120-member Computer Science club as President, organizing 8 workshops and 2 hackathons per semester, growing membership by 40% year-over-year”
Open Source Bullet
Before: “Contributed to an open source project”
After: “Submitted 5 merged PRs to Apache Airflow fixing scheduler race conditions, reviewed 15+ community PRs, and authored documentation for the new TaskFlow API”
Common Bullet Point Mistakes
1. Starting with “I”
Resume bullets are implied first-person. Never start with “I.”
❌ “I developed a web application…” ✅ “Developed a web application…”
2. Being Vague
❌ “Worked on various projects” ✅ “Led development of 3 customer-facing features across 2 product lines”
3. Listing Responsibilities Instead of Achievements
❌ “Responsible for code reviews” ✅ “Conducted 200+ code reviews, establishing team standards that reduced production bugs by 30%”
4. Too Many Bullets
3-5 bullets per role. Older/less relevant roles can have 2-3.
5. Repeating the Same Action Verb
Vary your verbs across bullets. Don’t start three bullets with “Developed.”
6. Including Irrelevant Details
❌ “Attended daily standup meetings” ✅ Focus on what you built, shipped, or improved
7. Passive Voice
❌ “The system was redesigned to handle more traffic” ✅ “Redesigned the system architecture to handle 3x traffic growth”
Bullet Point Templates
Software Engineering Internship
- [Action verb] [feature/system] using [tech stack], [quantified impact]
- [Improved/Reduced] [metric] by [amount] through [specific technique]
- Collaborated with [team size] [team type] to deliver [deliverable] within [timeframe]
- Wrote [number] unit/integration tests achieving [coverage %], ensuring [quality outcome]
Personal/Academic Project
- Built [application type] with [tech stack] supporting [scale/feature]
- Implemented [technical feature] reducing [metric] by [amount]
- Deployed on [platform] with [reliability metric] uptime over [timeframe]
- Open-sourced project garnering [stars/forks/downloads] on GitHub
Research Experience
- [Researched/Developed] [topic] using [methodology], achieving [result]
- Published/presented findings at [venue/conference]
- Analyzed [dataset size] dataset using [tools], discovering [insight]
- Collaborated with [number] researchers across [institutions]
Practice Exercise
Take your current resume bullets and rewrite each one:
- Start with a strong action verb
- Add specific technologies
- Include at least one number
- End with impact or result
Then have someone review them. If they can’t tell what you actually did, rewrite.
Key Takeaways
- Lead with action — Strong verb + specific achievement
- Quantify everything — Numbers catch the eye
- Show impact — What changed because of your work?
- Be specific — Name technologies, tools, metrics
- Be concise — Every word should earn its place
- Tailor to the role — Emphasize relevant experience