Resume bullet points for software engineers, with examples
By Mubeen Jawed, founder of ResumeForDev · Updated
Write each software engineer resume bullet as: action verb + what you built or changed + the technology + the scale + the measurable result. For example: “Migrated nightly batch jobs from cron to Airflow on AWS, cutting failed runs from ~12 a month to 1 and saving the data team 6 hours a week.” Aim for 1–2 lines, one idea per bullet, and a number in most of them.
Key points
- Start with a strong verb: built, migrated, cut, shipped, automated, designed.
- Name the system and the stack, so the reader knows what you actually touched.
- Add scale (users, requests, rows, services) and a before/after where you have one.
- Cut filler: “responsible for”, “worked on”, “helped with”, “leveraged”.
The formula
| Part | Question it answers | Example |
|---|---|---|
| Verb | What did you do? | Rebuilt |
| Thing | What did you build or change? | the checkout service's payment retry logic |
| Tech | With what? | in Go with a Redis-backed queue |
| Scale | How big was it? | handling 40k orders a day |
| Outcome | What changed? | reducing failed payments by 18% |
Before and after, by role
Backend
Before:Responsible for maintaining APIs and improving performance.
After:Added cursor pagination and a read replica to the orders API in Django and PostgreSQL, dropping p99 latency from 2.1s to 340ms at 300 requests/second.
Frontend
Before:Worked on the frontend using React.
After:Split the React and TypeScript onboarding flow into route-level chunks and lazy-loaded the chart library, cutting initial JavaScript from 1.4MB to 480KB and raising mobile Lighthouse performance from 52 to 91.
DevOps and platform
Before:Helped with CI/CD and cloud infrastructure.
After:Moved 14 services from hand-built EC2 hosts to Terraform-managed ECS, and added GitHub Actions deploys that took releases from a 2-hour manual process to 12 minutes.
Data and ML
Before:Built machine learning models for the business.
After:Trained a gradient-boosted churn model in Python (XGBoost) on 2.3M customer records and shipped it as a weekly batch job, which the retention team used to target 8,000 at-risk accounts a month.
Student or side project
Before:Made a web app for students at my university.
After:Built a course-review site in Next.js and Supabase with university SSO login; 1,900 students signed up in the first semester and posted 4,300 reviews.
Verbs that work, phrases to cut
| Instead of | Try |
|---|---|
| Responsible for | Owned, ran, maintained |
| Worked on | Built, shipped, rebuilt, implemented |
| Helped with | Contributed X to, paired on, reviewed |
| Leveraged / utilized | Used, built with (or just name the tool) |
| Improved | Cut, reduced, raised, doubled (with the number) |
| Was involved in | Say what you specifically did |
ResumeForDev's score flags weak openers and buzzwords automatically. Its writing-quality check looks for bullets that start with an action verb, stay readable in length, and avoid phrases like “responsible for” and “leveraged”.
How to find the numbers you've forgotten
- Dashboards: Datadog, Grafana, Sentry, CloudWatch, Lighthouse reports.
- Old pull requests and their descriptions: the benchmark is often in there.
- Release notes, incident postmortems, sprint demos.
- Product analytics: daily or monthly active users, conversion.
- Ask a former teammate. They often remember the before/after better than you.
This is what ResumeForDev's follow-up interview is for. After you describe your work, it asks targeted questions like “faster by how much?” or “how many people use that dashboard?”. Your answers become the only figures the writer is allowed to use.
Frequently asked questions
- How long should a resume bullet be?
- One to two lines on the page, roughly 18–40 words. Longer than that and it's probably two achievements that should be split.
- Should every bullet have a number?
- Most should, not all. Aim for a number or a clear scope in the majority of bullets. Forcing a number into every one leads to vague or made-up figures.
- Can I use AI to write my resume bullets?
- Yes, as long as the facts are yours. General chatbots often add impressive-sounding metrics you never gave them. Check every number, or use a tool that only writes from your own answers.
- How many bullet points per job on a resume?
- Three to five for your recent or most relevant roles, one or two for older ones. Projects usually get two or three. Fewer strong bullets beat more weak ones.
- Should I use the STAR or XYZ method for resume bullets?
- Both point at the same thing: what you did and what changed. Google's XYZ format (accomplished X, measured by Y, by doing Z) fits a one-line bullet well. STAR is better for interview answers.
Keep reading
- GuidesHow to write a software engineer resumeStep by step: how to write a one-page software engineer resume, with section order, a bullet formula, skills, projects, resume examples, and what ATS software and recruiters check.Read
- CompareResumeForDev vs. ChatGPT for writing a developer resumeShould you write your software engineer resume with ChatGPT or a dedicated tool? A fair comparison of accuracy, formatting, ATS checks and effort.Read
- GuidesHow to write a computer science resume as a student, intern or new gradHow CS students and new grads should write a one-page computer science resume with little or no experience: education, projects, internships, skills, hackathons, and examples.Read
- GuidesHow to write the skills section of a software engineer resumeWhat skills to put on a software engineer resume, how many to list, how to group technical skills, and examples for front end, backend, full stack, DevOps and data roles.Read
- GuidesResume summary examples for software engineersWhat a resume summary is, when a developer resume needs one, and copyable professional summary examples for backend, frontend, new grad, senior, career-change and architect roles.Read