I started moving away from code-only positions once I reached 10 years in the industry - 2015. Now, I am 37 transitioned and while still write A LOT of code ( mostly back-end, high performance APIs, DB stuff ), review a lot of code, but bareley touch front-end work. I grok it, can make the changes, but I am too old for front-end work. At my role ( 1 level away from C-Level executives) it's not expected to code at all…
Let's say there is a big project in your company called DigiRefresh - the projects aims to consolidate all data sources, standartize them and in the future extract correlated value via AI/ML - one of the most common projects in modern-day IT.
Now, someone at the TOP has secured N million dollars for this project, but he has also 5-6 other N million dollar projects. Such big projects are more or less the soldiers/power point slides of the C-level executive by which he justifies his existence to the board of the company.
All these projects on high-level sound like a must-do. Your job most probably will be to make the vision of the big guys into reality - deliver it. Which is a messsy process. Big guys don't care about the technology that much, they don't care how it will be done - they just want it done, because somebody commited to someone else for a date that makes somebody look good :)
So, your job 99% of the time is to deliver and deal with the small details like what techology will be used, how many people are needed for the tasks, orchestrate it and give yellow-green-red style reports to the top management.
The more you take away from their worry and the more time they have to play golf and the more seamless delivery you provide - the more you will raise in the corporate ladder.