Skip to content
Resume Writing

How to Write Work Experience on a Resume (India 2026)

The work experience section is the most important part of your resume — and the most commonly written wrong. Here's how to write experience bullets that pass ATS and impress recruiters.

7 min readPublished 20 Jun 2026Updated 22 Jun 2026

What Recruiters and ATS Look for in Your Experience Section

Your work experience section does two different jobs: it must pass the ATS keyword scan, and it must impress the human recruiter who reads it after. Most resume advice focuses on one or the other — but your bullets need to do both simultaneously. ATS looks for: specific keywords matching the job description, action verbs at the start of each bullet, measurable results, and relevant technology or tool names. Human recruiters look for: scale and impact (what was the scope of your work), specificity (what exactly did you do), evidence of progression (are you growing in responsibility), and proof of outcomes (what changed because of your work). The bullet point structure that satisfies both: [Action verb] + [what you did] + [how you did it / with what tools] + [measurable result].

  • "Reduced" is not enough. "Reduced API latency by 35% by migrating legacy synchronous calls to async event-driven architecture using Kafka" tells the ATS you know Kafka and event-driven architecture, tells the recruiter you understand performance optimisation, and proves the result with a number.
  • Every bullet should answer: so what? "Managed the migration of 15 microservices to AWS" — so what? "Managed the migration of 15 microservices to AWS, reducing infrastructure costs by ₹18 lakhs per year and improving uptime from 99.5% to 99.95%" — now the recruiter understands the impact.
  • Context matters. "Led a team" means nothing. "Led a 5-person backend team across 3 time zones to ship the payment reconciliation module 2 weeks ahead of schedule" tells the recruiter your leadership scope, the complexity, and the outcome.

💡 Pro tip: Read your bullets out loud. If they sound generic — "responsible for developing features", "contributed to team projects" — they will not impress any recruiter. Replace every passive phrase with an active result.

The Work Experience Section Format for India

Indian resume conventions differ slightly from global standards. Here is the correct format for the work experience section in India 2026.

  • Header format: [Company Name] | [Location] | [Start Month Year] – [End Month Year or Present]. Use the full company name (TCS, not just Tata). Include the city (Bengaluru, not just India).
  • Role title below header: [Exact Job Title]. If you had multiple roles at the same company, list each separately with its own dates. Promotions should be shown as distinct entries — they demonstrate career progression.
  • Bullet count: 3–5 bullets per role. Senior roles with more scope can have up to 6. Do not write 10 bullets per role — it signals you cannot prioritise. For older roles (5+ years ago), 2–3 bullets is sufficient.
  • Reverse chronological order: Always. Most recent role first. Indian ATS systems and recruiters expect this. Functional or skills-based formats are ATS-incompatible and raise red flags with Indian HR professionals.
  • Employment dates: Month and year format (June 2023 – Present). Do not omit months — unexplained gaps can arise from date ambiguity. For current role, write 'Present' not a speculative end date.
  • CTC or salary: Never include in the resume. Indian culture often has this expectation but including CTC in the resume weakens your negotiating position and adds no value to the document.

💡 Pro tip: If you were promoted at the same company, format it as: [Company] — two separate role blocks within the same company entry, with different titles and dates. This shows growth without looking like you job-hopped.

Action Verbs That Actually Work for Indian Resumes

Starting every bullet with a strong action verb is one of the simplest improvements you can make to your resume. The wrong action verbs make bullets weak. The right ones signal leadership, impact, and specificity.

  • Engineering and technical roles: Architected, Engineered, Built, Implemented, Optimised, Migrated, Deployed, Automated, Designed, Debugged, Profiled, Refactored, Scaled, Integrated. Avoid: 'worked on', 'helped with', 'involved in', 'responsible for'.
  • Data and analytics roles: Analysed, Built (models, dashboards), Forecasted, Identified (trends, anomalies), Automated, Developed (pipelines), Deployed (ML models), Validated, Visualised. Avoid: 'used data to', 'performed analysis of'.
  • Product management roles: Launched, Shipped, Defined, Prioritised, Led (roadmap, sprint), Grew (DAU, retention, revenue), Reduced (churn, drop-off), Partnered, Aligned. Avoid: 'was responsible for', 'managed the product'.
  • Business and operations roles: Generated (₹X in revenue), Reduced (costs by Y%), Led (team of N), Negotiated, Implemented, Streamlined, Managed (P&L, budget), Coordinated, Delivered. Avoid: 'helped the team', 'worked with stakeholders'.
  • Sales roles: Closed (₹X ARR), Grew (territory revenue by Y%), Exceeded (quota by Z%), Developed (pipeline of ₹X), Onboarded (N enterprise accounts), Built (relationships with C-suite). Avoid: 'responsible for sales in', 'worked on deals'.

💡 Pro tip: Review every bullet and highlight the first word. If any bullet starts with 'I', 'The', 'Was', 'Responsible', 'Helped', or 'Worked' — rewrite it. Every bullet must start with a past-tense action verb.

How to Quantify Your Experience (Even Without Big Numbers)

