Free dry goods, damn it!

Open source: github.com/hzfe/awesom…

Writing background

As we have accumulated and summarized our experience in front-end interview in recent years, we all agree that there is a critical path for the review of front-end interview. Based on our internal needs, we also iterated several versions of the question bank.

From the perspective of interview, the most typical characteristic of interview is the limited time. This means that the interviewer and the candidate need to communicate as effectively as possible with limited time.

How effectively and comprehensively an interviewer can get to know a candidate is another matter. The challenge for a candidate is to respond effectively to a question within a minute or two. An effective response is one that gives a two – or three-sentence summary of the question and leads the interviewer to further questions about the key words mentioned. Based on the above writing background, we can reach two consensis:

  1. Interview time is always limited

    The duration of a general technical question is 1-3 minutes, and the duration of a technical interview is 30-60 minutes. Questions usually cover a wide range of topics.

  2. Answers to questions are usually top-down

    Give feedback with a broad response, which often leads to further questions based on key points mentioned in the candidate’s answer or other key points identified by the interviewer.

Based on some common interview cases, we can summarize the following common interview mistakes:

  • Weak interview presentation: “I know how to use those things, but I don’t speak them well in an interview.”
  • Review unclear key: “big factory interview feeling very difficult, there are a lot of things to review, also don’t know whether will be asked.”
  • Learning efficiency is low: “ALL kinds of face classics I have to see, their roughly classified the frequency of the topic, but the answer has to check again.”
  • Low interest in learning: “I have checked some materials by myself, which are very detailed and difficult. It takes a lot of time to chew on one.”

In the limited time, it is impossible to absorb and summarize the high-frequency knowledge points, and can only constantly try and error in the interview process, resulting in high opportunity cost and time cost.

What did we do

To reduce the cost of preparation and trial and error, we’ve written this book for the front-end interview scenario, intended to be a candidate’s guide to technical questions. This book is a compilation of frequent interview questions and their corresponding answers with limited length. High-frequency questions are designed to improve candidates’ review efficiency, while answers with controllable length save candidates’ reading time:

  • Combine high frequency questions in an efficient way
  • Refine interview response points

In general, this book tries its best to start from the perspective of candidates, so that candidates can quickly get reference answers to common technical questions in the interview, and also provide candidates with a relatively simple knowledge point in-depth summary.

At present, the content structure is mainly based on the interview topic + key words +1-2 minutes of summary description + directly related knowledge points. The content direction at present: basic, framework, browser, engineering, network, coding, comprehensive topics and so on. Welcome to the parade!

Suits the crowd

  • Intended to sprint the front end of the Internet factory developers, can refer to the book title and answer outline, independent in-depth study, check gaps.
  • Front-end developers who have a short interview can use this book to quickly understand frequently asked technical questions and their answers.
  • Front-end interviewers can refer to the book’s question types and topics, according to the needs of the job candidates have a gradient investigation.