The introduction
It has been more than one and a half months since I wrote about the interview. During this time, I not only found my next job, but also became an interviewer when I entered the job. I am now in charge of building the Shanghai development team from scratch, and the interview has become the focus of my work for the first time.
Speaking of interviews, I have had a lot of trouble in the past two years. I have changed jobs three times, and I have had 30 interviews, which seems to be more times than I have interviewed other people.
My interview strategy is basically “to match training”, usually continuous interview, find their weaknesses, and then targeted to strengthen.
How to Interview candidates
However, as an interviewer, how to formulate their own investigation strategy?
“Attack and defense are of the same origin”. From the perspective of specific questions, I recall the companies I interviewed before, and the back-end interview questions can be basically divided into the following categories:
- Pure algorithms or data structures
- Programming language features. For example: golang’s GPM, js’s delete operator.
- Use of Redis. High concurrency cache design and distributed lock ask the most times.
- MySql indexes and locks (this is almost mandatory).
- Project Experience (It seems that there are few problems with project experience. On the one hand, it may be difficult to have the same project and can directly reuse experience. On the other hand, it is a test for the interviewer to discern the value of your contributions from your descriptions)
- Offline big assignments (Talk is cheap, show me the code.Maybe it’s the best way, but it takes more time.)
In my last article, I argued that the 1-4 test is based on a perspective that is easy to quantify and measure, and that this simple and direct survey is a good way to approach the “buyer’s” market, that is, the big companies that don’t need to be interviewed. After all, if you have to meet five or six people a day without a template, you really don’t have the energy to ask them all. (As a result, nowadays the popular interview can also be memorized)
If there are not so many people coming to interview, do you have to focus on project experience? (It must not be black and white)
This is really to be considered, some people are doing a lot but can not say; Or it’s so “easy” that you don’t feel it’s worth it. But the most afraid of is, a person said that the smallpox is drunk, in fact, have high eyes and low hand, after entering office, or a black sheep.
Best Fit is better than Best Engineer
I think, if there’s a strategy, I think there’s one. Find the right one.
It’s really not too much trouble! A long time ago (maybe three years ago), AS an Engineer, I used to think that Best Engineer must be employed. When my position became a team lead, I needed to consider more angles and find Best Fit after balancing.
The degree of Fit, on the one hand, depends on specific skill requirements; On the other hand, it also depends on the composition of the current recruitment team, the position budget, the different stages of recruitment, management costs and even the consistency of the three views.
So, if you’ve ever had an interview where you had a great conversation and didn’t get an offer, it’s probably not because you weren’t good at it. It’s more likely that you weren’t the best fit in some other area.
Now I have two open positions in thunes Shanghai team: full stack development (vueJs+ Python or Golang) and back-end development golang.
Considering the new projects to be started soon and the reserve of my own technology stack, it is most suitable for me to recruit a full-stack development, or the development of the prenatal end is better than that of the back-end end. Our interviews mainly focus on large assignments, with more emphasis on candidates’ engineering skills. Everyone is welcome to recommend and recommend. Please send your resume to [email protected].
By the way, how can it be a job Posting?
