Author's original description: This article has been quoted countless times by various CSDN and other platforms since it was published in the blog garden. Some people have also vowed to add the original description.
So how do you judge that this article is my original?
1 At first glance, the publication time of this article in the blog garden is this: https://www.cnblogs.com/JavaArchitect/p/7586949.html
posted on 2017-09-24 13:04 hsm_computer Reading (70478) Comments (31), you can compare the publication time of other articles.
2 Second, this article is actually an excerpt from my book, "Java Web Lightweight Development Interview Tutorial", https://item.jd.com/14861686043.html , the publisher’s certification is the best proof of originality.
Okay, the text begins.
///
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 the resume in terms of time period or technology. This will cause the following consequences .
1 The first impression is not good, at least it feels 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 the candidate does not If you say yes, 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.
-------------------------------------------------------------------------------------------------
1 Prepare the project description before the interview, don’t be afraid, because the interviewer doesn’t know anything
The interviewer is a human, not a god. When you get your resume, you can’t verify the details of your project (generally, the company will use a background check 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).
|
|
you |
Interviewer |
| On your previous projects and skills |
know it well |
I can only listen to what you say, and only make judgments based on what you say |
| Responsibilities during the interview |
Defend successfully in a short period of time |
If you can’t find a loophole, you can only count as you did it before |
| Preparation time |
You have plenty of time to prepare before the interview |
Usually spend 30 minutes to read your resume before the interview |
| Communication process |
You can make mistakes, but don't make critical mistakes |
Won't embarrass you too much unless you are too bad |
| skill |
You have enough skills, and you can find enough interview questions online |
Actually just ask some general and regular questions |
Since the interviewer cannot understand your details, how can they verify your project experience and skills? Some commonly used questioning methods are summarized below.
| Question method |
purpose |
| Let you describe your work experience and projects (most likely the most recent), and see if what you say is consistent with your resume |
See if you have actually done these projects |
| Look at the technologies used in the project on your resume, such as frameworks and databases, and then ask some basic questions about these technologies |
Or verify whether you have done the project, and at the same time see if you understand these technologies, and prepare for further questions |
| For a certain project, keep asking some technical questions in depth, or ask some technical implementations from different sides, and see if there is any contradiction in your answers before and after |
In-depth verification of your project details |
| For a certain technology, ask questions that will be encountered in the project. For example, if a candidate says that he has done a database, he will ask questions about indexing. |
Through such questions, verify whether the candidate really has project experience (or just learning experience) |
2 Prepare the various details of the project. Once asked, it means you haven’t 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 more fluent, because you can know what you want to say after you are 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 following table lists some bad answers.
| Answer method |
as a result of |
| I did XX portal project in XX software company, this project achieved XX function, specifically XX and XX modules, each module did XX function, the client was XX, and finally this project made XX money |
Interrupt directly, because I don’t need to understand the business requirements, I will directly ask him about the technology in the project |
| (Need to hire a Java back-end development, Spring MVC) I implemented a recent project using C# (or other non-Java technology) and realized it... Or what I did recently is not development, but testing... Or my recent project did not use Spring MVC |
Ask a question, when did you use SSH technology recently, and write in your comment: Haven't been exposed to SSH in the last XX time |
| In the graduation project (or while studying, while studying, in the XX training school, in the XX training course),... |
Interrupt directly and ask you if this is a commercial project. If not, do you have any other commercial experience. If there is no commercial project experience, unless it is a school recruitment, the interview will be ended directly |
| When describing the project, some key elements (such as company, time, technology used, etc.) do not match with the resume |
We will investigate this inconsistency in depth. If it is a fraudulent resume, 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 bad answers, you can prepare project introductions with the elements given in the following table. 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.
| element |
style |
| Within 1 minute, tell the basic situation of the project, such as the name of the project, background, which customer to do, basic things completed, how long it has been done, how large the project is, what technologies are used, and what database is used, and then briefly talk as appropriate. Click on the module. Focus on background, technology, database and other technology-related information. |
I built the XX foreign exchange margin trading platform in XX company. The client is XX Bank. It mainly completed the functions of listing, firm transaction, margin leverage transaction, etc. The database is Oracle, the front desk uses JS and other technologies, and the backstage uses Java's SSH , A few people did 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. |
| To proactively say what you have done, this part of the description must be consistent with your technical background. |
I made the foreign exchange real trading system, the pending order transaction system, and the XXX module, and did it for X months |
| Describe your role in the project |
I mainly did development, but before the development, under the leadership of the project manager, I participated in business research, database design, etc., and later I participated in testing and deployment. |
| You can describe the technical details used, especially the technical details you use. Pay special attention to this part. You must know what you say, because the interviewer will ask it based on this later. If you have made 5 modules, you would rather just say that you are proficient in 2 catchy ones. |
The collections in Java, JDBC, ... and other technologies are used, and the Spring MVC and other frameworks are used to connect to the database with technology.
|
| You take this part at your own risk, and if you can, you can quietly say some popular elements, such as Linux, big data, and heavy access pressure. But once you say it, the interviewer will ask the 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. The average visitor is XXX per minute. |
Before the interview, you must prepare and be confident, but you must also avoid the following situations.
| Situation to avoid |
Correct way |
the reason |
| The answer is simple. Ask what to answer, often answer in one sentence |
Speak out what you know, focus on the ideas you know, frame |
Q: Have you used SSH? Answer: Used. Q: In what project is it used? Answer: An insurance item Q: What did you do? Answer: Development I just don't ask |
| Speak too fluently |
Pause appropriately and talk while thinking |
Let the interviewer feel that you are memorizing what you have prepared, so that the following questions will be difficult |
| Say everything when the project is introduced, |
Just talk about what you have just prepared, and say it logically |
Make the interviewer feel that your thinking is too messy |
| Don’t introduce too much technical details, just talk about the technology you are familiar with |
The technical side is over, wait for the interviewer to ask |
你说到的所有技术要点，都可能会被深问。面试官一般会有自己的面试节奏，如果你在介绍时就太多说技术细节，很有可能被打断，从而没法说出你准备好的亮点。 |
3 不露痕迹地说出面试官爱听的话
在项目介绍的时候（当然包括后继的面试），面试官其实很想要听一些关键点，只要你说出来，而且回答相关问题比较好，这绝对是加分项。我在面试别人的时候，一旦这些关键点得到确认，我是绝对会在评语上加上一笔的。
下面列些面试官爱听的关键点和对应的说辞。
| 关键点 |
说辞 |
| 能考虑到代码的扩展性，有参与框架设计的意识 |
我的项目XX保险项目，用到SSH技术，数据库是Oracle，（这个是铺垫），开发的时候，我会先和项目经理一起设计框架，并参与了框架的构建，连接数据库的时候，我们用到了DAO，这样做的理由是，把SQL语句封装到DAO层，一旦要扩展功能模块，就可以不用做太多的改动。 |
| 有调优意识，能通过监控发现问题点，然后解决
|
在开发阶段，我就注意到内存的性能问题和SQL运行的时间问题，在压力测试阶段，我会通过xx工具来监控内存和数据库，发现待提升的代码点，然后通过查资料来优化。最后等项目上线后，我们会部署监控系统，一旦发现内存和数据库问题，我们会第一时间解决。 |
| 动手能力很强，肯干活，会的东西比较多，团队合作精神比较好 |
在项目里，我不仅要做开发的工作，而且需要自己测试，需要自己根据一些日志的输出到数据库或Java端去debug，当我开好一个模块时，需要自己部署到Linux上测试。 或者，一旦遇到问题，如果是业务方面的，我会及时和项目经理沟通，如果是技术方面的，我会自己查资料，如果是测试方面的，我会及时和测试的人沟通。 |
| 责任心比较强，能适应大压力的环境 |
被问“你如果在项目里遇到问题怎么办？” 回答：遇到问题我先查资料，如果实在没法解决，不会拖，会及时问相关的人，即使加班，也会在规定的时间内解决。 |
| 有主见，能不断探索新的知识 |
在项目里，我会在保证进度的前提下和项目经理说我的想法，提出我的解决方案。在开发过程中，我会先思考一下，用一种比较好的方式，比如效率最高的方法实现。 另外你要找机会说出：平时我会不断看一些新技术（比如大数据Hadoop），会不断深入了解一些框架和技术的实现底层。 |
4 一定要主动，面试官没有义务挖掘你的亮点
我去面试人家的时候，往往会特别提问：你项目里有什么亮点？或者你作为应聘者，有什么其他加分项能帮你成功应聘到这个岗位。即使这样问，还有些人直接说没有。
我这样问已经是处于角色错位了，作为面试者，应当主动说出，而不是等着问，但请注意，说的时候要有技巧，找机会说，通常是找一些开放性的问题说。
比如：在这个项目里用到了什么技术？你除了说一些基本的技术，比如Spring MVC，Hibernate，还有数据库方面的常规技术时，还得说，用到了Java内存管理，这样能减少对虚拟机内存的压力，或者说用到了大数据处理技术等。也就是说，得找一切机会说出你拿得出手的而且当前也非常热门的技术。
或者找个相关的问题做扩展性说明，比如被问到：你有没有用到过一对多和多对多？你除了说基本知识点以外，还可以说，一般我还会根据需求适当地设置cascade和inverse关键字，随后通过一个实际的案例来说明合理设计对你项目的帮助，这样就能延伸性地说明你的技能了。相反如果你不说，面试话一定会认为你只会简单的一对一和一对多操作。
面试的时候，如果候选人回答问题很简单，有一说一，不会扩展，或者用非常吝啬的语句来回答我的问题，那么我一般会给机会让他们深入讲述（但我不敢保证不是每个面试官都会深入提问），如果回答再简洁，那么也会很吝啬地给出好的评语。
记住：面试官不是你的亲戚，面试官很忙，能挖掘出你的亮点的面试官很少，而说出你的亮点是你的义务。
我在面试别人过程中，根据不同的情况一般会给出如下的评语。
1 回答很简答，但回答里能证明出他对框架等技术确实是做过，我会在评语里些“对框架了解一般，不知道一些深层次的知识（我都问了多次了你都回答很简答，那么对不起了，我只能这么写，或许你确实技术很强，那也没办法，谁让你不肯说呢？）”，同时会加一句“表达能力很一般，沟通能力不强”，这样即使他通过技术面试，后面的面试他也会很吃力。
2 回答很简单，通过回答我没法验证他是在项目里做过这个技术，还是仅仅在平时学习中学过这个技术。我就会写“在简历中说用过XX技术，但对某些细节说不上来，没法看出在项目里用到这个技术”，如果这个技术是职务必需点，那么他通过面试的可能性就非常小。
3 回答很简单，而且只通过嗯啊之类的虚词回答，经过提醒还这样，我会敷衍几句结束面试，直接写“技术很薄弱，没法通过面试”。
4 虽然通过回答能很好地展示自己的技能，但逻辑调理不清晰，那么我会让他通过技术面试，但会写上“技能很好，但表达能力一般（或有待提高），请后继面试经理斟酌”。这样通过后继综合面试的机会就一般了，毕竟综合面试会着重考察表达能力交往能力等非技术因素。
不管怎样，一旦回答简单，不主动说出你的擅长点，或没有条理很清楚地说出你的亮点，就算我让你通过面试，也不会写上“框架细节了解比较深，数据库应用比较熟练”等之类的好评语，你即使通过技术和后面的综合面试，工资也是比较低的。
5 一旦有低级错误，可能会直接出局
面试过程中有些方面你是绝对不能出错，所以你在准备过程中需要尤其注意如下的因素。下面列了些会导致你直接出局的错误回答。
| 错误类型 |
导致的后果 |
| 前后矛盾，后面的回答无法证明你的项目描述，比如一开始说用到了Spring MVC，后面没法说出最基本的实现，比如不知道Spring有哪些类，或者没法说出项目的细节。 |
我会怀疑这个项目的真实性，我就会进一步问：数据库用什么，数据量多少？多少人做了多少时间，一旦再出现明显漏洞，比如一个小项目用到非常多的时间，那么就不仅仅是技术问题，而是在面试过程中企图“蒙混过关”的性质了。 |
| 项目里一定会用到的基本概念性问题都回答不上，Spring的依赖注入概念是什么，怎么用的，或者Hibernate的一对多怎么实现 |
一旦被我发现概念不知道，我就会通过更多问题确认，如果被我确认很弱，这就相当严重，因为技术能力差和技术没用过是两个截然不同的状况，技术没用过会导致直接出局。 |
| 面试时说出的工作经验和简历上的不一致 |
我会直接怀疑简历是编的，我会让候选人解释，即使是说简历写错了，我也会问比较深入的问题来核实他的技能和能力。 |
| 简历上的技能描述和回答出来的明显不一致，比如明明是只会简单的Linux，但吹得天花乱坠 |
我会通过一些比较深的问题核实其他技能，找出其他方面吹嘘的水分。 所以建议，你可以适当夸张，但别过分，比如你在项目里没搭建框架但平时学习时搭建过，你可以写“XX项目的框架是你搭建的”，但你不能说你是一个架构师，非常了解项目的底层。 |
| 让面试官感觉你不稳定，很浮躁，比如说话不庄重，或者面试时打扮非常不正规，就穿背心来。 |
即使你技术再好，这个会可能导致你直接出局。 我对油嘴滑舌的候选人一般会直接写上不好的评语，这样很难过后面项目经理的面试。 我还遇到一个人，简历上工作是半年一换，我问他为什么经常换，他直接说是待遇问题，这个人我是直接Fail掉。 |
| 明说不能加班，不能出差 |
其实虽然有这一问，但公司里未必真的会加班会出差。但 听到这类回答，说明这个人不能承受大压力的工作，或者责任心不强，大多数公司是不会要这种人的。 |
6 引导篇：准备些加分点，在介绍时有意提到，但别说全
在做项目介绍的时候，你可以穿插说出一些你的亮点，但请记得，不论在介绍项目还是在回答问题，你当前的职责不是说明亮点而是介绍项目，一旦你详细说，可能会让面试官感觉你跑题了。
所以这时你可以一笔带过，比如你可以说，“我们的项目对数据要求比较大，忙的时候平均每小时要处理几十万条数据”，这样就可以把面试官引入“大数据”的方向。
你在面试前可以根据职位的需求，准备好这种“一笔带过”的话。比如这个职位的需求点是Spring MVC框架，大数据高并发，要有数据库调优经验，那么介绍以往项目时，你就最好突出这些方面你的实际技能。
再给大家举个例子，比如Java虚拟机内存管理和数据库优化是绝大多数项目都要遇到的两大问题，大家都可以在叙述项目经验时说，在这个项目里，我们需要考虑内存因素，因为我们的代码只允许在2G内存环境中运行，而且对数据库性能要求比较高，所以我们经常要监控优化内存和数据库里的SQL语句。这样当面试官深入提问时，就能抛出自己准备好的虚拟机内存优化和数据库优化方面的说辞。
实在不行，你也可以说“我除了做开发，也做了了解需求，测试和部署的工作，因为这个项目人手比较少，压力比较大”，这样你也能展示你有过独挡一面的经历。
我在面试过程中，一旦听到有亮点，就会等到他说好当前问题后，顺口去问，一般技术面试最多办半小时，你把时间用在回答准备好的问题点上的时候，被问其他问题的时间就会少了。
7 你可以引导，但不能自说自话
我面试的时候，也会遇到些有准备的人，其实如果你真的想应聘的话，一定要事先准备，这点我能理解，甚至赞同，你只要别露出太明显的痕迹，我不会写上“似乎有准备，没法考察真实技能”这种话，更何况未必每个面试官都能感觉出你准备过。 但你不能凭着有准备而太强势，毕竟面试是面试官主导的。
我遇到个别面试的人，他们说话太多，一般会主动扩展，比如我问他数据库用什么，他不仅回答数据库是什么，自己做了什么，甚至顺便会把大数据处理技术都说出来。
其实过犹不及，我就会重点考察你说的每个细节，因为我怀疑你说的都是你从网上看的，而不是你项目中用到的，我甚至会直接威胁：“你先和我说实话这个技术你真在项目里用到，我后面会重点考察，一旦被认为你项目里没做，这个性质就是蒙混过关了”，往往这些人会主动坦白。
不过话说回来，他如果仅仅说，数据量比较大，但点到为止，不继续说后面的话，我就会深入去问，他自然有机会表达。同时请注意，一般在面试过程中，一旦你亮出加分点，但面试官没接嘴，这个加分点可能就不是项目必备的，也不是他所关注的，当前你就可以别再说了，或者等到你提问题的时候再说。
8 不是结尾的总结
到这里，我们已经给出了介绍项目的一些技巧。这些技巧都是从 Java Web轻量级开发面试教程和Java核心技术及面试指南里摘录的。
两句话，第一，面试前一定要准备，第二，本文给出是的方法，不是教条，大家可以按本文给出的方向结合自己的项目背景做准备，而不是死记硬背本文给出的一些说辞。
当大家介绍好项目背景后，面试才刚刚开始，哪怕你说得再好，哪怕你把问题引导到你准备的范围里，这也得应付Java Web（比如Spring MVC,ORM等）、Java Core（多线程、集合、JDBC等）和数据库等方面的问题。
那么本文的价值体现在哪呢？如果引导不好，你根本没机会展示自己的能力。这就是本文给出的方法价值所在。说句自夸的话，本文给出的一些方法和说辞不是拍脑袋想出来的，而是从面试上百个候选人的经历中抽取出来的，其中有不少血泪，也有不少人成功的途径，这篇文章多少对大家（尤其是经验不满3年的初级程序员）有帮助，这也是本文申请放入首页的理由。
这不是结尾，我们还将在合适的时候写一些关于“如何应对常见问题”或“如何快速提升自己能力”等方面的博文。
请大家关注我的公众号：一起进步，一起挣钱，在本公众号里，会有更多精彩文章。
