…“what is your story and experience?” , and linking in the point about “can you combine being manager and practitioner?”
I want to think of myself as being multi-skilled, but only because I can read and input on a c/C++/java or even a C# pull request. Teams need people who can do this in order to get a Jira task across the line. Code review even by a duck has value when everyone is too busy to lend you their eyeballs, but when the tester can eyeball a logic change, it can lead them to a deeper system or E2E behavior knowledge. Your skills as tester do need to be manual and automation as well as CI/CD maintainer. And that often means knowing just enough coding language skill in all the tooling glue code. I suspect, more than ever, you are dead as a tester if you don’t apply yourself to all of the testing assistance pieces.
Not knowing how a tool helps, or it’s specific value, to the quality picture is a big ask, and I find old rusty tools in the drawer all of the time. Go looking! Which comes on to the manager role, I think you can be manager and practitioner. I’m not good enough myself to, but if you are able to manage the process, and be a people organiser with test skills, these people do exist. I want a manager who knows which old bins to go hunting around in for old tools, and when it pays to create new tools or just buy them in. All testers should want to get your promotion to test manager, and then carve out time to get your hands dirty at some level. It’s not for everyone to be both, but when you can, you have so much more of a quality impact than a practitioner. (At least in my mind.)