Current location - Education and Training Encyclopedia - Resume - How do programmers write resumes? What is the resume of a good programmer?
How do programmers write resumes? What is the resume of a good programmer?
Part I: Basic information.

Must have: name, contact information (e-mail+phone number), date of birth (generally only year), position applied for, working years, address (if there is a city, the specific address can be written or not).

You can have: motto, social network address (don't put it anywhere), and expect treatment.

It's best not to have: photos (unless you are particularly confident about your appearance, but if you want to show them, enlarge them instead of artistic photos, thank you), constellation blood type (if you apply for this company, it's another matter).

Part II: Educational experience.

Must have: university name, major, start time, end time, GPA (or average grade).

There can be: high school experience (if your high school is famous, such as the high school attached to the National People's Congress), description and introduction of major or university (if it is not a well-known university, it is recommended to write it out), and short-term exchange at MIT and other distinctive training courses.

It's best not to have: the experience of kindergarten and remedial classes in junior high school and primary school, and the evaluation of your own school (don't write the statement that "I mainly rely on self-study because my teacher is not good").

Part III: Honor.

Must have: academic honors obtained during the university (as long as you have a title, you can also write a merit award), scholarships, and some social honors (such as being brave).

You can have: excellent honors in middle school (such as the first prize in the national mathematics competition), awards won in other institutions (such as outstanding students in a summer camp at MIT, or some awards from Intel).

It's best not to have: another bottle of Master Kong (I'm not kidding, I really see a lot of people writing on their resumes, which is not humorous at all), unimportant awards before college (first prize in the composition contest of the whole school in Grade Two), and some fictional awards.

Part IV: Work and internship experience.

Must have: name of work unit, position, description of specific work content (language, framework, development platform, where I saw it, if I can't see it, tell me what effect I achieved), work start time, end time, and all projects I have done, including open source projects.

You can: briefly explain how you feel about your job in one or two sentences, such as but don't make negative remarks.

It's best not to have: non-work-related work experience (about one-fifth of people have cleaning or cashier jobs in KFC or McDonald's on their resumes, so if you really don't, don't write it, even if you do).

//Let me give you an example here:

From June 2009 to September 2009, Beijing Umbrella Technology Co., Ltd. worked as an intern PHP programmer.

Responsible for the secondary development of the company's internal management system, and independently developed a new version of the internal communication system based on XMPP+PHP+MySQL. In addition to completing the new interface and architecture, it also optimizes the original underlying algorithm and improves the missing documents, which can be used normally in companies with10 million zombies.

What needs to be noted here is that don't jump to conclusions, all you need is to provide arguments.

Part V: Technology.

Required: language and platform. Pay special attention here. Don't just write "proficient". Every time I see someone write "Mastering C++", I ask him something about the Boost source code. If you don't answer confidently, don't say proficient. Here I make a general comparison:

Understand: I know what this thing is for, and I can also write something in order.

Familiarity: I have written more than 10000 lines of code, completed projects and read at least one of the most classic technical books.

Proficient: I have written120,000 lines of code, completed many projects, read the source code of some languages or standard libraries, can understand the underlying architecture of languages, and have the ability to speak languages to others.

In addition, this place is best to see your Github address or blog address.

Part VI: Others.

General ability: English (CET-6, TOEFL 100 ... this is a must), other languages. ...

Hobbies: go, marathon ... (only write positive, not stingy)

Specialties: piano master level, held art exhibitions, published books ... (or just write positive things, not quick tricks, sparks and the like)

Special background: He is the core leader in the blabla project. ...

Note: you don't have to write in the above order, but you should know in your mind whether what you write belongs to it. Finally, summarize with A4 size paper, no more than two pages.

In addition, the first priority principle of typesetting is neatness. Don't make it too fancy, with black words on a white background, and don't use fonts indiscriminately. Song's style is still bold and good. Pay attention to punctuation marks at all angles and half angles.

The text of your resume should be as serious as possible, and it doesn't hurt to be cute once in a while, but please don't keep such content. I once saw a boy's resume, and every sentence was followed by a face.