How do you introduce your project experience during an interview?

During the interview, usually after a few pleasantries (sometimes asking you to introduce yourself), the interviewer will ask you to start introducing your project experience.

A common question is: "Tell me about your most recent (or most successful) project".

Based on my many years of interview experience, I found that many interviewees were completely unprepared for this, and some even said that the project experience did not match the resume in terms of time period or technology. , which will cause the following consequences.

1. The first impression is not good, at least you will feel that the candidate has poor presentation ability.

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, at least 5 questions will be based on the project background introduced by the candidate. To ask, if the candidate fails to say yes, then he will not be able to guide the subsequent questions well, which is equivalent to completely handing over the right to ask questions to the interviewer.

During the interview, 7 points depend on ability and 3 points depend on skills, and the introduction project at the beginning is the top priority among skills, so this article will start from "INTRODUCTION" and " Guidance"Two major levels tell you how to prepare for the project introduction during the interview.

Okay, 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 he gets your resume, he cannot verify the details of your project (generally, companies will use background checks to verify the details after hiring) ). What's more, the projects you do are calculated on a monthly basis, and the interviewer takes up to 30 minutes to learn about your project experience from your resume, so your familiarity with the project is far greater than that of the interviewer, so you No need to 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 becoming an expert in interviews, and everyone can do it too).

	「你」	「面试官」
I know a lot about your previous projects and skills		I can only listen to what you say, and I can only act based on what you say Make judgments about the content
Responsibilities in the interview process	Successful defense in a short period of time	If no loopholes can be found , it can only be considered that you have done it before
Preparation time	You have enough time to prepare before the interview	Usually 30 minutes before the interview Read your resume
Communication process	You can make mistakes, but don’t make critical mistakes	It won’t be too difficult for you unless you are too Poor
Skills	If you have enough skills, you can also find enough interview questions from the Internet	In fact, just ask some general and regular questions The problem

Since the interviewer cannot know your details, how can they verify your project experience and technology? Below is a summary of some commonly used questions.

「How to ask questions」

「Purpose」

Ask you to describe your work experience and projects (most likely recent) and see if what you said is consistent with what is on your resume

See if you have actually done it These projects

Look at the technologies used in the projects on your resume, such as frameworks and databases, and then ask some basic questions about these technologies

or verify whether you have done it project, and see if you understand these technologies, and prepare for further questions

For a certain project, ask some technical questions in depth, or ask about technical implementation from different aspects , see if there are any contradictions in your answers If people say they have done database work, they will ask questions about indexing

Through these types of questions, verify whether the candidate really has project experience (or just learning experience)

"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.

「Answer method」	「Consequences」
I worked on XX portal project at XX software company. This project achieved XX functions, specifically XX and XX modules. Each module performed XX functions. The customer was XX. In the end, this project made money. XX Qian	interrupts directly, because I don’t need to understand the business needs. I will directly ask him about the technology in the project
(need to recruit a Java back-end developer, Knowing Spring MVC) I implemented my most recent project using C# (or other non-Java technology), and it was implemented... Or what I did recently was not development, but testing... Or my recent project did not use Spring MVC	Ask, when was the last project that you used SSH technology, and then write in the comment: I haven’t been exposed to SSH recently in XX time
During graduation project (or While studying, while studying, in XX training school, in XX practical training course),...	interrupted directly and asked you whether this is a commercial project, and if not, do you have any other projects? business experience. If you have no experience in commercial projects, unless it is a school recruitment, you will just end the interview.
When describing the project, some key elements (such as company, time, technology used, etc.) and the differences on the resume Match	We will investigate this inconsistency in depth. If the resume is fake, the interview may be interrupted directly. If it is really a clerical error, then a reasonable explanation needs to be provided

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.

「Elements」	「Style」
Control it within 1 minute and tell the basic situation of the project, such as project name, background, which client it is for, basic things completed, how long it has been done, how big the project is, what technologies are used, and database What to use, and then briefly talk about the module as appropriate. Highlight background, technology, databases and other technology-related information.	I built XX foreign exchange margin trading platform in XX company. The customer is XX bank. It mainly completes the functions of listing, real offer transaction, margin leverage transaction and other functions. The database is Oracle, and JS and other technologies are used at the front desk. Java's SSH is used in the background, and several people have been working on it for X months. There is no need to describe each functional module in detail, and there is no need to say too much about business but not technology. If the interviewer is interested, wait for him to ask.
Take the initiative to tell what you have done. This part of the description must be consistent with your technical background.	I built the foreign exchange real offer trading system, the pending order transaction system, and the XXX module for X months
Describe your role in the project	I mainly did development, but before development, I participated in business research, database design and other work under the leadership of the project manager. Later, I participated in testing and deployment work.
You can describe the technical details used, especially the technical details you used. Pay special attention to this part. You must know what you say, because the interviewer will use it later. This is the question. If you have done 5 modules, you would rather only say 2 that you can speak proficiently and catchyly.	Used collections in Java, JDBC,... and other technologies, used frameworks such as Spring MVC, and used technologies to connect to the database.
You bear this part at your own risk. If you can, talk about some popular elements without saying anything, such as Linux, big data, high access pressure, etc. But once you say it, the interviewer will ask for details directly.	In this system, deployed on Linux, the amount of data to be processed every day is XX, and the requirement is to process 50 million pieces of data in 4 hours and 1G of memory. Average visitors are XXX per minute.

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

