background

For my job, I’ve seen 100+ front-end resumes in recent months.

After reading it, I will reply to them with my review suggestions for their reference.

It’s been a patchwork of one-on-one responses, and it’s time to put together a list of common questions. On the one hand to share for everyone as a reference, after all, spring recruitment is flourishing. On the other side, I make my own summary and review.

The main questions

Use PDF files

A lot of resumes are in Word format. I use the browsing function of email to preview, sometimes the format is wrong. It is recommended to use the PDF format uniformly, in any case there will be no confusion.

Also, keep your resume short and concise, with black text on a white background. Use common tables, headings, lists, etc. for formatting, nothing too fancy.

There are too many resumes

Some resumes are four pages long and unnecessary. Under normal circumstances, fresh graduates 1-2 pages, 2-3 pages of the social recruitment, enough to present your advantages.

Some of you may wonder: I’ve done a lot of projects, and if I had to write on them, 3 pages would not have been enough. For this question, there will be an explanation later, that is, the project experience is not required to write a few representative.

The order of your resume

Hr resumes are like gaokao papers, with only a few seconds to read each resume. Be sure to present your resume in the usual order, otherwise it won’t be easy for the hr to read.

The usual order is: Personal information > educational experience > work experience > Professional skills > project experience. These are enough, nothing else is needed.

Some details of personal information

Awards, certificates, English, blogs or open source are also important.

Age, if very young, if work >= 5 years do not need to write. Your age can be inferred from your education and work experience.

Marital status is not required; it will be covered in the hr interview. But girls will be asked specifically and will be concerned about when you have a baby because maternity leave can take months.

Expect salary do not write, do not easily expose their cards. We’ll talk about salary later.

Finally, blogging/open source, if the content is good, write first, don’t write last – that’s a big competitive advantage! PS: The biggest advantages of resume: 1. School (especially fresh graduates); 2. Work experience in big factory; 3. Influence of open source projects, blogs and other communities (especially suitable for internal promotion)

Don’t write a self-introduction or self-evaluation

Many resumes end with a self-evaluation, an introduction, and a few words. Nothing more than “conscientious/enthusiastic/love to learn” — honestly, it doesn’t work. For example, if you don’t even write a blog and you say you “love learning/technology”, who would believe it?

Depending on the format of your resume, the good stuff is already spelled out, and the rest is just empty talk, which won’t just be written and will be examined in other ways.

Also, it’s no use writing about your interests. No one follows your interests. And if you have a driver’s license, it won’t help. It’s not hiring a driver.

So, you don’t have to write it. Nobody reads it.

Professional skills should be written well and coherently

Professional skills should be written clearly, and each item should only say one thing. For example, write a separate item for vUE, a separate item for React, and a separate item for engineering, Nodejs, and small programs.

Important skills such as Vue React webpack, etc., write some rich, some commonly used tools around the write. Hr does not know the technology, so you can write down all the commonly used technology, so hr can better match it.

Don’t write too much about the basics. For example, jQuery echarts bootstrap… These are not competitive. Combine the basic content into one: proficient in HTML, CSS, Javascript and common front-end tools. That will do.

Professional skills, to match project experience, otherwise not credible. For example, it would certainly seem strange to write “proficient in NodeJS” on your professional skills list, but then have no nodeJS projects in your project history.

Finally, proficiency (understanding, familiarity, proficiency, proficiency) must progress, not blind writing. Never write “proficient in XXX”. Our country is originally a culture of moderation, plus programmers is a very rigorous profession, do not write disorderly.

Stop writing “fake XXX” projects

Maybe you don’t have enough work experience right now, so you’ve taken a course or created a project that mimics it. But you should never write “copy XXX” projects in your project history. It’s easy, you change the name of the project slightly, and nothing else.

Because “imitation XXX” the name is very conspicuous, give a person’s first impression is: you are a rookie, but also need to imitate, no. That is, the first impression of the project is very important. So if you change the name of the project, it will be considered as a normal project, which will be relatively fair.

Mainly, it’s not cheating, and I’m totally against cheating on my resume. It’s a skill.

The correct format of the project experience

When describing a project, don’t lump everything together and write it in large chunks. Some even use little punctuation. Modern day staring at the computer mobile phone, the eyes have been very tired, and then see a large section of text he will be very repulsive. Me, too.

So, work around a little bit and break it down. This is rich without being messy. The contents of the project may include:

• Project introduction
• Technology stack
• The main work
• End product (or project output)

Project experience is not a running list

[Note] This is very, very important!

The essence of a resume is to communicate your technical skills and experience in simple words. And, want to use as little as possible cost, let choose and employ persons unit identify as soon as possible.

Instead of resumes, consider two extreme examples and do a thought experiment:

• First, if the employer really wants to seriously detailed understanding of your technical ability, your experience, if not talking about cost, he should listen to you in detail about all your work after graduation, but also see all your code, documents, diagrams and other information. That’s the most detailed way, right? — But no one does. Why? Because it’s too slow, too expensive, or not worth it.
• Second, if the employer wants to solve the problem quickly, the best way is to trust you completely. He’ll believe what you say you can do and give you whatever you say you’re worth (as long as he can afford it). It’s the fastest and most efficient, right? — But no one does. Why? — Because what you said is not credible ah, you say what skills you can, how to prove it?

So now everyone is using a compromise plan – resume + interview. The above thought experiment may not be feasible, but you can use it to think about the value of a resume, or project experience — the value of a project experience is to validate your technical skills, not to keep track of your work history.

So, don’t have too many projects, multiple projects with overlapping technology stacks are combined. As long as your project reflects your skills, it’s ok. It doesn’t even matter if you did the project or not. You can write about a project that a colleague did, and as long as you master the skills of the project, you can say that you did it in the interview and no one will believe you. Assuming you have the technical ability.

So, in our daily work, do not only focus on their own work. Take an active part in, or watch, a good project in your company for future interviews.

Other problems

A careful and conscientious attitude

Take your resume seriously, don’t just dash it off. If your resume is sloppy, the interviewer will be sloppy. Someone sent me a resume with the last page blank and nothing. It’s not a good look. To be a programmer, you need to be careful and conscientious. Also, some technical nouns in The English word spelling mistakes, this is a very bad thing.

The technology stack is too monolithic

Most people’s technology stack is too simple, mostly vUE, not many people familiar with React, not many people familiar with NodeJS. This will affect their chances, after all, the more people vUE, the more serious the volume, the more intense the competition. So look for differentiation.

The project lacks complexity, competitiveness, and bright spots

Many people tell me this problem through their resumes: they feel that they have worked for many years, but there is no project to be done. The complexity is not high, but they add, delete, change and check those things, and move bricks every day. This is a good question, I believe many people have this problem, and the more work experience this problem highlights the more obvious.

In theory, just a few years after graduation to do basic coding work, slowly 3-5 years after the work, began to do some design, review, technical scheme, management, leader and so on. However, every company is a pyramid-shaped talent structure, which requires fewer high-level talents. Therefore, there must be a lot of people who cannot reach the high-level for various reasons.

In daily work, I should make efforts to get close to the core business of the company, and actively discuss and participate in the projects with high complexity. After the interview also some said, highlight their own bright spot.

conclusion

This article summarizes some common problems in the front-end resume, it is estimated that we should be more or less also encountered. These questions are just for your reference. I’ll share with you when I find something new.