In March and April, spring returns to the earth, everything recovers (please bring Mr. Zhao Zhongxiang's BGM), and it is time for many students to change jobs.
Recently, the team has also been recruiting people. During this period, many resumes have been screened and some candidates have been interviewed. Let me talk about my own understanding of " how to answer interview questions ".
All old drivers and new drivers are welcome to leave a message and exchange. Let's discuss together, whether as an "interviewer" or a "job seeker", how to answer the interview questions, so as to better answer the questions and achieve your job search goals. .
1. Listen to the question clearly, do not rush to answer
An interview is first and foremost a process of communicating with people. Sometimes, before the interviewer has finished the question, the interviewer will interrupt and say "I know this question...". Interrupting is not conducive to communication, and at the same time, it actually causes the interview questions to be unclear. For example, when the interview question is "How to understand Java's JMM,...", the interviewer interrupted and said, "I know what you said, including method area, heap, stack balabala" and answered all strayed.
Second, from the global to the specific
If the question is "what is Spring and how to understand it". Many people will directly answer "Ioc and Aop." It's not wrong to say this, but I personally think it's better to start with a more macro approach, and then introduce one or more aspects of Spring that you have an in-depth understanding of. Some.
Today, Spring is not just Ioc and Aop, but a XX that includes a series of functions, such as Spring Boot for rapid development, Spring Cloud for microservice support, Spring Security for authentication and authentication, support for various An abstract xxxTemplate provided by Spring data, Testing, and now using many Spring MVC. Of course Denpendency Injection and AOP are still the core.
Another example is to answer how to understand Java's garbage collection mechanism. Compared with a direct answer to the generalization of "clearing useless objects out of memory", if you describe garbage collection, when will garbage collection occur, the specific collection method, and what collection algorithms are known. How to adjust when OOM occurs, as well as JVM memory division, etc., I feel that the effect will be much better.
3. Don’t be arrogant and conceited, and don’t belittle yourself
After the interviewer asked the question, some candidates have not finished listening to the question, one is rushing to answer, and the other is disdain. I wondered why such a simple question was asked. In fact, everyone understands the interview as a " communication " that constantly communicates and discovers the strengths of the interviewer. For example, when some interviewers hear "Please write a singleton mode", they will be slightly unhappy, as if their talents are buried, but they carelessly miss the "double lock check", ignoring the impact of CPU instruction reordering.
There are also interviewers, when the interviewer just said "Next, let's write an algorithm question..." before finishing, they will throw options, "How about I write a quick sort, binary search? balabala", If you were the interviewer, what would you do?
There are also some interviewers who, when asked about the projects written in their resumes, have "gloomy eyes" and say, "We haven't done anything with technical content, and we can't compare with you", or when the interviewer mentions a certain project in the project. When one is realized, they will say "you have used it too", and then some dare not say it, as if the resume is overwrapped, while others feel that there are more common topics, and start to discuss realization, selection, etc. So boldly show yourself, at least one chance.
Fourth, the resume should not be too exaggerated, not to mention all product descriptions
I have read a lot of resumes, and some of the projects in the entire resume are all business and product introductions. The whole article does not mention a few technical points, does not talk about implementation, does not write what technology is used, and is full of text descriptions. As a technical interview, nothing technical.
There are also a lot of them. Their resumes say they are proficient in XX technology and YY framework, and they are ZZ experts. In fact, in actual communication, it is really only used and has not been configured.
A " familiar " level will most of the time be greater than a " proficient " level.
5. Breadth and depth
If you want to learn Java performance optimization, engineering, high performance and distributed, simple language. Friends of microservices, Spring, MyBatis, and Netty source code analysis can add 454377428 to the group. There are Ali Daniel's live broadcast technology and Java large-scale Internet technology videos to share with you for free.
The general interview will correspond to the breadth and depth according to the actual work experience of the interviewee. But between the broad and the deep, I think it is better to go deep into a field, a concept, and then expand it.
And in the interview process, if you ask a topic every time, it is normal, or you have simply understood it, it will give people a feeling of having just tasted it. If you are in-depth in a certain aspect, you can be handy when answering the corresponding questions, and you can even be more confident when answering "What are you best at?" For example, let's talk about concurrency in Java. In addition to being able to describe sync, first from the global to the specific, you can describe the "memory model", as well as the difference between Happens Before, Lock and sync. The corresponding implementations of Lock and sync, as well as the JVM's monitor instructions, AQS ...
Last year, I interviewed an intern by phone. I was still in the self-study stage about the development framework. When I asked about some unlearned parts, I would honestly say "I haven't learned it yet", and even said that XX technology "will be learned today." Plan, have the ability to learn. However, the learning methods, attitudes, and mastery and understanding of the parts that have been learned, as well as the level of performance, are impressive. Later, when I came to the company for an internship, I did not use the framework, but used new technologies according to the needs, and it did not disappoint.
6. Be proactive
My own understanding is that when answering questions, I can show what I am good at. For example, if it is written in the resume that "the project has used RPC", when answering how to use RPC in the project, you can describe the design and implementation ideas of some RPC frameworks, such as "I have a general understanding of how Dubbo is designed", and "Thrift There are these differences", of course, the interviewer may ask at this time, have you ever understood grpc? what would you do?
In addition, when talking about the technology used in the project, you can incidentally explain why you did this and why you chose to use this technology, so that the rich information outside the resume will allow the interviewer to have a more three-dimensional understanding, thus opening up the situation for " communication ".
7. It is better to have proof
If you can attach a long-term active open source project, continuous output of blogs, etc. to your resume, it is also a "platform" for people to have a more comprehensive understanding of your code style, show the way of design, thinking, and learning.
Not much to say, the foreman called me to move the bricks, ;)