This article is mainly from the project, so it will start from the following aspects.
- How to introduce the project?
- How to introduce the difficulties and highlights of the project?
- Which module are you responsible for?
- How to satisfy the interviewer?
How to introduce the project?
When I just started the interview, I also encountered this problem, and it was also the first question I thought about. How to introduce my project can let the interviewer understand the project more comprehensively, and at the same time, it will not make the interviewer feel it. Too much nonsense. After so many interviews, I found that generally this kind of routine is more appropriate to introduce the project. Of course, this is just my feeling, there is no best way, only the most suitable method.
Introduce the background of the project -> Introduce the technology stack of the project -> Introduce the modules and functions that the project is responsible for
Follow this line of thinking to introduce the project.
First introduce the background of the project , so that the interviewer can understand the background of the project in a simple way. Of course, we must remember not to put the cart before the horse. The background only needs a brief introduction, and the latter is the focus.
Secondly, introduce the technology stack in the project , such as what framework you are using, ssm, springboot, etc., whether you use the caching framework redis, and whether distributed is involved. These all need to be introduced. It is best to briefly introduce The reason for using these techniques will make the interviewer feel that you are familiar with the project, for example, you can introduce it like this.
The framework used by my project is ssm, which uses the activiti workflow framework. This is because there are a lot of work approval services in the project, and the shiro framework is used at the same time. In addition, in order to realize the single sign-on function, the redis framework is added.
The above is just an example, as long as it is to introduce why this technology is used, it will not be very rigid.
Finally, introduce the modules you are responsible for in this project . This point should be paid special attention. When introducing this, you can see the difficulty of the modules you are responsible for, that is, the difficulty of the work you are doing.
If you introduce it like this: I am responsible for a user module, including the addition, deletion, modification, and checking of users, as well as the user's login function .
When the interviewer heard that the job you are doing is not difficult, it does not reflect your ability, and your role in this project and your own value. The interviewer definitely doesn't want to hear such an answer.
Therefore, when introducing the modules that you are responsible for, try to use some modules with more complicated business and heavy workload. The difficulty of the entire module is relatively large. In this case, the interviewer will be interested in continuing after listening. Keep asking.
After accomplishing the above three points, the interviewer estimates that he already has a lot of recognition for your project, at least he will not think that he is fooling him, haha.
We are all very honest, there is no fooling around. . .
How to introduce the difficulties and highlights of the project?
It was originally divided into two aspects: difficulty and highlight, but after thinking about it, I found that there are still great commonalities, so I put it together.
I have been interviewing for such a long time, no, it should be said that I have been stunned for such a long time. I am so miserable. Whenever I ask about the project, when I have introduced the project, then there is a classic memorable quote from the interviewer: " Can you introduce the difficulties of your project "?
I. . . After hesitating, why is this problem again? It's too difficult for me!
However, after so many interview experiences, I finally solved this problem. When the interviewer asked me, he arranged it to obey and post. Haha, it’s fun, it’s noisy. Don't joke about the interview! ! !
Let me talk about an idea here: In fact, when the interviewer asks about the difficulty of your project, it is nothing more than to see how well you understand the project. So, in fact, in many cases, we only need to take the knowledge we have learned and then compare it to the actual project. It is very simple to solve this problem by conducting a thorough understanding.
Here is an example:
For example, you said, I optimized the database in the project, and then you talk about the entire optimization process, and you have not been exposed to this aspect of work before, there are certain challenges, and the amount of data is particularly large, but through Through my own exploration, I finally solved the problem and achieved good results. Of course, the most important thing is that you describe your optimization process, so that the interviewer can feel that you really do the job; it is best to learn from you during the presentation. The past knowledge is used, for example, indexing, database design and so on.
In this way, the difficulty is solved for you.
Which module are you responsible for?
For this, it’s actually quite easy to say, just be careful not to tell the interviewer about the very simple modules that you have made, and then give the interviewer the feeling that there is no technical content, so you should introduce you in this project. Module.
1. The module you are responsible for should be the core module in this project . Remember, don't be a user module, simply add, delete, modify, and check. 2. The module you are responsible for should have a certain degree of difficulty , or a certain degree of difficulty for you, and finally you have overcome the difficulty and realized the function. 3. The module you are responsible for should have some difficulties , so that the interviewer can ask you questions, and then you can continue to brag.
Of course, there is one thing that the interviewer must do before, and that is to be familiar with the entire project. At the same time, he must be very familiar with the technology used in the project. When the interviewer asks about the project, he may ask about a technology randomly. Questions, if you are not prepared, you will definitely not be able to answer them. This result will cause the interviewer to feel that you are not familiar with the project.
Experience it by yourself haha
How to satisfy the interviewer?
This problem has actually been solved when you see it here. In addition to the above aspects, as long as you pay attention to the communication and communication, then the interviewer should be satisfied with the interview, so you should have good news. Congratulations on your offer !
If there are any deficiencies, please advise, if there is a little effect, please give me a thumbs up~
I am here to organize interview questions related to Android intermediate and high-level to share with you Android learning PDF + architecture video + interview document + source code notes, advanced architecture technology advanced brain map, Android development interview topic materials, advanced advanced architecture materials, if If you need it, you can also privately message me [Advanced] to get it for free
