Preface
Recently, a friend went to an interview and got feedback that his "front-end foundation" was not good. I suddenly think this is a very interesting question. For example, for a martial artist, if you let him do a horse stance for an hour, you will know if his foundation is good; for a singer, if you ask him to sing and sight-read, you will know his foundation. OK.
In technical interviews, everyone is often the first few companies to face the cannon fodder, and then as the interview process continues to brush up questions or memorize concepts, after memorizing the HTTP protocol concepts, network attacks, and asynchronous standards, they finally face the Nth. I got an offer when I was at home.
The problem is that just a few weeks does not actually increase much knowledge and experience, but it can easily change from "bad foundation" to "solid foundation". After all, we have a problem with the definition of "foundation". Or is there a problem with the "basic" evaluation criteria?
It stands to reason that there should be an open standard for basic investigation, that is, whether you know the topic in advance, it will hardly affect the score obtained, so for the front-end, what is the foundation that can be consolidated after long-term accumulation? How should we quantify and judge it during the interview?
Generally, people will encounter the kind of knowledge that can know the answer to the question asked by Google, especially when interviewing the junior front-end. In fact, facing this kind of interviewer is very simple:
1. Brush the questions
2. Write down all the questions asked by the last interviewer, go back to check it, and repeat it so that you can deal with this bunch of interviewers.
In fact, in the final analysis, there are two important points that the interviewer values:
1. What knowledge does
the interviewer know at present 2. Can the interviewer handle our job in the future?
Most interviewers will choose 1, and I may also be related to my experience and characteristics. Personally, I will pay more attention to 2. I have interviewed many recent graduates, all of them are good universities in China. I found that my philosophy is very different from that of other interviewers. Some two-sided interviewers asked me, this person has never heard of AMD, why don't you reject him. Ok? Is AMD important, do I have to reject it if I don’t know? Isn't this a contract between two functions? It's fast to learn under the guidance. Don't you who haven't stepped on the pit? I have stepped on it. Does your team have no code review? In fact, it is because I pay more attention to other aspects of the interviewer's characteristics. The basics of the front-end, to be honest, will basically be enough after two months of teaching. If you never plan to teach a new person, just assume I didn't say it. I am more concerned about his English level, whether he has programming thinking, whether he can communicate effectively with me, whether he will immediately report back to me when he encounters a problem instead of doing it, whether he can quickly grasp the knowledge that he does not currently do. Will it be liked by people in the team? Also, to put it bluntly, some front-end teams are not good at training newcomers, trying to recruit a mid-level front-end at the price of newcomers. These teams also want to lose their minds, give up early.
judgment
Back to the topic, if you really want to test a person's level. The first step is to examine the basic programming foundation and ask a few basic programming questions, which may or may not be related to the front end. For example, how garbage collection is roughly done, and what setTimeout roughly does (saying that it will execute the callback in another thread and kill it directly).
The second step is to examine the knowledge and ask about the basic knowledge of http and tcp, how does dns work, or the implementation principles of commonly used frameworks, and see if the candidate cares about nothing but his own one-third of the land.
The third step is to examine the ability of hold business logic. Starting from a simple registration page or query page, let’s first talk about the basic structure of the code, and then increase the requirements, performance, reliability, and security layers to see if it can be fast Feedback from the solution. Either you have done it before, or something of this kind of complexity is a small case for him.
The first three steps are okay. Basically, it means that the candidate is already okay, but to what extent, I don’t know. If you want to find something more powerful, add a fourth step, highlight project investigation.
In general, if the interviewer examines ideas, he will start with the projects you have actually done, examine your actual coding ability, and let you type codes on the computer, depending on what editor, plug-ins, coding habits, etc. you use. So when we answer the interviewer’s questions, we have a clear logical idea. It’s good to know that we are talking to the interviewer about the project and technology. The editor organizes a set of front-end interview questions for the front-end interview questions and shares them for free. Everyone, I hope it will be helpful to the friends who go to the interview!
Due to space reasons, if you need the complete PDF of the above study notes, you can click here to collect it for free. It
is not easy to organize it. Friends who feel helpful can help like and share and support Xiaobian~ Xiaobian is here to thank you all!
For more front-end learning related materials, click here to get free