Data Analyst Resume for India
A data analyst resume should prove one thing: you can turn messy data into a clear answer someone acted on. This guide shows how to do that, whether you are a fresher or have a few years of experience.
A good data analyst resume in India is one page for freshers (up to two for experienced), puts SQL, Excel, a BI tool and Python in a clear skills block, and shows 2-3 projects or achievements with the question asked, the data used, the method, and the result. Use real numbers only; if you cannot measure impact, describe the decision it supported.
What a data analyst resume needs to show
Hiring managers reading analyst resumes want to see three things: that you can handle data (SQL, spreadsheets, a programming language), that you can communicate findings (dashboards, summaries), and that you understand the business question behind the numbers.
A list of tools alone proves none of these. A line such as "Analysed customer churn data in SQL and Python to find which plan types left earliest" proves all three at once. Aim for that kind of line throughout your resume.
Keep the layout simple. Many companies in India use an applicant tracking system, so avoid tables for the main content, multi-column layouts and icons for skills. Our guide on what an ATS resume is explains why.
The best section order
Order depends on how much work experience you have. Use the table as a starting point.
| Section | Fresher | 1-5 years experience |
|---|---|---|
| Header (name, phone, email, LinkedIn, GitHub or portfolio) | 1st | 1st |
| Summary (2-3 lines) | 2nd | 2nd |
| Skills | 3rd | 3rd |
| Projects | 4th | After experience |
| Experience or internships | 5th | 4th |
| Education and certifications | 6th | Last |
Freshers lead with projects because that is their proof of skill. Experienced candidates lead with work history because results at a real job carry more weight than practice projects. For wording ideas, see resume summary examples.
How to list SQL, Excel, Power BI, Tableau and Python
Group tools by purpose so a reader can scan them in a few seconds. Do not rate yourself with stars or percentage bars; they mean nothing to a recruiter and ATS software cannot read them.
- Querying: SQL (joins, window functions, CTEs, subqueries), MySQL, PostgreSQL
- Spreadsheets: Excel (pivot tables, XLOOKUP, Power Query), Google Sheets
- Visualisation: Power BI (DAX basics, dashboards), Tableau (basic)
- Programming: Python (pandas, NumPy, Matplotlib), basic statistics
Be honest about depth. Writing "Tableau (basic)" is better than claiming expertise and failing a practical test. Only list what you could explain or demonstrate in an interview. If a job post asks for a tool you have only used once, mention it in a project instead of listing it as a core skill. More on this in skills for resume.
Projects with datasets: a fictional worked example
For freshers, projects are the heart of the resume. A strong project states the question, the dataset, what you did, and what you found. Name the data source so a reader can check it, for example a public government open-data portal or a Kaggle dataset. Add a GitHub or dashboard link.
Metro Ride Demand Analysis | Python, SQL, Power BI | GitHub link
- Question: at which hours and zones do cab requests exceed available cars?
- Cleaned a public ride-booking dataset of about 80,000 rows (removed duplicates, fixed timestamp formats, handled missing pickup zones) using pandas.
- Wrote SQL queries to compare weekday and weekend demand by zone and hour.
- Built a Power BI dashboard with hour and zone filters; the findings suggested that evening demand in two zones was the main gap.
Notice what is missing: no invented business impact. The project does not claim it "increased revenue by 30%" because it was a practice dataset. It states what was found. That honesty reads as credible. Our projects section guide has more layouts.
Describing impact without inflating numbers
Numbers help, but only true ones. If you cannot defend a figure in an interview, remove it. Ask what changed, how you know, and who used it.
- Before: Responsible for making reports.
After: Built a weekly sales report in Excel using pivot tables, replacing a manual copy-paste process the team used earlier. - Before: Improved company performance by 50%.
After: Analysed repeat-order data and shared three findings with the operations lead, who changed the packing schedule for slow-moving items. - Before: Expert in data analysis.
After: Used window functions in SQL to rank products by monthly sales across 12 stores.
If you do have a measured result, state how it was measured: "report preparation time reduced from about two hours to 30 minutes (my own timing over four weeks)". If you only know the direction, say so: "reduced manual effort". Use counts you actually know, such as rows, tables, stores, reports or users, rather than guessing percentages.
Freshers versus experienced analysts
If you are a fresher
Show two or three projects, any internship, and relevant certifications. Include your degree, college and CGPA or percentage if your target company asks for it. Certificates from training providers can show learning effort, but projects matter more than certificate count.
If you have experience
Give each role two to four bullets. Start with the business problem, then the tool, then the outcome. Mention the size of data or the number of stakeholders. Career changers, for example from operations or finance, should highlight earlier work that already involved reports, reconciliations or forecasts. The experienced resume format and fresher resume format guides cover the layout in detail.
Common mistakes to avoid
- Listing 25 tools with no evidence of using them.
- Describing duties ("responsible for dashboards") instead of what you did and what it helped decide.
- Pasting dashboard screenshots as images; ATS software cannot read them. Link to a live dashboard or GitHub instead.
- Including an old-style objective line like "seeking a challenging role". Use a short summary with your tools and domain.
- Sending a Word file with broken formatting. Check PDF or Word before you submit.
Final checklist before you apply
- Can every tool in your skills block be backed by a project or job bullet?
- Does each bullet say what you did, with what, and what happened next?
- Is every number something you could explain in an interview?
- Do your GitHub or dashboard links open without a login?
- Are job-post keywords such as SQL, Power BI or Excel used where they are true?
- Run the final file through an ATS resume checker and read it once on a phone screen.
Build your data analyst resume — free
Pick a clean, ATS-friendly template and add your skills and projects in minutes.
Create my resume →Frequently asked questions
Should a data analyst fresher include projects?
Yes. Projects are the main proof of skill when you have no work history. Pick two or three with a clear question, a named dataset, and a link to your code or dashboard.
Which tools should I list first: SQL, Excel or Python?
List the tools that the job post mentions first, and that you can actually use. For many entry-level analyst roles, SQL and Excel are asked for before Python, but check each job description.
How do I show impact if I only have practice projects?
Describe the finding or decision your analysis supports, not a made-up business gain. For example, say what pattern you found and how the dashboard helps a reader see it.
Do I need certifications for a data analyst job?
They are optional. A certificate can help a fresher show learning effort, but projects with real data and clear explanations usually say more about your ability.
How long should a data analyst resume be?
One page for freshers and up to two pages for candidates with several years of relevant experience. Cut older or unrelated content before reducing font size.