One, foreword

“Why do resumes go unanswered? !” Regardless of your skill level, if you have this kind of problem then this article is for you.

Many people blame bad skills, previous company background, education, etc., but few people pay attention to the possibility that there is something wrong with a resume. When it comes to a resume, most people will probably download a template from the Internet and fill it out in less than an hour.

In my five years in the business, I’ve met a variety of developers and read countless resumes, giving me some insights and feelings about front-end interviewing. Therefore, I plan to do a series of columns about how to interview recently. My writing is not good, so it is only for reference! Welcome to add the author’s wechat: Iderxu, talk about life and ideal together.

In this paper, the target

I hope you can learn from reading this article:

  • Small goal: Learn about hidden resume skills
  • 【 Ultimate goal 】 Learn how to design a high-quality resume

Second, the conclusion

A good resume increases the chance of being invited for an interview

2. A bad resume can happen during an interviewWith partialThe interviewer

If you are invited for an interview, the interviewer will compare your resume to your resume in the Face to Face process, and even if you make an offer, you will end up with a much lower salary.

3. Never use a resume template

Resume styles vary greatly from industry to industry. Generic templates are intended for beginners and people who don’t know how to write a resume, so they can’t be used directly.

The role of the resume

1. Decide whether to invite you for an interview

2. Look for material to talk about during the interview

Key “first screen” design

Here emphasis is [design] two words, the design here is not to refer to the resume typesetting should be good-looking interface design, but refers to the content of the resume design, this is the core and focus!

The first page of your resume is critical, just like the first screen of your App. Do your best to show what the interviewer wants to see, and don’t expect the interviewer to skim your resume.

Developers are not designers, so there is no need to pay special attention to proportion, padding, aesthetics, etc. Focus on content, material/goods is the absolute truth.

To reiterate: The core and focus of your resume isContent of the design

5. Common cases

First, post a resume with 3 years of development experience recently received (sensitive information in the resume has been processed by coding, has been approved by the author, please do not reprint!).

Next, let’s take you to understand the composition and order of the resume.

Ps: “from general to overall analysis” is used here to explain the common problems in the resume, so this paper does not include more cases, just as the explanation.

Six, resume composition and sequencing

For mid – to high-level front-end interviews, both HR and technical interviewers will unconsciously look for some Key Information in the resume. In order of weight, it can be:

A:

  1. Working fixed number of year
  2. Technology stack
  3. Flash point (ignored by many people, no item)
  4. History project
  5. The basic information

B:

  1. The basic information
  2. Working fixed number of year
  3. Technology stack
  4. sparkle
  5. History project

Ps: [Basic information] includes: name/age/educational experience/gender/unmarried and married (whether pregnancy is possible), etc

C: Other sorts

Why and what’s the use of sorting your resume? What is the basis for sorting?

Years of working:

The preliminary judgment is whether it is an “old bird”, whether it can match the current pit, for example: 1 year may be primary, 3 years may be senior, etc., this is only an estimate.

Technology stack:

According to the working years, you can judge whether you are a positive and enterprising “good social youth” who loves learning and suffering, and whether you have a certain breadth of skills.

Some people may say that technical depth is good, but I would like to say that as a developer, the advice is inAt the beginning“To expand their technical breadth, and then to expand their depth. Having depth without breadth is problematic for the average person, and vice versa is not a contradiction. Just like the education before university is horizontal, I choose a major to study in university, so that I can adapt to the society with my advantages and expertise, create value for the society and survive.

Sparkle:

Will you be good at “selling” yourself, highlighting the interviewer’s impression and standing out from the rest of the resume? From deep to actually, you can see from this point is the person has a certain comprehensive ability, of course, this is pluses, a lot of people didn’t write, in fact, everyone has, if not then may need to adjust the direction of career planning, or all, are “mass production”, the enterprise who are all the same, there is no advantage.

Examples: management experience, writing/working on an open source project, etc

If you are a recent graduate, you can write about the competitions you participated in and the awards you won, preferably related to the interview, such as ACM, hackathon, etc. What monitor/dormitory administrator/instructor small assistant do not write. If it is a few years of graduation to write what technology to the former company to create much value, do not write to call wechat API to complete the payment function so low point. Good example: 1

History project

From the history, we can know the candidate’s past practical experience, depth of application of technology stack, and recent projects. Can you give the interviewer some information that he can communicate during the face to face interview?

