(Update on March 17) This rookie ate a few interviews and “the way of front-end interview” on the stage, courage is commendable, but the heart is not sure.

I just finished the video interview this morning. The interviewer was about the same age as me and spoke in a friendly way, so the whole process was quite relaxed, except for the awkward pause when I couldn’t think of the answer.

Strike while the iron is hot to remember the interview questions to write down, for everyone to do a reference, by the way their own summary to strengthen the review.

Layout problems

Vertical center horizontal center which method is more compatible?

I said Flex?

Three-column layout (understand both horizontal and vertical columns!)

CSS doesn’t ask much, and then there are the web and JS questions

Cross domain related

The question is not deep, to solve the cross-domain solution to say once again.

Understanding of cookies

Extending to storage, I casually mentioned the difference between local storage and session storage

The cache

Strong cache and negotiated cache, implementation methods need to remember, do not like I want to suppress a long time out of a control…

Common HTTP status code

I only remembered 4 and I got 2 wrong… What goldfish memory??

Closures and application scenarios

I talked a little bit about closures and what they do. It takes a while to remember to use callback functions (preferably in depth) and avoid global contamination.

Prototypes and prototype chains and applications (handwritten code)

I was nervous to function, class will not write, cool cool

Anti-shake and throttling

I had to write the code by hand, which I had reviewed the day before. I only remember the very simple anti-shake…

New ES6 features

Let, const, arrow function, map, etc

Mobile adaptation

I only made small program before, wechat directly encapsulated, did not consider this. Then vue’s mobile project uses name = viewPort, and browser adaptation doesn’t touch much.

Browser Performance optimization

Not much. Just tell the truth and think about it, okay

webpack

Without a deep discussion, I asked if I had used Webpack and what its features were. I said that I usually just used to package the project, for the webpack module hot update impression is quite deep, can update the modified code without refreshing the browser.

Difficulties encountered in the project and how to solve them

I knew I’d be asked, but I didn’t prepare for it… I stutter, I don’t know what I’m saying. You can summarize two or three problems that are technically difficult.

Vue related

Since the project was done with VUE, the interviewer asked me if I knew anything about the implementation principle of VUE.

I talked briefly about vUE’s two-way data binding.

The interviewer also asked about data transfer between components. I said there are about three: props for parent components, BUS for sibling components, and vuex.

How to learn the front end at ordinary times? What are you going to learn next?

Random answers, read blogs, Github, redbook, etc

conclusion

About the face of 50min (originally with my level I think 15min can be asked, unexpected satisfaction? …). , basically we look at the face after much, answer will be more smooth, remember not to read a few times! Blood and tears!

The interviewer may feel that there is no good to ask, the last question is to ask me what questions, I said to my JS learning what advice?

He said that the three frameworks, Node these learning is relatively fast, the most important is the foundation (because I inherit writing is very bad), usually to write some native JS.

Then there is no and then, go back to wait for the notice, most likely cool, but as my first interview fortunately not particularly hit confidence.

Keep up the good work!