How to write a resume for beginner/advanced front-end development?

1 Introduction

This article is only for junior and senior technical positions.

The spring recruitment season is about to come. Last year, I participated in the department's intern recruitment work and received many resumes from classmates. I found that some of my classmates' resumes were not very good-looking. However, after a careful chat, I discovered that these students are actually very skilled, but they don't know how to write on their resumes, and they don't know how to "package" themselves.

In the process, I also gave some suggestions to some students' resumes, combined with my own resume writing experience, write an article here to chat, if there are deficiencies, I hope to point out and add them.

The main content of this article:

  • Why write a resume seriously
  • When writing a resume, what do we need to care about
  • How to better present yourself on your resume
  • What else do you need to prepare when you write your resume and after the resume is written

Build it ~

1.1 The importance of a resume

How important a resume is, let’s take a look at a scene in life.

Think about it, the first time you date with the goddess, will you put on a handsome suit, comb your hair like an adult, and keep looking in the mirror to see if you are the most handsome today.

The same applies to finding a job. Your resume is your **"front" and your "stepping stone"**. Even if your skills are very good and you are well prepared for the interview, if your resume is not well written, you may not even have the opportunity to interview.

HR may need to process hundreds or even thousands of resumes a day, and the time spent on a resume may not exceed "30" seconds. Some resumes can even be passed after "10" seconds. Interested resumes Will take more time to look at it.

Many people complain that they have submitted countless resumes, communicated with countless people on a certain recruitment software, but did not receive an interview. At this time, you may need to think about whether your resume has been carefully prepared.

Moreover, the resume is to accompany you throughout the interview process and is the only way for all interviewers to get to know you.

Therefore, the resume is really important.

1.2 The importance of interpolation

This is a digression.

Come, let’s take a look at the scenes in life. For example, when you’re on a blind date, does the introducer say a lot of the advantages of pairing (don’t look at me, I’m listening to others), after the introduction, your impression of the other person is Wouldn't it be better? Arrange now!

In the same way, when you are looking for a job, you can refer to the target company's employees. The referee will first help you with your resume, chat with you, then give you some suggestions, and finally give your resume to the boss and give some positive comments!

Therefore, referrals are also really important.

Recruitment, Alibaba Internationalization Department-AE Technology Department, Front-end/Java... and other technical positions, P6/P7, and are still available for the 21st Spring Internship Car, interested in private chat.

2. Contents of the resume

My understanding of the resume is like this. The resume does not need to be very complicated. It is a **"simple resume" , whose function is to allow people who read resumes to quickly and accurately capture "useful information"**.

You just need to make it clear who you are, where you are, and what you are doing.

No, it should be these three points:

  1. who are you
  2. what have you done
  3. Which aspect of you is better

I think it is enough to show these three points elegantly.

2.1 Personal information

"Three elements of personal information" : name, phone number, and email address.

This is the way for HR and interviewers to contact you. If you lose the interview opportunity because you can’t reach the phone or email, you’re really going to lose.

If it's convenient, you can also leave a WeChat on your resume. After all, if you can't be reached by phone, the interviewer can add you to WeChat to find you.

Recently, I have encountered many students abroad. Three points that need special attention:

  • Ask the referrer if he supports English resumes
  • Ask the referee if they support foreign calls, and the area code must be written in full
  • Due to the time difference, you'd better leave a convenient time period in Beijing time on your resume to reduce communication costs

I met many classmates and I reported that I did not receive a call from the interviewer due to the time difference, and then I needed to communicate with the interviewer to make an appointment through me. This communication cost is still relatively large.

In addition to the three elements, if you have your own GitHub or blog and think it's pretty good, you can also write it up. However, if it is a GitHub that has no repo, no commit, etc., it is not necessary to write it up.

Some other personal information: political outlook, age, working years, whether you are single, etc., actually don’t need to be written on your resume.

By the way, there are also photos. If you are really confident about your looks and really want to take photos (the kind that can’t be stopped), then put a serious ID photo, but don’t take a selfie. Just put it on your resume.

2.2 Educational experience

Just write down the school, major, time of enrollment/graduation, etc. clearly.

Educational experience is the key point for interns/graduates, so social recruitment is not a key point.

"Interns/ Freshmen"

Each academic qualification must be written in full. If you think your academic qualifications are an advantage, or your grade points are outstanding, you can bold it.

Also need to pay attention to the graduation time, it must be written accurately to reduce unnecessary trouble.

"Social Recruitment" : Write the highest degree.

2.3 Internship/work experience

