How to understand that you are a Senior Developer?

Question

Career in IT

How to understand that the person who is in front of you is really a standing developer and not a charlatan with a tambourine?
Or how can a developer understand that it's time to set a "new" tariff?
After all, technology, wow, how fast they go, and you seem to know so much today, and tomorrow nothing. And all your seniority comes out in such a way that you are taught by those who from this area, for example, have already written on a new framework, or have studied the mechanics of the library in more detail.
Is there any limit?
Perhaps a stack?
Stack of what? Why?
What should he know, and what would be a plus?
Should he know the 0.0.0.0.1 version of the 70 languages ​​that are asked in interviews?
What about questions about x2*24/132*15e-4+132?
Or write working BrainFuck bubble sort code here and now on a piece of toilet paper without a pen or pencil?
How many frameworks to know, how deep?
How many languages, libraries, how good?
Work fast or slow?
How do you imagine SeniorDevelopera in general?
Where to look for this "Prince on a white horse" or "Pig in a poke"?
UPD. https://docs.google.com/document/d/1FVvoSY35YD4BfA...

Answer 1

Senior is, first of all, a tremendous experience. He should work not fast or slow, but exactly as much as necessary to solve the problem. When asked to solve some garbage on a piece of paper, the seigneur will probably get up and leave. Ask him questions about past experiences and he will overwhelm you with such a stream of information that there will be no doubt.

Answer 2

I divide it like this for myself:
junior = demands to be explained how to do the assigned task
middle = performs the assigned task
senior = can tell in what ways the task can be done and what are the advantages / disadvantages of each of the methods, and of course, can complete the task in any of the indicated Ways
To understand what a senior is in front of you, you need to set him a task and ask how many solutions he knows and what are the pros / cons of each of them.

Answer 3

Ask another Senior Developer.

Answer 4

Alas, today you know a lot, but tomorrow nothing in real life exists.

Answer 5

In fact, apart from a test period, nothing will tell you about it. Abstraction from languages, now there are a lot of different languages, most of them are similar in syntax, for a senior to fix some kind of bug in an ancient service written in some language little known to him, should not stop him. He must learn quickly, he knows how to do it right. Know the intricacies of your primary language. Do not say that he will come and rewrite everything here. Able to predict the terms of work (and most importantly, possible places where these terms may increase). They are not afraid of new tools and features. Has the ability to write a piece of code (we are talking about memorized algorithms, but about just business logic) of a medium size, so that it is more likely to work right away.

Answer 6

Instead of writing code for your project, it will mow down unnecessary pieces and reduce existing ones. Make code simpler, clearer, faster and more stable.