How to Write a Data Analyst Resume That Gets Shortlisted (With Examples)

Most data analyst resume guides give you a list of skills somebody thought sounded right. We wanted to know what Indian employers actually write in their job posts, so we checked. JobTether reads the career boards of a few thousand companies hiring in India every day, and on 17 October 2026 there were 125 live postings titled “Data Analyst”, at 82 different companies.

This guide builds the resume around what those postings ask for: which skills to lead with, how to write bullets that prove impact, and why a data analyst resume and a business analyst resume should look different.

What Indian data analyst postings actually ask for

For the 69 of those postings whose full description we hold, we pulled out the named skills in the requirements section. Here is how often each one appeared:

Four things stand out.

• SQL is the only near-universal requirement. Nearly four in five postings name it. If your resume does not show SQL used on real data, nothing else on it will compensate.
• Power BI beats Tableau in India. 42% against 29%. Plenty of guides written for the US market lead with Tableau. If you only have time to learn one tool well, the Indian postings point to Power BI.
• Excel is not dead. More than a third still name it, often alongside Power BI. Write it down; do not assume it is implied.
• The cloud warehouse matters more than you would think. Snowflake, Databricks and Azure each show up in about one posting in six. If you have used one, name it. “SQL (Snowflake)” tells a reader more than “SQL”.

Notice also what is not near the top: no single skill after SQL appears in every posting. Postings with the same title ask for different things, which is why we recommend tailoring (more on that below). Our study of requirement overlap found that two postings with the identical title share a median of only 10.5% of their named requirements.

Data analyst vs. business analyst: two different resumes

Students often apply to both with the same document. The postings suggest that is a mistake. We ran the same count on the 100 “Business Analyst” postings we had descriptions for:

A data analyst resume should lead with querying, analysis and dashboards. A business analyst resume should lead with requirements gathering, working with stakeholders and delivery process (Agile, user stories, Jira), with SQL as a supporting skill. Same person, same experience, different emphasis. Keep two versions.

The technical skills section

Put it right under your summary, and group it so a recruiter can scan it in a few seconds. Order the groups by what the postings ask for, not alphabetically:

• Querying: SQL (PostgreSQL, BigQuery, Snowflake)
• Visualisation: Power BI (DAX), Tableau, Excel (pivot tables, Power Query)
• Programming: Python (pandas, NumPy), R if you genuinely use it
• Analysis: statistics, A/B testing, forecasting, cohort analysis
• Data tools: dbt, Databricks, Git

Only list what you could defend in an interview. If you write “DAX”, expect to be asked how a CALCULATE filter works. A shorter honest list beats a long one that collapses in the technical round.

The summary

Skip “passionate data professional seeking to leverage skills”. Write three lines: who you are, what you use, and one result.

“Data analyst with 3 years in e-commerce, working in SQL, Python and Power BI. Built a customer segmentation in BigQuery that the retention team used to target win-back offers, cutting monthly churn from 6.1% to 5.4%. Looking for a senior analyst role in consumer tech.”

For a fresher:

“Final-year B.Com student moving into analytics. Comfortable in SQL, Excel and Power BI. Built a sales dashboard for a local retailer covering 14 months of transactions, which they now use for weekly stock orders.”

Experience bullets: action, tool, analysis, impact

“Analysed data for the marketing team” tells a reader nothing. Use this pattern: action verb + tool + what you analysed + the business result, with a number.

• Weak: Created dashboards for the sales team.
• Strong: Built 5 Power BI dashboards tracking daily sales KPIs for 40 regional managers, replacing a manual Excel report and saving the team about 15 hours a week.
• Weak: Found data anomalies.
• Strong: Audited 1M+ rows of transaction data in Python (pandas) and traced a duplicate-billing bug that had cost ₹15 lakh in refunds over two quarters.
• Weak: Helped with A/B testing.
• Strong: Analysed an A/B test of the new checkout flow in SQL, confirmed a 4.2% conversion lift at 95% confidence, and made the case for full rollout.
• Weak: Did forecasting.
• Strong: Built a weekly demand forecast for 300 SKUs in Python, reducing stock-outs in the top 50 products by a third over one quarter.

