The shift you're describing is real, but it's actually clarifying what your actual job is - and it's not the mechanical parts. The stuff that gets automated is usually the stuff that was never the point anyway. I've watched this play out with people around me: the ones who panicked about being replaced were fixating on the tasks they could hand off, while the ones who stayed engaged realized they'd suddenly gained time to do the thinking that actually matters - figuring out what questions to ask, why the data matters to the business, how to communicate findings to people who don't speak statistics. That's the work that compounds and gets harder to replace, not easier. Your job security over the next five years probably depends less on typing faster or knowing one more Python library and more on being the person who can say "here's what this data actually means for what we should do next."
The honest move isn't to bet against AI taking over routine analysis - that's probably coming. It's to intentionally shift where you're spending your energy now, toward the parts of your work that currently feel harder or slower or require talking to humans instead of running code. That's where the meaningful part lives, and where people actually need someone who thinks.