How do you introduce your project experience during an interview?

"Second, once you are asked about the various details of the project preparation, it means you have never done it"

Generally speaking, before the interview, everyone should prepare a project description, be more confident, because you have the final say in this part, and be fluent, because you have been fully prepared Finally, you can know what you want to say. And these are your actual project experiences (not learning experience or training experience), so once the interviewer feels that you can't even speak, your credibility will be very low.

Many people are stuck on "what business was done in the project and the details of the code implementation", which is equivalent to directly handing over the right to ask subsequent questions to the interviewer. The table below lists some bad ways to answer.

While avoiding the above-mentioned bad answers, you can prepare a project introduction based on the elements given in the table. If possible, please also prepare a description in English. In fact, fresh graduates or people with less work experience have similar English proficiency, but as you said, this is a qualitative improvement.

Before the interview, you must be prepared and confident, but you must also avoid the following situations.

"Third, say what the interviewer likes to hear without revealing any trace"

During the project introduction (of course including subsequent interviews), the interviewer actually wants to hear some key points. As long as you speak out and answer relevant questions well, this is definitely a plus. When I interview others, once these key points are confirmed, I will definitely add a comment to the review.

The following are 5 key points and corresponding rhetoric that interviewers like to hear.

"Four. You must take the initiative. The interviewer is not obliged to dig out your highlights"

When I go to interview people, I often ask special questions: What are the highlights of your project? Or as a candidate, what other bonus points can help you successfully apply for this position? Even if you ask this, some people will directly say no.

I am already in a misplaced role when I ask this. As an interviewer, you should take the initiative to speak out instead of waiting to ask. But please note that you must be skillful when speaking and find opportunities to speak, usually by finding some Open question said.

For example: What technologies were used in this project? In addition to talking about some basic technologies, such as Spring MVC, MyBatis, and conventional database technologies, you also have to mention the use of Java memory management, which can reduce the pressure on the virtual machine memory, or the use of big data processing. Technology etc. In other words, you have to find every opportunity to talk about the technologies you have that are currently very popular.

Or find a related question for extended explanation, such as being asked: Have you ever used one-to-many and many-to-many? In addition to the basic knowledge points, you can also say that generally I will set the cascade and inverse keywords appropriately according to the needs, and then use a practical case to illustrate the help of reasonable design to your project, so that I can extend the explanation Your skills are up. On the contrary, if you don't say it, the interviewer will definitely think that you can only do simple one-to-one and one-to-many operations.

