What is the difference between junior and middle? and Senior?

Question

PHP

Well, how to understand this fine line?
If we can say about a senior that he should know almost everything, be a guru, then what should a middle man know and be able to do? Junior? How do they differ from each other?

Answer 1

Here's what it looks like from t.z. employer
- the interview
speaks exclusively in slang (most of which he cannot clearly explain), he is ready to write a new OS alone in a week, or two - in one and a half, unless for this you have to learn assembler, despite his young age, already the owner of the rights to both versions and one backup of a personal website with a photo of a cat in a pink frame and knows that the singleton is an absolute evil, although he cannot write it without mistakes.
- trial period
fussing for a long time with the settings of the workplace, which regularly flies under the weight of thousands of plugins, shells and screensavers, pesters admins, finds two (spelling) errors in the project documentation and one quick alternative way to fork from SVN, after which the project, unfortunately, does not build not only for him, but for the whole team. It is taken to fix everything immediately with the help of another miraculous plugin (an unexpected bug in which two middles have to be fixed), after which it is forcibly deprived of the root, plugins and shells and begins to study the project under the strict control of swearing middles.
- work
learned how to build a project, write tests and commit without dropping the build, understood the meaning of many slang expressions, made friends with middles and admins, does not get confused in the names of key technologies, radically reduced the number of plugins, deleted the site with a cat, it works.
- the interview
is not deep, but confidently knows the key technologies, the difference between an abstract class and an interface, and three or four polite answers to the question "how long can it take."
- the probationary period
has joined the project and is working.
- work
is stable and productive.
- interview
indicates an error in the test task, offers two solutions to the problem that the team has been puffing over for the last week and an alternative technology stack to which the project can be transferred
- the trial period
refactors the project, makes the build joon-stable, writes an algorithm for the killer feature along the way, scheduled only for the next quarter and at the end of the trial period organizes a workshop where he presents his achievements "in his spare time" on transferring the project to another technology stack, in which most of the functionality of the next release has already been implemented.
- work
helps the team with kicks in the transition to a new stack approved by the management, in which he is actively supported by jun, inspired by the fact that now no one will notice his accumulated jambs, transfers the project to a new stack, doubles productivity, transfers again a year later, periodically generates ideas for new products, may disappear for a week and return with a new feature, or may go on vacation accumulated over several years and never return, because. I accidentally met an old friend who proposed another mega-project with a giga-salary.

Answer 2

Salary and the ability to say "I am a middle" or "I am a junior" and convince the interlocutor of this.

Answer 3

Just went through a series of interviews for a middle position (js language). I’ll say for sure that the middle is required to understand how the code works in the mind, how to fix the non-working code in the mind. Understanding some subtleties in the work of the interpreter, what updates the language had and how to use features (this is rather a feature of js es17). At the same time, understanding of algorithms, design and programming patterns (i.e. Know what a factory, singleton, etc. is, how MVC differs from MVP). And of course, have experience in commercial development on modern js frameworks.