Original text: before the interview, your resume: to the front the school recruit students resume suggested | AlloyTeam author: TAT. The old professor

Preface: As a front-end interviewer, I have shared my views on the front-end school recruitment interview. This time, I would like to talk about my resume. Long wanted to write this, just recently and brush a batch of autumn recruitment advance approval, read more resume, heart feel, chat a few words, I hope to help everyone to participate in the front school recruitment!

A word, only for reference ~

Resume is often the first impression to the interviewer, but many students who have not stepped out of school do not know how to write a good resume, I often do not know how to interview him with a resume. In autumn recruitment season, it’s easy to ignore a resume if it doesn’t catch your attention in a short time.

What kind of front-end resume is a good resume?

Resume Ideas

Large companies often have technical reviews. Take our company as an example. As long as you have stayed at the current technical level for several years, you can prepare a PPT and make a presentation to several senior technical personnel (judges) arranged by the company. In this process, you will need to demonstrate that you have met the requirements for the next technical level. This usually includes a brief description of your professional experience, project experience, and then a technical case study, using one or more technical cases, to illustrate how your skills have brought value to the project, the team, and the company. The jury challenges you to see if you really understand the technology, evaluates the value of your technical results, and decides whether you pass.

What’s the point? Number one, you. You have to talk about your role and your role and you have to talk about exactly what projects you’ve done or directed, and ultimately the judges are looking at you alone. Second, technical output. As a technical developer, no matter how good the project you participate in is used by many people, it is also the cattle of product managers and operation personnel. It is none of your business. What technical personnel look at is the optimization and output related to technology. Two things put together: you’re a technical bull.

Technical review is the same, internship is not similar, writing a resume is not similar?

With that as a core idea, have you clearly defined your role and role in a team project? It’s not how many big companies you’ve interned for, it’s what you’ve accomplished. Write how many scholarships, how many papers, the weight is not so heavy, we still want to hear the front end of the interview related. It’s not true how broad your interests are or how good your personality is. When it comes to skills, your personality will come through during the interview.

Once you’ve thought this through, you’ll know what to focus on.

How do I swipe my resume

Open your resume and look at colleges first. Whether you like it or not, the atmosphere and quality of programming development at some universities is better, and there are hidden pluses.

Secondly, internship experience, internship in Tencent, Alibaba, Toutiao and other big companies is definitely a big advantage (if you have it, it is not too much to focus on the big black), well-known companies in the industry is also good. So if you’re interested in going that route, try to get an internship at a big company during your first few years of college.

Professional skills, in particular, if you’re sifting through a big resume pool, you’ll quickly scan it to make sure it’s not someone backstage who made the wrong set. If you’re looking at your resume before an interview, you might want to take a closer look at it, which I’ll talk about in a later section.

Then, the focus is on project experience. Look at what, keywords! For example, I have written a paper on XX and participated in social practice, but the focus is still on projects like “online system development”, “small program development”, “XX WebApp development” and “author of an open source component”. Then a long paragraph about the introduction and description of the project is not much use, the focus is on the technical capabilities and keywords revealed in the project, such as “app Service Worker did XX”, “Based on React Hook”, “implemented a perfect unit test”, “improved page opening time by applying certain ideas”. Blah, blah, blah. It all interests me. If none of these are available, you’ll write things like React+Redux, Node +Koa, or all about what pages are being developed, and give up pretty quickly.

Just a few pieces, just a quick scan of the past can build up a mental picture of the student’s technology. Instead of some key words quickly capturing the interviewer’s interest, you rely on a long paragraph of text to make him do the reading comprehension. I’m sorry and you’re sorry.

How to write a good resume

The above is to tell you how the resume will be seen by others (although from my experience, but I think it is representative), then talk about several main modules how to write, personal basic information module will not say, too basic.

Technical skills (also called personal skills, professional skills)

A common part, but many people did not write a good attention. You often see descriptions like this:

What do you think?

I don’t think so, because there’s not enough interesting information. If by the criteria of resume screening, the keywords in it are ok:

But if you see it before the interview, you will feel that there are too few interesting points. On the one hand, familiar with three languages, too basic requirements, familiar with MVVM, React, Redux, computer network these, can ask. The third point is a bit of a bluff, while the fifth point is largely ignored outright. If it was my second interview, I’d start looking for highlights. Why is that? Because the foundation of the first pass is not too poor, the significance of the investigation is not too big, the project practice of the school enrollment is generally not too rich, and may not be enough to carry out. Then what is it? Then I would expect him to have a slightly in-depth study on one or a few small technical items, some thoughts of his own, and the technology he is interested in. That’s the highlight.

Or the above resume for example, I think the interesting point is only one:

