1, to ensure authenticity. The project experience is real and precious. Don't really think about a fake resume. The interviewer will ask the things on your resume a little deeper to ensure that you will look stupid, and those tall technologies on your resume will eventually become the handle for you to be caught by the interviewer.

What you write must be related to you. Many friends, including me, have made a mistake, that is, they like to write about the project experience, such as writing the development work of the whole system on their resumes, moving technology stack from the department to their resumes, and writing all the work they didn't participate in on their resumes. Actually, it just looks beautiful When the interviewer asks you a module you are not familiar with, you can only say that you haven't done this, you haven't done it. This is embarrassing, and it must be a big deduction for the interviewer.

3, narrative points, coherent. This is not so much a principle as a skill. Translating "point-by-point narration" into vernacular means "introducing a module in a paragraph". If you have made three modules, you can divide them into 1, 2 and 3 points and introduce the content in one sentence respectively. "