Every part of your existing job is transforming before your eyes.
If you cling to definitions and static roles, you're going to have a bad time.
Systems design, architecture, database fundamentals, a bit of SRE. That matters. Not coding and syntax and toy problem solving with data structures and algorithms.
My own experience is that coding, syntax, and some kinds of toy problem solving are important skills to use AI coding tools most effectively. I routinely get PRs these days whose descriptions seem plausible but are clearly wrong from a glance at the code, and I've had times when I'm unable to communicate to someone why a PR is wrong because they're not able to form a sufficiently detailed mental model of what it's doing.