You have fallen into the trap of just looking at a job title.
In IT in particular, the specific job responsibilities for a role vary widely. An IT Manager (or in some cases, even a director or VP title) may have no or few subordinates and be expected to do technical work. I am a senior person with a lot of management experience, and I've learned to ask close questions about the exact responsibilities of a job. "VP of Engineering!" "Oh really, how much of this role's time do you expect to be coding?" "60%!" -> (Either a startup, or just a place with bad managers.) Some things I can't do, other things I could but I'm not interested in individual-contributor technical roles any more.
"IT Manager" at many places, especially small shops, is "the one person who knows everything about the network, PCs, phone system, etc etc." At some places, it is a pure management role with largely personnel management/project management/financial responsibilities. There is no "right answer" to what an IT manager is and thinking that way will lead you into a lot of problems.
You don't know unless you ask very specific questions about what the role does. A good question is "what does the average day look like," "what hands on technical tasks will this person be doing..." Then match your abilities and interests with those responsibilities.