Data Analyst Salary and Career Path: Why the Best Move Is Sideways

A data analyst salary in the US runs from about $65,000 for a junior role to roughly $107,000 for a senior one, and in India from about ₹4 to ₹10 lakh, with tech companies paying well above both. The biggest jump after that rarely comes from chasing the "data scientist" title. It comes from which company you sit in and which layer of the data stack you own. Here are the numbers by level and market, each from a named source, then the path that actually moves them.

Level	US (per year)	India (per year)
Entry / junior	$64,599 junior average (Indeed, Sep 2026); $63,574 under one year (PayScale, Jul 2026)	₹5,15,010 entry-level average (Indeed India, Sep 2026); ₹4,13,462 entry level (PayScale India, Jul 2026)
Data analyst, all levels	$86,747 base (Indeed, Sep 2026); $70,643 base (PayScale, Jul 2026)	₹6,25,085 (Indeed India, Sep 2026); ₹5,77,472 base (PayScale India, Jul 2026)
Senior data analyst	$107,037 (Indeed, Sep 2026)	₹10,05,840 (Indeed India, Sep 2026)
Tech companies, median total comp	$110,000 from 1,116 reports (Levels.fyi, Oct 2026)	₹14,67,887 from 428 reports (Levels.fyi, Oct 2026)
Government benchmark	$88,940 median for operations research analysts, the closest BLS occupation (May 2025)	No official equivalent

Here's what most people get wrong. They read that table as a staircase: analyst, senior analyst, data scientist, more money. So they grind a machine-learning course to earn the scientist title. But look at the bottom rows. The same job title shows a $70,643 average base on PayScale and a $110,000 median total comp on Levels.fyi, which skews toward tech companies, and ₹5.8 lakh versus ₹14.7 lakh in India. The real driver of pay isn't the word on your business card. It's the employer you work for and whether your work feeds the systems the whole company depends on.

How much does a data analyst make in the US and India?

In the US, expect roughly $64,000 to $65,000 to start and $70,000 to $87,000 for the plain data analyst title, depending on which source you trust. In India, expect ₹4 to ₹5 lakh to start and around ₹6 lakh on average, with large spreads by city and employer.

The sources disagree because they count different people. Indeed's figures come from 6.1k salaries taken from job postings in the past 36 months, so they reflect what employers advertise. PayScale's come from self-reported profiles, and its US data shows slow early growth: $63,574 under one year and $69,828 at one to four years. Levels.fyi skews toward tech firms, and counts total compensation, not just base, which is why its US median sits at $110,000, with the 90th percentile at $190,000. None is wrong. Each describes a different slice of the market.

India shows the same split, wider. Indeed India puts the top cities at ₹8,11,819 in Gurgaon, ₹7,76,646 in Bengaluru and ₹7,54,655 in Noida, while Levels.fyi's tech-company reports put the 75th percentile at ₹2.38 million and the 90th at ₹3.36 million. A Bengaluru analyst at a services firm and one at a product company can hold the identical title and, going by those two sources, earn two to three times apart. When you quote a number in a negotiation, say which slice it comes from.

The official government figure needs a caveat. The US Bureau of Labor Statistics has no "data analyst" occupation, so most guides borrow operations research analysts, whose median was $88,940 in May 2025, against $50,980 for all occupations. Use it as a sanity check, not a quote.

What does the data analyst career path look like?

The path forks after two or three years. You start as a junior or associate analyst, become a senior analyst, and then choose between four directions that pay very differently.

Next move from senior analyst	What changes	Pay signal
Stay a specialist analyst	Deeper domain, harder questions	61% of North American data analysts earn over $100K (dbt Labs survey, 2024)
Sideways into analytics engineering	You own the modeled data everyone else uses	78% of North American analytics engineers earn over $100K (same survey)
Up into data science	More statistics and modeling, often a new title for similar work	$120,230 BLS median for data scientists (May 2025)
Up into analytics management	Headcount, roadmap, stakeholders	$184,000 for analytics managers and $255,000 for directors, per Glassdoor figures cited by Coursera (Sep 2026)

The management numbers are estimates from a single site, so hold them loosely. The direction is clear, though. Scope pays. Leading a team or owning a core system lifts you further than a title change alone. Engineers hit a version of this too, in the ceiling on a full stack developer salary. Product management works the same way, with PM pay that jumps at rungs, not years.

Is data science or analytics engineering the better next step?

For most analysts who like the technical work, analytics engineering is the better bet. It builds on the SQL you already use, and it pays at least as well.

The pay signal comes from dbt Labs, a vendor whose tool analytics engineers use, so read it as a vendor survey. In its 2024 report of 456 data practitioners and leaders, 78% of North American analytics engineers earned over $100K, versus 61% of data analysts and 66% of data engineers. The role sits between analyst and data engineer and owns the transformation layer: the cleaned, tested tables that every dashboard and model reads from. When your work is that foundation, your scope is hard to shrink.

