From software engineers to headhunting: How to Write your resume

As an IT headhunting specialist, I have seen countless resumes. I have seen a great deal of excitement. Some of them look big, some are vomiting blood, and some directly cause people to crash ....
Some are a large descriptive text written in your resume, so that HR or headhunters can get such a resume. How can you read the scenery in your mood?
How to get to know you? Even if you are a sweaty BMW, even the best bole may not be able to see your galloping posture.
　　
Some of them are simple and have no focus or hierarchy. Unless you have a very good background Company, it will stimulate the interviewer's nerves. Otherwise, even if you invest in the past, it must be a sea.
　　
There is another way: I have not written much about my own experience, but I have written too much nonsense to express my revenge for the company's position. These are useless. My resume is actually a very rational thing,
It is of little use to add more and more emotional details. If you have to write, simply sum up one or two sentences and put them at the end. For senior positions, you can also write a short section of cover lever to the end. However, this is not necessary for technical positions.
　　
What kind of resume is most attractive to others: In simple terms, it is clean, highlighted, organized, and hierarchical. let headhunting, HR, and hiring managers get this resume first, so they have the urge to read it. Instead of leaving it aside, it is regarded as waste paper.
　　
The following sections are easy to see:
　　
1. Personal information, which is nothing to say, including name, birthday, location, email, and phone number. In addition, the current salary and expected salary can be included or not included,
Generally, you do not need to write it if the company you want to apply for is not required.
If you want to apply for a company, and you think you can discuss the salary, you can write (you can discuss) negotiable.
Most of the photos do not need to be attached unless any assistant to the general manager .....
There is also no need to write the ID card number to avoid being used by others.
　　
2. The resume must have a qualification summary, which is the most visible part for recruiters, usually behind the personal information.
The main words are as follows:
　　
5 years experience in...
Versed in...
Master...
Familiar...
....
Solid/strong/Good/deep experience/understanding in ......
Excellent/Good interpersonal and communication skills, good team spirit... this can describe your potential
Fluent/proficent/Good/average written English and oral English ....../English description .....
　　
3. this is the most important part of my work experience. Here I mainly talk about responsiblity. Writing duties is the easiest mistake for everyone. Some people like to write a lot of text, like a small English essay with four or six levels, the logic is unclear, which is the most taboo. Some sentences are not parallel. When writing duties, it is best to start with a verb or an adjective. Even if you can use all cells or past tense, each item must be in parallel.
BTW: I have studied English in college.
Generally, the subject should be removed from each item. I made the project schedule... directly remove the subject and use the parallel format of the dynamic object!
For example
Responsibilities:
? * Make project schedule and arrange manpower.
? * Discuss SRS with system engineer ....
? * Trace progress of projects.
? * Write framework code ....
For candidates who participate in or lead a specific project, the general responsibilities should first write a summary responsibility,
Then, when separately introducing specific projects, you should write the responsibility in the project. For senior personnel, they are no longer responsible for a specific project. You can save the project part, enrich and enrich the description of summary responsibility.
　　
Example:
　　
Hua Xing communication company CO., 2003.6-now
Position: Project Manager (2005.08-now)
Responsibilities: (general responsibilities)
? * Schedule the project and prepare the project plan
? * Discuss project requirements with System Engineers
? * Tracking Project Progress
? * Write some main code
Project 1: XXX
Project Description: (brief description of the project)
Software environment: (for technical positions)
Hardware environment: (for technical positions)
Responsibilities: (mainly for project responsibilities)
? * Communicate with foreign engineers on project cooperation
? * Tracking Project Progress
? * Scenario responsible for writing protocol forwarding
? * Instruct New engineers to learn the Protocol
　　
Hua Xing Co., 2007.8-now
Main role: Project Leader (08/2005-now)
Responsibilities :( summary responsiblity as the role)
? * Make project schedule and assign Development Engineer.
? * Discuss the SRS with system engineer ....
? * Trace progress of projects.
? * Write a part of codes
Project1: ×××××
Description :( Summary of the project)
Software environment: (for technical engineer)
Hardware environment: (for technical engineer)
Responsibilities:
? * Communicate with foreign Engineer
? * Make the project schedule.
? * Write the scenario of ARP module.
? * Deliver the release version on time .......
? * Make training for new engineer...
　　
Of course, writing a resume is not that rigid, but there is no need for anything too fancy.
The focus is to grasp those keywords: clean, highlighted, well-organized, and well-defined.