How to write a resume of inexperienced front-end development?

After the recruitment information of the recruitment season is sent out, a large number of resumes will be received in the mailbox, and most of the email titles and attachments are basically unsigned.

Second, you must have a resume in word or pdf file.

Third, the resume should have highlights, preferably works.

Front-end technology is also seriously differentiated now. If it is not strictly divided, there are directions such as NodeJS, H5, mixing, architecture and business research and development. There are many libraries and specifications now, but the difficulty of each branch is similar to the technical baseline (for example, the time taken to reach the advanced level is similar), so it is good to have a full stack generalist. It is a little difficult for people in every direction to go deep, but at least one direction should be very refined and deep. Therefore, it is important to highlight this point in your resume. In fact, the "skills" of 90% resumes are almost the same, and almost all the technologies used in the front end are listed, which occupies the golden section of the resume meaningless.

So since the whole stack is not easy, it is better to highlight the language or technology that you are best at, bypass the others directly during the interview, and do some technical backing from this "highlighting and bolding" part to guide the interviewer to ask what you are good at, which is more conducive to fostering strengths and avoiding weaknesses.

Fourth, highlight key points and demonstrate ability.

It is not difficult to recruit someone who can work now, but it is difficult to recruit someone who can solve the problem. Especially for business research and development like Ali, we should not only get the demand from the business side, but also be alert to the demand trap, accurately identify the rigid demand, formulate the plan, promote the implementation and release the results. Therefore, it is best to show the skills needed to deal with each link in your resume. Specifically, when describing each project, you should not only have the background and process, but also have the results you have brought to this project. For example, describe the project as follows:

I transformed the XX project, adopted the technical scheme of XX, and overcame the difficulties of XX. Finally, demand changes like XX can be quickly digested, developed, online and standardized in data collection. R&D costs have been greatly reduced, and data accumulation has increased rapidly, such as XX. Finally, it began to be promoted in XX product line.

In the interview, this description can easily lead to targeted topics to talk about, and it is precisely because of these foreshadowing in the resume that it can save a lot of time for face-to-face chat and make judgments faster.

By contrast, this description is not good:

The front-end research and development of XX project uses AngluarJS, and the whole project is completed independently, including the whole Boss system acceptance fee, commodity retail, PHS SMS group sending, cable TV charging, salesperson/business point checkout and other modules.

This description only conveys one message, that is, you used AngularJS. As for how many technologies were chosen at the beginning, how to choose AngluarJS, how to couple these system modules based on Angular JS, whether there is a front-end architecture, how deep Angular JS is used, how to divide the work among project members, and how to conduct parallel research and development? What problems have you encountered that you think are valuable, and put forward solutions to these problems, which are code solutions or organizational solutions? This process can only be clarified by asking and answering questions for a long time during the interview. If you can't ask, basically skip it. If you show it in your resume, you will be embarrassed in your heart, and face-to-face chat will not be very procrastinating, and your ability evaluation will naturally be high.

In addition, many people have the habit of writing blogs and summarizing, which is good. It would be better if you could make a summary of the projects you have done in your resume.

Fifth, all-green Github submits records.

Attach Github to your resume. It's best to submit a record of how green it is. If you go to Github's homepage, you want to click on the project list and find a project to read. If you see such a long-term maintenance, Readme clearly and solemnly says "Reprinted with a source", basically grab the phone and start chatting, and the result will not be bad.

Sixth, other concerns and non-concerns

Note: Every job-hopping, the reasons for leaving, quantifiable work results and projects that can represent your highest level should be written in detail, highlighted and underlined in red, and emphasized in your resume.

No concern: certificate, CET-4 and CET-6, programming language you know (don't write unless you are proficient), what you are not good at, personal introduction.

Seventh, typical problems.

I will definitely ask some technical questions. In addition, everyone in the interview will ask:

1. Which project satisfies you the most and represents your highest level? How?

2. One (technical) difficulty that impressed you the most made you work for a long time. How was it finally solved? What have you learned?

You have been engaged in a project (or product) for the longest time. What problems do you see in this project and what can you do?

4. What can you bring to our team or products?

These problems are not rigid, mainly depending on whether we are thinking about things other than technology at ordinary times, especially on the basis of the basic formation of many BU products in Ali, we need to do trial and error, innovation, efficiency improvement, refinement and direction finding. In this case, it is far from enough to have only technical ability (to complete rigid requirements), but it needs to be carried out dialectically.