I have learned to play chess before, and now I have also upgraded to 8-1 in Tiantian Chess. If I take appropriate training seriously, my bottleneck is estimated to be weak at 8-3, which is said to be weak at Shanghai level. I plan to participate in some games recently. Earn some extra money in district-level city-level competitions.
When I was self-training to improve the level of chess, I accidentally discovered that the doorway and the method of interview improvement are similar. When I used this method to prepare for interviews for my part-time training students, I discovered that the efficiency and success rate of interview preparation have improved to a certain extent. So in this article, from the perspective of improving chess, I will talk about the way to improve the interview. I hope everyone will have some enlightenment after laughing. In addition, if you also want to improve the level of chess, this article can at least help you beat Master Park.
1 For zero-based noobs, first ask them to recite the basic jose
In my training class, through 4 or 5 lessons, some Java-based beginners can at least run through a Spring Boot + front-end + database project, and they can also use basic Java, database and framework syntax.
At this stage, if you want to play chess just now, you know the interview process, and you can also talk about the project, but once you encounter the interviewer’s questions, it is estimated that you will not be able to survive 3 questions. At this time, I let them recite the formula.
In chess, you can familiarize yourself with the basic ultimate moves through ancient scores such as Plum Blossom Tree, Plum Blossom Spring and Invincible Hand from the Hole. You can familiarize yourself with the basic moves such as eight moves by reading the endgame book. You can also learn about the initial moves by recitation of the opening formula. Way of walking. As for these novices, I will let them recite the following formulae from the shallower to the deeper.
1 Basic interview questions about Java and database, such as why HashCode needs to be rewritten, etc. There are too many materials on the Internet, of course I have them too, so I won't mention them in order to avoid advertising.
2 "Introduce your own project?" In response to this question, ask them to memorize familiar words based on their own project practice.
3 Recite some remarks on self-introduction, introduction in English, and remarks on common interview questions such as "what are your strengths and weaknesses".
4 Memorize some basic algorithms and written test questions.
If you can be familiar with the basic opening endgames and ultimate moves in chess, you can get rid of the chaotic stage. For interview Xiaobai, at this level, at least he can talk to the interviewer. Although it may still be more defeated than wins, but At least it can last a quarter of an hour, or it can avoid the embarrassment that most of the questions cannot be answered.
2 Through more practice, try to avoid mistakes
Then I asked them to ask each other questions, such as Xiao Zhang introducing the project to Xiao Li, asking Xiao Li to hear if there were obvious problems such as "project time is wrong" or "technical introduction", or asking them to ask each other about the Java database or Interview questions about the framework.
This is equivalent to memorizing questions before the previous exams and making fewer low-level calculation errors when answering questions. What questions should I recite in the Java interview? Java core, database, Java Web, Spring Boot and middleware components, where are the problems? Search on the Internet and search a few more sets, and you will find that it is basically the same.
The purpose of this is to first allow them to further accumulate interview questions and answers, and second to allow them to say a few more times to avoid low-level errors. For example, at this stage, there are really people who make "Dubbo is a message middleware" error. At this stage, if you encounter unfamiliar skills, you must not go back to the theoretical answer, you must practice it. For example, if you encounter hashcode and equals problems, you must write Java code to debug it. If you encounter Dubbo problems, you must configure a basic program to understand usage and allocation methods.
In chess, you can move + give fewer pieces, and then wait for the opponent to make a mistake, so that you are qualified to play chess with the street master. In the interview scene, you can talk about basic questions, plus you can introduce the project, and don’t make it obvious. I’m going to interview a small company at this time. I guess I can really try my luck.
3 Tell them the skills to show the highlights for a specific scene
But the interview must not rely on luck, and a small company is definitely not our goal, so I will teach my students some highlights. Of course, this has to be practiced repeatedly before we can say it well. Here are some of the highlights of the rhetoric.
The core aspect of Java.
1 Combine the underlying source code such as ArrayList and iterator or HashMap to talk about the running process of these collections.
2 Combine the actual design patterns used in the project.
3 Combine CorrentHashMap to comprehensively display thread concurrency and data structure.
4 Talk about how to solve the OOM problem and so on based on the case.
The database aspect.
1 Through the index and the data structure of the index, talk about the techniques of data tuning.
2 Look at the log and talk about troubleshooting to solve the problem of slow SQL.
3 Through Redis + MySQL cluster + MyCAT, let's talk about the techniques of distributed tuning. Of course, specific cases will be given here.
and so on
Framework and distributed components.
1 Combined with the case, let's talk about the full stack process of Spring Boot and the meaning of key annotations.
2 Through the log and other cases, talk about the usage of AOP, IOC, etc.
3 Then, we will talk about the usage of Redis, Dubbo, Kakfa and other components in combination with the spike and other cases.
and so on
With these technologies, after being honed in a learning project, Java Xiaobai is not difficult to get started. On the basis of getting started and seeing the effect, it is possible to explain these highlights while drawing. After a short training, it is also possible.
This is like getting some people who can play chess to memorize basic ancient scores and some basic opening and basic endgame moves. If you play chess to this level, you will not only rely on the opponent's mistakes to win the game, but you can also rely on your own initiative to attack to win chess. For some candidates who want to find a job, after achieving this level, the interviewer will not feel that they can only do basic tasks, such as adding, deleting, modifying, and checking, and they can also leave the interviewer with "familiar with the bottom layer and understanding the framework." You must have a basic understanding of tuning and tuning, so that you can at least compete with the interviewers of the big factory, and even if you fail, it won’t make people feel “too bad”.
4 Good fighters have no traces, and they should be described naturally in conjunction with the project
Learning chess to this level, because I have read a lot of masters and ancient scores, I can't wait for every move to be earth-shaking. Once my students have memorized some highlights, most of them will be eager to try them, and they can't wait to include words such as "distributed components", "low-level source code" and "design patterns" in each question.
When playing chess, if every move looks gorgeous, for example, it’s obvious to take a piece to kill a target, so that once you encounter a master, you can firstly block the three axe, and secondly look for it from the opponent's big opening and closing. When a flaw occurs, it is generally estimated to be defeated. And if you continue to show off valuable technical points in the interview without the support of project background or basic knowledge, you can at most get a "familiar theory" evaluation. In this way, interviews with small outsourcing companies will probably not have big problems, but the interview has a certain scale. Software companies are more susceptible.
At this time, I will give the following suggestions accordingly.
1 Peace of mind, the rhetoric that you learn valuable skills can not be used to show off.
2 Find a pavement for each valuable point, such as talking about the factory model through the full stack requirements in the project, talking about distributed components with the order concurrency requirements as the paving, to troubleshoot iterative problems, and then talk about the underlying source code. This is also a kung fu job, and I will let my students practice it repeatedly as to how to lay the groundwork.
3 Put an end to mediocrity. When answering a question, don't stop at the usage and configuration methods, and try to figure out whether you can link to valuable skills.
4 At the same time, we need to do more technical accumulation, such as accumulating Spring Boot, so that we can explore more valuable technical rhetoric.
When I look at some large coaching games, I look at every move and it is almost plain. However, due to the proper coordination of a few moves, you can immediately accumulate an advantage by taking 3 to 5 moves, and then taking another 7 or 8 moves. This advantage can grow bigger and bigger. Since some masters can integrate one goal into several tactical combinations, the opponent will unknowingly fall into a disadvantage. In fact, the interview is similar. You can pave the project background and basic knowledge through an answer, and then show the configuration and basic method parameters of valuable skills through an answer, and then talk about valuable skills through the underlying source code through several questions, so that the interviewer may be If you are recruited before you know it, you can feel that you are really good, and you can also think that your valuable skills have a project background.
In fact, I let my students talk about the technical points, just like flying elephants in chess. Anyone knows what to say, such as OOM rhetoric and multi-threaded rhetoric. I found a lot of them on the Internet, but I let them Incorporate into the project, through 3 to 5 answers, let the interviewer discover a technical highlight, so that by the end of the interview, they can accumulate small wins into big wins, and can comprehensively demonstrate the Java core, data and framework, and even distributed components and tuning. skill. Compared with candidates who only passively demonstrate mediocre skills of "addition, deletion, modification and investigation", to be honest, my students are really better when doing projects, which is not necessarily, but the interviewer compares each other. There is a high probability that I will want my students.
5 Know yourself and your opponent, understand the interviewer’s motivation for asking questions
When playing chess, it is best to know the purpose of the opponent's chess. Of course, if the opponent moves without purpose, it is better to win. During the interview, when the interviewer asks questions, he will definitely have a purpose. I will make a targeted analysis and give the corresponding response.
For example, when the interviewer asks the number of people and the development model of the project, they are confirming the authenticity of the project. Then, in the corresponding rhetoric, my students will comprehensively demonstrate the practical points of agile development, and the specific return in the project. After doing testing, deployment, release, etc., you can use project rhetoric to prove your ability to the greatest extent.
For example, when interviewers ask if they can work overtime and what to do if they encounter problems, they are mostly confirming the candidate’s pressure-bearing ability and work attitude. There are too many standard answers on this type of teamwork and work attitude on the Internet. Let my students give examples to illustrate that they are very dedicated.
Another example is when the interviewer asks for details of a certain technical point (such as Redis cache), it is estimated that he is investigating the usage of related technologies in the project. At this time, I will ask my students to answer the relevant questions more Let me just say a word, combining the project problems that have been solved, and actually talk about the usage, details and even the underlying source code of the relevant skills.
Even if the interviewer seems to be chatting with you, such as asking what hobbies do you have, what do you usually do? This is by no means a mess with you, but to judge your stress-bearing ability, learning ability and self-motivatedness based on your usual things. After you understand this, it is not difficult to prepare an excuse accordingly.
Of course, after understanding the interviewer’s motives for asking questions, he should be more aware of the pretense of being confused. At this time, after dealing with the current question, he should say something that the interviewer loves to listen to, and must not be clever to show through the interviewer. The intention of the question is, otherwise, it may really be self-defeating.
6 Not only must tactics be appropriate, but also be able to control the situation
When learning to play chess, not only must learn how to deal with static situations, but also the means of comprehensive control of the situation. For example, in some seemingly unremarkable situations, you need to use active tactics or tactics to let your situation take the initiative. In particular, it is necessary to further determine the position advantage through active offensive moves in some key nodes.
In the process of learning chess, if you can really achieve this level, it is estimated that you will at least be eligible to participate in district-level competitions. In order to achieve this level, one must try to figure out the motivation of Wang Tianyi and other super masters when playing chess, and try to simulate and use the ideas of super masters to analyze, judge and deal with the situation. This does not sound easy. However, when I coach my students during the interview, I will pass a case to tell them what kind of display method should be used at the key points of the interview, so as to achieve the effect of controlling the interview situation. Of course, the premise is that my students have to memorize various static rhetoric about "self-introduction", "introduction projects", "answering technical questions" and "introducing solved problems" in advance (this is physical work).
Someone might say that the interviewer is dominant in the interview, so the candidate can only answer passively and cannot control the interview. In fact, it may not be necessary. The interviewer is also a human being. It may take two or three minutes to scan the candidate's resume in advance, so as long as the candidate has the right skills, he can definitely control it. Generally speaking, the interview skills I give will involve the following key nodes in the interview. Some examples are given below.
In the self-introduction stage, the average candidate will introduce age schools, etc., and then talk about the previous company, and then roughly talk about the technology used. It may not necessarily be exhaustive. But I will let my students first explain all the technologies they are familiar with, and immediately tell about the experience of using these technologies in the project, and solve practical problems, so that I can lay a good job for showing valuable skills with project experience in the future. At the same time, the interview can enter the project introduction stage immediately, so that some interviewers will not ask random questions.
In the project stage, the average candidate may focus on business needs, even if it involves technology, due to lack of preparation, they may not be able to show all the valuable technical points they have mastered, and I will let my students talk about business and focus on Combining the application background of relevant technology with demand points (distributed components, etc.), and strive to explain the highlights of the preparation before the interview. At the same time, it must be mentioned (in terms of valuable technology) that you have experience in solving actual online problems. After this, the first few questions will most likely be controlled at the points mentioned before. And because my students have prepared before, so even if the project experience is insufficient, they can say it well.
Nowadays, distributed components are a must-question point in interviews. My advice to my students is, either. If the interviewer asks, for example, how to use caching in the project, then first talk about usage scenarios and second talk about usage The important parameters and configuration of the, if you have memorized the underlying source code in advance, it will also be thrown out. The third is the actual problem that has been solved, and the last one is to say that other components have been used. In this way, compared with other unprepared candidates, my students can first ensure a good answer, and second, they can control the subsequent questions with a certain probability.
Moreover, even if the interviewer only asks basic questions, such as collections, I don’t let my students just answer the question. I just answer the question itself and wait for the interviewer to ask the next question. Instead, I use the “say one more sentence” method. Find the opportunity to draw and talk about the highlights of the "low-level source code".
In chess, it is a tactical problem to play a strong hand in a key position to gain an advantage. It is a strategic problem to find a way to get to this position. It also depends on the ability to control the position. If this can be done well, in the amateur It should be considered strong in the crowd. Corresponding to this, in the interview, you can answer the questions well when you are asked. This is also a tactical question. At the same time, I will teach my students how to ask the interviewer to ask the questions you have prepared. Through this technique of "controlling the interview situation", my candidate may not be much better than others in real-world projects, but he will definitely be able to demonstrate technology more comprehensively, especially valuable technology.
7 Through specific actual combat, understand the shortcomings and improvement points of each interview
Regarding interview skills, I will give my students intensive training for at most one week. They must be interviewed. If it is a face-to-face interview, they must remember the questions and answers as much as possible. If it is a telephone interview, it will let them even more. The whole process of recording is for the purpose of replay, and the specific things to do are as follows.
First, when you encounter unanswered questions, you have to draw inferences. For example, if the thread pool does not answer well in multi-threading, you must review the concurrency throughout the whole process. If you encounter Redis component deployment, you must practice it again. These things are normal. Let the students do it themselves.
Secondly, if you encounter "self-introduction" or "what are the advantages and disadvantages" and do not say well, I usually let them prepare by themselves.
Thirdly, if the technical details are not explained well, or the project requirements are not explained well, for example, the problem of Netty sticky package is not explained well in combination with practical applications. I will ask the students to organize it again and tell me about it.
Fourth, after the interview, you must compare the many highlights prepared in advance. For example, you are ready to talk about OOM based on actual problems, or talk about design patterns based on projects. If you find that you don’t say it, then you have to practice again. What methods should be used to guide the interview.
Fifth, I usually take some cases and analyze them. For example, a student did not lead to typical problems such as ConcurrentHashMap after he talked about HashMap. This needs to be explained in a unified way so that my students can further master the "maximum display of skills and highlights", etc. Interview skills.
If you play chess well and don’t analyze it, you may not be able to summarize the highlights first, and you will make the same mistakes after the second, so that there will be no improvement in the so-called 100 games, and the same is true for interviews. Generally, after my students go out for an interview with 3 companies, and then prepare well, at least they will look good when I do mock interviews for them, and there is a high probability that they will be successful when I go out to interview a small company. On this basis, in terms of technology, we will make up for what is lacking, take out and comprehensively improve the interview skills, and even if we go out to the big factory, the probability of success will generally not be too low.
8 Summary, in fact, the interviewer may not be better at playing games than you
In terms of the ability to do projects, most interviewers may be better than the candidates, and more than just a little better, but the so-called chances have no chance.
In many cases, the interviewer is still chatting with others in a meeting before the interview, or is still trying to fix bugs. In more cases, the interviewer is also temporarily selected by the leader to interview others, so most interviewers Just spend 1,2 minutes in advance, looking at the resume while walking, and during the interview, it is nothing more than looking for some questions from the Internet, and in the interview, it is more likely to continue to follow the words mentioned by the candidate. ask. On the contrary, as a candidate, you can recite the highlights before the interview, prepare fixed questions such as "self-introduction", and rehearse the "guided speech" of "speaking casually". For most questions, you can also Can find ready answers.
Moreover, your purpose in the interview is not to "prove better than the interviewer", but to "defense and avoid loopholes." It is difficult to win and easy to make peace. Take my students, for example, a class of 40 people, as long as they want to, most of them can successfully change jobs, and the final salary increase by 20% is considered to be few. And to improve interview skills, as long as the method is right, the time required will not be too long. Generally, one month is the best.
This article is the first one in my "Interview Review Series", and it can be considered as an attempt. If you feel good, please like me, or express your thoughts through comments. If everyone responds well, I will continue to write down in this series, such as giving me many finalized rhetoric for my students to recite, as well as highlight rhetoric that can be used in general for junior developers.
This article is written here. Finally, please pay attention to my official account: Make progress together and make money together. In this official account, there will be more wonderful articles.
