Required level to work as a junior?

Question

IT education

Good afternoon!
I am a 1st year student of one (still good in my eyes) St. Petersburg university.
I came here already with a large (relative to 95% of students) baggage of specific knowledge, which even now allows me to work, probably at the junior level (in fact, I already work). The level that this university gives ... let's just say, I do not quite believe that all my classmates will work in the profession after such training.
However, I myself try to fool and blur the brains of my classmates by saying that working as a junior involves initial training within the walls of the employing company, and I myself believe in this. So really, what is meant by a "Junior Developer" job? The fact that I should have just the most basic knowledge (a la the implementation of the simplest algorithms and knowledge of data structures) or specific knowledge that will make it possible to join the workflow on the very first day of work?

Answer 1

Who else would tell the employer about this.
And then, sometimes they recruit Juniors, and the requirements are like for Seniors.

Answer 2

The best thing to do is to google and see what the market currently understands by the concept of Junior specifically for your industry.
Junior C++ dev and Junior php dev can differ greatly in terms of skill quantity/quality requirements.

Answer 3

You know, no one can tell you for sure. It will depend on the company where you want to work and who you want to work with (whether you mark Junior in Yandex or Opa-shitsite, write in PHP or Assembler). You can spend a lot of time preparing and it will not give any benefit.
Therefore, my advice is to go to a couple of interviews at once. At first, you can embellish your skills in your resume. And during the interview, honestly say that you really want to work and are ready to learn in the process. For Junior'a, the main thing is just to be adequate and want to develop very quickly. At the interview, you will understand what areas and knowledge are needed for work and you will be able to pull them up in a couple of months. In addition, if you show yourself adequate, but lack knowledge, the company will not mind interviewing you later.

Answer 4

Junior is a specialist who is able to perform the functional duties assigned to him, with a "discount" for the lack of experience in a team.

Answer 5

I once interviewed in one small office, so there was a very interesting sign, it outlined the levels of the developer and his knowledge / skills with responsibilities. It was very interesting to be closer to a senior developer. Duties were prescribed for him, for example, to conduct master classes for colleagues and share experience.
Oh, I wish I could find this sign or something similar ...

Answer 6

How do you agree. From "no work experience in the specialty, the main thing is to have a head on your shoulders" to "at least 2 years of work with our technologies." Well, as I once noted (like here ), in my understanding, a junior should want to learn new things and do it on his own . Nothing is forced into the head.

Answer 7

I'm slowly going to specialize in c# for the second year, and almost all the vacancies that I saw had 2+ years of development. Something tells me that this is 2 years of full time, and not like me, a couple of hours in the evening for the soul ...
Although at such a pace I can rather finish and release my solution, it seems to me, while gaining experience in the full development cycle

Answer 8

IMHO - with experience less than 1-2 years.
The trick is that although experience is important, it is not decisive. Experience won't do much to improve brain function.