I'd call this "not junior". To me, "senior" would be the person leading a small multi-person effort or doing the hand-holding of junior engineers.
and if you can find: POSITION CLASSIFICATION STANDARD FOR ELECTRICAL ENGINEERING SERIES, GS-0850 ELECTRONICS ENGINEERING SERIES, GS-0855 TS-3 February 1971 It has good information on what level engineers are working.
I think you have the correct frame of reference, senior level positions are those who are used to handling projects/questions without guidance from others (although most senior folks are willing to ask questions to learn)
I feel I can do anything as well, because if I can't then I will simply find a way to learn it, because to me it's not a question of whether I'm capable of learning it but how fast I'm capable of learning it. So I'd be careful with that vibe as a heuristic ;-)
i.e. how far along are you in the progression of... - being given clearly defined tasks - self-guided work on feature level - self-guided work on project level - self-guided work on team level - self-guided work across teams etc.
This is my definition. Can I assign the PROBLEM, "important customer ABC has some kind of weird bug, talk to Nav in Tech Support" and know that problem is now off my plate. They'll usually solve it or come back with a hot fix recommendation. Worse case, they come back with a "we can't figure it out, we need more eyes on this".
The important part is this: the problem is now something I don't need to worry about.
If I need to follow up, they're not a senior developer. They're a junior with skills.
People I consider senior software engineers have a can-do-anything vibe about them. They have a wide range of skills in the field, and have that T-shaped experience profile: there's some area they seem to know everything about, and then they somehow are able to say something sensible about a whole lot of other areas. For instance I worked with a guy who wrote financial exchanges but could also write a modern front-end, understood how kubernetes worked, and knew a fair bit about databases. You couldn't throw out a term that he couldn't place (X is a language / framework / pattern / OSS project), and you couldn't come up with a problem that he didn't know the closest well-known adjacency for.
That's a vague outline of what I think a senior dev is.
To get there is a long story. I think you need the good fortune of not being siloed in something very specific or superficial. That might even include having the "good fortune" of being forced to change jobs a few times. You also need some luck in your personal life to be able to explore a bunch of stuff in your own time, plus some funds (probably less relevant today where everything is an online service).