Project introduction is an important part of the interview process. How do you focus on the core of the project and whether you actually did the project
01 preface
How do you introduce your project in the interview? You can think about the introduction of the project when the main points are stated, whether the interviewer’s most important questions answered? If what you say is all right, it’s not a problem. However, I found that many of my friends only mentioned a few words when answering the questions, such as this is a XXX project, I took the XXX position in it, and what technology stack I used. There is nothing wrong with what you say, but I think you can go a little further and show the interviewer that you are really involved in the project and that you are familiar with it.
So how do we make it look like you’ve actually done a project? In fact, everything is a step in the inside, there is a process in the inside. You’ve also heard that it takes skill to memorize answers for an interview. To get a complete overview of your project, start with the following points.
02 Project Introduction Procedure
People may think that it is good to just say something casually, but what you ignore is the process of expression. How you answer represents your thinking logic. There is no problem with logic, which is methodical and based, so there is no problem with your project introduction. But if you are vague and inaccurate, then people have absolute reason to suspect that you are not a fake project.
In fact, this is also the same as human speaking, logic is a sign of your thought process, the most straightforward point is that you will write fewer errors. To be logical, we can start from the following aspects:
Introduction to the background
The context of the project is a key factor, because it’s where the project starts and it’s where you do the project. You can talk about what the initial needs were, what pain points you solved through the project, what scenarios you met, etc. In fact, many people may ignore this point, do not say the background of the project, leading to the beginning of the technical points, how to achieve, and so on, resulting in the interviewer is not clear about your project, it is difficult to ask questions.
Bear the role
Describe your role in the project, which part of the module development you undertook, and how you dealt with the technical difficulties in connecting with the rest of the project. You can say that you are responsible for the login module or the XXX management module development. One thing to note here is that you must define your role accurately and do not exaggerate your role. If you mean that you are in charge of the project, then you should master the technical architecture, technical system and technical selection of the project. You also know how to design projects as a whole, and you must know how to assign tasks, arrange people, and communicate things that are not technical. You know how to mediate conflicts between project people. These are your technical level and technical vision of the most direct embodiment.
So we don’t mean to make your position as high and important as possible. You can clarify the technical points of a module, and then expand on the core content if there are similar projects that use this point, why it is used by many people, what are the key technical points, etc. Saying your understanding of the technical point is also a bonus. We can beautify ourselves on the premise of your control, but it should not be beyond your control, or you will not be able to answer when the interviewer asks you questions, only the situation of minus marks.
Project results
Through this project, what kind of effect you have made, whether it meets your expected direction, how long the real cycle of the project, how difficult the project, etc. You can also talk about what the data was like after the launch, what problems you found on the way and how you solved the problems, whether there was a slow network loading, and what project optimization you did. These are the kinds of questions that interviewers often ask, and they tend to be a little bit more divergent, so they can tell you how good you really are, whether you’ve actually worked on projects.
In fact, many people have not tried server deployment, think this is not the front end should do things. I think this is one of the development of the front-end skill points instead, through on-line process we can know what a real project long what kind, is how to get the request of the network, online and offline environment if there was any different, met you is how to locate and solve, these are the front the most frequently asked questions. Plus, if you can answer what server you are using, how the project is placed, whether you are using a reverse proxy, etc., you are a bonus. But the answer can not come out of the relationship, just that your technical vision is still to improve.
Project summary
This is actually a test of whether you really grow in the project, through the review and reproduction of the entire project to see how high you absorb the project. Many students will put the project aside after it is finished and write it directly on the resume without any summary. However, when I ask you, I can’t remember the technical difficulties and specific implementation details, so you are in fact the same as if you did not do this project.
What do you get out of the project? What skills did you learn? What are the shortcomings? How about improvement methods? Whether these technical points can actually be transferred to other projects, etc. The summary of the project itself is to analyze existing problems and find future problems. If you encounter potholes, you will not step on them in the future. If you encounter potholes, it is easy to analyze and solve them in the future. This is the problem analysis ability, which is also summarized from the projects you have done.
Some people may say that my project is very smooth, I have never encountered a pit, and there are few problems. So do not rule out you are really skilled, but you should also think about you is simply to add and delete operations, you do the project is done many times before, if so you are actually doing a simple repetitive work, there is no help for their technology to promote, it is better to find some challenging projects, Even if the pit is a lot, you are sure to grow. Ten years of experience means you have a lot of project experience, have seen it in a variety of places, and are technically comfortable with it, not ten years of one year of experience.
Summary:
Basically you can answer the above steps, your project introduction is successful, others will really recognize your project, think you are really done rather than say it out of mouth, the answer itself has depth you are not simple. Next time we ask you about a project, you can explain your understanding according to the steps above, but the premise is that you must be prepared before the interview, think carefully about how you should answer these questions, so that you have a clear idea of the natural won’t panic.
The key points are the selection of technical solution, how to deal with data, project difficulties and so on. These are the things the interviewer most wants to hear. You can think about this aspect more when preparing.
03 summary
In my opinion, the introduction of projects can best reflect one’s technical level. Unlike some basic knowledge points, which have specific routines and answer modes, the knowledge points can be explained according to others’ answers, which is also relatively easy. But projects are different, everyone does different projects, and there’s no counterfeiting in there, unless you’re working on a project together. Ask for details in the project, and then ask for details about your foundation.
If you don’t have a decent project, don’t panic. You can think about whether you have been in contact with some large projects, and talk about the design structure of the project. So if you have time, you can visit Github or nuggets community, you will find a different world.
