After you receive the interview notice, the following preparation can greatly improve the interview success rate

As I have done a relatively long time technical interviewer, according to my interview experience, many students received after the interview, what preparation will not do, then will come.

The consequence of this is: do not know, no bosom friend, every war will be dangerous. Even if you get lucky, your salary will be very low.

In fact, the company willing to take the time to let you go to the interview, the prerequisite must be through your resume, must have found you and the company's matching point, that is, there must be a hiring intention.

In the technical interview time period (up to 1 hours), if you can show your advantage that is the best, but if you do not do this, simple, let the interviewer feel you have reached the minimum standard. This is like in the university exam, some students on a course of knowledge points completely do not understand, but also may pass the test before the assault and brush questions to pass the exam (do not cheat), but also may test high scores.

As for the technical interview, the project manager or personnel interview is generally poor filtering, such as the study of teamwork and communication skills, which should not be a problem for everyone. So in this article, we take the Java back-end advanced development as an example to tell the preparation point of the interview. The method is generic, and so can other students in other directions.

-----------------------------------------------------------------------------------------------------

1 set a minimum of 2 days of preparation time

The preparation time of the interview is usually less than 2 days, if you can, extend some, but not too long.

For example, to go on-site interview, you can find more excuses, such as project busy, will be more, time interval of more than 5 working days. For example, Tuesday received notice, as far as possible to Friday, if it is Wednesday Thursday, then do not exceed the next Tuesday.

Telephone interview, the excuse is not much, generally can be about two days later.

But it is not recommended to be notified today, tomorrow will be directly on the phone or on the spot, on the one hand, the company will think you are busy at present, on the other hand, you really do not have much preparation time.

2 Be sure to read the company's job requirements again

Is like the examination, first got examining, the general direction is wrong, ready to do the white.

For example, a job description like the next.

We can dig out the following skills requirements from these points:

1 3 years experience, familiar with common class Library 2 familiar with spring and MyBatis Framework 3 familiar with the distributed middleware (such as message, cache middleware) 4 familiar with the database, preferably NoSQL 5 preferably have big data experience

The requirements for non-technical skills are as follows:

1 have a sense of responsibility, initiative 2 need to have the ability to team work 3 need to have good coding habits, learning ability to be strong.

In fact, before the resume, you can adjust to the above requirements to fine-tune the resume, so that the job interview opportunities can be greater. However, in this article, we will take the above requirements as an example, to tell the preparation before the interview.

3 Before you brush the title, prepare the description of the project

I see a lot of candidates, before the interview, will focus on brush questions, such as reading algorithm problems, basic problems, this is necessary.

However, in the interview, the first link is generally a project introduction, that is, if the interviewer through the project, see your skills and position mismatch, you do not even have the opportunity to be asked other questions.

Here are some highlights of the project description:

1 Business requirements can be a stroke, with a few words to introduce the background of the project, roughly do what, the duration and number of people can, don't talk too much, because the interviewer does not care. Here's a case for a story.

My last project is to do telecommunications system billing software, the customer is XXX, the duration is xxx months, there are 5 people to do together, what I do is to develop.

2 according to the actual needs of the project, introduce the technology used in the project, for example, in the above job description, the requirements of spring MVC, message Middleware, database and other requirements, the following also give the case of each story.

In this project, we used the spring MVC(or Spring boot or Spring Cloud) framework, the database is used with the Oracle,orm component is Mytabis, in the project, We are sending a successful message through message queue, message middleware we use Kafka, in order to reduce the number of database accesses, we will put the customer information in the Redis cache. In addition, we have access to nginx load balancer at the gateway layer.

We can see, in the above-mentioned rhetoric, we combine the case, say the recruitment needs of the technical points, but please note, here is only the introduction of the project, combined with the function point to say the technology can, do not too much , because once the excessive expansion, will let the interviewer feel your thinking is unclear, or by virtue of preparing emboldened.

3 Re-integration project, said the recruiter needs non-technical requirements.

In this project, we used the XX design model, and we will regularly review code, in order to ensure the quality of the code, and, when the project duration is tight, I will also guest configuration management role. In this project, I have a problem and will immediately communicate with the manager or the person in the test or other group.

4 If there is, say the highlights of your project, such as the use of some better technology.

This project has high database performance and memory performance requirements, so I used Oracle tuning technology and JVM Memory optimization technology, in addition, we also use the Big data analysis tools to optimize the billing model.

As you can see, the above-mentioned rhetoric is not complex, ready to say, it is estimated to be 2, 3 minutes but through the above rhetoric, light up your basic information, but also to leave the interviewer clear thinking, technology matching impression.

