It takes about 5 minutes to read this article.
Author: Huang oblique
As a programmer, you must have done some projects before, and maybe there are still some projects on hand.
However, there are still a lot of student friends who ask me "what to do if there is no project". Of course, there are indeed many students who have no internship experience and no decent project experience. For such students, the project experience on the resume can only be empty. Yet.
In fact, even if you are following some courses to do the project, you can also turn the project into your own by enriching the content of the project. As long as you really do it, you really understand the logic of the code and gain something. This project It is valuable, and it is possible to board the elegant hall of the resume.
Because of this, the quality of the project experience on many resumes is uneven, and some project experiences are very similar. The interviewer can know at a glance whether your project is true or not.
Most interviewers will ask questions about your project experience. Can you describe your project experience clearly and in place and determine the value of your project? Even if the project is not good enough, you ca n’t explain it clearly. no good.
Therefore, there are skills to follow when answering questions about the project. More important than the skills are the 3 principles. This is what I have summarized after various interviews.
1. Authenticity
Project experience, it ’s really true, do n’t think about resume falsification, the interviewer asks you a little deeper about what ’s on your resume, and you ’ll be ashamed. Those tall skills on your resume will eventually become your interviewer Grasp the handle.
What is true, first of all, you have really done these projects, and secondly, the description of the project should be true, which can be modified appropriately, but not too exaggerated.
The project is real, and you will have a bottom in your heart. Only if the interviewer asks a question can you be sure to answer it. If you really lie to the interviewer, then you can't blame yourself. If your resume is found to be fraudulent in the future, the penalty will be very serious.
2. What you write must be relevant to you
Many friends have made a mistake, including me, that is, they like to write about the experience of the project, such as writing the entire system development work on the resume, moving the department's technology stack to the resume, and putting those that you did not participate The work is written on the resume.
In fact, this just looks beautiful. When the interviewer asks you about a less familiar module, you can only say that this is not what you did, and that is not what you did. This is very embarrassing. Points are also greatly deducted.
After having suffered such losses several times, the project experience on my resume no longer showed anything unrelated to me. The interviewer asked about the implementation details and I was able to cope with it. After all, I had done it myself, and my heart must be clear.
So, instead of expecting to use someone else ’s module to fish in muddy water, it ’s better to think about how to refine your project content. Even if it ’s really just a simple CRUD, it does n’t matter. The so-called “bright spot search”, you should think about this time Way to find the highlights in the project.
For example, which ORM framework do you use to implement database interaction, why use Mybatis instead of Hibernate, or which web framework, logging system, and build tool do you use, or what database and cache do you use, and why use these technologies.
In addition, you can also introduce how to optimize the performance of the module, and how to implement complex business logic.
[External chain image transfer failed. The source site may have an anti-theft chain mechanism. It is recommended to save the image and upload it directly (img-GdANiGoo-1573478994023) (http://picturecdn.ejianmedia.com/bfad6f438119499ca8ccc7faff3c068e.jpg "bfad6f438119499ca8ccc7faff3c068e.jpg" ]
3. Point-by-point narrative, clearly organized
This is more a skill than a principle. Translating "point-point narrative" into vernacular text is "a module is introduced in one paragraph. If you make 3 modules, then divide them into 1, 2, and 3 points and introduce the content in one sentence."
To add here, you can mention the technology stack in the sub-point description, or introduce the relevant technology stack in the project summary section.
For example: 1. I am responsible for the development of the department ’s data operation report module. I use JUC concurrency tools, thread pools and other technologies to complete the business logic development of the module, and use the MySQL database and Hibernate framework to complete the data layer processing. The business code has been optimized to improve the response speed of the data report by 30%.
Why point out the narrative is actually to make your project more organized. The interviewer can easily see which modules you have done and can ask questions accordingly.
Before, I did n’t describe the project by points. As a result, the interviewer could only extract some keywords from a large paragraph to ask questions, which might make the interviewer very dissatisfied.
Not only the modules in the project experience need to be described in points, but you should also complete this way when introducing your own projects. The benefits are obvious.
You will soon be able to introduce your project to each interviewer clearly and clearly, and for each module, you can naturally state their difficulties, highlights, and implementation process.
Do n’t ask me why I know that when I get more interviews, I ’m used to introducing projects and answering project questions. So every time I encounter a question about the project, I basically come to open my mouth. As soon as the interviewer asks, I know what I have to answer.
Although the above three principles cannot cure all diseases, it should be quite beneficial to many students.
WeChat public account
Personal public number: programmer Huang Xiaoxie
Huang is a small ramp 985 master's, Alibaba Java engineers with extensive experience and insights in terms of self-programming, job search techniques, learning Java, hoping to help more programmers want to engage in the Internet industry. JAVA authors focus on the back-end technology stack, keen to share programmers dry, learning experience, job experience, and related dry self-programming and Java technology stack. Huang is a little oblique slash youth, adhere to the study and writing, believe in the power of lifelong learning, hope and more programmers make friends, progress and grow together!
Original e-book:
follow the WeChat public account [programmer Huang Xiaoxie] and reply [original e-book] to receive my original e-book "Cookie Programmer's Training Manual: From Technical Xiaobai to Alibaba Java Engineer" The book summarizes my 2 years of Java learning path, including learning methods, technical summary, job search experience and interview skills, etc., has helped many programmers get their favorite offer!
Programmer's 3T technology learning resources: some programmers' resource packages for learning technology. After paying attention to the public account , the background reply keyword "information" can be obtained free of charge, including Java, python, C, big data, machine learning, front end , Mobile terminal and other technical information.
Technology public number: Java technology rivers and lakes
If you want to follow my updated articles and shared dry goods in real time, you can follow my WeChat public account [Java Technology Rivers and Lakes]
This is a technical station for an Ali Java engineer. Author Huang Xiaoxie, focusing on Java-related technologies: SSM, SpringBoot, MySQL, distributed, middleware, cluster, Linux, network, multi-thread, occasionally talk about Docker, ELK, and also share technical dry goods and learning experience, dedicated to Java Full stack development!
Essential learning resources for Java engineers:
follow the public account and reply to "Java" to receive free learning materials such as Java basics, advanced, projects and architects, and more popular technology learning videos such as databases, distributed, microservices, etc. , Taking into account the principles and practice, in addition will also give the author's original Java learning guide, Java programmer interview guide and other dry goods resources
