AI Already Does the Data Work. Here's What You Do Now.
Everything you think you know about your job is about to change. What comes next is better
“AI won’t replace the data scientist, but a data scientist who uses AI will replace the data scientist who doesn’t.”
You’ve heard this line. You’ve probably said it, at a conference, in a team meeting, maybe scrolling LinkedIn. It felt right. You could keep doing your job, add some AI for the boring parts, and the human work would stay yours. Business as usual, but shinier.
You could picture yourself in that future. It was comfortable.
Maybe that was true before. It’s not true anymore.
The models got good enough to do the whole job. Not just help with pieces of it. The whole thing, from question to finished deck, end to end. And it happened fast. Things that weren’t possible three months ago are possible today. What changed isn’t that AI got “a little better.” It crossed a line. The thing you do all day can be done by AI. Right now.
AI is going to replace the data analyst. It’s going to replace the analytics engineer. It’s going to replace the data scientist. Not “augment.” Not “change the way you work.” Replace.
Your job right now. Writing queries, building dashboards, answering the same segmentation question for the third time this quarter. That job is done.
The “augment, not replace” line is bullshit. It’s a comfortable story we told ourselves while the ground was shifting. I know because I told it to myself too, right up until I built the system that does my job better than I do.
I’ve been doing this for over a decade. I built an AI data analyst, tested it on the worst data I’ve ever worked with. It caught mistakes I had been making for months. Numbers I report to leadership. Numbers I’d been confident in.
It scared the shit out of me. I’m not writing this from a comfortable distance. More on that at the end.
What comes after the fear is something better. I’m on the other side of it. Stay with me.
Your current job is done. Your next job is more interesting.
The Order of Falling
There’s an order to how this hits the data profession. The roles closest to coding fall first. Coding was the first thing AI got really good at.
Software engineering falls first. It’s already fallen. Building pipelines, shipping applications, infrastructure. What used to require a development team now requires a conversation. And the people who made this happen? Coders, building the tools that automated their own work. They could validate the output because they knew what good code looked like. The expert builds the system that replaces them. Remember that pattern.
Data analysts are next. It’s already here. The core loop of a data analyst is: take a question, explore data, find the answer, present it. AI can do every step of that right now.
Think about what covers 80-90% of the questions your data team fields: funnel analysis, segmentation, drivers and root-cause analysis, trend analysis, cohort analysis, opportunity sizing. If your daily work is on that list, the AI already does it.
A straightforward segmentation or funnel analysis that takes an analyst three days? The AI produces it in ten minutes. Prompt to finished deck. A complex deep-dive that takes three to four weeks? Forty minutes to an hour and a half.
Most of the work data teams do is pattern execution. Not because the people are bad. The patterns are just predictable. And predictable is exactly where AI is strongest.
The output competes with the strongest analysts I’ve worked with. The ones everyone goes to with the hard questions. I’m not running a study here. It’s what I’ve seen, and my boss who built his own version sees the same thing.
Analytics engineering gets absorbed next. Nobody sees this one coming. Analytics engineering doesn’t get replaced by a separate AI system. It gets consumed as a side effect of the AI analyst getting smarter.
As the AI analyst runs analyses, it hits walls. It needs better data, cleaner tables, business context it can trust. So what does it do? It starts building the clean, documented semantic tables that analytics engineers spend months on. It stores its learnings and builds rules from its mistakes. This isn’t a prediction. It’s already started happening. I watched it happen. The AI analyst started building exactly the kind of semantic tables our analytics engineering team had been working on for months.
The critical business context trapped in people’s heads? The AI extracts it through conversation and puts it where anyone can use it.
Data science is the last domino. Causal inference and experimental design require more sophisticated reasoning. It’s months behind, not years. If you’re a data scientist, the five paths below apply to you too. Especially Validator and Translator. Your training in experimental design makes you perfect for those.
You want a timeline? Watch the pace of frontier model releases. It’s not a date on a calendar. It’s a rate of acceleration most people haven’t internalized.
The Proof
I built an AI data analyst in about a week by talking to it. Tens of thousands of lines of code, all generated through conversation. Not by writing code. By describing standards, correcting mistakes, teaching it what good analysis looks like. Then we tested it on real internal company data. Eleven years of bad data foundations at my company. The kind of data where people give up and just work around the problems.
I ran it against our North Star metrics. That’s where it got scary. Numbers I report to leadership. Numbers I’ve been working with for months. A query with 10+ CTEs, some with 15+ table joins. Everything tied out except one number. I asked the AI why. It found the bug: two table abbreviations were accidentally swapped in a join, pulling data from the wrong tables. The system doesn’t re-run your SQL. It writes its own query from scratch to verify every number independently.
The AI was right. I had been reporting the wrong number to the business for three months.
That’s when it got really scary.
It wasn’t a one-time thing. It caught multiple errors across different analyses. Silent errors that had been passing through normal review for months. These weren’t stupid mistakes. They were the kind of errors that pass peer review because everyone makes the same assumptions about the data. The profession’s quality floor is lower than anyone wants to admit, and the AI just exposed it. The system is not infallible. It makes mistakes too. But it learns from correction, and it documents everything it does. More than most teams can say.
I thought this might be a fluke. My boss, who manages the data team, built his own version. Another data professional did it independently, different data, different domain. Same pattern. Same results.
Five Paths Forward
I sat with that fear for a while before I started asking a different question: if the job you have today is done, what’s the job you have tomorrow?
These aren’t a numbered list to pick from. They’re a landscape.
Become the Builder
You are the subject matter expert. You are the single best person in the world to build the AI system that replaces your current role.
If a software engineer tries to build an AI analyst, they have to hire you to check their work. They can’t tell if the output is right or wrong. Only you know your data well enough to validate it.
The skill isn’t coding. Coding is solved. A data professional who couldn’t ship a production application a year ago can build one now by describing what they need. The skill is domain expertise. You know what right looks like. You know which questions to ask. The frontier models and tooling to do this are here right now. They just need someone who knows the domain to sit down and start talking.
Monday morning: Take a question you answered last week. Feed it to an AI with your data. See what comes back. Don’t worry about whether it’s perfect. Worry about whether you can tell what’s wrong and teach it to fix it. If you can, you’re already doing the new job.
Become the Validator
Once the AI is doing the analysis, the problem shifts from producing work to trusting it. Someone has to answer: “Can we act on this?”
That trust doesn’t come from gut feeling. You build it by testing the AI against questions with known answers to establish ground truth. You annotate your team’s historical query library as a benchmark. You set up feedback loops where the people consuming the analysis flag what feels wrong.
Nobody panics about human drivers killing 40,000 people a year. One AI accident makes national news. The AI analyst will face that same scrutiny, and it doesn’t need to be perfect. It needs to be better than you. It already has one permanent advantage: it documents everything, every time, automatically. So your job as validator isn’t to catch every mistake. It’s to build the systems that make trust scalable.
Monday morning: Take the last 10 analyses your team produced. Feed the same questions to the AI. Compare. Track every divergence. That divergence log is the beginning of your validation framework.
Become the Translator
There’s a gap between what a business needs and what an automated system produces. That gap is your job.
A VP asks “why is conversion down?” and you turn that into the real questions. Is it traffic? Is it the product? Is it seasonal? That kind of breakdown is what keeps decisions grounded instead of reactive.
Then you go the other direction. The AI produces findings. You turn them into decisions. You know which finding matters this quarter and which one can wait. You read the politics. Why is that VP really asking right now? Is someone’s job on the line?
This is a human skill. It takes empathy and business context. You have to know the organization and how to talk to people. The AI can do the analysis. It can’t sit in the room and read the room.
Monday morning: Look at the last stakeholder request your team received. Write down the question they asked, then the question they actually meant. Those are probably different. That gap is your job security.
Become the Architect
Messy data and undocumented business logic. The AI can work around some of it, but someone needs to actually fix it.
Analysts work around messy data. They build workarounds into their queries, store the knowledge in their heads, and move on. All that stuff in your head? It needs to get out and into a system. That’s the shift. Stop working around bad data. Start fixing it.
Nothing you do will matter more than this. Every improvement to the data foundation makes every automated analysis better, automatically, forever. Fix a metric definition once and every analysis that touches it gets it right from now on. It’s the analytics engineering job, evolved. Not maintaining tables. Building the data layer that makes trust work. The AI analyst is already doing this as a side effect of getting smarter. Your job is to guide that process and make it production-grade.
Monday morning: Write down the three things about your data that everyone on your team knows but nobody has documented. A metric that means different things in different contexts. A table with a known edge case. A date column that doesn’t mean what its name implies. Getting that out of your head and into a system is the work.
Become the Solver
Do the damn work. Get shit done.
You automated your own domain. You know your data, your metrics, your edge cases cold. Good. That was the Builder path. But here is what happens next. You start noticing things that have nothing to do with your team.
You are sitting in a product review and someone mentions onboarding dropout is up. You pull churn data later that day and see the same cohort. You check support tickets. Same spike, same timeline, same customers. Three teams, three dashboards, three conversations, and nobody connected them because nobody sits across all three datasets. You do now.
That is the Solver. Not deeper expertise in one domain. Broader vision across all of them. Organizations are full of walls that humans built and never questioned. The person who walks into a room they do not own and says “teach me your numbers” is the person who finds the problems nobody else can see. Domain expertise got you in the door. Humility gets you into every other room.
Monday morning: Find a problem that touches two teams. Pull both datasets. See what nobody’s connecting. Then start building the fix.
The Window Is Open. It Won’t Be Forever.
Right now, today, very few data professionals understand what’s happening. Most are still debating whether AI will “augment” their work. Their companies are running AI strategy workshops and pilots.
Meanwhile, a small number of people are already generating months of analytical output every week. In two days, I produced more validated analyses than I’d normally deliver in a month. Not every analysis was a deep-dive. Many were the routine segmentations and trend analyses that eat most of your time. But that’s the point. The routine work is what fills your calendar, and the routine work is exactly what AI handles first.
The people who move now build the deepest expertise, take the most interesting roles, and shape how their organizations adopt this. The people who wait get handed a playbook someone else wrote.
Ten years ago, the people who built the first data teams became the VPs of data. Same thing is happening now.
If your organization won’t adapt, find one that will. I know that’s a hard thing to say. The alternative is worse.
If your organization is fighting it, build the skills anyway. Start with the willing. Let results speak.
The technology is ready. Your organization probably isn’t. That gap between what’s possible and what’s adopted is your runway. Use it.
Automate Yourself Out. Bring Everyone With You.
The new job is three things:
Grow and nurture AI systems. Treat them like people you’re onboarding. Not a metaphor. It’s literally how it works. You talk to them. You teach them. You correct them. You watch them learn. You don’t configure software. You develop a colleague. Every company needs the person who can do this. Almost nobody has them.
Execute on what they produce. The AI will generate more good ideas than you can implement. Your job is no longer generating insight. It’s turning insight into action. Building the thing, not just recommending it. Which is actually the job you wanted when you got into data in the first place.
Bring everyone with you. Open source what you build. Teach people willing to learn. The code costs nothing now, so give it away. The people you help today become the network that helps you tomorrow. This isn’t altruism. It’s strategy. And it’s the right thing to do.
That process of building, teaching, and correcting these systems? It transfers. Once you’ve done it for your domain, you can do it for any domain.
Automate yourself out. Bring everyone with you.
Send this to your data team. Send it to your manager who still thinks this is five years away. Start the conversation now.
Take Care of Yourself
This mindset shift is hard. It hit me hard. Over the past couple months, as all of this became clearer, I went to therapy. I quit drinking. I changed my entire lifestyle. The technology wasn’t the hard part. Watching the thing you’ve spent your career getting good at become automatable -- that’s its own kind of crisis. It rearranges how you think about who you are.
If you’re feeling that right now, you’re not weak. You’re paying attention.
You need a clear head to build what comes next. You can’t reinvent yourself while you’re falling apart. The decisions you’re going to make in the next six months will define your career for the next decade. Make them clear-headed.
When you start doing this, you’re going to get unlocked. You won’t be able to stop. It’ll be scary and exhilarating at once.
Get outside. Move your body. See your friends every week.
Take care of yourself while you do it.
And start.
The system I built is open source.