Give it a like and take a look. Good habit! In this paper, making github.com/OUYANGSIHAI… It has been included. This is the summary of Java interview for first-tier big factories that I spent 3 months summarizing. I have received offers from Tencent and other big factories.

The above article has been written after 0, there is no energy to write, in fact, energy or some, mainly pity their own life, keep hair matters, otherwise double 11 and get group purchase hair shampoo.

These two days after the release of the last article, a friend said that the most want to see the next article, this is not, I quickly put the second article to put out.

This article is mainly followed by the idea of the last article to write, so, from the following aspects.

  • How to introduce the project?
  • How to introduce the project difficulties and highlights?
  • Which module are you responsible for?
  • How to satisfy the interviewer?

How to introduce the project?

At the beginning of the interview, I also encountered this problem, which was also the first question I thought about. How to introduce my project can not only comprehensively let the interviewer know about this project, but also not let the interviewer feel that there is too much nonsense. After so many interviews, I found that such a routine to introduce the project is more appropriate, of course, this is just my feeling, there is no best way, only the most suitable way.

Introduce the project background -> Introduce the technical stack of the project -> introduce the modules and functions responsible for the project

Present the project along these lines.

First introduce the background of the project, so that the interviewer can simply understand the background of the project, of course, must remember that do not put the cart before the horse, the background only needs a simple introduction, the following is the key point.

Secondly, introduce the technology stack in the project, such as what framework you use, SSM, springboot, etc., whether there is no cache framework Redis, whether distributed is involved, all these need to be introduced, it is best to briefly introduce the reason for using these technologies, so that the interviewer will feel that you are familiar with the project. For example, it could be introduced like this.

The framework I use for this project is SSM, in which I use activiti workflow framework, because there are a lot of work approval business in the project, shiro framework is used, in addition, in order to realize the single sign-on function, I add Redis framework.

The above is just an example, as long as it is an introduction to why this technique is used, it won’t be too blunt.

Finally, introduce the modules that you are responsible for on the project. Again, this should be very important, so that you can see the difficulty of the modules that you are responsible for, that is, the difficulty of the work that you are doing.

If you introduce: I am responsible for a user module, including user add, delete, change and check, as well as user login function.

The interviewer will definitely not want to hear that the job is not difficult and does not reflect your ability and your role in the project and your value.

Therefore, in the introduction of the module in charge of their own, as far as possible some of the business is more complex, the workload of the module is relatively large, the difficulty of the whole module is relatively large, so that the interviewer will be interested in continuing to ask.

Do the above three points, the interviewer is estimated to have a great deal of recognition of your project, at least not think is to fool him, haha.

We are very honest, there is no fooling ha…

How to introduce the project difficulties and highlights?

It was originally divided into two difficulties and highlights, but after thinking about it, I found that there is a great commonality, so I put it together.

After such a long time of interview, I often hate for such a long time. When I ask about the project, after I introduce the project, the interviewer will say a classic and unforgettable sentence: “Can you introduce the difficulties of your project?”

I… After hesitation, how is this problem, I am too difficult!

However, after so many times of my interview experience, I finally put this problem to solve, and then the interviewer asked me, it is arranged obediently, ha ha, play to play, make to make, do not take the interview joke!!

Here’s an idea: In fact, the interviewer asks you about the difficulty of the project, just want to see how much you know about the project, so, in fact, most of the time as long as we have learned knowledge, and then with the actual project to integrate, it is very simple to solve the problem.

Here’s an example:

Like you said, I have to optimize the database in the project, and then you put the whole optimization process said again, you say no contact with this kind of work before, there are certain challenges, and particularly large amount of data, however, by their own error, finally solved the problem, achieved good effect, of course, the process of optimizing the main or tell you, Show the interviewer that you are really doing the work; You should be able to use the knowledge you have learned, such as index, database design, etc.

In this way, the difficulty is solved for you.

Which module are you responsible for?

For this point, in fact, it is easier to say, as long as you do not say their very simple module, and then give the impression of the interviewer is not any technical content, so you should introduce you in this project in charge of the module.

1, the module you are responsible for should be the core module of the project, remember, not the user module, such a simple add, delete, change and check. 2. The module you are in charge of should be difficult, or it should be difficult for you. Finally, you overcome the difficulties and realize the function. 3. The modules you are responsible for should be difficult so that the interviewer can ask you about them, and then you can move on.

Before, of course, the interviewer must do one thing, that is to be familiar with the whole project, at the same time, also want to familiarize yourself with the technology used in the project, when the interviewer asked project may ask a technical question, if you are not ready, are you sure answer not to come out, the result will lead to the interviewer will think you for this project are familiar enough.

if(Familiar) Nextelse 
  out
Copy the code

Feel it for yourself haha,

How to satisfy the interviewer?

This problem has been solved by seeing here. In addition to the above aspects, as long as you pay attention to communication properly, then the interviewer should be satisfied with the interview, so you should have good news, congratulations on your proposal of offer!

In order to write this article without stopping, if there is insufficient place welcome advice, if there is a little bit of effect, trouble point a praise, the original is not easy!

Finally, I would like to share the Java interview + Java backend technology learning guide that I summarized for three months, which is my summary of these years and spring recruitment. I have received the offer from a big factory and organized it into an e-book. Please take it as follows:

Now free to share everyone, in my public number to learn Java reply Java interview can be obtained.

Have a harvest? Hope the old iron people come to a triple whammy, give more people to see this article

1, old friends, follow my original wechat public account “Learn Java well”, focusing on Java, data structure and algorithm, micro services, middleware and other technology sharing, to ensure that you will gain something after reading.

Give me a thumbs up, can let more people see this article, by the way inspire me to continue to write, hee hee.

“Like” is the biggest encouragement for me