A directory

What’s the difference between a free front end and a salted fish

directory
A directory
The preface
Iii resume Preparation
Iv Interview Process
 4.1 Self-Introduction
 4.2 Technical Examination
 4.3 Ask questions of the interviewer
5 Other Sharing

The preface

Returns the directory

About the interview experience, Jsliang collated and shared content.

Iii resume Preparation

Returns the directory

Jsliang sorted out the resume in 2019, and then sorted it out again this year (2020). Welcome to compare and compare:

  • 2019 resumes
  • 2020 resumes

Iv Interview Process

Returns the directory

Technical interviews usually go through at least three rounds:

  1. Based on the interview: Mainly investigate the questions related to the basic knowledge of the job and resume, including part of the algorithm and scene design interview questions, which may involve the scenecoding.
  2. Project interview: mainly investigate the resume involved in the project, will involve your project related business knowledge, role, technology trade-off, technology and so on.
  3. HR interview: This aspect is usually the check of HR, mainly involving behavioral interview, to check whether the candidate’s values match the requirements of the company, how stable the job is, how good communication and collaboration skills are, etc.

A normal technical interview process is as follows:

  1. To introduce myself
  2. Project (technology) examination
  3. Ask questions of the interviewer

4.1 Self-Introduction

Returns the directory

A few essential elements of self-introduction:

  • Personal Information: If your previous employer is a big factory (BAT), it is best to mention your education background (985 or master’s degree or doctoral degree or CS strong school like BUPT). No one cares about other things like girlfriend or only child, so don’t take up space. This section focuses on who are you? .
  • Technical skills: Briefly introduce your technology stack. Don’t mention that you have simply used it, written a few demos or looked at the documentation. The point of this section is “What can you do? .
  • Skills: focus on the introduction of their skills, such as performance optimization, high concurrency, system architecture design or communication and coordination skills, do not exaggerate, to be realistic, this is the focus of the later investigation. This part focuses on what are you good at? .

Self-introduction time is best controlled in 1-3 minutes, such as Jsliang’s self-introduction:

Hi, my name is Jsliang.

It has been more than two years since I started front-end work in May 2018.

The technical stacks I have experienced during this period include jQuery + H5, Vue + ECharts, wechat applet, React, etc.

I have used PHP, Node and other back-end languages, MongoDB, MySQL and other databases, but because I don’t use them often, I forgot to use them.

Since 2018, I have been writing blogs on Github and Nuggets to enrich my front-end knowledge system, record problems encountered in work, and also hope to provide reference for other partners.

Right now the Nuggets have 1.3 million followers and Github has 2.3 million stars.

In May 2019, I started to contact algorithms and brush LeetCode every day.

I started from the easy difficulty and finished all the LeetCode problems in the easy difficulty by February 2020.

I started brushing by label: string, array, stack, queue, BFS, DFS, backtrace, etc.

Now I have accumulated 470+ LeetCode problem solutions, but I still have some shortcomings, such as dynamic planning, greedy algorithm, etc., I am not skilled enough, so I will continue to brush problems in the future, hoping that one day I can synchronize LeetCode to update the problem speed.

Because the business of the previous company was quite complicated, I wrote 100+ WIKI articles to help the front-end and the whole project team to sort out the business. I hope that if I work in XX factory, I can build a better team with my friends.

thank you

4.2 Technical Examination

Returns the directory

  • Not the topic must not guess, often the interviewer to you dig a hole is to hope you to guess in the wrong direction, must answer do not know
  • Don’t talk too much about anything that’s not relevant to the question at hand, and answer as many questions as you can unless the interviewer asks you to think outside the box
  • If you don’t understand the question, try asking the interviewer: Do you want to ask about XXX?
  • Be sure to refine some of these issues in advance (such as scope chains, inheritance, and prototype chains)
  • If the interviewer is asking about a particular technique and has used it in some situations or seen it used in others, explain it in context of those situations (show the interviewer that not only do you understand it, you can use it well).
  • If you are a Vue technology stack, you want to be able to dig into the source code or at least understand some of the source code analysis of others

If you are asked to describe your favorite project, answer the following questions:

  • Background: Give a brief background about the project and let the interviewer know what the project does
  • Personal Role: Let the interviewer know your role in the project
  • Difficulties: Let the interviewer know what difficulties you encountered during the development of the project
  • Solutions: What solutions do you have for the above difficulties, and how do you choose according to the business
  • Summary and precipitation: have you settled a set of general solutions after overcoming the above difficulties, and have you promoted your own solutions in large departments, etc

Jsliang lists some of the things he encountered during the interview:

  • The interview question

Of course, there will be more! Mainly jsliang feel in the review of knowledge points, if you will jsliang review of knowledge points are made, then the basic no problem sa ~

4.3 Ask questions of the interviewer

Returns the directory

First we declare a few minefields:

  • Don’t ask for results: It’s useless to ask. Most company policies don’t disclose results, and you’re embarrassing everyone
  • Never ask about salary: Never talk to a technical interviewer about salary unless the HR person is talking to you about it
  • Don’t ask technical questions: Don’t ask the interviewer technical questions that you don’t know. It’s pointless

Here are some good questions to consider:

  • What would you like me to accomplish in the first three months if I were to enter this position?
  • Why did my predecessor leave this position and what can I do better?
  • What are you looking for in an ideal candidate for this position?

5 Other Sharing

Returns the directory

Article address: Interview sharing: two years of work experience successful interview Ali P6 summary

  • Keep your mind calm and assume that it’s normal for you not to answer the first question. The interviewer won’t PASS you just because you don’t know the first question
  • Ali: What do you think you are good at
  • Be sincere and don’t cut corners
  • Be humble when interviewing

More information will be collected later, so this is the interview experience.


Jsliang’s document library is licensed by Junrong Liang under the Creative Commons Attribution – Non-commercial – Share alike 4.0 International License. Based on the github.com/LiangJunron… On the creation of works. Outside of this license agreement authorized access can be from creativecommons.org/licenses/by… Obtained.