These resume bullet points examples cover ten kinds of role in India, from software engineer to fresher. Each one has a number in it, but not a real one. Where a result goes, you will see a placeholder such as [X]% or [N] users, because a sample figure copied into your resume is a claim you will have to defend in an interview.
Write them in any editor. The free resume builder is free for the editing and export, and its AI bullets (a Pro feature, run on credits) draft bullets that leave [X] placeholders for you to fill in, which is the same rule this post uses.
The formula: verb, what you did, the number
A bullet that works has three parts, in this order:
- A verb that says what you did, in the past tense for finished work and the present tense for your current role: built, cut, ran, closed, filed.
- The thing it acted on, specific enough that a stranger can picture it: the UPI payment flow, the monthly bank reconciliation, the onboarding for new joiners.
- The number, with its unit: a count, a percentage, rupees, hours, or a before and after.
Take a line most resumes carry: “Helped with the company careers page”. Rewritten, it becomes “Redesigned the careers page, raising applications by [X]% across [N] monthly visitors”. The first says you were present. The second says what happened while you were there.
You do not need all three parts in every line, and you do not need a number in every bullet. The top two bullets for each role are the ones to quantify first, because that is where a skimming reader is most likely to look. The step-by-step version of that is in how to improve your ATS score. For the verb itself, action verbs for your resume lists them by role, with the weak openers to drop.
Where the numbers come from when you think you have none
Almost everyone has numbers. They are just not written down. These are the five places to look:
- How many. Tickets, calls, leads, invoices, candidates, test cases, releases, customers, users.
- How long or how often. Hours saved a week, days to close, how often a report ran, the time it took before and after.
- How much money. Revenue closed, cost cut, budget managed, spend saved. In India this reads best in rupees, lakh or crore, in the unit your company reported it.
- How big. Team size, number of cities or branches, number of services, number of people who used your work.
- Before and after. The strongest form: from [X] to [Y]. If you only know one side, say the one you know.
Where do you find them? In old sprint boards and ticket exports, in monthly reports and review decks, in sales sheets, in Tally or Excel files, in email threads about a launch. If a figure is approximate, say so: “about [N]” is honest, a wrong exact number is not.
The placeholder rule. When you do not have the figure yet, write the bullet with a bracket where the number goes: [X]%, [N] users, ₹[X] lakh. When a bullet needs several counts, number them [N1], [N2], and use [X] and [Y] for a before and after. Keep it in your draft, fill in the real number, then search your file for ”[” before you send it. The free builder’s resume check flags any [X] left in a field, and in any editor a search does the same job.
No number at all? The answer for “how to quantify a resume without numbers” is to use scope you can defend: the size of the team, how many people used the thing, how often it ran. If even that is missing, write a plain, true outcome, such as “adopted as the team’s standard template”, and move on. A true line with no number beats a number you invented.
40 resume bullet points examples by role
The 40 numbered bullets are fill-in templates: every figure is a placeholder. Replace each with your own real number, or cut the bullet. For each role, the first bullet is the rewrite of the weak line above it. After each role there is one finished example, so you can see what a filled-in bullet reads like. Those figures are illustrative, invented for this example, and are not real results. Do not copy them.
Software engineer
The numbers live in latency, traffic, test coverage and delivery speed.
Weak: Worked on the backend of the order service.
- Reduced p95 API latency from [X] ms to [Y] ms by adding Redis caching to the order service, which handles [N] requests a day
- Cut checkout drop-off by [X]% by rebuilding the UPI payment flow in React for [N] customers a month
- Shipped [N1] features across [N2] sprints in a team of [N3] engineers, with [X]% test coverage on the new modules
- Moved [N] services from a monolith to microservices on AWS, cutting deploy time from [X] minutes to [Y]
Finished example (illustrative, figures invented for this example, not a real result): Reduced p95 API latency from 480 ms to 190 ms by adding Redis caching to the order service, which handles 120,000 requests a day
Data analyst
The numbers live in hours saved, rows handled and decisions changed.
Weak: Made dashboards for the sales team.
- Built a Power BI dashboard used by [N] regional managers, replacing a weekly report that took [X] hours to prepare
- Found that [X]% of cart abandonment came from one checkout step, and led the fix, recovering about ₹[Y] lakh a month
- Wrote SQL queries over [N] million rows to track churn, cutting monthly reporting time by [X]%
- Ran an A/B test on [N] users that raised conversion from [X]% to [Y]%
Finished example (illustrative, figures invented for this example, not a real result): Built a Power BI dashboard used by 14 regional managers, replacing a weekly report that took 6 hours to prepare
QA and test
The numbers live in test cases, defects found early and regression time.
Weak: Tested the mobile app before release.
- Wrote [N1] automated test cases in Selenium covering [X]% of the regression suite, cutting a full regression run from [Y] days to [Z] hours
- Logged and triaged [N1] defects across [N2] releases, [X]% of them found before production
- Reduced production bugs by [X]% over [N] quarters by adding API tests with Postman and RestAssured to the CI pipeline
- Tested on [N1] device and OS combinations, including low-end Android phones, ahead of a launch to [N2] users
Finished example (illustrative, figures invented for this example, not a real result): Wrote 220 automated test cases in Selenium covering 65% of the regression suite, cutting a full regression run from 3 days to 5 hours
DevOps and cloud
The numbers live in deploy time, uptime and cloud spend.
Weak: Managed the deployment process.
- Cut deployment time from [X] minutes to [Y] by building a CI/CD pipeline in Jenkins for [N] services
- Lowered monthly AWS spend by ₹[X] lakh ([Y]%) by right-sizing [N] instances and switching off non-production environments at night
- Kept uptime at [X]% across [N] production services with Prometheus alerts and an on-call runbook
- Automated [N] environments with Terraform, so a new one takes [X] minutes instead of [Y] days
Finished example (illustrative, figures invented for this example, not a real result): Cut deployment time from 35 minutes to 9 by building a CI/CD pipeline in Jenkins for 12 services
Sales and business development
The numbers live in revenue, pipeline, conversion and deal size.
Weak: Responsible for selling to enterprise clients.
- Closed ₹[X] crore in new business in [N] months against a target of ₹[Y] crore
- Grew the pipeline from [N1] to [N2] qualified leads a quarter by building an outreach sequence for mid-size accounts
- Converted [X]% of [N] demos into paid accounts, against a team average of [Y]%
- Won [N] enterprise accounts in [city or region], with an average deal size of ₹[X] lakh
Finished example (illustrative, figures invented for this example, not a real result): Closed ₹2.4 crore in new business in 9 months against a target of ₹2 crore
HR and recruitment
The numbers live in time to hire, offer acceptance and attrition.
Weak: Handled hiring and onboarding.
- Filled [N1] roles in [N2] months, bringing the average time to hire from [X] days to [Y]
- Screened [N1] resumes a month from Naukri and LinkedIn and ran [N2] interviews, with [X]% of offered candidates joining
- Cut first-year attrition from [X]% to [Y]% by redesigning onboarding for [N] new joiners a quarter
- Processed payroll for [N1] employees across [N2] locations, including PF and ESI filings, with [N3] late submissions in [N4] months
Finished example (illustrative, figures invented for this example, not a real result): Filled 38 roles in 6 months, bringing the average time to hire from 45 days to 31
Marketing
The numbers live in traffic, cost per lead and conversion.
Weak: Managed social media and ads.
- Grew organic traffic from [N1] to [N2] monthly visits in [N3] months by publishing [N4] SEO articles
- Cut cost per lead from ₹[X] to ₹[Y] by reworking Google Ads and Meta campaigns on a ₹[Z] lakh monthly budget
- Raised email open rate from [X]% to [Y]% by segmenting a list of [N] subscribers
- Launched [N1] campaigns that brought in [N2] sign-ups, [X]% of them through WhatsApp referrals
Finished example (illustrative, figures invented for this example, not a real result): Grew organic traffic from 8,000 to 21,000 monthly visits in 7 months by publishing 30 SEO articles
Finance and accounts
The numbers live in close time, filings, receivables and reconciliations.
Weak: Prepared monthly accounts and filed returns.
- Closed the monthly books in [X] working days instead of [Y] by automating bank reconciliation in Tally and Excel
- Filed GST returns for [N1] entities on time for [N2] consecutive months
- Reduced overdue receivables by ₹[X] lakh over [N1] quarters by following up [N2] outstanding invoices
- Cut audit queries by [X]% by reconciling [N] ledgers before the statutory audit
Finished example (illustrative, figures invented for this example, not a real result): Closed the monthly books in 6 working days instead of 9 by automating bank reconciliation in Tally and Excel
Customer support and operations
The numbers live in ticket volume, response time and dispatch speed.
Weak: Handled customer queries.
- Resolved [N] tickets a week with a first-response time of [X] minutes, against a target of [Y]
- Raised customer satisfaction from [X]% to [Y]% by writing [N] help articles for the most repeated issues
- Cut order dispatch time from [X] hours to [Y] at a warehouse handling [N] orders a day
- Trained [N] new support agents and cut their ramp-up time from [X] weeks to [Y]
Finished example (illustrative, figures invented for this example, not a real result): Resolved 310 tickets a week with a first-response time of 12 minutes, against a target of 20
Fresher (projects and internships)
Without a job, the numbers live in users, scale, time and results of a project.
Weak: Did an internship and learned a lot.
- Interned for [N1] months on a payments team, fixing [N2] bugs in a React front end and merging [N3] pull requests
- Built a Flask and React expense tracker used by [N1] classmates, handling about [N2] entries a day at peak
- Placed in the top [N1] of [N2] teams at a college hackathon with an app that [what it did]
- Led a team of [N1] students to run a tech fest with [N2] attendees and ₹[X] lakh in sponsorship
Finished example (illustrative, figures invented for this example, not a real result): Built a Flask and React expense tracker used by 40 classmates, handling about 150 entries a day at peak
If you are a fresher, resume for freshers by branch has more on which projects to show. A bullet that reads well also needs to match the job: tailor your resume to the job description and ATS keywords for resume cover that half.
How many bullet points per job
There is no measured rule, so treat this as general guidance. Give your latest or most relevant role the most, usually 3 to 6 bullets. Older roles can have 2 to 4, and roles from many years back 1 or 2. An internship can carry 2 to 3.
Recency and relevance decide, not fairness between jobs. If a role from five years ago is closer to the job you want than the one you have now, give it more space. And cut any bullet that does not support the role you are applying for, even a good one. If you write in a free builder, check its page limit first: free resume builders compared notes where the limits sit. The bullets add up to a page count too, and how long should a resume be says how many pages is right. The tools you name in the bullets also belong in your skills section, which what to put in the skills section of a resume covers.
Do not invent the number
An invented number is a bad trade. It will not look like a problem on the page. It shows up in the interview, when someone asks “how did you measure the [X]%?” and you are defending a figure you made up. In my experience, interviewers ask about the numbers, because those are the part they can probe.
So the rule is to use your own real figure or a placeholder, and nothing in between. If a figure is approximate, write it as approximate, and be ready to say where it came from.
My view on the rest: do not spend a night polishing one bullet. Write one solid, quantified base resume, then send it. Volume beats per-application perfectionism, especially for freshers, who have no experience edge to spend, as long as the volume is targeted at the right role and city.
Picture a fresher who applies to 15 jobs a night by hand, agonizing over each one, convinced that quality is the lever. It is not. Without work experience to differentiate the profile, what matters is how many matching openings you actually reach. Once the same fresher covers every matching opening in their city instead of the 15 they had energy for, the callbacks follow. The applications are not better. There are just enough of them to clear the noise.
So spend an evening on honest, quantified bullets, then stop. Before you send, search for ”[”. If any [X] is left, fill it in or cut the bullet. If you want a place to write them, you can open the free builder and paste them in.