table of Contents
1, how to prepare project description? Do not be afraid, I do not know what the interviewer
2, ready to project details, once asked back, to show that you did not do
3, without a trace to tell the interviewer wants to hear
4, take the initiative, the interviewer has no obligation to dig your highlights
5, low-level errors may lead directly out
6, guide: Preparing plus points, dished out a low profile in the introduction, but let alone the whole
7, you can direct, but not telling their own stories
8, summary
0, EDITORIAL
In the interview, after the greeting, the interviewer will introduce general project experience. Common question is asked is that you say at the nearest (or most any decent) project.
According to our interview experience, I found that many candidates did not prepare for this, that it stammered, and some even say the project does not match the experience from the aspects such as time period or technology and curriculum vitae, which would result in the following consequences .
The first impression is not good, at least you feel that the candidate is not strong representation.
In general, the interviewer will be put under the project background candidates in question will ask 10 questions when interviewing hypothesis, then there will be at least five questions to ask the candidates according to the project described in the background, did not say if the candidate well, it would not be able to guide a good follow-up question, the equivalent of the right questions entirely to the interviewer.
When interviewed by seven capacity, 3 parts by the time of skills, and introduce the project at the beginning is the most important skill, so the "introduction" and the paper will "guide" two levels to tell you how to prepare for interview Project Introduction.
Well, the following is the text content.
1, how to prepare project description? Do not be afraid, I do not know what the interviewer
The interviewer is a human, not a god, get your resume when you are unable to verify the details of the project (usually after hiring companies to verify by way of background checks).
What's more, you do project is based on monthly basis counted, up to 30 minutes while the interviewer to understand your project experience from your resume, so you familiarity with the project is much more than the interviewer, so you It is also not nervous.
If your work experience is also richer than the interviewer, you can even control the entire interview process (after interviewing the author into a fine often do such a thing, we must also do it).
Now that the interviewer can not know your number, then they how to verify your project experience and technology? The following summarizes some of the common questions are asked.
2, ready to project details: Once asked back, to show that you did not do
In general, the rhetoric before the interview, you should be prepared to describe the project, be confident, because this part you have the final say, after you are well prepared, you can know what you have to say.
And these are your actual project experience (not a learning experience, not a training experience), once the interviewer feel you can not tell, then the credibility is very low.
Many people are particular about "what to do in the project business, as well as details of the implementation of the code", which is equivalent to the subsequent question right directly to the interviewer.
The following table lists some bad way to answer.
At the same time to avoid the above bad answer, you can press the elements of preparation of the project description given in the table. If you can, please be prepared to describe it in English.
In fact, fewer recent graduates, or work experience, English language skills are similar, but you say, this is a qualitative step forward.
Before the interview, you must prepare, must have self-confidence, but also to avoid some of the situations below.
3, without a trace to tell the interviewer wants to hear
When the project presented (including of course the subsequent interview), the interviewer wants to hear it in fact some of the key points, as long as you say it, and answer the questions better, this is definitely a plus point.
When I was interviewing someone else, once these key points is confirmed, I will definitely add a sum in the comment.
Here interviewer hear some key points and the corresponding column rhetoric.
4, take the initiative, the interviewer has no obligation to dig your highlights
When I went to interview people, they often ask questions in particular: What is your project's highlights? Or you as a candidate, what other bonus items to help you successfully apply for this post.
Even so asked, some people just say no.
I ask already in the role of dislocation, as the interviewer, should take the initiative to say, rather than waiting to ask, but please note that the time to have skills, look for opportunities to say, usually find some open questions said.
For example: In this project we use what technology?
You said that in addition to basic technologies such as Spring MVC, Hibernate, database and other conventional techniques. I have to say use a Java memory management, which could reduce the pressure on the virtual machine memory, or use a large data processing technology.
In other words, you have to look for every opportunity to speak and current technology is also very popular show for you.
Or find related problems do scalability explanation, asked example: you have not used before, and many-to-many?
You said that in addition to the basic knowledge, it also can say that in general I will set appropriately and inverse cascade keywords based on demand, followed by an actual case to illustrate the rational design help for your project, so you can explain the extension your skills.
If you do not say the contrary, if the interview would think you would have a simple one to one and one to many operations.
面试的时候，如果候选人回答问题很简单，有一说一，不会扩展，或者用非常吝啬的语句来回答我的问题，那么我一般会给机会让他们深入讲述（但我不敢保证不是每个面试官都会深入提问），如果回答再简洁，那么也会很吝啬地给出好的评语。
记住：面试官不是你的亲戚，面试官很忙，能挖掘出你的亮点的面试官很少，而说出你的亮点是你的义务。
我在面试别人过程中，根据不同的情况一般会给出如下的评语。
1、回答很简单，但回答里能证明出他对框架等技术确实是做过。
我会在评语里些“对框架了解一般，不知道一些深层次的知识（我都问了多次了你都回答很简答，那么对不起了，我只能这么写，或许你确实技术很强，那也没办法，谁让你不肯说呢？）”。
同时会加一句“表达能力很一般，沟通能力不强”，这样即使他通过技术面试，后面的面试他也会很吃力。
2、回答很简单，没法验证是在项目里做过这个技术，还是仅仅学过这个技术。
我就会写“在简历中说用过XX技术，但对某些细节说不上来，没法看出在项目里用到这个技术”，如果这个技术是职务必需点，那么他通过面试的可能性就非常小。
3、回答很简单，而且只通过嗯啊之类的虚词回答，经过提醒还这样。
我会敷衍几句结束面试，直接写“技术很薄弱，没法通过面试”。
4、虽然通过回答能很好地展示自己的技能，但逻辑调理不清晰。
那么我会让他通过技术面试，但会写上“技能很好，但表达能力一般（或有待提高），请后继面试经理斟酌”。
这样通过后继综合面试的机会就一般了，毕竟综合面试会着重考察表达能力交往能力等非技术因素。
不管怎样，一旦回答简单，不主动说出你的擅长点，或没有条理很清楚地说出你的亮点，就算我让你通过面试，也不会写上“框架细节了解比较深，数据库应用比较熟练”等之类的好评语，你即使通过技术和后面的综合面试，工资也是比较低的。
5、低级错误可能导致直接出局
面试过程中有些方面你是绝对不能出错，所以你在准备过程中需要尤其注意如下的因素。下面列了些会导致你直接出局的错误回答。
6、引导：准备加分点，在介绍时低调抛出，但别说全
在做项目介绍的时候，你可以穿插说出一些你的亮点，但请记得，不论在介绍项目还是在回答问题，你当前的职责不是说明亮点而是介绍项目，一旦你详细说，可能会让面试官感觉你跑题了。
所以这时你可以一笔带过，比如你可以说，“我们的项目对数据要求比较大，忙的时候平均每小时要处理几十万条数据”，这样就可以把面试官引入“大数据”的方向。
你在面试前可以根据职位的需求，准备好这种“一笔带过”的话。比如这个职位的需求点是Spring MVC框架，大数据高并发，要有数据库调优经验，那么介绍以往项目时，你就最好突出这些方面你的实际技能。
再给大家举个例子，比如Java虚拟机内存管理和数据库优化是绝大多数项目都要遇到的两大问题，大家都可以在叙述项目经验时说，在这个项目里，我们需要考虑内存因素，因为我们的代码只允许在2G内存环境中运行，而且对数据库性能要求比较高，所以我们经常要监控优化内存和数据库里的SQL语句。
这样当面试官深入提问时，就能抛出自己准备好的虚拟机内存优化和数据库优化方面的说辞。
实在不行，你也可以说“我除了做开发，也做了了解需求，测试和部署的工作，因为这个项目人手比较少，压力比较大”，这样你也能展示你有过独挡一面的经历。
我在面试过程中，一旦听到有亮点，就会等到他说好当前问题后，顺口去问。
一般技术面试最多办半小时，你把时间用在回答准备好的问题点上的时候，被问其他问题的时间就会少了。
7、你可以引导，但不能自说自话
我面试的时候，也会遇到些有准备的人，其实如果你真的想应聘的话，一定要事先准备，这点我能理解，甚至赞同。
你只要别露出太明显的痕迹，我不会写上“似乎有准备，没法考察真实技能”这种话，更何况未必每个面试官都能感觉出你准备过。 但你不能凭着有准备而太强势，毕竟面试是面试官主导的。
我遇到个别面试的人，他们说话太多，一般会主动扩展，比如我问他数据库用什么，他不仅回答数据库是什么，自己做了什么，甚至顺便会把大数据处理技术都说出来。
In fact, too far, I would say focus on every detail of your investigation, because I suspect that what you say you are from the Internet to see, not what you used in the project.
I would even direct threat: "You first, and I tell the truth this technology you really use in the project, my back will be the focus of study, once considered your project's not done, this nature is to muddle through," often these people will the initiative to confess.
But having said that, if he just said, a greater amount of data, but go beyond that, do not continue to say back then, I would further ask, he naturally had the opportunity to express.
Also note that, in general in the interview process, once you've flashed a plus point, but the interviewer did not answer the mouth, this may be a plus point of the project is not necessary, nor is he concerned, you can currently do not say or wait until you ask questions to say.
8, summary
Here, we have given some tips introduction project, to sum up:
Two things, first, be sure to prepare before the interview, second, given herein is a method, not a dogma, we can combine the direction of this paper is to prepare their project background, rather than rote given article Some of rhetoric.
When we introduce a good project background, the interview has just begun, even if you put it better, even if you have a question directed to the preparation of your range in which they have to deal with Java Web (such as Spring MVC, ORM, etc.), Java Core ( multithreading, collections, JDBC and other issues) and databases.
Then the value of the article in which it? If the boot is not good, you do not have the chance to show their ability. This is how the value of this paper lies.
To be boastful words, rhetoric and some of the methods set forth herein are not racking our brains to come out, but drawn from experience in interviewing hundreds of candidates, many of which blood and tears, but also the way many successful people, how much help everyone (especially less than 3 years experience of junior programmers).