2. Your position in the project team, and whether you can solve the problem independently; 3. Your business knowledge and teamwork ability. Technology is obviously the most important, but you need to describe the technical framework of the whole project very carefully, let the recruiter know that you are familiar with the macro framework, and then highlight the technical problems you solve. Let's refer to a project description: "This project is developed by JSP+JavaBean+Struts and adopts MVC mode. The presentation layer is separated from the business layer, which is easy to maintain and expand." The following is the description of the project (virtual) I wrote: "This project is structurally divided into presentation layer, business layer and data access layer, and the dependencies between the layers are bottom-up. The technologies adopted include Struts, Spring, Hibernate, Log4J, JDom, etc. The presentation layer is developed with Struts framework. The business layer encapsulates the business process. In order to adapt to the change of business, each business module has a special interface and implementation class, which is injected into the action; By using the IoC function of Spring. The data access layer is realized by Hibernate, and the code is concise, which can adapt to different databases. The transaction part uses Spring's declarative transaction management. In order to improve the performance, the project "Servlet Filter is used to realize cache proxy" briefly outlines the system architecture, which also shows that you are very familiar with Struts, Spring and Hiberante technologies. At the same time, it can be noted that some important links are described very briefly, such as transactions and caching agents, which are actually intentional. During the interview, many people are afraid that the other party will suddenly ask a question for which they are unprepared, and often lack the ability to cope. On the one hand, you need to practice more, on the other hand, you need to know that you are not always passive in the interview, waiting for the other party to ask questions. If you just give the other person an ordinary resume, which only mentions JSP and Struts that everyone will mention, then you have to wait for the other person's random questions. However, if your project experience and description are the same as just now, the other party will probably ask you how to apply transactions in Spring and how to use caching agents (if the other party is a technician). At this time, you have changed from passive to active ... of course, the premise is that you must master these technical points and have thought about the expression in advance! This is just a little interview skill. In short, writing a description of the project experience in your resume is also a job search method.