How to Write Work Experience on a Resume (With 25+ Examples)
Priya Sharma · Career Coach & Ex-Recruiter
The work experience section makes or breaks your resume. This guide covers the exact formula for writing bullet points that pass ATS filters and impress human recruiters — with real before/after rewrites for every role.
How to Structure the Work Experience Section
Each job in your work experience section should follow this layout:
The CAR Formula: The Best Framework for Resume Bullet Points
The most effective resume bullets follow the CAR framework: Context → Action → Result. You don't need all three in every bullet, but the best ones always lead with Action and end with Result.
The situation or scope. How big was the team? What was the problem? What was the scale?
"For a 500K DAU consumer app..."
What YOU specifically did. Use a strong past-tense verb. Be precise.
"...redesigned the notification system..."
The measurable outcome. Percentages, time saved, revenue, users, or relative improvement.
"...reducing opt-out rate by 34% and improving D30 retention by 6pp."
Start Every Bullet With a Strong Action Verb
The verb is the first word in every bullet. It signals what you did. Never start with “Responsible for” or “Helped” — these are passive and vague.
❌ Weak verbs to avoid
✓ Strong verbs that work
Before & After: Real Resume Bullet Rewrites
These are the most common types of weak bullets we see — and how to fix them.
Responsible for building and maintaining backend APIs.
Designed and shipped 12 REST APIs in Node.js serving 500K+ daily requests with 99.95% uptime, reducing average response latency by 40% through Redis caching.
What changed: Added action verb, scope, tech stack, scale, and measurable outcome.
Worked with various datasets to create reports for management.
Built automated SQL + Python reporting pipeline that reduced monthly analytics delivery from 3 days to 2 hours, directly informing ₹50Cr inventory decisions.
What changed: Replaced vague language with specific tools, time saved, and business impact.
Helped improve the onboarding experience for new users.
Led redesign of 5-step onboarding flow (Figma → A/B test → launch) increasing D7 activation from 24% to 61%, contributing ₹1.2Cr incremental MRR.
What changed: Named the process, tools, metric baseline, improvement, and revenue impact.
Managed Google Ads campaigns for the company.
Managed ₹80L/month Google Search and Performance Max campaigns for D2C brand, improving ROAS from 2.1x to 3.8x through systematic bid strategy restructuring and negative keyword pruning.
What changed: Added spend scale, platform specifics, metric baseline, and optimization method.
Was responsible for coordinating with vendors and ensuring timely delivery.
Managed 23-vendor logistics network across 4 states, reducing average delivery TAT from 5.2 to 3.1 days through route optimization and SLA dashboards — saving ₹18L annually in penalty costs.
What changed: Added scope (# vendors, states), specific metric improvement, method, and financial impact.
Recruited candidates across different departments.
Owned full-cycle recruitment for 6 engineering and 3 product teams, reducing average time-to-hire from 45 to 28 days and achieving 4.2/5 hiring manager satisfaction (Greenhouse data).
What changed: Added scope, specific metric change, and satisfaction benchmark.
How to Quantify Achievements When You Don't Have Metrics
The #1 excuse we hear: “My job doesn't have measurable outcomes.” Almost every role has something that can be quantified. Here's how to find numbers you may have forgotten:
How many users, clients, transactions, files, reports, APIs, features, teammates?
Did something take 3 days that now takes 2 hours? Cut the review cycle from weekly to daily?
Budget you managed, cost savings, revenue influenced, deals closed, penalty costs avoided?
Error rate reduced? Conversion improved? Attrition lowered? Even rough estimates are valuable.
"Led 3 engineers" or "collaborated with a 12-person cross-functional team" add scope and weight.
"200+ daily" or "across 5 geographies" or "for 3 enterprise clients" shows impact without needing a hard number.
The ATS Side of Work Experience
Your work experience section is where ATS systems look for keyword matches. The tools you list (Python, SQL, Figma, Salesforce), the methodologies (Agile, SCRUM, OKRs), and even job title keywords all affect your score.
The key rule: if the JD mentions a skill and you have it, it should appear somewhere in your work experience — not just in your skills section. ATS weight is higher when keywords appear in context (e.g., “Built a Python pipeline...”) vs. just listed (“Skills: Python”).
Check Your Keyword Coverage →