Some questions found in recent interviews:
- The attitude is not serious enough. If you ask a question on the one hand and still can’t answer it on the second, you may not value the opportunity so much.
- The foundation is not solid enough. The problem description is not clear and can only be vague. I have this problem myself, and I have to work harder
Ali's interview article summary:
Things not to do in an interview:
- Ask some knowledgeable questions, such as do you know what a command does and how the API is called. Know the knowledge, google or carefully read the document to know
- Ask some very complex questions, such as a very complex algorithm, ask a very abstract big question, but it is difficult to give an answer in time
- Ask some hypothetical questions, assuming you are involved in the project, where do you think you need to optimize
These questions are difficult to measure the ability of the interviewer. Don't try to prove that others are not as good as you in the interview , it is meaningless, no one is perfect, and there is always something that cannot be covered. If you recruit according to this rule, you will miss many excellent talents.
What to do in an interview:
- ask what has happened
For example, when interviewing a mobile developer, carefully look at the APPs he has made, what the specific work is, and prepare some related questions. Here you can see what the accumulation of work is and how deep it is .
- problem solving ideas
For project experience and some learning experience, you should ask what is the solution to the problem after you get it, and why do you do it in what scenario. According to the interviewer's plan, the analysis methodology can roughly understand whether the interviewer is smart and knowledgeable. It is broad enough, and will it be inferred when encountering problems.
A simple example can be given. Many students say that they have done architecture, and then they will say that they have built a decoupling and layered framework. In fact, there are many such frameworks in iOS, and there are various solutions on the external github. The container rules that were precipitated when the bundle was split in Alibaba’s internal Taobao earlier, beeHive which was open sourced by Tmall, Xframework in Xianyu, or spring mvc on the server side, all of them actually implement IoC, but there are both implementations and ideas. Some differences, and why they are done, are actually different. Here, you can see the breadth of knowledge, the ability to summarize and reason, and the technical judgment on the key path.
- Ask less and listen more
Generally, students who are just starting to be interviewers like to ask questions. However, because everyone has different knowledge systems and different growth environments, it is difficult to find the advantages of the interviewer by asking directly, so try to let the candidates make their own statements. , and then ask questions about the doubtful places in the statement with the mentality of learning and communication, which will make it easier for the examinee to relax, and it is easier for the examinee to express himself more comprehensively. In addition, when the question is about the same, you can add a sentence at the end: What do you think I did not ask in the interview just now, and what do you want to add? At the end, let me ask again: I have finished asking my question, do you have anything to ask me?
STAR Principle
situation,task,action,result
Identify true and false STAR:
- The description is vague
- only express opinion
- hypothetical description
Original address: https://mp.weixin.qq.com/s/LAUKwTo4c0pvzSarKFM-rg