The most common objection to quantifying experience: 'I did not have metrics in my role.' This is almost never true — almost every professional role has some measurable dimension. Here is how to find and express your numbers.

  • Team size: 'Led a team of 8 engineers' or 'Managed 3 direct reports'. Team size is always a number.
  • Time savings: 'Reduced manual reporting time from 4 hours to 30 minutes per week' — no revenue impact needed.
  • Volume: 'Reviewed 150+ vendor contracts per quarter' or 'Handled 200+ daily customer escalations'.
  • Percentage improvements: If you do not have exact numbers, reasonable estimates are acceptable — 'Reduced bug resolution time by approximately 30%'. Flag estimated metrics if needed.
  • Scope of impact: 'Deployed to 40,000 daily active users' or 'Managed a ₹2 crore quarterly budget' — scope signals responsibility even without an outcome metric.
  • Before/After: The clearest quantification structure is before → after. 'ATS rejection rate: 78% → 45% after resume restructuring'. 'API response time: 800ms → 120ms after caching implementation'.
  • If you genuinely have no metrics: describe specificity instead. 'Built the notification system for [ProductName] used by [customer segment]' is better than 'developed backend features'. Specific is always better than generic.

💡 Pro tip: For your current role, start noting specific metrics now — even informally. Response times, user counts, revenue numbers, cost savings. Tracking these while you are in the role is infinitely easier than reconstructing them during a job search.

Common Work Experience Mistakes on Indian Resumes

The same experience section mistakes appear across tens of thousands of Indian resumes. Avoiding these puts your resume ahead of the majority.

  • Listing job duties instead of achievements. 'Responsible for developing new features using React' is a duty. 'Built the search autocomplete feature in React that reduced user drop-off by 18%' is an achievement. Indian resumes skew toward duties because that is what job descriptions contain — but a resume is a marketing document, not a job description.
  • Using the same bullets for every application. A senior data scientist resume submitted to a startup should not look identical to one submitted to an IT services company. Tailor your top 2–3 bullets per role to match the keywords and priorities of each JD.
  • Listing old technologies from 10 years ago. If you used Java 6 and COBOL in your first job, remove them from your skills and experience bullets unless directly relevant to the target role. Skills sections cluttered with outdated technologies dilute ATS keyword matching.
  • Omitting gaps — or explaining them awkwardly. Employment gaps are common in India (caregiving, exams, health, migration). Do not hide them with ambiguous date formatting. If you have a gap, be prepared to explain it — briefly and positively. The resume itself should not attempt a cover-up.
  • Abbreviating company names or role titles. 'HDFC' instead of 'HDFC Bank', 'AM' instead of 'Assistant Manager' — ATS systems often fail to recognise abbreviated company names and titles.

💡 Pro tip: After writing your work experience section, read it from the perspective of a recruiter who knows nothing about your company. Does it communicate what you did, at what scale, and with what outcome? If any bullet could describe anyone who held this job title, rewrite it.

Frequently asked questions

How many bullets should each job have on a resume?

The standard is 3–5 bullets per role for most positions. Your current or most recent role can have 4–6 bullets if the scope is broad. Older roles (5+ years ago) should have 2–3 bullets — enough to show the experience without overwhelming the reader. More than 6 bullets per role signals an inability to prioritise, and will likely be skimmed past.

Should I include my first job from 10 years ago on my resume?

Yes, but briefly — 2 bullets maximum. Your most recent 3–5 years of experience get the most resume space because they are most relevant. Older roles establish your career history and total years of experience, but should not take up half your resume. For experienced professionals (10+ years), a brief 'Early Career' or 'Previous Experience' section can condense older roles without eliminating them entirely.

How do I write work experience when I have no formal work experience?

If you have no formal work experience, substitute with: internships (treat them exactly like work experience — same section, same bullet format), freelance or contract projects (listed as 'Freelance [Role] | Self-employed'), significant academic or personal projects (listed with impact metrics), and volunteer or open-source contributions. Never leave the work experience section empty — create equivalent entries from what you have. CV Prime's fresher resume guide covers this in detail at cv-prime.in/fresher-resume.

How do I explain a gap in employment in the work experience section?

The cleanest approach: do not leave a blank period that recruiters will notice. If your gap was less than 3 months, list your last role as ending and your next role as beginning without highlighting the gap. For longer gaps, add a brief entry: '[Year] — Career Break: [One-sentence explanation, e.g., pursuing full-time MBA / family caregiving / health recovery / relocation]'. This is better than an unexplained hole in your employment dates.

Should my resume work experience match my LinkedIn profile?

Yes — exactly. Job titles, company names, and employment dates must be identical between your resume and LinkedIn. Discrepancies are the first thing background verification teams check, and mismatches can result in offer withdrawal even at the final stage. Content and bullet points can differ (LinkedIn allows more text), but the factual data points must align perfectly.

Write stronger experience bullets with CV Prime

CV Prime's AI rewrites your experience bullets to be outcome-driven, keyword-rich, and ATS-optimised. Paste your resume and any job description — AI handles the rewrite. Free to try.

Related articles

Help us improve CV Prime

We use privacy-conscious product analytics only after consent. No CV text or API keys are tracked.