How to write a resume for a web front-end engineer

The role of resume has actually been ignored. Even if someone recommends it, the resume must be taken seriously. Although a resume will contain some general information, the occupation determines the core content of the resume and the success or failure of your job search. A resume is more than just a resume, its important role is to demonstrate capabilities. Therefore, this resume should reflect as much as possible that you are a qualified front-end engineer.

First, self-recommended resumes must be signed

After the recruitment information is sent out during the recruitment season, a large number of resumes will be received in the mailbox. Basically, most of the email titles and attachments are unsigned. After the resume evaluation interview, not every resume will be written with a complete evaluation and entered into the system. Especially some resumes that are not sure, you want to hold them for a while and then take a look at them after they are all processed. However, when reviewing these resumes, start from What you see in the mailing list is often like this:

I have long forgotten which email contains whose resume, and then look through the attachments one by one (some are PDF, some are Word, some are HTML, and some are simply a zip, some are just a URL, and some simply paste the resume into the body of the email...) It is very time-consuming and extremely inefficient to review the originally written evaluation. Even if you finally find the resume you are looking for, your points will have been greatly reduced. Therefore, if you recommend a resume, you must write clearly in the email title and resume attachment file name who you are applying for, what position you are applying for, and the recommended level (junior, senior, expert). Anyway, I don’t need to rename it after downloading the attachment.

Second, be sure to have a resume in word or pdf file

Nowadays, many people’s resumes are directly posted online, or in HTML. It is very difficult for me to process this kind of resume. Effortless. Alibaba’s internal recruitment system supports word and pdf formats best. When I entered the system, many fields were read directly by the system after uploading the attachment. HTML resume support was the worst. After uploading the attachment, I still need another one. It is completely meaningless to fill it out manually and spend energy on it. And from my experience, one page of HTML resume source code can express very limited things. After all, we are not recruiting junior (P5 and below) front-ends now. Therefore, the carriers in word and pdf format are enough, and focus more on the content of your resume.

Third, the resume should show highlights, preferably with works

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, etc. There are many libraries and specifications for the direction, but the difficulty and technical baseline of each branch are similar (for example, the time it takes to reach senior level is similar), so it is good to be a full-stack generalist, but it is a bit too difficult to go in-depth in each direction, but at least A certain direction needs to be drilled very carefully and deeply. Therefore, this strength should be highlighted in the resume. In fact, the "skills" section in 90% of resumes is almost the same. They almost list the technologies used in the front-end, meaninglessly occupying prime space in the resume.

So, since the full stack is not easy, it is better to highlight and bold the language or technology that you are best at. During the interview, I will directly bypass the others and focus on this "highlight and bold" part. Do some technical research to guide the interviewer to ask you about the parts you are good at, which will help you maximize your strengths and avoid your weaknesses.

How to do technical exploration? Look at the work! If you are good at Node, just take a look at the modules submitted on NPM, install them and demonstrate them, and talk about the core code. If it is a component, just look at the Demo and talk about design and packaging ideas. If it is a set of scaffolding tools, directly draw the architecture diagram and explain the principles and applicable scenarios. If it is a project, then show the Release email you sent as PM! The works are not just these, they can also be technical patents, design plans, successful leadership cases, successful team building cases, etc. As long as the content is substantial and down-to-earth, and the context (it can be code or one thing) clear, During the show, my eyes were gleaming and spittle was flying everywhere. It felt right to have this feeling. Therefore, you should include these well-prepared works in your resume and prepare to show them off during the interview.

Fourth, highlight the key points and demonstrate capabilities

It is not difficult to recruit someone who can do the job, but it is difficult to recruit someone who can solve the problem. Especially for business R&D like Alibaba, we must not only obtain demands from the business side, but also be wary of demand traps, accurately identify rigid demands, come up with plans, promote execution, and release results. Therefore, it is best to express the skills required for each link in your 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 restructured the XX project, used XX technical solutions, and overcame the difficulties of XX. In the end, demand changes such as XX can be digested quickly, with extremely fast development, rapid launch, and data collection. Standardization has also been achieved, research and development costs have been greatly reduced, and data accumulation has grown rapidly, such as XX, and finally began to be promoted in the XX product line.

During the interview, this kind of description can easily lead to targeted topics to talk about. Precisely because the resume has these foreshadowings, it can save a lot of interview time and make judgments faster.

In contrast, this description is not good:
XX project front-end research and development, using AngluarJS, the entire project is completed independently, including the entire Boss system acceptance fees, commodity retail, PHS SMS group sending, cable TV Charge collection, salesperson/business point checkout and other modules.

This description only conveys one message, that is, you have used AngularJS. As for how many technology choices were faced at the beginning, how did you choose AngularJS? How are these system modules coupled based on AngularJS? Is there any front-end architecture involved? How deeply is AngularJS used? What is the division of labor among project members? How to conduct parallel research and development? What problems have you encountered that you think are valuable, and have you proposed solutions to them? Is it a code solution or an organizational solution? This process can only be clarified by asking questions during the interview for a long time. If you can't figure it out, you will basically skip it. If it is expressed in the resume, the mind is very loud, the interview will not be very procrastinating, and the ability evaluation will naturally be very high.

One more thing, many people have the habit of writing blogs and summaries. This habit is very good. It would be even better if a summary can be combined with the projects in the resume.

Fifth, all-green Github submission record

Attach Github to your resume. It is best to submit the record there because it is very green. If you go to the Github homepage and want to click on the project list, find Go read the project, and if you see one that has been maintained for a long time, has a clearly written Readme, and says "reprinted with the source" in a serious manner, you will basically pick up the phone and start a chat, and the results will basically be good.

Sixth, other concerns and non-concerns

Attention: Reasons for leaving each job, quantifiable work results, and projects that can represent your highest level should be written in detail, marked in red Thick underline for emphasis in your resume.

Do not pay attention to: certificates, CET-4 or CET-6, programming languages ​​​​that you know (if you are not proficient, don’t write), what you are not good at, and personal profile.

Seventh, typical questions

There will definitely be some technical probing questions. In addition, everyone in the interview will ask:

1. Which project makes you most satisfied? Representing your highest level? How?
2. A (technical) difficulty that impressed you the most, and it took you a long time to solve it. How did you solve it in the end? What are your thoughts?
3. The longest project (or product) you have worked on, what problems do you see with this project, and what can you do?
4. What can you bring to our team or product?

Of course, these are all suggestions. Whether you think they are useful or not, stick to one principle, that is, "A resume is not just a resume (what you have done), its important role is to demonstrate ability.

The above is the detailed content of How to write a resume for a web front-end engineer. For more information, please follow other related articles on the PHP Chinese website!