Link to Nealyang/personalBlog

There are a lot of articles about interview in the market, but most of them analyze the problem from the perspective of the applicant, but not from the perspective of the recruiter. This article will share from my personal recruitment experience about the front end of some thoughts and their own perceptions. All thoughts below are personal thoughts of the author and do not represent any. If there is anything wrong, please point out

In fact, have to say, looking for a job, really seven points strength, three points luck. Different interviewers have different priorities, so don’t let one failure get you lost.

The interview process

This article will not make a detailed analysis of the answers to the interview questions. For each specific knowledge point, the author will try to update a relevant knowledge point article two weeks later in the public full stack front selection, welcome attention, discussion and sharing. Below is a summary technical article that the author plans to write later.

To introduce myself

Basic interview this is the inevitable opening, I have interviewed a few people in the company, the peak of the basic every night to interview one or two, heard a variety of opening introduction. Here are a few of my likes and dislikes as an interviewer.

My name is XXX, graduated from (currently working in) XXX, from XXX, technology stack XXXX, like XXX…

Like the above self introduction, in fact, many are written on the resume, and even a lot of I do not care about.

All I care about is your ability to match my position. Therefore, such a brief introduction, the author is hoping to be short. When I’m interviewing, I like to hear what great projects I’ve worked on, how hard it was, how I tackled it, what you learned from it, and even how it improved the team, the department, and even the company. Or you can introduce what awards you have won in school, what it means and what you have grown.

The above introduction will actually impress the interviewer, because it will show you how much you think about the project and how much it has taught you.

Highlight: We all know that the next part of the interview is to ask questions about knowledge, so it is appropriate to throw out the technical difficulties. Arouse the interviewer’s interest and ask questions. We should learn to master the pace of the interview, don’t always be led by the interviewer

To this point, there are basically two branches:

  • The interviewer is interested in your project (award) and will follow up and ask for technical implementation details. (So here oneself must not brag x, and then not back)
  • The interviewer is not very interested (and possibly a technical blind spot, as I was). Haha) and ask yourself some of the questions you’ve prepared…

It should be noted here that when the author interviews the students applying for P7, he will like your thinking about this project more, such as asking the title:

  • Existing technical solutions, industry comparison
  • What is the most valuable project you have done or optimization you have initiated? Why is that? How does it help the business?
  • Can you duplicate what you’ve done for another team?
  • Horizontal and market known XXX solutions, what is your advantage?

These thoughts, in fact, I am not up to the present. However, this is not necessarily required of the interviewer, and the dimensions of the project are not so deep. I’ve never eaten pork before and I’ve never seen a pig run.

The interview questions

As mentioned above, if a candidate brings up a technical direction or technical point that interests me during an interview, I’m more likely to ask. When it comes to technical areas where I’m not very good, I don’t ask for technical details.

The whole side of the time is probably about half an hour, plus before and after the introduction, the basic topic on four or five questions. I do not have a fixed interview questions, usually based on the applicant’s experience and ask. Here is an example of the introduction above without any bright spot at all (basically cold half), the author like to ask a kind of questions.

Assessment of Basic Questions

JavaScript object-oriented understanding and perception

The basic questions at the beginning of the question are relatively simple and assessment of the basis, such as sometimes the author of the first question generally asked: ** JavaScript object-oriented understanding and perception **, the topic is very open. Gave you a big enough stage to show off.

Say this question in my heart when interviewing someone to score points:

  • First of all, I definitely need you to tell me what object orientation is, what features object orientation has, and an explanation of these features.
  • How JavaScript implements features such as encapsulation, inheritance, polymorphism. If you can explain how many implementations there are and what the pros and cons are for each of these three things. And what the popular solutions have been in recent years. That’s a plus, like inheritance. Class inheritance, constructor inheritance, composition inheritance, prototype inheritance, parasitic composition inheritance, etc., give a general idea and pros and cons, then talk about the implementation of extends or mixins, and you can even derive modularity from JavaScript and even why TS is so popular today. So you can say that this part of the solution is very good.
  • After answering the question of object orientation in JavaScript, is it possible to derive the reason why object orientation is needed? And the preemptive thinking about highly cohesive, low-coupling software design? What’s a big summary of this?

To sum up, it is not difficult to see that the more basic and open the topic, it can be a trap, but also can be an opportunity. Because a question can feel the foundation that apply for all aspects really is solid.

The author of the following topic basically like according to the applicant’s answer of the last question or even the knowledge point that the applicant casually said, continue to ask. However, since this is a shared article, this form is difficult to demonstrate. Let’s move on to the next topic.

Browser input URL to the page display, specific what happened can expand to say

Broken in the above topic knowledge point. The second question I usually like to ask some of the investigation can be deep or shallow some questions, injection: the browser input URL to the page display, what specifically happened can be expanded to say

The basic answer is yes

  • Enter the URL in the browser address bar
  • The browser parses the URL to obtain the protocol, host, port, and path
  • The browser assembles an HTTP (GET) request packet
  • The browser obtains the host IP address
  • Open a socket and set up a TCP link with the destination IP address
  • HTTP requests are sent after the TCP link is established
  • The server sends the response packet back to the browser through THE TCP connection, and the browser receives the HTTP response
  • Determine what to do based on the type of resource (assuming the resource is an HTML document)
  • Parse HTML documents, build DOM trees, download resources, construct CSSOM trees, execute JS scripts
  • Finally, show it to the user