This is very important and will likely influence the direction of your communication with the interviewer. Resumes are typically viewed from the top down, in person, and will learn more about you from your recent projects.

Of course, people may say that the technical interviewers I met are all looking at technical knowledge points. In my opinion, as an interviewer, if you can’t find something to ask about in your resume, the interviewer will follow his own routine to “question” the points he is interested in one by one, and then expand to examine you.

But if I have your resume, I still like to find something I can talk about with you through your resume.

Cautionary tale

1.

Encountering the above resume will make the interviewer can’t cut in, can’t ask! Follow the interviewer’s interview process without looking at your resume, and you won’t get to know your strengths. It’s likely to be awkward and confusing, as the interviewer takes you into familiar territory, but an intellectual blind spot for you.

For example, Xiao Wang recently did a project related to using Node, but it was only a simple use, and he did not have a thorough understanding of the theoretical knowledge of Node. If it was put in the first part of the project introduction, then the interviewer will naturally ask you about this knowledge point. For example, he will ask you to introduce the project, then ask you what you did, what problems you encountered and how you solved them. Then give you a scenario, ask you what you would do, and you’re done.

Positive materials:

First of all, you can be ready or your well organized 8 ~ 10 optimized content, can request from the network resource loading strength cache (HTTP), technology stack optimization means, webpack packing optimization method, and so on, and even behind can be described by use of the technology stack source implementation, etc., so you can actually tell at least half an hour or more.

Now that you’ve shown the breadth and depth of your knowledge from an optimization project, you’ll be more comfortable talking about it, so be good at guiding the interviewer to examine the questions you’ve given yourself.

What it all boils down to is that you have the opportunity to present yourself to the interviewer, and you have something to talk about, something to talk about, and something that is familiar to you. It saves you time and the interviewer’s time by not having to think too hard about what you have to dig up.

To reiterate: “guide” the interviewer to examine the questions you’ve given yourself!!

7. Case analysis

With that said, let’s take a look at this resume I recently received by comparing it to the content and order listed above:

The main problems are as follows:

Critical information is not readily available (missing/scattered)

  • [Missing] Years of work
  • [Missing] jobs
  • 【 missing 】 the shining point
  • [Scattered] Technology stack (no “really familiar” technology stack can be found on the home page)

Too much useless information

  • [Skills and Expertise] This whole introduction can be removed, unnecessary and useless information to the interviewer

Random text description

  • The terms proficient, understanding, etc. in [Skills and Expertise] are very negative and do not properly convey the use and knowledge of these technology stacks

Eight, talk about the interviewer’s psychology

The cognitive model

“Do not let me think!” Don’t make the interviewer think, just give him as much information as he needs. The interviewer needs to get as much information as possible about the candidate from one piece of paper in the shortest amount of time. Visual Cognition is used in academic terms:

Visual cognitive theory emphasizes the value of concrete experience in promoting individual development, and places great emphasis on the careful layout of learning content in order to make it meaningful, easy to understand, easy to remember, and more attractive, and can arouse people’s attention to information design problems.

Ultimately, a resume is about the design of information. People have vision and construct their perceived candidates based on several key pieces of information. (The interviewer) will make a preliminary judgment about the candidate based on his/her previous life/work experience and then decide whether to call him/her in for a Face to Face interview.

Nine. Precautions for common problems

  • Github doesn’t have any projects to go on
  • Don’t highlight schools that aren’t 211/985 or awesome
  • “Cet-4” is not recommended to put on the home page, interviewers are not likely to care, unless it is a level 6 + can be put
  • “Putonghua certificate/computer certificate/Office software certificate/accounting certificate” do not put
  • “Political status” of party members need not be written below
  • “Work experience“Don’t put such a prominent position, but highlights the candidate’s frequent job-hopping, seriously exposed their own shortcomings!
  • [Salary expectation] Not recommended
  • After 9012 years, jQuery is not recommended
  • Don’t write advice from a training class
  • [Resume format] Use a PDF, less than 1 MB
  • [Resume name] Do not use “front-end development” and other names, to indicate their name, years of work, position, such as “Zhang SAN -3 years – front-end development”
  • [Layout color] no more than 3

Here I believe you have at least a little bit of ideas and direction, so how to write, please look forward to the next column. Found that there is a public account in the case of unauthorized reprint without my consent, in this warning do not arbitrarily reprint, reprint by my consent.