Given how often I get asked private questions about front-end interviews, a lot of times I’m busy and don’t reply, and then forget to reply later. With the help of this article, I will make a summary that you can read in about 5 minutes.

I. Resume

How important is a person’s resume to his job search? 🤔

It’s a great way to get your foot in the door, not only to get an interview, but also to make the company think better of you. In a world where all you know about yourself is your resume, your resume is basically the only leverage you have.

So how to write a good resume to initially attract HR and interviewers?

1. Personal highlights

Start by identifying your own highlights and the highlights of previous projects you have worked on. Many people always say that they have no bright spot, really no bright spot? Just list some of the best things you’ve ever done, and that’s your highlight.

Highlights are things that you accumulate on a daily basis and research deeply, such as

Depending on how you think about your business, for example

I don’t know if you’ve noticed, but WHERE I think there are bright spots, if there are quantitative indicators, I will list them. For example, to describe the community, IN order to prove that I am really active in various communities, I put some key and real data on it. For performance optimization in the business, I also quantified key results. One thing to keep in mind is that without data, it’s almost empty bullshit.

But, remember, don’t write something you don’t have to show your ability, or you will be very embarrassed.

2. Clear hierarchy

Break down the level of work you’ve done for the company and the projects you’ve been responsible for. Don’t jot it down as a running list, and don’t try to describe it in a few words, or your first impression will deteriorate instantly. Give some examples for companies and projects

I. Company experience

Example 1:

In example 1, we can hardly see what the candidate has done in the company, so if you were the interviewer, what would you think?

Example 2:

In example 2, the candidate’s responsibilities are clearly described, but not sorted out, which I don’t want to follow up on anyway

Example 3 (in itself) :

In example 3, I described my responsibilities in the company and quantified some of the outputs. At a glance, the interviewer can get a sense of what I do in the company. If you look closely, you can see some bright spots.

Ii. Project experience

Like the company’s experience, the project you are responsible for should be described point by point, and the key indicators that can be quantified should be quantified as much as possible. And then just as importantly, remember to describe it in points. Do not like the picture below, let a person see a direct head pain

Even if it’s a little bit simple, it works a lot better, like

3. Several taboos

  • Don’t exaggerate. For example, if you were responsible for a small part of a project, your resume says you were responsible for the entire project
  • Never write proficient or skilled if you are not very familiar with some system. “Proficient” basically means you’re declaring war on the interviewer, so don’t write “proficient” even if you know it well. If you do, you can write “proficient.”
  • Don’t write descriptions of your company or project all in one place. Look at the example above
  • More points to add

4. Some suggestions

  • The output resume should be in PDF format as much as possible
  • Do not name your resume “Chinese resume of XXX”, please indicate your purpose, such as “XXX-XX front-end Development -2019”.
  • Graduation school, major, graduation date, date of birth, contact information and other personal information written clearly
  • Project experience, if you have a lot of projects don’t write them all at once, get rid of some of the similarities
  • Try not to include salary on your resume. If you must, both current and expected salary should be in the form of “monthly salary * N salary + equity (if any)”
  • Waiting patiently for a response and not getting back to you in a few days may just be because the interviewer is too busy to read the resume

Two, self-introduction

You need to summarize your university, major, graduation, your professional experience, each company responsible for content and other personal information in about five minutes. Such as

Dear interviewer, my name is XXX and I have been engaged in front-end service for XXX years. I graduated from XXX school in XXX, majoring in XXX. I worked in XXX Company from XXX to XXX, mainly responsible for XXX…

Don’t summarize yourself in one sentence, and then have the interviewer ask you about what you did, for example

Hello, interviewer, my name is XXX.

That would be really awkward

Three, STAR rule

First of all, what is STAR

S: Situation, context — A concrete business context

T: What are your tasks

What actions have you taken in relation to the business context

R: Result — What is the final output

In fact, the content I mentioned in my resume also follows the STAR principle.

The same goes for an interview. If the interviewer asks you to describe a project that you are proud of, always follow the STAR Rule. Such as

In order to integrate XXX business (S), I assumed the role of XXX and was specifically responsible for XXX (T). Do XXX things (A), resulting in XXX results (R)

Then do the same when describing the highlights of the project, for example

Due to the reason of project XXX (S), I need to improve XXX (T), and then conduct XXX processing (A). Finally, XXX result is produced, and the data comparison is XXX (R).

Overall, it will appear that you are thoughtful, and have action, can create value for the enterprise, which is also one of the most critical indicators for the interviewer to assess candidates.

4. Interview etiquette

In the last chapter, I will give you my advice on interview etiquette.

  • Take care of your appearance and don’t go to an interview looking sloppy, like wearing slippers
  • Before the interview, do your homework and take the time to find out about the company and the needs of the position
  • Be confident when you go into an interview
  • Pause for thought during the interview, but don’t keep pausing and don’t stammer over questions
  • Don’t interrupt at the drop of a hat
  • Be humble at all times
  • Pay attention during the interview. Make eye contact with the interviewer and don’t look away. This is a sign of basic respect
  • Keep your eyes open during the interview. If the interviewer isn’t interested in what you’re talking about, change the subject or end it
  • Use appropriate body language to make your point during the interview
  • At the end of the interview, thank the interviewer for the interview and shake his or her hand (it may seem like polite, but this is basic etiquette)

The above is my own collation of some interview related to all the content, in fact, these content is not only applicable to the front-end interview, I think at least all the technical interview is suitable.

However, due to my limited experience and ability, some points may not be described very well, but I still hope that these contents can be more or less helpful to my friends. Of course, personal strength is the most important when it comes to the actual interview.

Finally, I wish all partners who are looking for or preparing to seek new opportunities can harvest their own satisfactory offer.

Finally, I set up a front-end communication group: 731175396, welcome friends to join