During the interview, if the candidate answers the question very simply, says one thing without expanding on it, or answers my question with very stingy sentences, then I usually give them the opportunity to talk in depth (but I can't guarantee that not every interviewer will ask in-depth questions). If the answer is concise, he will be stingy in giving good comments.

❝

Remember: the interviewer is not your relative, the interviewer is very busy, and there are very few interviewers who can dig out your highlights, and to tell you your highlights is Your obligation.

❞

When I interview others, I usually give the following comments based on different situations.

1. The answer is very short, but the answer can prove that he has indeed done something about frameworks and other technologies. I will write in the comments, "I have a general understanding of frameworks, but I don't know some deep-level knowledge." knowledge (I have asked many times and you have always given very short answers, so I’m sorry, I can only write like this. Maybe you are indeed very technical, but there is nothing you can do about it. Who told you not to say it?)”, At the same time, he will add the sentence "My expression skills are average and my communication skills are not strong." In this way, even if he passes the technical interview, he will have a hard time in the subsequent interviews.

2. #The answer is very simple. Through the answer, I cannot verify whether he has done this technology in the project or just learned this technology in his daily study. I would write "In the resume, it said that I have used XX technology, but I can't tell some details, and I can't see that this technology was used in the project." If this technology is necessary for the job, then there is a possibility that he will pass the interview. Just very small.

3. The answer is very simple, and I only use function words such as um and ah. After being reminded, I will end the interview with a few perfunctory words and directly write "technical" It’s so weak that I can’t pass the interview.”

4. Although he can demonstrate his skills well through his answers, but the logic is not clear, then I will let him pass the technical interview, but will write " Your skills are very good, but your expressive ability is average (or needs to be improved), please consider it with the subsequent interview manager." In this way, the chance of passing the subsequent comprehensive interview is average. After all, the comprehensive interview will focus on non-technical factors such as expressive ability and communication skills.

# "No matter what, once you give a simple answer and don't take the initiative to tell me what you are good at, or don't tell your highlights in an organized and clear way, even if I let you If you pass the interview, you won't write down favorable comments such as "You have a deep understanding of the framework details and you are proficient in database applications." Even if you pass the technical and subsequent comprehensive interviews, your salary will be relatively low."

「5. Once there is a low-level mistake, you may be eliminated directly」

There are certain aspects during the interview process that you absolutely cannot make mistakes, so you need to pay special attention to the following factors during the preparation process. Here are some incorrect answers that will get you out of the game.

「VI. Introduction:」Prepare some bonus points and mention them intentionally during the introduction, but don’t say them全

When introducing the project, you can intersperse some of your highlights, but please remember that whether you are introducing the project or answering questions, your current responsibilities Instead of explaining the highlights, introduce the project. Once you elaborate on it, the interviewer may feel that you are off topic.

So at this time you can explain it in one stroke. For example, you can say, "Our project has relatively large data requirements. When we are busy, we have to process hundreds of thousands of data per hour on average." This way you can introduce the interviewer. The direction of "big data".

Before the interview, you can prepare this kind of "pass-through" words according to the needs of the position. For example, the requirements for this position are the Spring MVC framework, high concurrency of big data, and experience in database tuning. Then when introducing past projects, you'd better highlight your actual skills in these aspects.

Let me give you another example. For example, Java virtual machine memory management and database optimization are two major problems that most projects will encounter. When describing the project experience, everyone can say that in this project , we need to consider memory factors, because our code is only allowed to run in a 2G memory environment, and has relatively high database performance requirements, so we often have to monitor and optimize the memory and SQL statements in the database. In this way, when the interviewer asks in-depth questions, he can throw out his prepared remarks on virtual machine memory optimization and database optimization.

If that doesn't work, you can also say "In addition to development, I also did the work of understanding requirements, testing and deployment, because this project has relatively few people and a lot of pressure." This way you can also show that you have Live your own experience.

During the interview process, once I hear something bright, I will wait until he has said the current question and then ask it casually. Generally, technical interviews can last up to half an hour, and you should spend your time answering prepared questions. When you click on it, you will have less time to be asked other questions.

「7. You can guide, but you cannot speak for yourself」

When I interview, I also meet some people who are well prepared. In fact, if you really want to apply for the job, you must prepare in advance. I can understand and even agree with this. As long as you don’t show too obvious signs, I would not write something like "It seems that you are prepared, but you cannot test your real skills", not to mention that not every interviewer can feel that you have been prepared. But you can’t be too strong just by being prepared. After all, the interview is led by the interviewer.

I met some interviewees who talked too much and usually took the initiative to expand. For example, when I asked him what the database was used for, he not only answered what the database was and what he had done, but even mentioned big data by the way. The processing techniques are all mentioned.

In fact, going too far is not enough, so I will focus on examining every detail you said, because I suspect that what you said is what you read online, not what you used in your project. I will even threaten you directly. : "Tell me the truth first. Did you really use this technology in the project? I will focus on the investigation later. Once it is considered that you did not use it in the project, it will be like a muddled pass." Often these people will take the initiative to confess.

But having said that, if he just said that the amount of data is relatively large, but stopped there and did not continue to talk about the rest, I would ask in depth, and he would naturally have the opportunity to express. At the same time, please note that generally during the interview process, once you show your bonus points, but the interviewer does not answer, the bonus points may not be necessary for the project, nor are they of concern to him, so you can stop talking about it now. , or wait until you ask the question.

「Eight, not the summary of the end」

So far, we have given some tips for introducing projects.

Two sentences, first, you must prepare before the interview. Second, this article gives a certain method, not a dogma. You can prepare according to the direction given in this article and combine it with your own project background, rather than Memorize by rote some of the rhetoric given in this article.

After everyone introduces the background of the project, the interview has just begun. No matter how well you speak, even if you guide the questions to the scope you prepared, you still have to deal with Java Web (such as Spring MVC, ORM etc.), Java Core (multi-threading, collections, JDBC, etc.) and database issues.

So where does the value of this article lie? If the guidance is not good, you will have no chance to show your ability. This is the value of the method given in this article. To be boastful, some of the methods and rhetoric given in this article are not thought up, but extracted from the experience of interviewing hundreds of candidates. There are many blood and tears in it, and there are also many ways for people to succeed. This article is somewhat helpful to everyone (especially students with less than 3 years of experience).