Please note that if you do not match the technology and requirements in the project, it is not recommended to fake it, but you can do it in the following way.

1 If your ORM is not using Mytabis, but itabis or simply hibernate, say so, because ORM is interlinked.

2 If this technology, such as Redis, is used in the project, but you did not do, you can understand the basis of the said, such as: " This project also used Reids...,redis is used in the XX module, the function is xxx", please note, here you said the project was used, Instead of you, here, if you can answer the question of redis usage and skills in a subsequent answer, the interviewer won't mind.

3 Some technology you are not used in this project, but you are more familiar with, you can also through the following remarks.

In other projects I also used the nginx (vague answer, did not deliberately say this project), the specific application is XXX (combined with the function point), the use of the XX configuration items (through some joints to verify that you have used)

It is important to note that when preparing a project, you can try to rely on the position as much as possible, but not too outrageous. Because every technical point you say, in the back, the interviewer may ask questions. If you do not have a technical point, in fact, the interviewer did not ask you to be perfect, but if you say you have used a technology, but through the following questions, the interviewer found that you actually did not use, or master degree not as you say so good, then this nature is not the same.

4 must be prepared. The technology mentioned in the project description

When you introduce a project, it's like fishing, attracting interviewers to focus on the technical points you're talking about.

So when preparing for an interview, be sure to prepare the technology that you mentioned in the project (most of the skills required for recruiting). You can follow the following ideas when preparing.

First, it must be combined with the project background, such as the need to prepare a distributed cache Redis, first say in which project in which scenario, such as in the telecommunications system just mentioned. This will make the interviewer feel the technology you have actually used, rather than simply learning experience.

Second, there are a lot of key points, you must be aware of the future, such as the basic data structure of redis, how to read and write, cache if the breakdown of what to do? These problems must be prepared, so-called bragging to make a draft. For example, you can say that, in the configuration of Redis, the XX configuration file with the XX attribute, it is what to do. It's not much, but when you say it, the interviewer will know you've really used it.

Third, you can prepare advanced questions about the technology, such as how a Redis cluster is built, and how a machine in a cluster fails to transfer heat. Again, you can talk about how to configure and how to use the key points. Alternatively, you can prepare the underlying implementation of the Redis distributed lock.

Keep in mind that any technology mentioned in your project needs to be prepared according to the above requirements, although some techniques may not be asked.

Here, if you are only using basic functions in the project, such as Redis using basic reading and writing, but you can properly see some high-level knowledge points and face test.

5 must prepare the highlight topic, and try to go around in this aspect, and the more bright topics

For Java advanced Development, you can prepare the following topics, you can also use this as a reference to prepare some other topics:

1 Virtual machine Memory Optimization 2 database Performance Tuning 3 distributed high concurrency Architecture 4 Some popular components, such as the usage of 5 big data directions such as Redis,nginx 6 the underlying implementation code for Java core (such as collections or multithreading) 7 spring Series (e.g. IOC, AOP, MV The underlying implementation code for c,spring Boot, Spring Cloud).

To be prepared to what extent:

1 It is best to combine projects to actually say that these techniques are actually used.

2 It is best to rely on performance tuning.

The following is a virtual machine, for example, how to elicit this topic in the interview, as well as what to say during the interview. Other highlight topics can also be prepared accordingly.

First, in the recent project introduction of the CV, add a similar description, "The project's memory requirements are relatively high, although the project allocated a lot of objects, but this project is allocated only 1G of memory, so in this project, I have to practice some troubleshooting memory problems in the skills, but also do some tuning work "So the interviewer will naturally ask questions when he sees the description of his resume."

Second, in the interview there will always be "project Introduction" This link, the interviewer would let the candidate introduce the latest (or most of the hand) of a project, so that we can take a homeopathic to say the description just given.

Third, we can answer the database or collection and other aspects of the topic, such as the answer to the JDBC problem, you can say, " with good connection object we will close in time, otherwise it is occupied by the memory objects can not be collected by GC", Or, when talking about a collection type such as list, say more, "we will clear out the good set object in time, otherwise the collection will also have a strong reference to some objects, which will delay the object recycling time ."

Four, in the self-summary, can be said that there is a virtual machine tuning experience.

So, what should I say during the interview?

1 We can start with the structure of the heap, and then explain the process of garbage collection in detail.

2 further explains how to write high-performance code.

For example, physical objects (such as connectio or IO) should be close immediately after being used well. Large objects should be set to NULL in time to revoke strong references. The collection object should be clear in time. Try not to use a string (or other immutable Class) object frequently, so that memory fragmentation is easily generated.

3 also displays comprehensive capabilities in monitoring, positioning and tuning. Here you can say, for example, how to tune the JVM performance through Jprofiler+jmeter.

