Aside from a few weeks training on an unrelated Masters I'm IT-unqualified, but got a job with an IT company making software for an industry. I started out coding, but knew I was never going to be great at it - although it can be really satisfying to make something 'elegant' that's yours.
Then moved into a more customer-facing role, trying to capture what they wanted the software to do. Learnt elegance was maybe of less importance, than solving real world problems.
Then moved into Product Management, which was maybe the first time I felt a 'good fit'. Gave me the opportunity to come up with 'big vague ideas/themes', and defer the implementation to the architects and devs who were actually good at the job. You try to break it down into consumable chunks - but it's on you to make it all come together.
Final thought is just that even outside of dev, I now realize there's a massive spectrum of people within it. Some want you to absolutely nail-down the down criteria and will deliver against it. Others want to understand why, and if you can explain it relatively succinctly, will come back with suggestions on how stuff can be improved.
I guess my point is that excellent coders are required - but the "rockstar coder trope" overlooks the vast majority of people working in IT. e.g. If you've say spent a decade serving food in or running a restaurant, you've got a way better understanding of what the requirements of a POS system are, than the people creating it. If you want to move to IT, you need to learn the vocab and grammar, but you don't have to be fluent - bring in your experience. IT can only solve an understood problem, and being able to articulate that is a prerequisite to a solution.