During the interview, after greetings, the general interviewer will introduce the project experience. A common question is to talk about your most recent (or best known) project.
According to our interview experience, we found that many candidates were unprepared for this. Some people even said that the project experience does not match with the resume in terms of time period or technology. This will cause the following consequences .
1. The first impression is not good, at least you will feel that the candidate is not strong in expression.
2. Generally speaking, the interviewer will ask questions based on the project background introduced by the candidate. Assuming that 10 questions will be asked during the interview, then at least 5 questions will be asked based on the project background introduced by the candidate. If you do not say it well, then you will not be able to guide the subsequent questions well, which is equivalent to giving the interviewer the right to ask questions completely.
In the interview, 7 are based on ability and 3 are based on skills. The introduction project at the beginning is the top priority of skills, so this article will tell you how to prepare for the interview from the two aspects of "introduction" and "guidance" Project Introduction.
Well, the following is the text content.
1. Prepare the project description before the interview, don’t be afraid, because the interviewer doesn’t know anything
The interviewer is a human being, not a god. When you get your resume, you can’t verify the details of your project (generally, the company will use background checks to verify it after being hired). What's more, the project you do is calculated on a monthly basis, and the interviewer spends up to 30 minutes to learn about your project experience from your resume, so you are more familiar with the project than the interviewer, so you Don't be nervous at all. If you have more work experience than the interviewer, you can even control the entire interview process (the author often does this kind of thing after being proficient in the interview, and everyone can do it too).
Since the interviewer cannot understand your details, how can they verify your project experience and skills? Below is a summary of some commonly used questioning methods.
2. The various details of the preparation project. Once asked, it means that you have not done it.
Generally speaking, before the interview, everyone should prepare the rhetoric of the project description, be more confident, because you have the final say in this part, and be fluent, because you can know what you want to say after you have fully prepared. And these are your actual project experience (not learning experience, nor training experience), so once you make the interviewer feel that you can't speak up, then the credibility is very low.
Many people are stuck on "what business is done in the project and the details of the code implementation", which is equivalent to giving the interviewer the right to follow-up questions directly. The table below lists some bad answers.
While avoiding the above bad answers, you can prepare project introductions based on the elements given in the table below. If possible, please 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 prepare and be confident, but you must also avoid the following situations.
3. Say what the interviewer loves to hear without revealing a trace
When introducing the project (including subsequent interviews of course), the interviewer actually wants to hear some key points, as long as you speak out and answer related questions better, this is definitely a plus. When I interview others, once these key points are confirmed, I will definitely add a sum to the comment.
Here are some key points and corresponding rhetoric that interviewers love to listen to.
4. Be proactive, 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, some people say no.
I’m already in a misplaced role when asking questions like this. As an interviewer, I should take the initiative to speak out instead of waiting to ask, but please note that you need to be skillful when speaking, find opportunities to speak, and usually find some open questions.
For example: What technology was used in this project? In addition to talking about some basic technologies, such as Spring MVC, Hibernate, and general database technologies, you also have to say that Java memory management is used, which can reduce the pressure on virtual machine memory, or use big data processing Technology etc. In other words, you have to find every opportunity to say what you can get and is currently very popular technology.
Or find a related question for expansibility, 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 a reasonable design for your project, so that you can extend the explanation Your skills too. On the contrary, if you don't say it, the interview will definitely think that you can only do simple one-to-one and one-to-many operations.
During the interview, if the candidates answer the questions very simple, have one thing to say, will not expand, or use very stingy sentences to answer my questions, then I will generally give them the opportunity to tell them in depth (but I can’t guarantee that not every Every interviewer will ask in-depth questions), if the answer is no more concise, then he will be very stingy to give good comments.
Remember: the interviewer is not your relative, the interviewer is very busy, there are few interviewers who can dig out your highlights, and it is your duty to tell your highlights.
In the process of interviewing others, I generally give the following comments according to different situations.
1. The answer is very short, but the answer can prove that he has indeed done the framework and other technologies, I will say in the comments "General knowledge of the framework, I don't know some deep knowledge (I have asked many times Your answer is very short, then I’m sorry, I can only write like this, maybe you are really very skilled, that’s no way, who would tell you not to say it?)”, at the same time add the sentence “expression ability is very ordinary, The communication skills are not strong", so even if he passes the technical interview, he will be very strenuous 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 usual study. I would write "In my resume, I said that I have used XX technology, but I can't tell some details. I can't see that this technology is used in the project." If this technology is necessary for the job, then the possibility of him passing the interview It's very small.
3. The answer is very simple, and only through function words such as ah, ah, etc. After being reminded, I will end the interview with a few perfunctory sentences and directly write "The technology is very weak and I cannot pass the interview".
4. Although the answer can show his skills well, but the logical adjustment is not clear, then I will let him pass the technical interview, but will write "The skills are very good, but the expression ability is average (or needs to be improved), please follow up The interview manager considers." In this way, the chance of passing the subsequent comprehensive interview is general. After all, the comprehensive interview will focus on non-technical factors such as communication skills and communication skills.
In any case, once the answer is simple, you don’t take the initiative to say what you are good at, or if you don’t say your highlights clearly, even if I let you pass the interview, I won’t write "the framework details have a deeper understanding of the database application Good comments such as "proficient", even if you pass the technical and subsequent comprehensive interviews, the salary is relatively low.
5. Once there is a low-level error, it may be out of the game directly
You must not make mistakes in some aspects of the interview process, so you need to pay special attention to the following factors during the preparation process. Below are some wrong answers that will cause you to go straight out.
6. Introductory chapter: prepare some extra points, which are deliberately mentioned in the introduction, but don’t say everything
When introducing the project, you can intersperse with some of your highlights, but please remember that whether you are introducing the project or answering questions, your current responsibility is not to explain the highlights but to introduce the project. Once you elaborate, you may The interviewer feels you have digressed.
So at this time you can take it all at once. For example, you can say, "Our project requires a lot of data, and when we are busy, we have to process hundreds of thousands of data per hour", so that the interviewer can be introduced into the direction of "big data" .
Before the interview, you can prepare this kind of "one-off" words according to the needs of the position. For example, the demand point of this position is the Spring MVC framework, big data high concurrency, and database tuning experience. Then when introducing past projects, you'd better highlight your practical skills in these areas.
Let me give you another example. For example, Java virtual machine memory management and database optimization are two major issues that most projects will encounter. When describing project experience, you 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 the database performance requirements are relatively high, so we often need 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 rhetoric about virtual machine memory optimization and database optimization.
If it 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 less staff and more pressure”, so that you can also show that you have a unique experience .
In the interview process, once I hear a bright spot, I will wait until he has said the current question, and then ask it. Generally, a technical interview can be held for up to half an hour. When you spend your time answering the prepared questions, you will be There will be less time to ask other questions.
7. You can guide, but you can't talk to yourself
When I interview, I will meet some people who are prepared. In fact, if you really want to apply for a job, you must prepare in advance. I can understand and even agree with this. As long as you don’t show too obvious traces, I won’t Write the words "seems to be prepared, unable to examine the real skills", not to mention that not every interviewer can feel that you have been prepared. But you can't be too strong with preparation, after all, the interview is led by the interviewer.
I met individual interviewers who talked too much and would usually take the initiative to expand. For example, when I asked him what the database used, he not only answered what the database was, what he did, and even talked about the big data processing technology by the way.
In fact, too much is too late, I will focus on every detail you said, because I suspect that what you are talking about is what you read from the Internet, and not what you used in your project. I will even directly threaten: "You tell me first To be honest, you really use this technology in the project, and I will focus on it later. Once you are deemed to have not done it in the project, this nature is a foolish 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 stop talking, I will ask in depth if he doesn't continue to say the following, he will naturally have the opportunity to express. At the same time, please note that in the interview process, once you show the bonus points, but the interviewer does not answer, this bonus point may not be necessary for the project, nor is it what he cares about. You can stop talking about it now. , Or wait until you ask questions.
8. Not the conclusion of the conclusion
So far, we have given some tips for introducing the project.
Two sentences. First, you must prepare before the interview. Second, this article gives you the method, not dogma. You can prepare according to the direction given in this article and combined with your project background, instead of memorizing it. Some rhetoric.
After everyone introduced the project background, the interview has just begun. Even if you say it well, even if you guide the question to the scope of your preparation, you have to deal with Java Web (such as Spring MVC, ORM, etc.), Java Core ( Multithreading, collections, JDBC, etc.) and database issues.
So where is the value of this article? If the guidance is not good, you will never have the opportunity to demonstrate your abilities. This is the value of the method given in this article. To make a boastful statement, some of the methods and rhetoric given in this article are not thought up by scratching their heads, but are drawn from the experience of interviewing hundreds of candidates. There are a lot of blood and tears, and there are many ways to succeed. This article is helpful to everyone (especially junior programmers with less than 3 years of experience). This is also the reason why this article is applied to the homepage.
This is not the end, we will also write some blog posts on "How to deal with common problems" or "How to quickly improve your ability" when appropriate.
By the way, I am currently working as a Java developer. If you encounter any questions about learning methods, learning routes, learning efficiency, etc. during the introductory learning of Java, you can apply to join my Java novice learning exchange group : 798844620, there are a lot of beginners who are learning Java technology. You can also come to me directly if you lack the basic video tutorials. I have the latest Java basics and detailed video tutorials. The group file also contains me doing Java technology. Some study manuals, interview questions, development tools, PDF documents, books and tutorials compiled during this time.