Data science is the move everyone is told to make, and the title is muddier than it looks. Many "data scientist" postings now describe SQL and reporting work, which is why the data scientist title is quietly demoting itself into three different jobs. You can spend a year earning the label and land in the same work at a different price. The sideways move compounds what you're already good at, the pattern where lateral moves build more career capital than titles.

Watch how the same analyst describes the same work. Picture Priya, a hypothetical senior analyst on a revenue team, writing her LinkedIn headline.

Weak version: "Data analyst with strong SQL and dashboard skills, looking to grow into a data scientist role. Currently taking machine-learning courses."

Strong version: "I own the SQL models our exec revenue dashboards run on. I rebuilt the churn tables so three teams stopped maintaining conflicting versions. Looking for an analytics engineering role where I own the transformation layer end to end."

The weak version asks permission to level up and prices her as a junior candidate for a new field. The strong one shows the lever is already in her hands and names the role that pays for it. One asks to be promoted. The other states a market rate.

What skills do you need, and can you start with no experience?

The top three skills are SQL, a BI or spreadsheet tool for communicating results, and the business judgment to pick the right question. Yes, it's a hard skill job, but the hard part is usually the judgment, not the syntax.

SQL is the foundation, and demand for it is not a fad. Labor-market analytics firm Lightcast counted 217,968 unique postings mentioning SQL in May 2021, with demand up 46% over 12 months, more than double the roughly 100,000 postings for HTML or CSS that month. Python helps, and statistics helps more as you move toward modeling, but an analyst who writes clean SQL and explains a result in two sentences will out-earn one who knows five libraries and can't.

On degrees: the BLS lists a bachelor's degree as the typical entry-level education for operations research analysts, and many postings ask for one in a quantitative field. It's a common filter, not a law. People do break in without one, usually from an adjacent job (finance, operations, marketing, support) where they were already the person pulling the numbers. Your first data role is often an internal move.

With no experience, proof beats credentials. A certificate tells a hiring manager you finished a course. A small project on real, messy public data, with a written question, your SQL, and a one-paragraph answer, tells them you can do the job. That's why a portfolio beats a resume for career switchers, and why most stacked certifications don't pay for themselves.

Will AI replace data analysts?

Not as a role, at least on current evidence, but it is already changing the work. Analysts who use AI to write and check code faster will crowd out analysts who don't.

Adoption moved fast. In dbt Labs' 2025 survey of 459 data practitioners and leaders (another vendor survey), 80% said they already use AI in their day-to-day workflow, up from 30% the year before, and 70% use it for analytics development in some form. The same survey found 40% of respondents reported headcount increases, compared to 14% the prior year. That isn't what replacement looks like.

The official projections point the same way. BLS projects operations research analyst employment to grow 12% from 2025 to 2035 and data scientist employment to grow 35% over the same decade, both much faster than average. Projections made in an AI transition are uncertain, so don't treat them as a promise. What they suggest is that the routine part of the job (pulling a number, formatting a report) shrinks, while the parts AI can't own yet grow: deciding which question matters and being accountable for the answer.

Who should not chase the sideways move? (the honest part)

The analytics engineering move isn't free, and it isn't for everyone.

First, it's real skill work, not a relabel. It demands software habits (version control, testing, code review, data modeling) that dashboard work never taught you. If your current job is dragging fields in a BI tool, budget months of deliberate practice, not a weekend.

Second, the role may not exist where you are. In small companies and young data teams, the work is folded into "analyst" or "data engineer." At a 40-person startup, you might have to build the case for the role before you can hold it.

Third, the evidence is thinner than it looks. The 78% figure comes from a vendor's survey and covers North American respondents only, and the salary sites in the table above disagree with each other by tens of thousands of dollars. Treat every number here as a range to test, not a fact to recite.

Finally, staying an analyst is not a trap. A senior analyst average of $107,037 in the US is a good living, and if you enjoy stakeholders more than schemas, the management track may suit you far better. The sideways move is the highest-leverage option for people who like the technical layer. It's not a verdict on everyone else.

What to do now

1. Find your slice of the market. Compare your pay to the right row: job-board averages if you work at a services firm or non-tech company, Levels.fyi if you work in tech. Then note your city.
2. Audit what you actually own. List the tables, models and dashboards other teams rely on. If that list is empty, that's your first project, not a new course.
3. Check whether the role exists. Search live data roles and three target companies for "analytics engineer." If the title is there, you have a target. If not, the work still exists under another name.
4. Close the software gap on purpose. Pick one of version control, testing, or a modeling tool like dbt, and build something real with it this quarter.
5. Rewrite your one-liner around ownership. Lead with the system you own and who depends on it, not the title you hope to earn.
6. Bring a sourced range to your next offer. Quote the source, market and date, and use it in the counter, the way the salary negotiation playbook lays out.

Not sure whether your next move is sideways into analytics engineering, up into management, or just a better price for the analyst role you already have? Send Praxy your current title, city and what you own on WhatsApp. I'll pull the right salary slice for your market, map which path fits your skills, and rewrite your headline so you're priced for the work you actually do.