E
E
Eduard Vakhrushev2019-09-10 01:52:07
Career in IT
Eduard Vakhrushev, 2019-09-10 01:52:07

How to pass an interview for a junior developer?

Hello!
I have a fairly popular problem that almost everyone had, constant rejections or ignores after interviews. I have no idea what is wrong, because the questions are asked there quite superficially, whether they are familiar with Git, Linux, many-to-many / 1-to-many relationships, which IDE I use, they rarely ask about OOP with its polymorphism and encapsulation, which is the principle of problems does not call.
In general, having probably failed about 30 social security services, I couldn’t think of anything better than to look for people who are ready to interview me for 10-15 minutes and give an adequate answer what’s wrong and what to pay attention to, I hope there are such people among you.
Here is my resume, so that it is approximately clear what's what
https://spb.hh.ru/resume/e5dc680aff03f122350039ed1...
Zp, it seems to me, I’m asking for not much, so I think there shouldn’t be any pitfalls, I suspect that all the problems are due to uncertainty, but it somehow comes by itself, even if the interview is on light, I can’t do anything with it (

Answer the question

In order to leave comments, you need to log in

3 answer(s)
D
DevMan, 2019-09-10
@Norgoroth

the question is meaningless: each office has its own selection criteria.
from the explicit one - remove the salary altogether, and work for 3 months followed by a break for a year is not very attractive for experience (I would remove it at the initial stage).

E
EVGENY T., 2019-09-10
@Beshere

If they don’t even charge for food, then you won’t get into the technological stack completely and you have experience that people don’t understand. The solution is simple, write after each social security in two pieces of paper:
1. First, write what the employer wants: buzzwords like Spring, Angular, etc.
2. In the second, write what you failed on: OOP principles, types of joins, O (N), reverse the line, etc.
According to the first list, select the most popular, and what should be pulled. Buy books, open the documentation and forward to the assault. The next time when there is a question about the experience / knowledge of another fashionable bullshit, calmly tell about it what you know.
Practicing the second list will give you a chance to casually display knowledge and skill, because these questions are repeated in one way or another from place to place.
Good luck, I understand how you suck.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question