Example · Data Analyst

58% of your week as a data analyst is still yours.

AI now runs the pulls and refreshes the decks. Knowing where the data is wrong stays with you.

Make my planA typical week at the middle pace. Your plan uses your own tasks.

Is data analyst a dying career?

In a typical week at the middle pace, 28% of this work needs your judgment and 30% is work you do using AI. AI could do about 42%. Pulls, deck refreshes, dashboard builds and clean-up are a large part of your week, and a frontier model with warehouse access does that work today. That is the routine work analysts tend to dread.

Read more

What it cannot do is know that a table double-counts something, decide whether a test can support the claim a PM (product manager) wants, or tell a VP that two percent is noise. That is what people come to you for.

This helps you, and it also creates a problem. The exposed work is why a company hires a junior analyst. The work that holds up is work you have grown into and are not yet paid for. If a seat on your team has closed unfilled, yours is safer than that one was. The plan helps you make your job the second kind while you have time.

The week, task by task

Who does each hour of a typical 40-hour week.

See every task
You28% · 11 hours

Needs your judgment.

  • Scoping the ask: turning a ticket into the question worth answering, or declining it7%
  • Data-trust stewardship: which tables to believe, known quirks, double-counts6%
  • Experiment design and validity review: power, sample-ratio checks, metric choice, peeking5%
  • Presenting and defending the number in the room; "this data can't support that"5%
  • + 1 smaller task3%
You using AI30% · 12 hours

AI does the slow parts. You still own it.

  • "Why did conversion drop?" analyses with an unclear question10%
  • A/B readout: compute lift and significance, write the recommendation9%
  • Debugging broken dashboards, reconciling numbers that disagree8%
  • Metric definition changes and dbt model edits with the analytics engineer4%
AI42% · 17 hours

AI could do most of it.

  • Ad-hoc pulls with a clear question ("orders from campaign X, by state, last 30 days")14%
  • Weekly metrics deck: refresh, annotate, send10%
  • Dashboard builds in the BI tool from a written spec8%
  • Data prep and cleaning for one-off analyses (Sheets, CSVs, notebooks)6%
  • + 1 smaller task5%
Why some tasks still need a person
Knowing which table double-counts what, and why attribution never matches finance

This rests on the cost of checking and on context. A model querying the warehouse returns a number that looks right. Discovering it is wrong takes someone who has been burned by that table before. This knowledge lives in you rather than in the dbt docs, and it is your best asset.

Deciding whether a test can support the claim

The cost of an unchecked wrong answer is highest here. A wrong readout ships a change that underperforms for a year, and nobody finds out. That is why a human who can spot a sample-ratio mismatch or a peeked result is protected.

Turning "can you pull X" into "what would you do differently if X were higher?"

This depends on context. The model answers the question asked. Knowing which question is worth asking requires knowing the team's plan for next quarter and what happened the last time they made that call.

Being the person who says "this number moved, and it isn't real"

This needs accountability and presence. Someone must be answerable in the room when a VP acts on a number. Often that person is you, after the fact. The moves above change when.

Reconciling numbers that disagree

What protects this is context. The model can diff two queries. Knowing that finance books returns on refund date and marketing on order date, and which one the board deck uses, is institutional memory.

Good to know

What is hard about this field, and what you can do about it.

The hard truth

Nearly half of analyst postings now ask about AI.

Tech hiring is thinner than it was before 2020, and the data postings that remain have changed. AI now shows up in close to half of them.

What you can doPut one AI-assisted analysis of public data in your portfolio. Show the prompt, how you checked the output, and the decision it changed.
Sources (2)

What's next after data analyst?

Plan A is the best move inside the work you do now.

APlan A

Grow in the job you have

The main focus. Most weekly sessions build toward it.

Your next stepAnalyst embedded with one team
Each week
4 sessions
Ready in
About 4 to 6 months
Why it fits

Why you. You already scope tickets for the teams you serve, and you know their data better than they do. If "in the room when the decision gets made" is where you want to be, this is the move.

The gap. You have no defined role and no recommendations with tracked outcomes yet. Setting the agenda is judged on outcomes and politics, which is different from a ticket count.

