Data analyst
Turns a business question into a query, a query into a number, and a number into a decision someone will act on.
This is not a probability of losing your job. It combines how much of the role's task load is exposed to automation with how far adoption has actually gone — useful for comparing occupations on one consistent basis, and for nothing else.
Written for business, product and marketing analysts who work in SQL, spreadsheets and BI tools. Data engineers, data scientists building models, and statisticians in research settings differ.
What is actually changing#
The unit of analysis is the task, not the job title. A role is not replaced — its task mix shifts.
Writing queries and building dashboards
Automating✓ Evidence-backedTranslating 'how many users did X last month' into SQL, and wiring the result into a chart someone can refresh.
Natural-language-to-SQL and chart generation are among the most mature applications of language models, and the BI vendors have built them into the products analysts already use. The mechanical translation step that filled much of an analyst's week is now a prompt, when the data is clean and the question is clear.
'When the data is clean and the question is clear' is a large condition. In most companies neither holds, and the tools produce confident wrong answers on ambiguous schemas.
Working out what is really being asked
Still human-led≈ Platform inferenceTurning a manager's vague worry into a measurable question, and knowing which definition of 'active user' they mean.
The hard part of analysis is upstream of the query: knowing the organisation's definitions, its politics, and what decision the number will feed. A tool answers the question as asked; the analyst's value was always in noticing the question was wrong.
Knowing when the data is lying
Still human-led≈ Platform inferenceSpotting the broken pipeline, the duplicated events, the timezone bug, the definition that changed in March.
This requires history with the specific data — remembering what happened to it and why — which is exactly what a model without organisational memory lacks. Faster query generation makes this more important, not less, because wrong answers now arrive faster and look more polished.
Making a number change a decision
Being augmented≈ Platform inferencePresenting a finding so that the person who has to act on it understands it, believes it, and does.
Drafting the narrative and the slides is faster. Persuading a sceptical director in a meeting, and knowing which caveat to lead with for this particular audience, remains a human task because it depends on reading the room and on the analyst's own credibility.
Owning the definitions the tools rely on
New task≈ Platform inferenceMaintaining the metric definitions, the documentation and the semantic layer that make natural-language querying produce correct answers.
Natural-language analytics only works on top of well-defined metrics, so the value of the analyst shifts from answering questions to curating the layer that lets everyone answer their own. This is new work, closer to data governance than to reporting, and it is where analyst headcount is being redirected.
Which technologies matter here#
Four separate signals. They are deliberately not added together — a job exposed to two technologies is not twice as exposed.
How it got here#
The index is not a static number. This is where it would have sat at each capability checkpoint since ChatGPT — reconstructed, and labelled as such.
● 1 verified event for this occupation, plotted at the date it happened — the parts of the line near a marker are anchored to something checkable.
BI self-service tools set the baseline. Text-to-SQL moved it hard in 2023–2024, but the curve decelerates afterwards for a specific reason: natural-language querying only produces correct answers on top of definitions someone maintains, so part of the exposure converted into new work rather than disappearing.
A flat line is not a forecast of safety. It says which tasks automation has reached so far — the occupations that moved least here are the ones where the constraint is physical or regulatory, and both of those can change.
Recent changes#
One company, limited release; Uber's platform runs about 1.2 million interactive queries a month, so this is a small share. The post itself flags hallucinated tables and columns and prompt quality as open problems.
An employer has put it into production. Can move the baseline — weighted by scale and how similar the setting is.
Uber — engineering blog ↗What this means for you#
Entering on SQL skill alone is weaker than it was, because that is the part the tools do. The stronger entry is domain plus data: learn one business area deeply enough to know what its numbers mean and how they break, and use the tools for the querying. Volunteer for the unglamorous work of documenting definitions — it is where the new analyst role is forming, and almost nobody wants it yet.
If most of your week is fulfilling report requests, expect that queue to shrink as requesters self-serve, and expect to be measured on what decisions your work changed rather than how many dashboards you shipped. Your accumulated knowledge of where the data breaks is the asset. Turn it into the semantic layer and the definitions, and you become the reason the self-serve tools give correct answers.
Your options#
Four directions, each with its real constraints and one thing you can test this week. Continuing as you are is a legitimate choice — it just has to be a chosen one.
From answering questions to owning definitions
Self-serve analytics moves the bottleneck from query-writing to whether the metrics underneath are right. Owning that layer is more durable and more senior than owning a dashboard.
Governance work is slow, political and rarely celebrated. It needs an organisation that has felt the pain of inconsistent numbers.
Pick the metric your company argues about most and write its definition precisely enough that two people would compute the same number. Circulate it and count the objections.
Analytics engineering
Building the models and pipelines that clean data upstream is where much analyst effort is moving, and it pays better than reporting.
Requires real software habits — version control, testing, code review — and a tolerance for work that is invisible when it goes well.
Take one query you run every week and turn it into a versioned, tested transformation. If that felt satisfying rather than tedious, look at this path seriously.
Embedded analyst in a business function
Finance, operations and product teams increasingly want their own analyst who knows the domain rather than a central service that takes tickets. The domain knowledge is the moat.
You become partly that function — expect to learn its vocabulary, its calendar and its politics.
Ask the leader of one function what question they wish they could answer and cannot. If you can see how to answer it, you have found your embedded seat.
Common questions#
Yes, but for a different reason than before. You will write less of it, and you will read and check much more of it. Understanding what a query does is what lets you catch the confident wrong answer the tool produced from an ambiguous schema — and that catch is now the job. Learn SQL the way an editor knows grammar: not to produce every sentence, but to know instantly when one is wrong.
Studying towards this?
These majors lead here. Their pages break down which of their competencies transfer and what graduates typically lack.
Method and sources#
- Assessment date
- 2026-09-10
- Basis of the task judgements
- 1 evidence-backed · 4 platform inference · 0 not enough evidence
- Verified events
- 1