What kind of resume are you looking for? .
The relevant resume template can be obtained by replying to “template” in the background of the public account “Programmer interviewer”.
Technical interviews usually go through at least three rounds:
- Basic interview: mainly investigate the questions related to basic knowledge in the job and resume, including some interview questions about algorithm and scene design, which may involve on-site coding.
- Project interview: mainly investigate the resume involved in the project, will involve your project related business knowledge, role, technology trade-off, technology and so on.
- HR interview: This aspect is usually the check of HR, mainly involving behavioral interview, to check whether the candidate’s values match the requirements of the company, how stable the job is, how good communication and collaboration skills are, etc.
Of course, the primary duty or school recruit students would involve a written examination, quite a lot of companies will face at the scene for a round of telephone interview before, the purpose is the most quickly and efficiently to does not conform to the requirements of the candidates, for individual needs the inter-departmental coordination jobs will involve cross interview, such as the front end will be the backend the interviewer interview candidates, some management demand jobs or important This may involve a director interview or VP interview.
A normal technical interview process (taking the project as an example) is divided into three parts:
- To introduce myself
- Project (technical) investigation
- Ask questions of the interviewer
So how do you prepare for a technical interview and take the initiative?
To introduce myself
Almost all interviews begin with an introduction of yourself, so it’s important to understand why this is often the first step in an interview.
Why do I need to introduce myself
First, there is a very common problem is that the interviewer is likely to just get your resume, he needs when you introduce yourself to a quick look at your resume, interview the interviewer a lot because technology is a line of employees, interview the candidate is only a small portion of the work, in many cases is not to read your resume in advance.
Secondly, self-introduction is actually a warm-up, the interviewer and the candidate are actually strangers, no matter in the interview or other circumstances, self-introduction is the starting point for two strangers to communicate with each other, but also a warm-up way to ease the awkwardness between the candidate and the interviewer.
Finally, the introduction is a way to present yourself and lead to the technical interview. It’s your chance to dictate the direction of the technical interview.
Knowing the above reasons, we can be better prepared to introduce ourselves.
A few essential elements of self-introduction
In the final analysis, self-introduction is a warm-up exercise, so do not take up a lot of space, on their birth experience to college like a rundown account, often interrupted by impatient interviewers, and this also exposes the candidate’s speech lack of focus, general communication skills shortcomings.
However, some key information must be included, and personally, the following information is required:
- Personal Information: At least reflects their names, positions and working fixed number of year, seniors must to introduce your own education background, if his former club as a giant (such as BAT) best, your record of formal schooling is bright spot (985 people or similar to the letter the CS college) best, what else have a girlfriend, is not only no one care about, Don’t take up space. This part focuses on “Who are you?” .
- Technical skills: Briefly introduce your technology stack. Don’t mention that you have simply used it, written a few demos or looked at the documentation. This section focuses on “What can you do?” .
- Skills: focus on the introduction of their skills, such as performance optimization, high concurrency, system architecture design or communication and coordination skills, do not exaggerate, to be realistic, this is the focus of the later investigation. This section focuses on “What are you good at?” .
Introduce yourself with a purpose
Focus on matching your current job’s technology stack
Your interview resume may contain a variety of skill stacks, but you need to match your introduction with the skills of your current position.
For example, if you are interviewing for a mobile H5 front-end development position, it would be unwise to highlight your mobile front-end experience in your introduction, at a time when it would be unwise to talk about how you supported your company’s Web project with Node.
Do deliberate guidance in self-introduction
If your introduction is like a run-through without any point, it’s difficult for the interviewer because he can’t follow up…
And as long as you make a little guide, for the most part the interviewer will pick you up ever, such as “you highlighted in the introduction of a project, met with some difficulties, and then is captured, you how good effect, and so on”, if I were the interviewer will ask “your xx xx project later the difficulty is how to solve?” .
The purpose of the interviewer is to examine the candidate’s ability and make an assessment of the candidate. Therefore, it is necessary to know what the candidate is good at and whether he or she matches the position. In most cases, the interviewer is willing to be guided by you intentionally or unintentionally, so that the communication and assessment of the two sides will be smooth, rather than deliberately making things difficult for the candidate.
How to prepare for self-introduction
In fact, the best way is also the most stupid way is to write down the self-introduction, the self-introduction must reflect the above mentioned several major essential elements, in the interview before the simple several times, can introduce the content of the smooth expression can be, avoid the same as the back text.
Self introduction of time best control between 1-3 minutes, the time the interviewer going over your resume, the interviewer just after watching the resume then you introduce yourself to the rhythm of the questions is the most comfortable, don’t come up to 10 minutes, the interviewer waiting time would be very awkward, so long that you must is a laundry list of self-introduction.
Technical inspection
At the beginning of a good technical investigation, there must be a good introduction and guidance. There is a situation that we often meet:
Candidate said a lot of key introduction, the interviewer was speechless, completely can’t get the focus of the candidates, also don’t know what candidates are good at, what is the window, and then in his resume technology stack the company is in the use of technologies, candidates at this time also started to sweat, because he’s good at it, this technology stack is not answer also have a hard time, The guidance and in-depth questioning of the interviewer did not achieve good results, and the interview was carried out in this awkward atmosphere. After the interview, the interviewer evaluated the candidate as not skilled in technology and not having a thorough understanding of the principle, and the candidate felt that the interviewer only picked questions that he could not understand.
So in the front part, we must do a good job in guiding the interviewer’s questions to the area we are good at, but this is not enough, the so-called do not fight unprepared battle, we still need to prepare for possible problems.
So how do you prepare for potential interview questions?
For example, if you are good at front-end performance optimization, you have done a good guide in the self-introduction part, and then the interviewer will focus on your performance optimization ability, which is likely to involve very in-depth questions. Even if you are good at this aspect of the technology, but if you are not prepared, you may be confused on the spot.
Multiple questions
Self-multiple questioning means that when a technical question is asked, you may face further questioning
Using front-end performance optimization as an example, interviewers might ask:
-
You’ve reduced the white screen time on this phone by over 150%. Where did you optimize it? This is a question that you can answer even if you haven’t done front-end performance tuning. Component segmentation, caching, tree shaking, etc. This is the first shallow question.
-
I see you use SplitChunksPlugin in webpack to divide chunk. What is your choice for dividing chunk? Which libraries should be in the same chunk and which should be separated? If you mention SplitChunksPlugin, you might ask a similar question. If you don’t have a candidate who has actually run the splugin plugin, you’re going to have a lot of trial and error.
-
Did you encounter any potholes in the process of dividing chunks? How did it work out? The SplitChunksPlugin plugin has a dark hole, which is that the increment of the chunk id causes the id to be not fixed and unique. It is possible that a new dependency will cause the ID to be scrambled, making the HTTP cache invalid.
This is just a question about optimizations for SplitChunksPlugin plugins. Of course, it’s possible to look at your performance testing, code level, but the idea is similar.
Therefore, we can not stay in a very superficial level of the answer to the question prepared by ourselves. On the one hand, we can not show our technical depth, and on the other hand, it is easy to lose points in the case of the depth of the interviewer. Therefore, we can conduct more self-questioning behind our answers to see if we can do more in-depth questions.
The answer law
Many interviews related problems of the bible are recommended STAR principles of reply, we don’t want to introduce the concept of the extra, part of the basic technical interview honestly answer the interviewer’s question, usually need to question to this rule is project of surface, such as allowing you to introduce you the most proud of the project, to answer the question of law have these a few key points:
- Background: Give a brief background about the project and let the interviewer know what the project does
- Personal Role: Let the interviewer know your role in the project
- Difficulties: Let the interviewer know what difficulties you encountered during the development of the project
- Solutions: What solutions do you have for the above difficulties, and how do you choose according to the business
- Summary and precipitation: have you settled a set of general solutions after overcoming the above difficulties, and have you promoted your own solutions in large departments, etc
The key point lies in the last three, which is also a part of your personal comprehensive quality. If I am an interviewer, I will appreciate those who can find problems, find a variety of solutions, compare and choose a variety of solutions, and summarize and settle general solutions to the team.
The above points can reflect a person’s technical enthusiasm, the ability to solve problems and the ability to summarize and improve.
Deliberately guide
Yes, you can also be deliberately guided when answering the interviewer’s questions.
Let’s take a few simple examples:
-
Have you used Angular besides Vue? We can do a better job of saying what you know. It’s important to say something like, “I haven’t used it yet, but I learned about Angular dirty checking while learning about bidirectional binding. You learned about dependency injection while studying Nestjs, which is similar to Angular. “The interviewer will definitely ask you about dirty checking and dependency injection. You have never used Angular, but you know the basics of Angular, which is a plus. Demonstrate a willingness to understand principles in depth and the ability to draw parallels
-
How does Vue implement bidirectional binding? A lot of candidates honestly answer how object.defineProperty works and then go away, but you can always add “Vue 3.0 chose a better Proxy instead of Object.defineProperty “or” Besides object.defineProperty, observer mode and dirty check can be bidirectional binding “. The interviewer will most likely ask “What’s good about Proxy?” Or “talk about the dirty check,” etc., so that the next problem is still under your control
In the first example, we turned the questions that could not be answered into a bonus for successfully demonstrating our ability. In the second example, we showed our ability more and kept the interviewer’s questions under our control.
Ask questions of the interviewer
This part basically came to the end of the interview, belongs to do a good job does not affect the overall situation, but may add points, if not done well is easy to step on thunder area.
First we declare a few minefields:
- Don’t ask for results: It’s useless to ask. Most company policies don’t disclose results, and you’re embarrassing everyone
- Never ask about salary: Never talk to a technical interviewer about salary unless the HR person is talking to you about it
- Don’t ask technical questions: Don’t ask the interviewer technical questions that you don’t know. It’s pointless
Here are some good questions to consider:
- What would you like me to accomplish in the first three months if I were to enter this position?
- Why did my predecessor leave this position and what can I do better?
- What are you looking for in an ideal candidate for this position?
Around your post questions as far as possible, this can make you faster familiar with your work content, also lets the interviewer to see your interest and enthusiasm to this job, it’s important to note that these questions for the interviewer can be either a brief answer, can also be detailed to you, if he is very enthusiastic about this position related with you, that you may do well, otherwise, You may not be on his waiting list, and that’s when you need to plan ahead.
conclusion
We cover a lot of technical interview techniques, but it comes down to the candidate’s basic skills and extensive project experience.
If you read the entire article with careful preparation, it’s a practical tip that will get you from 75 to 85, not a secret that will get you from 55 to 85.