「Situations to avoid」	「Correct approach」	『Reason』
The answer is simple. Answer whatever you ask, usually just answer in one sentence	Tell out everything you know, focus on the ideas you know, frame	Question: Have you ever used SSH? Answer: Used.Question: In what projects is it used? Answer: An insurance project. Question: What did you do? Answer: I won’t ask about development
Speak too fluently	Pause appropriately and think while speaking	Let the interviewer feel that you are memorizing Prepare things, so that the questions later will be difficult
Don’t say anything when introducing the project,	Just talk about the things you just prepared, and say it logically	It will make the interviewer feel that your thinking is too confusing
Don’t introduce too many technical details, just talk about the technology you are familiar with	The technical aspects are covered So far, wait until the interviewer comes to ask	all the technical points you mentioned, and you may be asked in depth. Interviewers generally have their own interview rhythm. If you talk too much about technical details during your introduction, you are likely to be interrupted and unable to express the highlights you prepared.

"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.

##Be able to consider the scalability of the code and have the awareness to participate in the framework designMy project XX insurance project uses SSH technology, and the database is Oracle, (this is the foreshadowing), When developing, I will first design the framework with the project manager and participate in the construction of the framework. When connecting to the database, we use DAO. The reason for this is to encapsulate the SQL statement into the DAO layer. Once the functional module needs to be expanded, , you don’t need to make too many changes. Have awareness of tuning and be able to find problem points through monitoring and then solve themDuring the development stage, I noticed memory performance issues and SQL running time issues , during the stress testing phase, I will use xx tools to monitor the memory and database, discover code points that need to be improved, and then optimize them by checking the information. Finally, after the project goes online, we will deploy a monitoring system. Once memory and database problems are discovered, we will solve them as soon as possible. I have strong hands-on ability, I am willing to work, I know a lot of things, and I have a good teamwork spiritIn the project, I not only have to do development work, And I need to test it myself. I need to debug it based on the output of some logs to the database or Java. When I open a module, I need to deploy it to Linux for testing. Or, once I encounter a problem, if it is business related, I will communicate with the project manager in time. If it is technical, I will check the information myself. If it is testing, I will communicate with the tester in time.

「Key points」	「Rhetoric」
Have a strong sense of responsibility and can adapt to a stressful environment	When asked, "What should you do if you encounter problems in the project?" Answer: I encounter problems. Check the information first. If it really can't be solved, we won't delay and will ask the relevant people in time. Even if we work overtime, we will solve it within the specified time.
Be independent-minded and able to continuously explore new knowledge	In the project, I will share my ideas with the project manager and put forward my suggestions while ensuring the progress. solution. During the development process, I will think about it first and implement it in a better way, such as the most efficient method. In addition, you need to find opportunities to say: I usually keep looking at some new technologies (such as big data Hadoop), and I will continue to have a deeper understanding of the underlying implementation of some frameworks and technologies.

"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.

「Error type」	「Consequences」
Inconsistencies, the following answers cannot prove your project description. For example, you say that Spring MVC is used at the beginning, but you cannot tell the most basic implementation later, for example, you don’t know what classes Spring has. Or unable to tell the details of the project.	I will doubt the authenticity of this project, and I will further ask: What is the database used and how much data is it? How many people have worked on it and how long it took. Once there are obvious loopholes, such as a small project that takes a lot of time, then it is not just a technical problem, but an attempt to "muddle through" during the interview process.
I can’t answer the basic conceptual questions that will definitely be used in the project. What is Spring’s dependency injection concept and how to use it, or what design patterns are used in MyBatis?	Once I find out that I don’t know the concept, I will confirm it through more questions. If it is confirmed by me that it is weak, this is quite serious, because poor technical ability and unused technology are two completely different things. In this situation, if the technology is not used, it will lead to direct elimination.
There are inconsistencies between the work experience mentioned during the interview and the resume	I will directly suspect that the resume is made up, and I will ask the candidate to explain, even if it is a resume If he makes a mistake, I will also ask more in-depth questions to verify his skills and abilities.
The skill description on the resume is obviously inconsistent with the answer. For example, it is obvious that I only know simple Linux, but I am boasting about it.	I will pass some more advanced ones Questions verify other skills and find out where others are boasting. Therefore, it is suggested that you can exaggerate appropriately, but not too much. For example, if you have not built a framework in the project but have built it during daily study, you can write "The framework of XX project was built by you", but you cannot say that you are an architect. , understands the low-level aspects of the project very well.
If you make the interviewer feel that you are unstable and impetuous, such as speaking rudely or dressing very informally during the interview, wear a vest.	No matter how good your skills are, this may cause you to be eliminated directly. I usually write bad comments directly on candidates who are smooth-talking, which makes it difficult for the project manager to interview later. I also met a person whose resume stated that he changed jobs every six months. I asked him why he changed jobs so often. He directly said it was due to salary issues. I simply failed this person.
It is clearly stated that overtime and business trips are not allowed	In fact, although there is this question, the company may not actually work overtime or go on business trips. But hearing this kind of answer means that the person cannot withstand high-pressure work or has a weak sense of responsibility. Most companies will not want such people.

「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).

The above is the detailed content of How do you introduce your project experience during an interview?. For more information, please follow other related articles on the PHP Chinese website!