Because it’s a relatively new technology, because a lot of admissions students don’t mention it, because it’s not a well-studied technology and there’s a lot of room for discussion. At this point, I would ask: “How to write Hook”, “why to develop Hook, what are the advantages”, “Hook principle is about”, “if I have an existing React plugin also want to support the Hook type writing method, what should I do?” Go layer by layer and really differentiate the strengths and weaknesses of the candidates, and if you’ve actually answered these questions, you’re pretty much done. After all, it is difficult for us to ask the school to recruit students with a wide range of front-end knowledge, but if they have a deep understanding of a certain aspect, even if he does not have a wide range of knowledge, we also believe that he can learn to do well in other front-end fields, because the learning ability and exploration ability reflected here is particularly important. This may answer many students’ perplexity: I think the interview answer is ok, why did not pass? Because you know too much but don’t know too much, you don’t have bright spots, you don’t show your ability to learn and so on, you will be outdone. (PS: THIS is the perspective of big companies, because big companies are more concerned with developing potential.)

Of course, I’m not asking you to work on React Hook. I’m not telling you shortcuts. You know, a senior interviewer also has technical weaknesses. If he is not familiar with hooks, he will not ask more questions. However, there are many similar highlights, such as “I like studying Webpack, and wrote Webpack plug-in to improve monitoring and packaging efficiency”, “I am familiar with performance-related tools and Lighthouse, and know some details of its evaluation of webpage performance”, “I know SSR, and have been in practice, and have done pressure measurement with industry tools. Know some of the points that are likely to become performance bottlenecks, etc., etc., students can also do research, in-depth thinking, always catch the highlights of the interviewer. These are the areas where you can excel, even if you can’t answer them thoroughly.

However, the most basic ones still need to be mastered, or you can’t even pass the written test, let alone show the highlights.

So far, come back. In the section on technical skills, it is best to list some general technical skills as well as some in-depth research on specific technical points. I would have liked to have seen the passage go something like this:

First distinguish between big abilities:

  • Master front-end basic skills
  • Mobile Web development capability
  • Nodejs development capability
  • Ability to develop small programs
  • Have Electron client development capability
  • Learn about new technology
  • …

Reclassify small abilities such as:

Mobile Web development capability:

  • Understand common screen adaptation solutions
  • Understand the differences between mobile and PC development
  • Understand the common optimization schemes of base64 and other mobile terminals

Finally fill in the highlights:

  • …
  • Studied some gesture library, understand the basic principle, can customize some special gestures to achieve special functions;

Isn’t this way of organizing your technical capabilities more organized and in-depth than the previous dry broad points?

Experience in project

Project Experience this section could include: projects you did as an intern, projects you worked on at a school studio or in a programming contest, and technical projects you worked on yourself. It is generally combed in chronological order.

At this point is not recommended to the programming of the front-end experience even put up, such as using c # to do a what kind of software, why not so good, because of your interview is front end, your interviewer may not be familiar with the language, he don’t know how to ask for you the experience, don’t know how to do it well, then directly ignored. Unless you can add in how well you did, such as winning second prize in Microsoft’s national competition, and even then, it’s not an important case (unless you don’t have other front-end projects).

I also don’t recommend writing about projects that are more than two years old, because if you write a couple of pages, I’ll just skim through them. The development of the front end is changing so fast, there are all kinds of new articles and practices every day every month, sometimes a new version of a framework can bring us new ideas, the technology used in the project two years ago has either become common sense or outdated, and even a year ago is not new. If you want to be on the front end, we want you to keep learning and keep paying attention to the front end.

I personally like to ask college students what technical projects have you worked on yourself. Because at this stage you don’t really get the opportunity to lead or develop an internship program, most of the time it’s a supporting role. Personal projects are different, where I can tell if you really like the front end, if you’re going to do some Web practice that you find fun, and if you’re going to get it right with your own thinking. A student who likes to toss about is more likely to surprise us and create some extra value in work. Such as have

Ok, now that we know what projects to write, let’s talk about how to write.

I’ve seen project descriptions like this:

Those of you who can understand my resume thinking in the first section can also understand why I don’t know how to ask this question when I look at this project experience. Because it does not explain clearly the technical results of your technology, and it does not explain clearly how to solve the difficulties to demonstrate technical ability. Is it useful to talk about that long project description? No use! I really don’t care about the product logic of the project unless it’s a technical project (e.g., developing a XX technology framework). A responsibility statement is fine, you need to be clear about your role, but it’s a vague statement about ensuring the quality of the project and controlling the development process. Rather than a brief example, give a specific strategy, such as what kind of architectural layering you did with single test. It’s not practical to write a long paragraph of concrete description, but at least give a few sentences of concrete description. Performance optimizations give small points too common.

Project experience is not really about explaining what the project is, it’s about highlighting the application of general technical knowledge behind the project and how you solved technical problems.

