1. Introduction to Project
- Introduce the big picture of the project, such as what the project is, what the motive is, and what the function is.
- Then introduce the specific application to the technology, the language, development environment, system architecture, system design.
- Using some specific use cases to describe the project in detail is like doing a verbal demo.
- Finally, say something about the future of the project. (optional)
2. Resume Tips
- The project experience is the most important, can include the course big homework. Write less irrelevant personal information to provide space for these
- Project experience to quantify, not to say how many lines of code, but to quantify your personal contribution to the performance improvement .
- Research projects to be as popular as possible, highlighting skills and knowledge related to positions
- Make a page as full as possible, rather than sparse, (if the project experience writes more This should be the case)
- If it is course project it is not necessary to mark course project at all.
- No matter how frustrated course project is, it can be written in a world of surprises and ghosts. I helped a friend write a 1000-line course Project 4, 5 bullet point, each bullet point has a number of very popular words, and no false, this is called embellish. The difference between an embellish resume and a embellish CV is not a bit.
- Project column 3 to 4 is all right, and then you can write the time long. Project is less than a bullet point sucks.
- Bullet Point is very fastidious, divided into three paragraphs, the first paragraph of the beginning of the verb to write what you completed, the second paragraph writing effect, the 3rd paragraph writing technology.
Implemented a XXXX module to YYYYYY by ZZZ technology. The data can be added to the high-level write, can not add data to find ways to add (within the possible range)
- If you are a former group of classmates other people solve the problem, if you are familiar with the words to write your own bullet point.
- All bullet point and project to be able to justify, this practice a little more, even if it is not the case, you can not be shot dead in the interview that is the case, practice makes perfect.
- Note that it is not too exaggerated that the technology in the resume, including your list of skill and you wrote in Bullet point, this must be
- Say that now it company's interview tendency, very obvious is heavy technical question, light experience. So there's no shortcut to technical questions. But the resume can be polished on the polishing, his role is to the HR see.
- Be prepared for a question: what is the most difficult bug you solve, how to find it, and how to solve it.
- CV on the project is like this, such as you said with the XXX technology made yyy, he generally will not be careful to investigate yyy details because he is not familiar with, but he will ask the details of XXX technology, so you can ....
Some things about RESUME
