(This article is reprinted in self – delight bytes)
Recently, we have contacted a lot of social recruitment programmers through our Lebyte platform, from junior to senior. I will not mention those who failed the interview or even failed the resume, but I found that most of the programmers who passed the interview with a high rate can not escape the following points:
01 –
High degree of job matching
This means you should screen your resume for positions that are a good match or are of high interest to you, rather than casting a wide net.
Otherwise, the recruiter will think that you are not sincere enough and that you are not clear about who you are, which will either fail to respond to your resume or send you on a tour, which is a waste of both parties’ time.
02 –
Full preparation
I find a lot of programmers interview in two mistakes: one is JD mentioned in the job requirements and then specific to say, but do not have a deep thinking about what they do; Second, they just talk about their daily work without thinking about the technical field or career plan.
The first kind of letbyte education, where programmers do my own work, is also afraid to recruit. If you can’t even explain what you are doing every day and the essential value of it, how can I believe that you can do a good job in this position?
The second type of programmer still has a lot of room for improvement. As an employee who only uses his hands and doesn’t use his brain, his development is very limited. I can’t see where your upper limit is.
So in the interview, in addition to fully understanding and understanding of the current job, it is also necessary to jump out of the routine execution and have in-depth thinking about their future plans.
03 –
Understand the interviewer’s psychology
Interview is actually a psychological game, is a very test of a person’s ability to resist pressure.
You may have heard of the “pressure interview”. Different interviewers will give you a stressful interview at different times and in different situations, and you can’t feel it. That’s why some people pass the interview when they think they look bad, while others fail when they think they look good…
How you feel about the interview as a whole is not an indicator of the interviewer’s impression of you. Sometimes he or she is just trying to gauge how well you can handle pressure.
Is, of course, there are other aspects can ponder the interviewer psychology, such as the interview he often see mobile phone watch, big probability is let him not happy with your answer, he is a bit impatient, at that time you will be offered to “my answer is in the direction of” or “this do you have any questions?”, the direction to the snapping back as soon as possible, Otherwise, you might hang up after a while because you don’t understand what the interviewer wants to hear.
04 –
Don’t pretend to know what you don’t know, but have your own thinking
It’s normal to ask questions that you don’t know how to answer. After all, today’s technical interviewers love to test you with tough questions or questions that they can’t solve in real life. But I hate people who pretend to have solved similar problems when they don’t understand them, and then ask them to elaborate and find a lot of flaws.
Wouldn’t it be nice to say you’re new to the subject, but have some personal ideas about how to solve a similar problem? Why does it have to be forced?
I am not afraid to recruit people who do not know some aspects, these can be learned by themselves, very quickly, interview building rocket work screw. But I don’t like hiring people who pretend to know what they don’t know. It’s a joke to me.
As an ancient saying goes, “Know yourself and know your enemy, and you can fight a hundred battles with no danger of defeat.”
This sentence is also applicable in the interview, fully understand the job demand, the interviewer’s psychology, the nature of the topic investigation, is every programmer in the interview can not be ignored, but also decide whether to pass the interview several key points.