The trade-off. You depend on one sponsor; if that VP leaves, a reorg dissolves the seat back into the queue. The queue also protected you, since nobody questions an analyst with 40 tickets. You trade a visible workload for a visible opinion, which can be wrong in public.

2 other moves that fit
  • Own test review: whether a test can support the claimReady in about 6 to 9 months
  • Own the metric definitions with the analytics engineer (the backup plan)Ready in about 6 to 9 months

What's a plan B for data analysts?

Plan B is meant to be different from this job. It was picked because skills from this role carry over.

BPlan B

Get ready for a new kind of job

A second option. A newer job AI is creating that these skills already fit.

A job to aim forAI evaluation specialist

Deciding whether a test can support the claim is the same skill AI teams need to judge model outputs and launches.

Each week
1 session
Outlook
Hiring now
Pay
$230K to $270K a year (one posting)One Anthropic safety evaluations posting, 2026; AI lab pay runs well above most employers.
2 other options
  • AI value and ROI analystReconciling numbers that disagree prepares you to measure whether AI tools save the time and money promised.
  • LLM evaluation data scientistYour SQL and experiment review work are a base for LLM evaluation, though most postings want a few more years of data science.

In your own plan you can switch to any of the 47 roles.

The 13 weeks

Small steps that add up. One plan for both: most sessions build Plan A, one a week builds Plan B.

By week 13 you will have

AFor Plan A

  • A one-page metrics memo that replaced the weekly deck
  • A test checklist the team uses before results go to leadership
  • A two-page recommendation for a VP

BAnd for Plan B

  • A draft write-up of your AI test
  • A published write-up of your AI test for your portfolio
Month 1Weeks 1 to 4
  1. 1Measure your week
  2. 2Test AI on the weekly deck
  3. 3Replace the deck with a memo
  4. 4Audit your A/B tests

You finish withA one-page test checklist

Month 2Weeks 5 to 8
  1. 5Ask to work with one team
  2. 6Write your first recommendation
  3. 7Start the test review
  4. 8Fix a data model

You finish withA written decision on which path to keep

Month 3Weeks 9 to 13
  1. 9Track your recommendations
  2. 10Check the job market
  3. 11Gather your results
  4. 12Make your ask
  5. 13Decide your next step

You finish withA one-paragraph decision with a date

Three courses from the plan
  • Trustworthy Online Controlled Experiments: A Practical Guide to A/B Testing (Kohavi, Tang, Xu)Cambridge University Press, 2020 · Price varies by retailer

    Yes, Weeks 4–7. It is the single highest-value purchase in this report.

  • Accelerating Innovation with A/B TestingMaven, taught by Ron Kohavi · $1,999

    Only on company money, and only after “Own test review: whether a test can support the claim” has a named owner. The book covers most of it.

  • The Effect: An Introduction to Research Design and Causality (Huntington-Klein)Free online at theeffectbook.net; print via Chapman & Hall · Free

    Yes, months 4–6, for the "why did it drop" analyses that aren't experiments.

Checked 2026-09-22.

The fuller picture

Risks beyond AI: moderateTech-cycle and supply risk

Analytics teams, especially at consumer and e-commerce companies, grew fast in 2020–21 and were cut in 2022–23 with the rest of tech. Hiring is soft, and entry-level jobs are crowded with certificate holders. Some of what you see comes from that cycle rather than the tool.

Where this could be wrong
  • The shares are guesses until Week 1. If your log shows 30% pulls rather than 14%, the share of your week tools can do reaches the mid-50s percent, junior openings shrink faster, and working embedded with one team is urgent.
  • Our view that AI handles ad-hoc pulls well rests on a benchmark. Spider 2.0-Snow at 96% is a leaderboard score on a fixed task set, not your warehouse with its undocumented quirks. Being "confidently wrong on our schema" is the counter-evidence.
  • We assumed a central team with an intake board. If you are already embedded, the embedded move is done and the plan starts at Week 4; if analytics reports to finance, accountability rises and the report is too pessimistic.
  • The 66% master's-or-PhD figure is for the "data scientist" title on Glassdoor US. Product analyst and "decision scientist" roles at consumer companies often skip the degree. We decline the title. The statistics are still worth learning.

This is an example. Your plan uses your own week.

Make my plan

Also matched: data analyst, analytics analyst, business analyst. Research checked 2026-09-22. Page updated .