Writing in the front
Working, I think, is like falling in love, not necessarily looking for the rich handsome or white rich beautiful, we can confirm each other’s eyes are right ~ and interview confidence and salary requirements, from your solid foundation and time of thinking, accumulation and summary ~
Leaving at the end of August is actually a naked resignation, of course, probably in the original owner of the product project team I am in the collective run away, so I also left his employer for a year and a half, after all, those who stay are to fill the pit. So I spent about two days to sort out the front-end knowledge and review the products I made and some problems I encountered. And then one week interviewed about 10 companies, an a in the afternoon, every morning contains hungry yao, millet, big search, Himalayan and love to recycle these large and medium-sized factory (is in the Shanghai area) the front end of the interview, then search ebay and other companies have recommend some foreign companies, mainly personal feel interviewed a week tired, Therefore, I got the news that four companies called to tell me that the interview had passed, and then I chose a company I liked better, so I stopped the interview. Of course, the interview was abused all over the body, and some went smoothly. Therefore, I would like to make a brief summary and share with you, hoping to help you with the interview and the exploration of the front end.
Tell me about myself
And this is the way it’s usually done in interviews, 90% of the interviewers come in and say something about themselves, and 10% of the interviewers come in and say something about your project, and that’s how I usually introduce myself
I graduated from XX University of Science and Technology in software engineering. My last company was mainly engaged in XXX. I was in charge of front-end development of XXX and XXX in XXX product project team, and the main technology stack was XXX/XXX. I also regularly summarize and write technical articles to share on my blog and in the technical communityCopy the code
In fact, there is nothing here. I would like to express the following points: I majored in computer science, I am familiar with the business situation, and I will study technology and share. Of course, there are a lot of interview skills can be used, my side of the words, according to their own actual situation description ~
About your resume
Here the interviewer basically won’t actually catch a lot of you introduced himself as the point of the interview, because his eyes tend to stare at your resume, and scan your resume, so I recommend resume write about your professional skills, work experience and project experience, personal items, the other can write all write up, suggest try to clarify things, multi-purpose data expression, Results oriented (of course, there is no good standard for this, just a personal opinion). If there is a good open source project to put on the resume, I will post some of my own description here (if you need to see my resume, please go to github).
The professional skills, must not have dug a pit for oneself, not clear or almost forgotten things don’t wrote (I have wrote digging holes, some of you got the certificate, such as intermediate software engineer, Linux network administrator authentication, then have a the interviewer asked me the Linux operating, I leave the last sentence, end embarrassed atmosphere). Personal advice is not full of a technical knowledge grasp, do not write proficient, the interviewer see this word, often will test you in the end is not proficient, or bragging force. So write skilled, familiar with, understand, understand…. To describe your technology stack in a more modest and dignified way.
Next can write personal item, if your company is not very prominent, and in the company to do project is not very bright, can only rely on their own open source to save yourself (ps: in fact my so-called in making things a nothing important also, are all very simple little demo, but the nuggets friends brother gave great support, At present, the star has accumulated 300+, you can directly visit my Github to have a look)
A resume
For job opportunities, one is mainly a technical community, the other is a job platform, friends can also tweet
For this, the author is not in a lot of online job platform, put their resume, mainly naked resignation, so resume or to hang about the job platform, mainly hanging boss direct hire, hunting hire these two platforms, the other hook…. Either way. To be honest, the two platforms of Boss Direct hire and Liepin are highly efficient. You can receive 20-30 messages every day once you put them on the platform. Many headhunting services of Liepin are also good. In boss direct hire, I basically saw the HR or front end personnel of the large and medium-sized factory sent me a message, and THEN I replied the message, chatting well and giving them the resume, something like this. If you see a company you like, take the initiative to reach out to HR
The interview
For the interview, divided into written and non-written, divided into the basic and professional inspection. Generally speaking, large factories value the foundation is not solid, small factories relatively inspect the skill level of a little more. Comb, nuggets of small volume has a “Web front-end interview guide and high frequency examination questions analysis” recommended a look, of course, I also bought, the content is good, MOOC network also has a few videos can, but for each basic knowledge points to add some of their own ideas and thinking will be better
Written test, basically test is some use of CSS, SOME basic JS, some simple algorithm questions, of course, there are computer based, back-end basis, and browser related. For projects, they will take your specific projects and analyze your understanding of technology and business from simple to deep. Here is my summary of some of the written tests and questions I encountered:
CSS
1, CSS selection weight (you can according to the normal description, suggest to add some knowledge in the framework, such as vue style related knowledge, such as vue scoped principle and penetration method? PostCSS translation implementation is definitely next.
2, handwriting some semicircles, gardens, triangles, trapezoids… (Note is handwritten similar to this, triangle principle [pseudo class can also achieve triangle] must understand)
3, sass, less, sass, less, sass, less, sass, less, sass, less, sass, less, sass, less, sass, less, sass, less
4. What are the features of CSS3?
Box-sizing: border-box; box-sizing: border-box; Clear float (several ways to clear float, the website is so spread out to say, basically through pseudo class), BFC (principle and creation), Z-index layer (for example, do not know that layer optimization can improve rendering performance, hint: such as GPU acceleration)
6, layout: three columns, two columns, nine grid, vertical center, horizontal center, adaptive response type (solution). You should be familiar with floating, absolute positioning, Flex, table layouts, and grid layouts, all of which have their advantages and disadvantages, as well as the principles and implementation of double Swallow and Holy Grail layouts
7, mobile pixel knowledge and Viewport knowledge, such as how to display the true 1px border and 12px font size in H5 web page
. Here are only the interviews and written exams I met, and there are many more…
JS(es5/es6/es7/es8)
1, basic JS-API, judge is not an integer, the operation of the array: add, delete, change to check (check), reorganization, sorting, array shuffling, these require expert hand to write code, of course, there are several ways to achieve these
2. Create objects, New operators, event streams (bubbling and capturing), native event bindings, BOM operations (e.g., judging for Ie9 and some operations)
Prototype chains, closures, classes and inheritance (implementation inheritance before class, constructor inheritance, prototype chain inheritance, composition inheritance, their advantages and disadvantages), synchronous asynchronous
6, new features in ES6/7/8, basic directives, arrow functions, string templates, Promise (principle, scenarios used), object-oriented, data formats (set/map),async/await(principle,a CTO asked me what this function looks like packaged with Babel)….
7, modular, functional programming, the use of higher-order functions, Coriolization functions, recursion…
Browser Web related
1. Loading process, rendering process (preferably with frame chat)
2, performance optimization (loading, rendering), can cooperate with the framework, such as VUE, asynchronous component routing lazy loading implementation principle, GPU acceleration to understand this piece
3, HTTP (various status codes, such as stateless connections, pipelining, strong caching, if you ask more deeply, will ask Nginx proxy and future HTTP thinking, etc.), storage cookies, localStorge, sessionStorge, their differences, of course, you need to go deeper into this section. For example, the working process of cookie, the parameters in it, why do you say that it is not safe, like recycling when the interviewer asked me, there was an embarrassing scene
4. Cross-domain: JSONP principle, CORS, IFrame, postMessage…. , of course, also want to know the front-end framework under the cross domain, such as vue\node under the cross domain how to achieve and handle
5. Front-end rendering and server rendering (single-page SEO application, such as Server rendering, nuxt.js, was proposed after the release of Vue2.3
Do you understand)
6. Front-end monitoring (data, performance, exception monitoring, burying and reporting), request-related (such as how to encapsulate AXIOS request under VUE, what will you think)
vue
1. Basic instructions, differences between WATCH and computed, and application scenarios, event handling/event modifiers…
2, responsive principle, life cycle, rendering priority
3, component, asynchronous component, parent-child component communication, sibling component communication, the parent component calls the method of the child component, the parent component adds method to the child component, the parent component changes the style of the child component, the parent component how to pass a parameter with $to the child component, the child component to the parent component declare its existence…. Can look at element source, there are a lot of places to learn
3, Vue-Router, Hash and history implementation principle, routing lazy loading principle, let you implement a route you will have what to think
Vuex, each API, application scenarios, let you realize a state management you will think about
5. Design a tree component that can be nested indefinitely and provide documentation to use it
6. What problems did you encounter during development and how did you solve them
.
Vue words main test principle more, require to see the source code, of course, there are a lot of summary of good resources online, as especially greatly recommended
Recommended “Vue technology insider”, “Vue. Js technology revealed”, of course, digging gold pamphlet “analysis of Vue. Js internal operation mechanism” is also written very well, worth a quick understanding, but it is best to see their own source
Node, Webpack, React, Angular, wechat official account, applets
These are all questions, because I am familiar with VUE in my resume, so I basically ask questions about VUE, other things are similar, such as Node two popular framework (KOA/Express),webpack inside and configure the front-end development environment, the time relationship is not a column.
other
1. What would you think if you were asked to design a front-end framework (usually asked by ctos)
Do you have any questions for me? Usually I would say that I want to know about the project business and technical stack of the position and the team. What role do I play in the team, and simply give me an evaluation and suggestion for this interview
3. What do you do outside of work? My answers are basically fixed, including running for half an hour every day and playing basketball on weekends (some interviewers say he also likes playing basketball). Besides these, I go to the technology community, look at the front-end technology, realize my own small ideas, and write articles on my website and the technology community to share….
Why did you leave your last company? Due to the business adjustment of the previous company, the staff of the project team stayed idle for a long time to do maintenance work instead of R & D work. I felt that MY personal value was not reflected, so I resigned
What would your former colleagues say about you? .
conclusion
In fact, there are deep memories of the interview
A, hungry? Interview, the process is very good, the interviewer is hungry? A front head, before share salon will be attended his technology, the whole interview process was easy, the back, he was speaking, I’d better take your programming ability, an online compiler, there is no code hinting, I am a man of a code prompt rely on… Result is cool, after the interview, he and I talked a lot, I also have to prepare before the measure of hungry? A few bugs on the website and app front end and some optimization, and their open source to communicate their views and his works, he has recommended to see “refactoring” “the path to clean code” of the code, have left WeChat, He said he could come back for an interview half a year later, and he would also optimize and let the department deal with the relevant questions I raised
Second, love recycling, this interview is relatively bad, not fully prepared, very knowledge, but not deep understanding, two interviewers take turns to interview me, resulting in one of the interviewers gave me the evaluation of knowledge breadth, depth. At the end of the conversation, another interviewer asked me where I was from, and then found that it was a fellow villager, and the feelings of fellow villager. Finally, he also combed the front-end knowledge with me, standing at a higher Angle and I talked about the front-end, and also left each other wechat, the result needless to say cool cool ~
Three, the front-end knowledge is patchy, in fact, most see knowledge with respect to ok, but must be to have their own thinking to answer this question, if we can only according to the summary of others may be you can’t digest, if your answer is the same as baidu to, most interviewers will feel not so good, so want to understand the extent of up to answer the question. Always write your own code, and try not to rely on code prompts.
Fourth, front-end knowledge, framework are a lot of, in fact, I think it is not necessary to be proficient, in-depth understanding of one or two technology stack is OK, the premise must be solid foundation, just like love recycle interviewer’s evaluation of me: There is no breadth of knowledge depth, although this evaluation is a little ruthless, but it does also whip me, to return to the basics, return to JS and data structure, read the front-end framework source code, and play node~
Five, the interview is not clear or don’t know of knowledge, you don’t panic, first to an embarrassing and polite smile, and say in this knowledge is in fact I long ago seen, now because the interview a little panic, in a short period of time can’t sum up a good answer, but I am thinking about to say something, if it is not clear, just say not clear. Everyone has a blind spot of knowledge, the interviewer also asked not to say to you what will, of course, if you the whole process of the interview, ask the question, do you know what you feel in the heart can answer very well, but I don’t suggest you all answer is good, save one or two topic performance is not so perfect answer, reason is very simple, a person should never be too strong, Some interviewers might think you’re a bit “crazy” and not easy to get along with, if you know what I mean
Six, the front is a sensitive animal, can usually around giant website and look at their products, the interesting places, to learn to write the corresponding code, and imitating the technical community and cattle people blog often see, of course, to understand the common sense, such as the recent vue/NPM/node version (stable) updated to how much, updated those things out. Interview confidence and salary requirements, from your solid foundation and time to think, accumulation and summary ~
I have sorted out a document for the js written test, and I have sorted out part of other knowledge points (but not necessarily the correct and best answers), including my own resume. If you are interested, you can move to my Github warehouse
Front-end-notes, online document pages can also be viewed as dictionaries, constantly updated…
Thank you for your correction. I also look forward to communicating with you in the comments section or submitting issues on Github. Finally, I wish you can harvest your desired offer in the job interview
Ps: If any front-end students want to change positions, please send your resume to my personal email: [email protected]. If my assessment is ok, you can push it inward. Of course, other companies can recommend it for you, and the coordinate is limited to Shanghai ~
For more information about digg autumn job essay campaign 👉Autumn recruit job, writing essay with a gifts | the nuggets technology