Two rules make these believable. First, numbers should be specific and plausible: “about 15 hours a week” reads as measured, “improved efficiency by 300%” reads as invented. Second, say what changed because of the analysis. A dashboard nobody used is not an achievement; a dashboard that changed a decision is.

Our guide to resume bullet points has more patterns.

The projects section (critical for freshers)

Postings titled simply “Data Analyst” skew experienced: more than half of the 125 we counted carried a Senior, Lead, Staff, Principal or level II/III tag, and only about a dozen were clearly junior or associate. So if you are a fresher or switching careers, your projects have to do the work that experience does for everyone else.

Skip the Titanic and Iris datasets; reviewers have seen them many times. A project that gets interviews has three parts:

• A real question. “Which Bengaluru neighbourhoods have the most rental listings under ₹20,000?” is a question. “Exploratory data analysis” is not.
• Data you collected or cleaned yourself. Scraped, downloaded from a government portal like data.gov.in, or exported from a real club or shop. Messy data is the job.
• A finished output. A live Power BI or Tableau Public dashboard, plus the SQL or notebook on GitHub. Link both from your resume.

Example project bullet: “Scraped 6 months of prices for 200 products across 4 e-commerce sites with Python, stored them in PostgreSQL, and built a Power BI price-tracker that flags when a competitor undercuts by more than 5%.”

Generative AI on a data analyst resume

About one posting in ten mentioned generative AI or LLMs, usually as a nice-to-have rather than a core requirement. If you have genuinely used an LLM in your analysis work (for example, classifying free-text survey responses, or generating first-draft SQL that you then checked), a single bullet is worth including. Do not build your resume around it: the core of the job, in every posting we read, is still SQL, a BI tool and clear thinking about the business question.

Certifications that are worth listing

• Microsoft Certified: Power BI Data Analyst Associate (PL-300). Given how often Power BI appears in Indian postings, this is the most directly useful.
• Google Data Analytics Professional Certificate. Good structure for beginners; it matters less once you have real projects.
• A cloud or warehouse certification (Databricks, Snowflake, Azure) only if the roles you target name that platform.

One caution: you will still see the AWS Certified Data Analytics – Specialty recommended in older guides. AWS retired that exam in 2024, so check that any certification is still offered before you pay for it. And skip generic course-completion certificates; show the project you built in the course instead.

Tailoring for each posting, in ten minutes

Because no two postings ask for the same mix, the best-performing resume is the one adjusted for each role. You do not need to rewrite it. For each application:

• Copy the requirements section of the posting and highlight every named tool and method.
• Reorder your skills section so the ones they named come first.
• Swap one or two bullets for ones that use their tool (if they say Looker and you used Looker on one project, move that project up).
• Mirror their exact words where they are true for you: “stakeholder management”, “data governance”, “forecasting”.
• Never add a skill you do not have. Tailoring is choosing what to emphasise, not inventing.

If you are applying to many roles, JobTether's job application agent does this step for you against each live posting, using only what is already on your resume.

Where the data analyst jobs are

Across the wider analyst family (data, business, product and BI analyst titles, 225 postings with descriptions), Bengaluru held about a third of the roles, followed by Delhi-NCR, Pune and Hyderabad at 11 to 14% each, and Mumbai at about 10%. Only around 3% were remote. If you are outside these cities, expect most interviews to lead to a relocation or hybrid conversation.

How we got these numbers

Postings come from JobTether's pool of live Indian jobs on 17 October 2026, read directly from company career boards. “Data Analyst” means the phrase appears in the job title (so “Senior Data Analyst” and “Clinical Data Analyst” are included). Skill shares are from the 69 of the 125 postings whose full description we had stored on 26 September, matched against a fixed skill vocabulary inside each posting's requirements section. A skill outside that vocabulary would not be counted, and 69 postings is a modest sample, so read the shares as a ranking rather than precise percentages. This is one day's snapshot of the market.

Does your analyst resume prove your impact?Tailor it to live data analyst postings with JobTether's job application agent →