If the candidate only goes back to the steps above and doesn’t mention a lot of the key steps (things you need to know at the front end), you’re halfway done. Here is a brief description of what I feel you should explain in detail.

  • The browser sends a request. Do you need to check the cache? Do request resources in cache and fresh, jump to the transcoding step? If the resource has been cached, is it fresh? How to check? What is the difference between http1.0 and HTTP1.1? What is the priority of these fields?
  • What is the process of browser parsing url fetching protocol? Can you introduce DNS recursive query?
  • Can you describe the three-way handshake for establishing a TCP link
  • The server received the request. Does the server need to check the cache? What fields are checked? What kind of caches need to be checked by the server?
  • After the server sends a TCP connection and the browser receives an HTTP response, what is the basis for deciding whether to close the connection? What are the four waves that close TCP?
  • Does the browser need to check the status code? What status codes are available? (Author’s high frequency test code: 304, 200)
  • When parsing, how to parse and whether there is an order. (Redraw and rearrange the high-frequency exam questions here)
  • In summary, as above, can we give some basic website optimization methods??

Each step of the above questions will be the next interview question.

The specific knowledge point introduction, is not the main content of this article, here is not much.

Problem solving ability test

In fact, the above two (big) problem, the basic foundation, network, browser, JS implementation, optimization has been assessed. For a job model of P6, another item is the ability to solve problems.

In fact, here is generally a problem, and then you give some of your implementation ideas, here do not do the distance, because it is too open!

Such as:

  • Do you have any optimizations for the frequent events that I now need to listen for
  • The realization idea of buried point
  • Non-recursive binary tree traversal
  • File upload breakpoint and resume
  • Assessment of application scenarios of design modes

, etc.

Remember: this kind of questions, must not say no, don’t know. Even if you really do not know, but also to give a general solution and implementation of the train of thought. Even if it’s wrong! Be sure to talk about your thought process.

Assessment of advanced questions

In interviews P6 and P7, an advanced question is usually followed (depending on the specific situation of the applicant).

There is no open answer in fact, so here the author will not elaborate on what to think and want to hear the point. As long as you’re right. Actually

  • VUE bidirectional binding principle
  • VUE/React Diff algorithm
  • Implementation of existing state management
  • Implementation of Loader and Plugin in WebPack
  • Implementation of webPack Lite
  • Implementation of KOA and Express middleware
  • Understanding and principle of React Fiber
  • Principles and implementation ideas of front-end build tools, Vue-CLI, create-React-app
  • Wait…

The end of the link

Half an hour, basically can only ask four or five questions so that, to be honest, the examination of the questions can account for about 90% of the reference, and the other 10% May be words and feelings. So here’s a bad feeling about the end:

Finally, is there anything you want to ask me

I would like to ask whether I can pass the interview. I don’t care about the salary. I am willing to learn, and I especially hope to study and experience together with Daniel in XXX.

Honestly, I’ve heard that many times before. If you’re watching and you hit this. I want to say, in fact, the company hired us to come in, is to move bricks, not for us to learn. Learn for your own sake, not for the company. Say this kind of words, too give oneself discount!

What do you want to ask me at the end of the interview

  • I care more about my technical direction and career development. Could you please briefly introduce my future work content and my value in the team if I get the job interview in your company?
  • I want to know how much the company attaches to the front end and how the team thinks about technology in the big front end era

I’m probably asking, what do I do for this position? Does it have value in the company? Does it fit with my own career and technical plans?

So! The interviewer will think, well, this guy is thinking ~~~ furthermore, if the interviewer gives you a very detailed introduction, then in fact, from the side, he is very satisfied with you! It’s time for the interviewer to start showing off

Like, doctor, is my wife having a boy or a girl? Can’t ask!! This is the policy

But: doctor, I this child birth I give him name to call wang Gang egg you see appropriate? _ Well… It’s not a good fit. It’s probably a girl

The last

In fact, I want to say that the interview, not only depends on luck and strength, in fact, sometimes it is also a game of psychology.

Every answer you give can lead to the next interview question. Consciously or unconsciously leaving a funnel of answers is also a way to beat.

If the interviewer asks a question and you can’t grasp what the interviewer is trying to tell you, it’s probably not cool

Secondly, I would like to say that the answers to the open-ended basic questions I mentioned above should not be misunderstood as more answers are better. Do not answer a question for half an hour, there is no need! Just stop at it and prove you’ve thought about it and have the knowledge. Don’t bore the interviewer with your answers.

And then, the key to getting your foot in the door: your resume. Not so much to say, not nothing to say.

In short: It’s boring for interviewers to sift through resumes. Basically, it’s passed at a glance, and it doesn’t go beyond the 40s on a resume.

So:

  • Keep your resume clean, concise, and concise. Really don’t densely are words, not so much patience to see.
  • Highlight, can be bold or color. For example: its own open-source React framework
  • Resume is an introduction but also a transcript, since it is a transcript, the results must be vomit: open source project 15K STAR, promote the company’s technology construction and so on
  • Have to say, famous school and big factory background. Very eyes.

Finally, autumn recruitment began, wish all the students looking for jobs, can get the offer smoothly! Come on ~

Do you know

Yeah, it’s always an AD at the end

Ali autumn recruit

Ali autumn recruit has officially started!!

Bu introduction please see: extra! Extra! Ali auction early autumn move!!

In short! 2020 class graduate, kneel beg resume AH I told you the interview question, still don’t send a resume to come over: [email protected]

Study and communication

Pay attention to the public number: [full stack front-end selection] daily to get good recommendations. Can also join the group, study and exchange together ~~