4 You can even see some of the underlying implementation details of the virtual machine, in the interview, this can greatly improve their professional quality.

6 more time, then go to brush the question

When everyone in the preparation of the project description, and when the project technology are prepared to say the words, but also according to the above requirements to prepare the bright spot, at this time to brush the question.

Please remember, brush the problem, the technical priority, the algorithm to see some basic, such as sorting, etc., and intellectual problems, unless it is a school recruit, otherwise generally not how to ask.

in the interview, you can use the method given above, through the multi-throw technology points, the interview into a ready range. In other words, if the interviewer finds the candidate's skills, other technical questions will not be asked.         

In the interview, you must be prepared to lead the interviewer to ask questions, otherwise, once the interviewer began to freely ask questions, everyone weak point exposure to the opportunity may be greatly increased.

7-side questions, ready to let the interviewer feel your soft power.

The interviewer can only take him into the company if he is sure that the candidate has no problem with the responsibility and teamwork ability. Some interviewers will confirm these two points by asking questions, but some experienced interviewers can even confirm them by the way the candidate answers the questions and the tone of the speech.

So everyone before the interview, the first can according to the following points, in peacetime life and work to practice good communication methods.

First, the speech is clear, the speed is not urgent, at least let the interview faculties understand what you say. And try to speak decisively, don't hesitate, this will show you have enough to play.

Second, communicate as far as possible visual interviewer, tone Bushin, don't too stiff, speak not too strong. The face can be properly smiled, the interviewer can properly nod the interaction when speaking, in short, let the interviewer feel and you do not struggle to communicate, the best also let the interviewer feel willing to communicate with you.

Third, should actively answer the interviewer's questions, if you do not understand the problem, do not stand up and wait for the interviewer to further explain, should be actively asked. If you feel that the interviewer does not fully understand his or her answer, or if he understands it correctly, he should take the initiative to explain the positive communication posture.

Finally, even if you do not agree with the interviewer's point of view, you should also communicate calmly, not impatient, do not easily interrupt the interviewer, you can listen to the interviewer after the words of patience with the exchange. Some interviewers may deliberately make a difficult candidate, in the name of the "stress test", in which case the candidate should be more calm and unable to argue.

During the interview process, an experienced interviewer may not be able to validate the candidate's "teamwork ability" (because it cannot be collaborated in a short time), but if you can leave the interviewer with a good impression of "no problem communicating", "being kind" and "being able to actively coordinate communication with difficulties", The interviewer is also generally able to recognize the candidate's team collaboration skills.

In addition, we can prepare the following rhetoric, once you can find the right opportunity to say, the interviewer will also recognize the responsibility of everyone and teamwork ability.

1: (At the time of the project) when the project was half done, the client side changed some demand points, which put a lot of pressure on our project team. Under the leadership of the project manager, we are assigned more tasks, in this case, I completed the task by the quality of overtime on time, and in the process, in the event of demand or technical problems, I will also take the initiative to find colleagues or project manager to confirm.

In short, in the event of a problem, you are not back, and can work overtime and other ways to actively face and solve problems, and once there is a problem, you do not muddle through, and will proactively confirm.

Story 2: (Introduction of their role in the project) in this project team, in addition to their own development work, I will actively communicate with the testers, on the one hand to tell them how to measure, on the other hand, once the problem is found, I will work with them to reproduce the problem, after the modification I will also take the initiative to tell the testers, Let them confirm as soon as possible.

In short, in the project, you can not only complete the job, but also with other team members to work together.

Rhetoric 3: (Introduction to the project's highlights) in the project, I met a demand point, which requires a number of teams to develop together, then I will meet with the relevant personnel to determine the respective task points and durations, after the completion of the function point we will be together.

4: (What if the interviewer asks you if you have problems that you can't solve?) I will not push off the task, I'll check the information first, if not, I will ask the project manager, on the basis of their solutions, I will refine into specific implementation code, and finally I will implement a good function point and project Manager to confirm, in order to not understand the deviation.

In the sense of responsibility and teamwork, it is not recommended to say "I have" directly, because this is equivalent to self-praise, the credibility is not high, we can use the above "with specific facts to prove" way, so that the interviewer after listening to the natural can recognize the relevant ability of everyone.

8 This article summarizes and asks the recommendation

This article is based on the relevant content in the Java Web Lightweight Development Interview tutorial.

This article is not short, and are based on my technical interviewer experience summed up, so to everyone a little help. If you see a slight merit, please also kindly click on the "Recommended button" below, everyone's recommendation, is the greatest help to me.

Finally, thank you again for reading this article. When you are welcome, please specify the source and author of the original text.