Just looked through the interview logs. 99 interviews. Two days ago, I shared some interview experience on the Intranet, and I also posted it to the nuggets, barely maintaining my activity. The interviewer can refer to the interview ideas, of course, all the development students can see, and maybe have some new thoughts on how to improve themselves.
Know what kind of person you want to hire
I always think interview is like blind date, in addition to the inspection of the hard ability of the interviewer, also depends on fate. The predestined relationship part honestly depends on the subjective feelings of the interviewer. Therefore, as an interviewer, you should first determine what kind of person you or your team want to hire, and most of the time, you should also consider HC. Such as more than you are now only P5 HC, which do you want to recruit is the sort of come to work, rather than some more potential, inexperienced but also have to take a while to learn, that besides the basic code, front-end, used for some technology stack (as long as there is mentioned his resume) asking questions.
Something I personally value
resume
If you have a blog or github link, you will usually go to see it. Bonus points for good content, minus points for bad content, or even fail your resume directly.
Thinking in daily work
In general, AT the beginning, I would ask him to introduce the projects he had done, and then I would ask him about some points I thought I could dig deeply during the description process, or I would directly ask him about the technical challenges or interesting things he had done. If it was an on-site interview, I would ask him to draw pictures on the paper and elaborate on them. This part if it is some of the more experienced, or the title is the interviewer architects, technical manager, you can focus on architecture design, technical scheme, let him tell me did draw the easel composition, tell me about his plan and the comparison of some existing solution on the market, at the time when facing some choice perspective and evaluation standards, and so on.
Ability to code
Code ability is actually the core ability, including thinking logic and JS language proficiency inspection. If the two code questions on the pen test are not particularly good (of course, at least to be able to answer a question, two questions can not answer the general written test will not pass), you can talk to him about the optimization of ideas, give some hints, see the other side’s reaction. If you do a good job on a pen-based test, you can ask him to do something by hand while you’re asking other questions. Such as:
If you can call/apply/bind, you can write a call by hand, even if you haven’t done it before. Call can change the orientation of this by assigning this to its first argument, obj, and then calling the function from obj.
If you are familiar with Vue, ask him how Vue data binding works. Most people can answer defineProperty and observer (subscribe and publish), so ask him to describe observer. If he can describe observer, he can implement an Observable constructor.
Of course, there are a lot of things for him to write, because we are not recruiting any algorithm master, there is no need to find difficult algorithm problems for others to do, the best in the process of asking questions to find some requirements for him to realize. For example, if you are asking about throttling and anti-shock, you can search for an example in real time and ask the person to implement debounce. Even if the person has not heard of the concept of throttling and anti-shock, they should have the right idea to implement it.
Framework related and JS based
The typical interviewee will include a few things that he or she is good at. Ask as many questions as you can. For example, if they say they are familiar with Redux, ask them how they use Redux in their projects, what Redux middleware they have used, how middleware is implemented, what scenarios do you think are really suitable for Redux, how Redux is implemented… In my interview experience, many people write that they are familiar with Redux when they are really just “used.”
And then JS, if they have on their resume closures and prototype chains and ES6 features like Promise/Proxy, you can ask them. If your resume is thin, ask him or her what he or she is good at, and then try to ask relevant questions.
Technical breadth
This is some knowledge outside the “front end” field, which is not required. I would ask if there is any on my resume, mainly to see active learning ability and interest in technology.
Soft skills
In fact, during the interview, you can see a person’s communication skills and general work attitude. When asking about a project, you can ask some things related to cooperation with others, how to promote your own project landing and so on. It is understandable that some students are nervous during the interview. However, some students have very good resumes and are eager to learn from their blogs and Github. However, they are so nervous that they cannot speak fluently. After all, psychological quality and ability to work under pressure is also an essential part of the work.
conclusion
This article is subjective and brings my own personal preferences (I never ask CSS for example… Because I don’t think our business requires a lot of UI, and people who have written a few projects can handle our UI), but that’s the way it is, it depends on the interviewer’s personal preferences. Most of the time I just read what’s on the resume and ask for something outside of this article. The interview is not a test. The process of the interview is to make the interviewer recognize the ability of the interviewer and willing to work with him. So even if there’s something on my resume that I’m not good at or that I haven’t touched on, I’ll ask for it, and if they can describe it clearly, that’s a bonus, and I’ll learn something new as an interviewer.
PS: I never expected to get a comment from someone who shared a little interview experience and what I thought was important for self-improvement. Reminds me of Sun’s picture:
Of course, welcome to exchange experience, questions and suggestions can also leave a message ~
