Resume example · Data Analyst · 2 to 5 years
Data Analyst resume with 2 to 5 years of experience: a sample from India
At two to five years a data analyst is read for what you own: which reports people rely on, how many of them, and what a number you found led to. Course projects and school marks come off, and every dashboard on the page needs readers, a refresh time or a decision beside it.
- Last reviewed
- October 2026
Summary examples for 2 to 5 years of experience
Two ways to open the page. Neither is the summary on the sample resume beside it, so you can see more than one approach.
Summary example 1
Summary example 2
Bullet rewrites, weak to strong
Each pair shows a line people really write and a stronger version of the same fact. The numbers are illustrations. If you have no number, see resume bullets with numbers when you have none.
- Before
Made reports for management
AfterAutomated the weekly sales MIS for 9 zonal managers with SQL and Power BI, cutting preparation from 10 hours to 1 and flagging a ₹1.6 Cr stock variance on the first run
WhyReaders, tools, time saved and a variance with a rupee value. 'Made reports' cannot be told apart from a data-entry job.
- Before
Wrote SQL queries for dashboards
AfterRedesigned the daily sales query set as 9 SQL views over a 40-million-row table, cutting dashboard refresh from 27 minutes to 4
WhyTable size and refresh time are checkable in an interview. 'Wrote queries' says nothing about difficulty or result.
- Before
Did data validation
AfterAdded 18 automated data-quality checks (row counts, null rates, duplicate keys) to a nightly load; bad data reaching dashboards fell from 7 incidents a month to 1
WhyNames the checks and the incident count before and after. Analysts who protect trust in numbers stand out from those who only build charts.
- Before
Presented insights to stakeholders
AfterPresented a churn analysis of 14,000 subscribers to the product and operations heads; the reminder-message change it led to lifted 90-day renewals from 41% to 47%
WhyAudience, sample size and what the business did next. A rewrite like this connects the analysis to a result a manager cares about.
- Before
Analysed sales data
AfterAnalysed 18 months of regional sales against targets and found that 2 of 11 regions explained 70% of the shortfall; leadership redirected 2 trainers to them
WhyPeriod, scope, the finding and the action. A finding that changed a decision is worth more than ten reports delivered.
- Before
Used Python for analysis
AfterWrote a Python script that merges 8 vendor price files and flags about 120 mismatches a month; the buyer renegotiated 3 contracts using the list
WhySays what the script does, how often it matters and what someone did with the output. Tool use becomes a business effect.
Skills to list, grouped
Group skills into three or four lines and keep only those you could discuss for ten minutes. Each should appear in a bullet, a project or a certificate.
- SQL and Python: SQL, Python, pandas, Window functions
- BI and reporting: Power BI, Excel, Power Query, Looker Studio
- Analysis: Forecasting, A/B Testing, Variance Analysis
- Practice: Stakeholder Reporting, Data Quality
What recruiters for this role tend to look for
- Reporting you own: dashboards or MIS that people use on a schedule, with the number of readers and the time saved.
- SQL depth inside the bullets: tables, rows, joins, views or window functions, not only the word 'SQL' in a list.
- Findings, not outputs: a variance found, its rupee value and what the business did next.
- Data-quality habits: checks, reconciliations and how errors were caught before leadership saw them.
- Domain words that match the posting (claims, labs, retail, logistics), used honestly in the summary and the bullets.
Mistakes common at this level
- Listing Power BI, Tableau and Qlik with one dashboard behind them. Keep the tools that have bullets.
- Naming reports ('Sales MIS', 'Daily dashboard') with no readers, refresh time or decision attached.
- Giving a rupee value without saying what it is. A saving, a recovery and a forecast are three different claims.
Section order on the sample
The sample uses the Experienced Impact template, A4 (210 by 297 mm), one column, with the sections in this order: Summary, Skills, Experience, Education, Certifications. The order follows the level: skills and experience lead and school marks have come off.
Questions people ask
Should I keep Excel on the resume after moving to SQL and Power BI?
Yes, if your work still uses it. Power Query, pivot tables and macros are often named in analyst postings. List it with what you do in it, and place it below SQL and BI tools when those are the core of the job.
How do I mention a rupee value I did not control?
Separate what you found from what the business did: 'identified ₹62 L of billing leakage; finance recovered ₹41 L'. Mark estimates as approximate. If nobody confirmed the figure, describe the size of the variance and the method instead.
Is the Power BI PL-300 certificate worth listing?
Yes, with the year, if you hold it. It signals tool depth, but it adds little unless your bullets show dashboards you built. Keep to one or two certificates that match the stack in the posting, then run the file through the ATS checker before applying.
Keep reading
- Same role, FresherData Analyst resume for freshers: a sample from India
- Same role, 5+ yearsData Analyst resume with 5+ years of experience: a sample from India
- Related role, 2 to 5 yearsSoftware Engineer resume with 2 to 5 years of experience: a sample from India
- Related role, 2 to 5 yearsQA Engineer resume with 2 to 5 years of experience: a sample from India
- GuideATS-friendly resume in India: what parsers read and what trips them
- GuideWhat to remove from an Indian resume, and when to keep it
- GuideResume bullets with numbers when you have none
Next step
Build yours in the chat
Answer a few questions, one at a time. The reviewer drafts each line, asks for the numbers it cannot guess and never adds a fact you did not give. Already have a resume? Check it first and see what a parser reads.