1. When talking about the technology you have done, you should mention the programming language used, personal contribution and product details. Sometimes I see someone passing past experiences on their resumes. For example, in a group of three people, they wrote some functions for email software. This is far from enough. People who read your resume want to know the difficulty of your work and how much it has to do with our company. You'd better write it in detail. For example, the automatic backup of network email is written in C++ language. In a three-person team, they are responsible for designing and writing storage servers. From the beginning of the design, one year later, the number of users of this function was pushed to 3,000. 2. Tell more facts and use fewer adjectives. When reading a resume, the person reading it needs to make a judgment, so you need the facts and figures in it. If you write quickly and improve the efficiency of software operation, it is difficult for people who read your resume to judge the difficulty of your grades. But it would be much better if you write it in three weeks and improve the efficiency of the software by 40%. Some modest friends don't want to say everything, you can also use this method. If you say that you are excellent or are often asked to put out fires in the project, it will inevitably sound a little proud. But you can also illustrate your point with undeniable facts. For example, what does The New York Journal say about this product? Highlights? , or joined three project teams that have fallen behind schedule, but all of them were completed on time with team members through hard work. I have a friend who has worked in a famous hardware company in Silicon Valley for six years. Her IP phone earned hundreds of millions of dollars for the company and won many awards for corporate and business reports. I once saw a billboard of her products on the roadside while driving on the highway in San Francisco. Another time, I went to Shanghai for a holiday and found one next to the Shanghai Expressway! Soon, this friend decided to change her job and let me see her resume. I was surprised to find that she wrote 1998 lightly? 2004: Head of VoIP product hardware engineer and his responsibilities. What about the product award? What about the money it makes for the company? I asked. Should I write those, too She said. Of course you should write. Someone asked, can I write about the projects I do in my spare time? I think as long as your project has a representative performance statement, it should be included. 4. Give priority to deleting unimportant achievements in comparison, so as not to dilute more outstanding achievements. As a summer intern in a company, I improved the numerical classification algorithm of video games and reduced the memory requirement of 10%. I wrote 3000 lines of user interface programs in Java. * Do two hours of manual testing every week. When you apply for the position of software engineer, I think the first two points are more appropriate, and the third point is actually unnecessary. Sometimes when I see some resumes, I will mention that the task has been completed on time and the products meet the original plan specifications. But people who read resumes usually take it for granted, and what you say will weaken the effect of resumes. Writing a resume is not easy, but it will also bring a sense of accomplishment (and a good job! )。