Just write down your work experience clearly. Generally speaking, HR and interviewers are more concerned about the following points:

  • Company name: It is better to write the abbreviation throughout the entire process
  • Job Title
  • Working time: What matters is whether your job is stable and whether you frequently change jobs
  • Main work: Briefly describe what you did in the company, which is reflected in the project experience

"Interns/ Freshmen"

If you have an internship experience, you must write it carefully. This is a bonus item. If you have an internship experience in a large factory, it is really good.

"Social Recruitment"

**"Actually"** Just fill in your recent 2~3 paragraphs of work experience.

By the way, for the average person, it is better not to change jobs frequently. Frequent job-hopping will make people feel that there is not enough thinking and precipitation in every part of the job.

2.4 Project experience

**"Project experience" is the "most important" part of a resume for development ! **"Project experience" is the "most important" part of a resume for development ! **"Project experience" is the "most important" part of a resume for development !

Since it is the most important thing, it may be difficult to choose a difficult player. What kind of project should be favored and written on the resume?

"1. Do it yourself"

Needless to say, it must be a project that you did yourself. Don't look at other people's projects, just use it to blow up, interviews and back-tuning may be helpful.

"2. Very familiar"

For this project, you must know everything about business and technical implementation:

  • Business: What is the business background of this project, what are the strong points in the business, how the business is promoted, etc.
  • Technical realization: What is the overall technical realization idea of ​​this project, what are the more powerful technologies used in the project, what are the more difficult problems solved, etc.

Don't have this idea: there is a really awesome thing in the project, but you didn't write it, and you don't understand it at all, but you just want to write it into the project.

"3. Highlights"

Good-looking skins are the same, interesting souls are one in a thousand

What the interviewer cares more about is the interesting things that are not visible on the surface of the project. Both business and technology are available.

  • What awesome things did this project do
  • What awesome things did you do in the project
  • What awesome technology has been used to solve difficult problems

Some students said that they don’t seem to have done any bright projects, so how should I write them on my resume?

Teach you two tricks, write about projects that are more difficult to solve and projects that produce results.

"4. Encountered problems that are more difficult to solve"

There must be some problems in the project development process. If not, it means that you have been in your comfort zone for a long time and you need to find something challenging to do.

Find a project like this and think about the following:

  • What's the problem: page performance problem
  • How do you troubleshoot problems during this process: How to troubleshoot page performance issues
  • How to locate the problem: Through the flame graph, it is found that there is a problem with the loading performance of a long list
  • Ultimately how to solve this problem: solve the problem of long lists through virtual lists

"5. Productive"

There is a kind of project that interviewers still like very much, that is, the project that is **"productive"**, which can be considered from the following points:

  • Thinking: The development template used by the team was found to be messy, and the code writing was not standardized
  • Design: Design a unified scaffolding tool, and design code specifications
  • Solution: Develop CLI tools and solve code specification issues through ESLint/Prettier
  • Promote: Promote tools to become the basic product of the team through preaching and other methods

"Summary: The project experience must be the part that the interviewer is more concerned about, and will definitely ask in detail during the interview, so don't be long-winded, choose what is awesome and interesting, and you can explain it clearly by yourself."

2.5 Professional skills

Professional skills are the technology stack you master.

Many people's professional skills are written like this, and they account for half of the resume:

  • Proficient in js/html/css
  • Familiar with es6
  • Proficient in vue
  • Familiar with ant-design to write pages
  • Familiar with webpack and bable

Here are a few questions, which are the "most taboo" when writing professional skills:

  1. Pay attention to the correct writing of technical terms. They bableare not familiar at first glance.
  2. Technical terms attention to the case, JavaScript/ HTML/ CSS/ Vue.jsetc.
  3. It says familiar with xxx, proficient in xxx, are you really familiar and proficient?

If it were me, I would use "knowledge/familiar/proficient" to describe the technology stack I master.

"To understanding"

  • Will use/used
  • Understand its thinking
  • Haven't learned deeply
  • Simply read the technical documentation or related articles, and know such a thing

"Familiar with"

  • Has a lot of practice
  • Have an in-depth understanding of the principle, and even read the source code
  • Can quickly come up with solutions when encountering complex problems
  • When others ask questions, they can quickly think of answers or ideas

"proficient"

  • In-depth understanding of the principle
  • A lot of practical experience in complex scenarios
  • A lot of relevant source code experience
  • Can guide others

I have received such an intern resume, and there are at least 10 familiar and 3 proficient in the professional skills. But looking at his project experience, it is actually relatively simple. Visual inspection should not know how to describe his technology stack.

