[Programmer resume should be written like this](# programmer resume should be written like this)
- [Why is a resume important? ](# Why resume is important)
  - [Before interviewing](#Before interviewing)
  - [Speaking from interview](#Speaking from interview)
- [The following points you must know](#The following points you must know)
- [Two Laws You Must Know](#Two Laws You Must Know)
  - [STAR Law (Situation Task Action Result)](#star 法 situation-task-action-result)
  - [FAB Rule (Feature Advantage Benefit)](# fab- 法法 feature-advantage-benefit)
- [How to write the project experience? ](# How to write the project experience)
- [How to write professional skills? ](# How to write professional skills)
- [Typographical Precautions](# Typographical Precautions)
- [Other small tips](# Other small tips)
- [Recommended Tools / Site](#Recommended Tools Website)

<!-/ TOC->

Programmer resume should be written like this

In addition to teaching you how to use Markdown to write a programmer-specific resume, this article will also recommend some good software or websites for writing Markdown resumes, and how to elegantly convert Markdown to PDF or other format.

It is recommended that you use Markdown syntax to write your resume, and then convert the Markdown format to PDF format for resume delivery.

If you don’t know much about Markdown syntax, you can take a brief look at Markdown syntax description for half an hour: http://www.markdown.cn.

Why is a resume important?

A good resume can play a very good role in the entire application interview and the interview process. Without exaggerating your abilities, writing a good resume is also a great ability. Why is a resume important?

Let’s start before the interview

If you are applying online, your resume will inevitably be screened by HR. It may take 10 seconds for a resume to look at HR. Then HR will decide whether your level is Fail or Pass.
If you are pushing in, if your resume doesn’t have any advantages, even the person pushing you in will not help you.

In addition, even if you pass the screening, in the subsequent interviews, the interviewer will use your resume to determine whether it is worth his time to interview.

Therefore, the resume is like a facade of us, it largely determines whether you can enter the next round of interviews.

From the interview

I find that everyone prefers to read the Noodle Scripture, which is understandable, but most of them don’t tell you that many questions are asked under certain conditions. To give a simple example: Generally, your resume will be asked about what you know (Java, data structure, network, and algorithm are the basic questions for everyone). For example, if you write, you will redis, Then the interviewer will most likely ask you some questions about redis. For example: common data types and application scenarios of redis, why is redis so fast in a single thread, the difference between redis and memcached, the redis memory elimination mechanism, and so on.

So, first of all, you need to be clear: Do not write on your resume if you do not know. In addition, ** you need to consider how you can make your highlights stand out in your resume **, for example: what you did in a certain project solves what problem (as long as there is a project, there must be problems to be solved) What technology has been used in your project to improve the overall performance and concurrency?

Interviews and work are two different things. Smart people lead interviewers to their areas of expertise, while others are led by the interviewers. Although interviews and jobs are two different things, if you want to get a satisfactory offer, you must be strong.

You must know the following points

The HR of most companies say that we do not value education (deceive you!), But if your school is not outstanding, it is difficult to stand out in a bunch of resumes, unless your resume has special highlights, such as : Internship experience at a certain large factory, won the award of a certain competition, etc.
Most fresh graduates have no work experience or internship to find a job. So if you are a fresh graduate, don’t miss the autumn and spring strokes. If you miss it, you will most likely face social recruitment later. At this time, you may face various obstacles because you have no work experience, and you will not find a good job
Be careful about what you write on your resume. This is where the interviewer asks a lot of questions;
It is very important to show your project experience perfectly.

Two rules you must understand

STAR LAW (Situation Task Action Result)

Situation: under what circumstances did things happen;
Task :: how do you define your task;
Action: For this kind of situation analysis, what action method did you use;
Result: What was the result, what did you learn in this situation?

In short, the STAR law is a way to tell your own story, or a clear and organized composition template. Whatever it is, using this rule reasonably and proficiently can easily explain the logical way in which the interviewer describes things, showing the clarity, orderliness, and logic of his own analysis and elaboration.

FAB Rule (Feature Advantage Benefit)

Feature: What is;
Advantage: Where is better than others;
Benefit: What benefits will recruiters get if they hire you.

In simple terms, this rule is mainly to let your interviewer know your advantages and how it will help the company after recruiting you.

How to write project experience?

It is normal to have one or two project experiences on the resume, but very few can really show the project experience to the interviewer. For the project experience, you can consider writing from the following points:

A feeling for the overall design of the project
What did you do, what did you do, what role did you play in this project
From this project you learned those things, used those technologies, and learned the use of new technologies.
In addition, in the description of the project, it is best to reflect your overall quality, such as how do you coordinate the project team members’ collaborative development or how do you solve it when you encounter a difficult problem? What technology is used to achieve what functions, such as: using redis as a cache to improve access speed and concurrency, using message queues to reduce peaks and drops, and so on.

How to write professional skills?

Ask yourself what you would like, and then see what your intended company needs. Generally HR may not know technology very well, so he may look at the keywords of your professional skills when screening resumes. For the skills that the company requires but you don’t, you can spend a few days learning it, and then write on the resume to understand this skill. For example, you can write it like this (excerpt from my resume below, everyone can make some modifications and improvements according to your own situation):

Computer network, data structure, algorithm, operating system and other basic knowledge: master
Java Basics: Mastering
JVM virtual machine (Java memory area, virtual machine garbage algorithm, virtual garbage collector, JVM memory management): master
High-concurrency, high-availability, high-performance system development: master
Struts2, Spring, Hibernate, Ajax, Mybatis, JQuery: Master
SSH integration, SSM integration, SOA architecture: Master
Dubbo: Master
Zookeeper: Master
Common Message Queue: Master
Linux: Master
Common MySQL optimization methods: Master
Spring Boot + Spring Cloud + Docker: Learn
HDFS, Storm, MapReduce, Hive, Hbase in Hadoop ecology related technologies: understand
Python basics, some common third-party libraries such as OpenCV, wxpy, wordcloud, matplotlib: familiar

typographical considerations

Be as concise as possible and not be too frivolous;
Don’t mistake the capitalization of some technical terms. For example, don’t write MySQL as mysql and Java as java. This is still quite taboo in my opinion, so be sure to pay attention to this detail;
Adding spaces between Chinese and digital English looks a little more comfortable;

Other small tips

Avoid subjective expressions as much as possible. A few semantically ambiguous adjectives should be concise and clear, and the logical structure should be clear.
If you have a blog or personal technology stack, writing it will give you a lot of points.
If your Github is more active, it will add a lot of points for you.
Pay attention to the authenticity of your resume. Do n’t write things you do n’t know or deceptive content.
The project experience is recommended to be sorted in reverse chronological order. In addition, the project experience is not so much but highlights.
If there is too much content, you don’t need to compress the content to one page, and keep the layout clean and tidy.
At the end of the resume, it is best to add: “Thank you for taking the time to read my resume, and look forward to having the opportunity to work with you.”

Recommended tools / sites

-Cool resume (MarkDown online resume tool, online preview, edit and generate PDF): https://johnwhite-leaf.github.io/coolresume
-Java programmer resume template