preface
Today’s front-end market is a mess, typical pyramid shape, with lots of people on the front end, but very few advanced developers and above. Front-end recruitment is also a pain point for all headhunters and HR. In this chaotic environment, how to make themselves stand out? It requires skill as well as strength. Because I am usually responsible for screening resumes, after reading a large number of resumes, I have some opinions on the content and form of resumes. This article will focus on what should be included in a technical resume and what not to do. It will not cover interview skills, after all, screening the resume is the first step. At the end of the article, I made a web version of the resume for your reference.
About the interview
Last year, I interviewed almost 100 people. After the interviews and interviews, I really have a lot of opinions on recruitment. Interviewing is a very difficult job. I’ve read a lot of articles about technical recruiting in order to make it sound, but no method is 100% accurate. Every interview method has its own side. But I admit that most interviewers tend to look for someone similar to themselves. The interviewer’s question must be addressed here. In many companies, including large companies, most of the interviewers may lack experience, the interview questions are not typical, and they are often hesitant to choose or reject the candidates. Therefore, in order to reduce the risk, the interviewers often choose to eliminate the candidates. So sometimes failing an interview is not necessarily the candidate’s problem.
In my opinion, candidates should be evaluated from the following perspectives: basic knowledge (HTML, CSS, JS), advanced part (source code, optimization, etc.), enthusiasm (open source projects, blog accumulation, etc.), vision (understanding and learning of new technologies). For senior front-end development or want to go to the big factory students, these content should be reflected in the resume. Write a separate essay about the details of the interview later when you have time.
content
First of all, take a look at the content of the resume. Personal information and project experience are the main contents and need to be filled in in detail. As a technical staff, in addition to the basic work experience, the usual accumulation should also be reflected in the resume, such as open source projects, technical articles. These can reflect the quality of technical personnel.
Let’s briefly talk about the degree, which is usually the selection criteria of HR. After I started working, I realized the importance of education, especially when you want to work in a first-tier Internet company or better treatment, education may become a stumbling block for you. A bachelor’s degree is almost a minimum. Do not use a few cases to comfort themselves, if there is really no this stepping-stone, strive for an adult undergraduate course. Or you can be so skilled that HR will ignore your degree.
Work experience
What employers care most about is a person’s work experience and project experience. A lot of people don’t write their projects in enough detail, or even a lot of fraud. For developers who work for small companies or have a light front end, the project may not have much to write about, and it can be a vicious cycle if you are not proactive. Even if you don’t have much to write about, don’t cheat and try to describe the project in detail. For example, what projects you have done, what technologies you have used, what problems you have encountered and how to solve them, these are the places where you should write clearly.
In the interview process, I see a lot of candidates who can’t explain the projects they’ve worked on, or write down some mainstream technology they haven’t used at all. In last year s interview, more than half of applicants were rejected based on basic knowledge and project experience.
The open source project
A few years ago, there was a project to turn GitHub content into a resume. Using GitHub as a resume is a straightforward way to do it. During the interview, I will directly ask the candidates if they have any codes that they can read, which may reduce some accidental factors. After all, the interview questions are one-sided. There’s a reason many companies now require high-quality GitHub addresses from job applicants.
Open source projects are a plus. But almost none of the people I interviewed had a project of their own, and many of them were on GitHub for interviews, mostly empty. We can’t deny a person’s ability, but at least it shows that the person’s enthusiasm needs to be improved. It doesn’t take a lot of technical skills to be an open source project, but a normal CSS project deserves respect. Many people don’t know how to start an open source project, and there are articles on how to start an open source project, such as this one. If you are good at thinking and summarizing outside of work, it is not difficult to do an open source project.
However, I am not a fan of doing open source projects just for the interview. It is a cumulative process and cannot be done overnight.
Technical articles
As a technician, it is a great honor to share technology through technical articles. In the big factory interview, the interviewer values the candidate’s ability to share, but in the work, can share the opportunity is not much, so you can write technical articles to compensate. Technical articles include both original articles and translations. In the early days, writing original articles may be difficult, so try translating good technical articles. In fact, most of the articles of many big cattle bloggers in China are digestion of foreign articles, and then write again with their own words. Personally, I think translating an article is often more rewarding than writing one myself.
Technical advantages
In terms of technical advantages, it is better to write clearly what you are good at, not just what is popular on your resume. I’ve seen a lot of situations where interviewers judge candidates based on what skills you have, so blindly writing about your skills is counterproductive. There are a lot of things you can write about technical advantages, don’t think that only JS related content is high, other things like SVG, WebGL, CSS3, etc., whatever you like and are good at, just write about it.
For the content of the resume, you can also refer to JobDeer resume template.
The space
Resume is not too long, for many years of work developers, there must be a lot of projects to write, all written out is not likely, and too much content will abandon the essence instead, cover up the main content, the best control in two pages, the most can reflect their value of content written clearly. One page is so short that there’s very little to write about, and unless you have a really good project, a few sentences will show you’re great.
In the form of
A programmer’s resume doesn’t have to be flashy, but as a front-end engineer, it doesn’t have to be plain, either. It has to represent the programmer, but it also has to be different from other developers.
Among the many resumes screened, the most common are the unpolished document style and the template resumes that come with some recruitment websites, rather than the tabular style. I think the document style is a good way to make the content clear through careful typography, but it would be better if it were modified a little bit.
In the initial screening stage, a stereotyped resume style can turn off the hiring manager. I remember when many HR contacted me, they all said that my resume was the only one out of dozens, I couldn’t help laughing. Resume styles can be a plus, or at least easy for HR to sift through. However, resume packaging is on the premise of content, if there is no content, only style, is bound to fail. As the modernist architect Louis Sullivan famously said, “Form follows function.”
In order to facilitate everyone’s reference, hastily made a web version of the resume template. Your resume is for reference only. Don’t copy blindly.
Making: github.com/nzbin/resum…
conclusion
There are plenty of articles online on how to write a technical resume, including FAB rules and STAR Rules, which only work if you actually have something to write about, but many times you just don’t know what to write about. Especially technical resume, accumulation is very important, without accumulation, resume can only be a blank sheet of paper.