"Personal suggestion, you don't need to write too much about professional skills, just write down some technology stacks that you want interviewers to understand that are not mentioned in your project experience."

For example, there may be more business development and less engineering involved in your work, but if you personally have a bit of research and research in engineering, you can write engineering and guide interviewers to ask questions.

If the interviewer is interested, he will pick a few technical stacks to ask you a few questions. If the answers are also great, it must be a proper bonus item.

Of course, the technology stack written here must be something you understand or master, otherwise you won't be able to ask two questions randomly, and it will become a sub-item.

"Summary: Please be cautious about your professional skills. It may be your bonus item or your deduction item."

2.6 Other

It's time to show yourself, show yourself as much as possible.

  • Community: GitHub Star 10k, Nuggets Lv6...
  • English ability: IELTS TOEFL CET, proficient in listening, speaking, reading and writing...
  • Hobbies: photography/fitness/travel...
  • Communication: It can not only promote product optimization, but also push down product demand...

How to be awesome, how to write it simply.

3. Style/Typography

As mentioned above, the resume is to allow the interviewer to accurately and quickly capture useful information.

Therefore, the resume must be **"simple"**.

3.1 Style

  • "One page is enough" : 10 ~ 30 seconds, maybe your second page of resume will never be seen
  • "Principle of white space" : White space is a commonly used technique in the creation of Chinese art works. It is also applicable to resumes. There needs to be some space between each line of text and each module to make the whole article more coordinated and highlight the key points.
  • "Standard font" : Times New Roman is fine, don’t use those fancy fonts
  • "Resume Template" : Weak visual effects, four colors of black, white, blue and gray are enough, simple and efficient. But don’t be too simple, don’t use tables

3.2 Module sorting

Regarding the ordering of the modules on the resume, personal suggestions:

  1. Personal information
  2. Internship/work experience
  3. Project experience
  4. professional skill
  5. other

**For the "Educational Experience" module, if it is an intern/graduate student, he should be placed between the "Personal Information " and "Internship/Work Experience" . If it is a social recruitment, I think it should be placed in "Others" It was just fine before, after all, "work experience" and "project experience"** are the key points.

4 Conclusion

in conclusion:

  • Resume must devote 100% energy to writing carefully
  • The resume must be real
  • After writing the resume does not mean that you will not read the resume. You must be very familiar with the content of the resume.

I can't think of other things temporarily. I am not an HR, so the above content is only a personal suggestion, and the author himself wrote the same when writing his resume. If there are deficiencies or inconsistent views, please point out and discuss them~

I hope it helps everyone~

Finally, the gold three silver four are coming soon, I will give you a small bonus. Here are some interview questions I compiled after work, including HTML, CSS, JavaScript, server and network, Vue, browser, react, etc.

HTML version

  • What is the difference between title and alt in the picture?
  • What are the new features of Html5 and what elements have been removed
  • How does the browser manage and load the offline storage resources of Html5?
  • What are the elements in the line? What are the block-level elements? What are the void elements?
  • What is the difference between setting the width and height of the canvas on the label and setting the width and height in the style
  • How does the browser manage and load the offline storage resources of HTML5?

CSS articles

  • The difference between link and @import in CSS:
  • The similarities and differences between absolute and fixed position:
  • What is the use of BFC
  • Several ways to clear floats
  • Css3 new pseudo-class-pseudo-element
  • IE box model, W3C box model
  • When will display:inline-block not show the gap?
  • Does the inline element become a block-level element after float:left?

Due to the large content, in order to avoid the reading experience, only part of the interview questions are displayed. The full version of the interview questions + analysis, [click me] is free to get.

JavaScript

  • The various positions of js, such as clientHeight, scrollHeight, offsetHeight, and the difference between scrollTop, offsetTop, clientTop?
  • Implementation of js drag and drop function
  • Asynchronously load js method
  • js anti-shake
  • Closures that cannot be bypassed
  • Talk about your understanding of scope chain
  • JavaScript prototype, prototype chain? What are the characteristics?
  • Please explain what is event delegation/event delegation
  • How does Javascript implement inheritance?

View

  • The role of key value in vue
  • Why must data in a Vue component be a function?
  • What is the State characteristic of vuex?
  • Introduce Vue's responsive system
  • The difference between computed and watch
  • Introduce the life cycle of Vue
  • Why component data must be a function
  • How do the components communicate

Due to limited space, only part of the interview questions can be shared, and more interview questions and answers can be read and downloaded by [click me] ~ Share it with everyone for free, it is a thankful feedback.

Guess you like

Origin blog.csdn.net/hugo233/article/details/112796231