My ideal scenario for this module would be:

  1. Project name, your role, time;
  2. In the project introduction, the function and value of the project can be clearly explained in one sentence. For example, “Resume management system, which provides students with resume suggestions and generation management functions, has been applied in more than 3 colleges of the university”;
  3. Introduction to technology stack;
  4. Technical difficulties encountered in the project and how to solve them. For example, “In the development of this Web game, there were many screen elements and high texture quality, which led to the lack of game fluency. At this time, XXX was optimized through XXX strategy, and XXX was improved through XXX. Finally, the frame rate of the game remained close to 60 frames.” “How to realize multi-person collaborative editing of brain maps and how to solve conflicts is a difficulty. At this time, I pre-studied XXX scheme, borrowed the source code of XXX framework, and finally made a strategy based on the characteristics of the project: XXX, realizing the function”.
  5. Related outputs, such as performance Recommendations for Web Development online Games with links, such as open sourcing a piece of technology, etc.;

At the end of the day, talk about technology, and preferably something that goes beyond the specific project and inspires other people, so that you can have a common conversation with the interviewer.

Other modules

Relate with post ability not big, basic not important, for instance scientific research achievement, for instance interest hobby, can omit, want to understand above section write clearly, resume already relatively substantial.

Of course, if you have other technology related, you can also fill in. Contribution to the community, such as separate section “in Denver on zhihu personal technology column, N the write post, including XX visits, a recommended home page”, “one of the contributors of nodejs, mentioned N MR accepted”, “one of the Chinese translators of XX framework”, “XX front-end technical meeting done booth share”, such as this, It’s kind of awesome.

For more details

Blabla has said so much, but let’s finish with a few more bits and pieces:

1. The keywords

No further details, according to the first section of the train of thought to analyze, directly marked black accentuation;

2. Highlight it

I will not say if the foundation is solid, if even the event proxy, cache related can not speak well, there is no need to go down. It is better to have your own thinking and understanding of the framework used in the projects you have done so that it is easy to dig out highlights. It doesn’t have to be the whole article is highlights, dozens of, think about what piece of technology you are best at, to have a main case, the main highlights.

3. Offer the topic

In addition to 2, it is an advanced skill to describe your resume without going into too much detail and to attract the interviewer to talk to you about this pre-prepared technical point.

4. Keep your resume specific

Don’t think about a resume, interview front-end, client, background with a resume, it is easy to let the interviewer see that you do not pay attention. Like this:

5. Value previous internships

I met a classmate earlier, who came to me and looked at the interview evaluation, which was quite good. I also worked as an intern in another department of the company before, so I looked at the information on the recruitment website of the Intranet, and found the previous internship evaluation, which was not good. The main problem was that he was not active enough in assigning affairs. This makes my impression of him lower a lot of points, this kind of interview is difficult to examine the questions we are most afraid of. Later, after a long hesitation, I decided to give him a second interview. With a critical view, I found that he had a good understanding of each technology and had his own thinking during the second interview. Indirectly, I found that he was also aware of his previous internship problems and had thought about how to improve them. I ended up giving him a second interview.

Your internship performance is your resume of sorts. Be positive about every internship, even if it’s not right for you, or you’ll screw yourself up next time.

6. Resume format

PDF.

Most large companies have their own recruitment resume platform, so if you’re scanning your resume in PDF format, you can open it in Chrome, which is very convenient. If it is in Word format, you have to download it, open it again, and then check it again when Word starts, which will bring some trouble to the interviewer. More is not recommended to zip package, packaged in his works, regardless of the whole process more trouble, the interviewer is business development tasks may not have so much time to look at your work, at this point it would be better in the resume enclosed and do their lot address, can let the interviewer interested he will go and see.

While an interviewer won’t reject a candidate based on the format of his or her CV file, there’s no need for schools to create obstacles for themselves.

conclusion

Talk about so much is to be lazy, if everyone’s resume core prominent, clear information, that we interviewers can save a lot of time, look at the resume can also look comfortable, how good ~

In the end, everything is on the paper, and any whitewash or technical vanity can be exposed. A resume is just a solid technical foundation and a good attitude to learn. I like challenges and counter-routines, now I am in the second interview, when you meet me continue to wish me luck ~

PS1: Attached is my last article for your reference “What should be inspected for front-end school Recruitment? An interviewer’s Thinking”.

PS2: The resume cases used in the article have been desensitized. If the resume author still feels inappropriate, please contact me to change it

PS3: Next time I want to write an article about the second part of the story, but I feel I have not thought about it deeply enough

AlloyTeam welcomes excellent friends to join. Resume submission: [email protected] For details, please click Tencent AlloyTeam to recruit Web front-end engineers.