What is the resume of an excellent front-end development engineer?
Published: 2021-08-26 01:24:20


A resume is not just a resume, its important role is to demonstrate ability ! ! !

Recruiting in Ali all year round, screening all kinds of resumes. Every recruitment season, the process of screening resumes and interviews is very energy-intensive. Of course, one of the reasons is that I want to recruit very good people. I would rather spend more time. On the other hand, in addition to the unqualified resumes, there are many resumes that are unclear and have to be confirmed repeatedly during the call. At the same time, in order to take into account the candidates’ feelings, they have to pretend to be very professional and do some interaction with him. A large number of people were sifted out, which encroached on a large area of ​​my time. In order to improve the efficiency of these people's resume (interview), here are some suggestions:

**First, the self-recommended resume must be signed**

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. After the resume evaluation + contact, not every resume will be written in a complete evaluation entry system, especially some inaccurate resumes. 

I can’t remember which email contains whose resume, and then go through the attachments one by one (some are PDFs, some are Word, some are HTML, some are simply a zip, some are a URL, and some simply paste the resume in the body of the email... .) It is very time-consuming and inefficient to evaluate the original evaluation. Even if I finally turned to the resume I was looking for, my points were already greatly reduced. Therefore, if you recommend your resume, you must write clearly in the email title and the file name of the resume attachment, who, what position you are applying for, and the recommended level (junior, senior, expert). Anyway, I don’t have to rename it after downloading the attachment.

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

Nowadays, a lot of people's resumes are directly posted online, or in HTML. It is very difficult for me to deal with this kind of resumes. Alibaba’s internal recruitment system supports word and pdf formats the best. When I entered the system, many fields were directly read by the system after uploading the attachments. The HTML resume support is the worst. After uploading the attachments, I need one more. It’s completely meaningless to fill in by hand, and it’s totally meaningless to spend energy on this. And from my experience, what can be expressed by a page of HTML resume source code is really limited. So word and pdf format carriers are enough, so spend more energy on resume content.

**Third, the resume must show bright spots, preferably with works**

The front-end technology is also very differentiated now. If it is not strictly divided, there are NodeJS, H5, Hybrid, architecture and business research and development directions. Now there are many libraries and specifications, but the difficulty and technical baseline of each branch are similar (for example, the cost of reaching senior It takes about the same time), so the full-stack generalist is good, it is a bit too difficult to go deep in each direction, but at least one direction should be very precise and very deep. So highlight this strength in your resume. In fact, the "skills" part of 90% of resumes is almost the same, and they almost list the technologies used in the front-end, meaninglessly occupying the prime location in the resume.

Therefore, since the full stack is not easy, it is better to highlight and bold the language or technology that I am best at. During the interview, I will directly bypass the others and focus on this "highlight and bold" part to do some technical probing. , In order to guide the interviewer to ask what you are good at, it is more conducive for you to use your strengths and avoid your weaknesses.

What do you usually do when you get to the bottom of technology? Look at the work! If you are good at Node, just take a look at the module submitted on NPM, install it and demonstrate it, and talk about the core code. If it is a component, just look at the Demo directly and talk about the design and packaging ideas. If it is a set of scaffolding tools, draw the architecture diagram directly, explaining the principles and applicable scenarios. If it's a project, then show the Release email you sent as a PM! The works are not only these, but also technical patents, design schemes, successful cases of leading people, successful team building cases, etc., as long as the content is substantial and grounded, and the pulse (it can be a code or one thing) is clear. During the show, the eyes gleamed and the stars flew around. This is the right feeling. Therefore, you should include these well-reserved works in your resume, and prepare them to show off during the interview.

**Fourth, highlight key points and demonstrate ability**

Now it is not difficult to recruit a person who can work, but the difficulty is to recruit someone who can solve the problem. In particular, business research and development such as Ali requires not only to get demand from the business side, but also to be alert to demand traps, accurately identify rigid demands, formulate plans, push for implementation, and release results. Therefore, the skills required to deal with each of these aspects are best shown in the resume. Specifically, when describing each project, you must not only have the background and process, but also the results you brought to the project . For example, describe the project like this:
> I refactored the XX project and used the XX technical solution to overcome the difficulties of XX. In the end, changes in the requirements of XX can be digested quickly and quickly, with rapid R&D, rapid launch, and standardized data collection. The cost of research and development is huge. Decrease, data accumulation grows rapidly, such as XX, and finally began to be promoted in the XX product line.

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

In contrast, this description is not good:

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

This description only conveys one message, that you have used AngularJS. As for how many types of technology we were faced with, how to choose AngluarJS, how to couple these system modules based on AngularJS, did it involve front-end architecture, how deep is AngularJS used, what is the division of labor among project members, and how to develop in parallel? What problems have you encountered that you think are valuable, and proposed a solution to this, is it a code solution or an organization solution? This process will take a long time to figure out the question and answer during the interview. If you can’t ask, you will basically skip it. If it is expressed in your resume, your mind will be awkward, and the interview will not be procrastinated, and your ability evaluation will naturally be very high.

One more thing. Many people have the habit of blogging and writing summaries. This habit is very good. If a summary can be combined with the project in the resume, it would be even better.

**Fifth, the all-green Github submission record**

Attach Github to your resume. It’s best to submit a record where it is very green. If you go to the Github homepage, you want to click on the project list and find the project to read. If you see the kind of long-term maintenance, the Readme is clearly written, Write "reprinted with an indication of the source" in a serious manner, basically grab the phone and start the chat, and the result is basically not bad.

**Sixth, other concerns and non-concerns**

Attention: The reasons for resignation every time you change jobs, quantifiable work results, and projects that can represent your highest level should be written in detail, marked in red and underlined in bold, and emphasized in your resume.

Don't pay attention to: certificate, level four or six, familiar programming language (if you are not proficient, don't write), what you are not good at, personal profile.

**Seventh, typical problems**

I will definitely ask some questions about the bottom of the technology. In addition, everyone in the interview will ask:

1. Which project satisfies you the most and represents your highest level? How to do it
2. The one (technical) difficulty that impressed you the most, which caused you to deal with it for a long time, how did you solve it in the end? What's your experience?
3. For the project (or product) you have done 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 product?

These problems are not hard and fast. They mainly depend on whether they usually think about something other than the technology, especially on the basis of the basic shape of Ali's many BU products. Trial and error, innovation, efficiency, refinement, and direction are needed. In this case, only having the technical ability (to complete rigid requirements) is no longer enough, and dialectical execution is needed.

**finally**

Of course, the above are all suggestions. Whether you think it is useful or not, stick to a principle, that is, "Resume is not just a resume (what you have done), its important role is to demonstrate ability (what you can do well)!! !"

**FURTHER READING**
▶ [Walkthrough007](https://www.walkthrough007.com/) - https://www.walkthrough007.com/