I'm just a couple years behind you and have been having a related discussion with my manager recently. He identified that for developers, there are (at least?)

I'm just a couple years behind you and have been having a related discussion with my manager recently. He identified that for developers, there are (at least?) two paths of progression: either you move into a management role (like technical director) or you move into some sort of domain expert/specialist role. Like you, I wanna make stuff, not manage people, and I told my manager that as well so we could set progression expectations. What this has looked like for me is still that I'm not doing as much coding as I was as a junior, but I am documenting a lot of things, formalizing development processes, teaching peers about dev ops practices, and so on. I keep on top of new developments, understanding what's worthwhile for our team and why, and disseminating that information to the rest of the team. My feeling is that you can be safe from younger coders if you continue to learn from your work and show the expertise you've gained from your years. On the other hand, I have also seen senior-titled engineers whose code was indistinguishable from fresh graduates, and that's a bad place to be.