-
preface
With the development of the business, the company has been recruiting people, and interviewed 50 or 60 people before and after, and communicated and shared with other team leaders, and found that there are always some candidates who make the technical officer speechless.
-
From a technical interviewer’s perspective
-
Resume problems
-
I’ve served too many companies. What would you say if you stayed at each company for less than a year and worked at three or four companies? Loyalty is low, resistance to differential pressure, can not long-term development and so on, at the beginning of the brownie points pulled down.
-
Technology stack appears in the words proficient, in-depth understanding. What is a master, estimates that few people dare to say, to see those words will only grinned (silly fork), a description of the technology stack for the technology behind the q&a is set, the more you write the cow force of the more likely they are to be friction (unless you really cow force, hand tore the interviewer), here there must be a balance, both can bright eye and can answer.
-
The project went on for several pages. Is it interesting to write so much? Really boring, the interviewer does not know your business is not interested in knowing your business, more will only feel that you do very fragmentary. Write a few representative, iteration of several versions, maintenance of a year or even a few years of more than the project, so that people feel that you are polishing a product rather than doing requirements, can pull up the relevant brownie points.
-
Self introduction Questions
-
This is really a headache, I think in addition to the introduction is a inherent pattern or the interviewer is listening to your introduction while browsing your resume a concurrent process, but often some candidates make you speechless. For example, a candidate who has worked for more than three years, his introduction is from college graduation to the present, the assembly line is the same to describe to you, you can live? It’s rude to interrupt, and uncomfortable not to. I understand also find relevant information, good self introduction is generally not more than 3 minutes, simple to introduce myself on the position of a company, is responsible for the function, simple to describe the recent business situation of the project, also almost. 3 minutes the interviewer probably will be able to look at the resume to you have a intuitive impression, a good beginning will have a good start.
-
Question and answer session
-
You should speak clearly and be familiar with the business you are responsible for. Sometimes the candidates are not familiar with their business. This kind of pass is basically passed
-
To write their own technology stack technology to have the ability to describe the relevant, such as you say you understand the source code, understand the underlying principles, if asked to answer is also very low related brownie points (unless it is difficult, otherwise is the candidate ability has a problem)
-
Depth and breadth of technology. The technical interview is unlikely to ask only about the technology stack on your resume, so your knowledge or familiarity with hot and cutting-edge technologies will stand out. If the underlying principles and implementation are clearly described, you’ll be able to stand out from the rest of the candidates.
-
Extended link, this is a generic, may be asked to improvise, such as suddenly ask you a technology or he doesn’t understand, I often ask candidates, I’ve never used this framework, you tell me something about), online question processing, some daily view of the development process, the code of specifications, etc., such as no clear answer to these questions, here is the test The candidate’s emergency response. There is no doubt that good performance is what you accumulate on a daily basis.
-
Ending part
-
The template is, “Is there anything you’d like to know?” , is too many template type answer, ask technology stack ah, ask the company structure ah, and so on, do not say there are problems, mainly is too ordinary, good no highlight. I was impressed by the responses from several candidates: “I’d like to know why the company wants this position, whether it’s a departure or a business necessity.” “I would like to know the size of the company and the business associated with it “…. There’s an immediate difference from the average candidate, a difference in depth.