Too long to look at the version

  • For internship (or even campus) recruitment, project experience may be the ticket to an interview, but the foundation is definitely the ticket.
  • Even for internships, whiteboard coding is likely to become a standard part of mainstream interviews. Be aware of your ability to do this or you won’t be able to do it without an IDE.
  • You must have a correct assessment of your true strength. A simple way to assess your ability is to say that your true ability level is about 50 percent or less of what you think you are.
  • Interview is a very tiring thing, to find their own position, avoid the sea.

Full Interview Review

Interview Process Record

It should be noted in advance that the process records are all from my experience of this interview, and others may be different.

Before an interview, there is usually an email notification that contains some important information that needs to be reviewed carefully. This is a video interview, so I found a quiet place in advance and made sure there was no problem with the interview equipment. Personally, IT is a sign of respect to “show up” half an hour before the interview.

After the interview begins, the first step is to introduce yourself. The interviewer may not have seen the resume in advance or just skimmed it, so it’s important to prepare a 3-5 minute introduction about yourself before the interview. Here, the interviewer asked me to focus on the problems I encountered in the project (excluding business logic) and how I solved them. As you can see from the “business logic out of the box” requirement, it’s not the project itself that matters, it’s how you glean from the project, even in a toy demo, your ability to solve problems.

After introducing myself, I will transition to the interview questions. There are two types of interview questions. One is to pick a piece of code and ask you to answer it. The other is the whiteboard code mentioned before, online joke tore code, the topic is not very difficult, but it is a test of basic skills, heavy IDEer may raise his hands at a loss (such as MYSELF QWQ). In the interview questions, even if you don’t know the questions, you can also talk about the information you can grasp, and the interviewer will give some timely hints.

After the interview, I took the opportunity to ask the interviewer a question that had been on my mind for a long time.

Summary of interview research points

Here is just a brief record of the research points that individuals encounter in the front-end interview:

Position and display, event mechanism, DOM, capture bubble, this and scope, prototype chain, ES6 (understand), vue’s bidirectional binding principle (preferably useful, to some extent to check the source code understanding), basic data structure… And so on.

Among them, one is dom, two are this and scope, one is data structure, and the others are all examined in the way of concept questions.

The following lessons can be drawn:

  • Js foundation is the top priority, and the front-end algorithm requirements are basically not particularly high, the basic data structure is firmly mastered no problem. In addition to the front end, brush algorithm is best used JS.
  • The interviewer isn’t going to delve into areas you haven’t had much exposure to; However, for the viral Vue framework, it is best to have an understanding and experience, and even in-depth source code.
  • An obvious phenomenon is that you know a concept, but you can’t necessarily explain it clearly; You may seem to know a concept carefully, but you may not be able to tell why it is when it is really examined. The best way to solve this problem is to blog.
  • Knowledge of websocket, NodeJS, etc. is not examined, and the interview requirements at this stage are not as high as those of online communication.

Reflection and planning

I have the following reflections on the various problems in this interview:

  1. Figure out what your technical direction is and then dig deep. I thought it would be cool to have multiple careers in technology, but now I find it easy to become an API user. Be sure to memorize the basis, in-depth principle, understand the source code.
  2. Be sure to have a technical blog. The knowledge points you can answer in this interview are all the knowledge recorded in blogs. On the other hand, a tech blog should not simply be a stack of knowledge points, but as many points as possible. With the mindset that I’m writing a tutorial, you’ll feel compelled to make your blog as detailed and comprehensive as possible.
  3. For their own projects, to consciously analyze and summarize, the interview process can be summed up these questions thrown out, there are always one or two will be the interviewer as a point of assessment.

Here’s the plan:

  1. Abandon the fickle mentality, the current stage should be the front-end development of its main technology stack and in-depth direction.
  2. As far as the front end is concerned, there’s nothing like building your own platform to exercise your skills. I plan to start my own blog from scratch after I finish my project, probably this summer.
  3. Technology blogs are more eager than new project plans. Mandatory weekly technical reviews from now on; Or keep reading technical books and taking notes.

BTW

In the interview process, the interviewer gave me a lot of advice, asking me to deepen the foundation through classic books, combined with the advice given to me by other seniors, listed the following three books:

  • JavaScript Advanced programming (comprehensive and broad, suitable for review)
  • JavaScript DOM Programming Art (essential for DOM understanding)
  • JavaScript you didn’t know (focus on the hard and hard aspects of JS, including prototype chains, closures, etc.)

These books are ready for you too!

How to get information: Join the fan group 963944895, click to join the group chat, private message administrator can