preface
From a certain point of view, “easy” here is not easy, because without certain technical skills, the interview is still difficult, but from another point of view, you are not P7, P8, P9, P10, P11… If you are just an ordinary engineer working in the front line, do not need to work for many years accumulated network and management experience, do not necessarily need a strong business ability, as long as you are outstanding in some aspects of technology, you will have a chance, is it much easier to think that?
To prepare
If you are interviewing with a large company (using my personal experience on Taobao as an example), preparation is definitely required, and even the technical geeks on the Internet are not prepared to answer specific technical questions when they are disconnected from their busy business projects. After all, it’s not like they have enough time to look up, digest and summarize when they write articles or answer questions.
For example, I used to learn JavaScript, saw Yuba “JavaScript deep series” Hu, I felt that the author is really a solid technical skills, and then had the honor to communicate with Yuba before the interview, he told me that he was in order to prepare for the interview, the article he wrote again, I thought it was because these people were serious, and then he told me it was because he forgot… Forget to… (/ / \ *)
Well, back to the point, so what are we going to prepare? It is important to know that technical questions are not the most important thing to prepare for.
Prepare scope
Front knowledge unimportant things, even if you want to master, is also insufficient, unable to do to prepare the interview, also is such, no one will be proficient in all aspects, said proficient in all aspects are very shallow, the interviewer also know it very well, actually, after all, also came from the grandson grandpa, especially interviewers tend to be the head of each technical team, Especially understand that team members are not good at the same aspects, the interview will not require interviewees to be proficient in all aspects, part of the in-depth understanding, part of the familiarity, and part of the understanding.
Therefore, for the interviewees, they may not be fully prepared for the interview. They can answer all the questions of algorithm, React principle, Vue source code, game engine, and EcmaScript specification in a simple way. Besides, they can show some potential as a leader and get the interviewers’ surprise… Wake up, kid. You may be better than your interviewer in skills, but you certainly won’t be better in knowledge.
And hold such fantasy, often in preparation for the interview process is very painful, because a lot of knowledge and not your book, check the data will be able to understand, not so long time to practice, to think, digest, you is difficult to have a deep understanding, to understand will attend, back a knowledge. It’s not a problem to memorize knowledge points, but if you say that you are awesome, ask a few in-depth questions during the interview, and your understanding level will be seen through, which will easily drag down the interviewer’s impression of you.
Therefore, if you want to prepare, the first thing you should do is to cut down the range of knowledge you need to prepare, and make in-depth exploration and preparation based on your actual business and the technology you are good at or interested in. For example, I chose the aspects I am good at, focusing on the knowledge of JavaScript, React, HTTP and other aspects. What algorithm, Canvas, Vue, this knowledge has not seen a bit, maybe you think, what if you are asked?
If asked, just say no! Most not for the interviewer is not the point deduction, but also can quickly help the interviewer to find out the direction of the interviewer is good at the most hate is clearly not familiar, but also want to freely hold, make yourself tall, wide in, has the probe, and then by the interviewer pester, finally only embarrassed said in fact I at ordinary times what to do or what is more… The interviewer must also be MMP in the mind, not cooked what bullshit!
How to prepare
Well, back to the point, you’ve got the scope, so how do you prepare?
Since chose real business, and be good at or interested in technology, you must know something you know you don’t know knowledge, such as I am a new man, new to the study of the front end though I don’t understand about the concept of prototype and prototype chain, but I have heard of, know you don’t know the prototype chain, then I can keep track the keywords “prototype”, Such key words you can remember a lot of the early, recorded after the class, then search on Google, the Denver nuggets, zhihu related articles, give priority to find some high traffic and high praise of the article or answer read and digest, think they understand about, trying to the role of an interviewer or introduce to the couple to comb these knowledge, It’s best to record it in time while combing.
In addition, when learning, you will certainly encounter many new knowledge points that you do not know, and then record them down. As long as you determine your scope, the new knowledge points will be less and less.
Maybe you will think, this preparation is so simple, but when it comes to preparing, such as preparing React, there are so many knowledge points, DON’t I have to prepare for at least one or two months?
A little more specific, such as the study of virtual DOM implementation, in the usual work, at least a month?
In fact, it is really, if you lack the foundation, prepare for a few months is really needed, otherwise you really think there is what secrets can easily take a variety of big factory offer?
But you also want to know, this is already a relatively fast road, not detours is the fastest way.
Also, if you really spend a month preparing just one implementation of the virtual DOM and are very clear about the DIff algorithm and the shortest editing algorithm, seriously, I’m going to have to talk about it every time!
Prepare degree
What to prepare and how to prepare. To what extent?
Most of the information you know is ok, but if all the information is just to know, such preparation is not enough.
Is there no doubt in the process of learning? Have you ever tried to dig deeper when in doubt?
When doing the project, have you ever thought about what function this project would have? Have you tried to implement it, even if you have to write a plug-in to do it?
When many people cooperate, do you feel that some aspects of the process need to be optimized, and have you ever thought about how to optimize and speed up the cooperation efficiency?
During team building, have you ever felt that there was something not done well in the team, whether it was the specification, or the scaffolding, or the component library, or some technical precipitation, and have you ever thought about helping the team to do better?
If you have these ideas, please cherish them and work on them, because you don’t need many of them, just a few, and they will take up less than 5% of your study and work time, but they will make up 50% of your interview.
case
In my opinion, it is to prepare a case that can show your outstanding characteristics. Since it is a case, you need to prepare in advance, and two need to start from your actual experience.
The ideas mentioned above, once you have worked hard to achieve, are very suitable for rewriting the case.
The basic structure of the case is what problems you encountered at that time, how to solve them, and what you finally gained, or what problems you were curious about when you were studying, and then you went into deep research to find out the reasons.
This is very important, but also very difficult, first of all, you have to start from your own business or the problem that you are interested in, and second of all, you have to try to solve or study the problem.
Two slightly specific examples, such as you develop a scaffolding, scaffold cannot fully meet the needs of you, however, you would have thought that if can realize the function of an automatic, various solutions and then you find over the Internet is not very satisfied, then you go to study, spent a week time to write a plug-in, released on the NPM, The problem was solved beautifully, and the plug-in was applied to various projects in the company.
Or when I was learning JavaScript chaos, I saw a way of implementing math.random (), which was amazing, but people said it didn’t really implement chaos. To get to the bottom of it, I delved into the V8 source code. Finally understand that the problem is caused by the V8 insertion sorting algorithm, (this specific reason can refer to Hu Yuda “JavaScript topic disorderly order”)
This is the basic routine. The more in-depth the solution or research, the better. These real three-dimensional examples will greatly improve your impression with the interviewer.
The interview
What is an interview? If you Google this question, you’ll get this definition:
Interview is a kind of personnel selection method that scientifically evaluates the ability, personality and other factors of the interviewee through the two-way communication method of face-to-face observation and conversation between the examiner and the interviewee under a specific scenario.
Although it is written on the basis of seemingly abstract things such as ability quality, personality quality, in fact, it is just three points:
- The technical ability is up to standard, able to complete the daily work of the team
- Make people want to be around them
- Will stay with the company for a long time
On top of that, it’s a big plus if you’ve had a few years and have demonstrated a good ability to learn, or a passion for technology, and it’s a big plus if you’ve had a long career and have a broader view of technology, contacts and management experience.
As for the first point, to complete the current work in the team, it is not necessary for the interviewer to match the technology stack of the team. For example, the main technology stack of the team is React. If you have a good Vue, as long as you are not biased against technology, it is still ok. The real question, however, is whether the candidate can demonstrate deep research in situations where the interviewer is not familiar, and whether he or she is open to starting over and relearning when the technology stack does not match.
For the second point, let a person willing to live with, because for the interviewer, recruit is not only a subordinate, or colleagues, to integrate into the team is a very important thing, for the interviewer, you need to show yourself some more bright eye traits, such as what national secondary athletes, piano level 6, secondary yuan V, bike to Tibet, and so on, These things will not only left a deep impression to the interviewer, and can let a person feel this is very interesting, is willing to live with, don’t really have, also does not have too big relationship, can be a good reflection on life first, and then said when asked simple under their own interests and hobbies, the most basic to the interviewer good attitude when I have good attitude.
About the third point, will stay in the company for a long time, if you work in a company is stable, for more than two years, the problem don’t need to worry too much, for those who frequent job-hopping, if we can sincerely explain the reason of the frequent job-hopping, willingness to work hard, believe that the interviewer and HR will also have a good understanding.
The interviewer
Communicate with the interviewer, you may feel panic, feel the interviewer good terrible one, but if you are hired after contact or ask the people around him, usually is a relatively easy-going person, think of is, the interview time is short, and from completely foreign to some strange, one party is able to determine your jobs, one thousand is a giant, Want the offer in a few minutes of our hearts, all kinds of asymmetric easily caused their inner fear, if encounter some setbacks during the interview process, it is easy to abandon directly, allow to oppressed, but if you can realize the interviewer is actually an easy-going person, in the play is not good, you can be magnanimous to admit that you are nervous, is not enough, Then regroup, guide the interview to their good aspects, the most afraid is to meet some problems, and then the momentum down, play worse and worse, finally can only heart with a little hope, hope that the interviewer can also give yourself a chance, such think of their own feel good pity.
Get back to business, in addition to the interviewer was easygoing, the level of the interviewer may also not as good as you, but should pay attention to is possible, only some of the interviewer is a main line of the team, this is good, busy all day to work overtime to do the business items, for the most part is that I do not have enough time to study technical details, and the interviewer’s the head of the team, pay more attention to management and business, These times require you to talk about some of the more in-depth details of the implementation, fully reflect your deep research in some technical aspects.
Taobao, of course, surface, for a lot of details to realize there is some people are very understanding person, but is, in fact, the interview face to face with feeling out, because there are some special people generally can’t help but show off your expertise, great god, too, for these technology technology is their specialty, these people tend to ask you details, It can also give you general knowledge based on your answers, which can lead you further. In this case, it’s up to you, but if the interviewer is just listening to you when he or she is asking for details, you can try to go into more detail.
Brush the topic
When you don’t have a clear range of skills to prepare for, brushing is tactical diligence to hide strategic laziness, and if you’re trying to find a face, the questions you scan online may not be the right ones for you…
But! Brush the problem is to want, just want clear scope.
guide
If let the interviewer to ask questions, most of the interviewers tend to bring problems to his good, this is the most dangerous, because the interviewer to ask question is often there is a clear answer, for the understanding of these questions you probably won’t be the interviewer’s understanding level, it is easy to be mastered the interviewer rhythm, So you need to start by leading the interviewer to ask questions about what you’re good at. Whether it’s your resume, your introduction, your answer, or even after acknowledging your lack of knowledge, try to guide the interviewer in the direction you’re good at or prepared to go.
resume
Your resume is very, very, very important, and the questions are going to be based on your resume, so your resume is going to largely determine the direction in which the questions are going to be asked.
So how do we write a good resume? I personally think on a standard: don’t write nonsense!
This requires that every sentence you write on your resume be meaningful and ready to be asked questions.
What is meaningful? Is it meaningful to write your name and contact information? Is it meaningful to write your horoscope? This problem is really different opinions, think carefully seems to have no meaning, but think again carefully, if my face is operation, write an Aquarius can show his young a kind of state of mind?
Is it meaningful to write about project experience, or is it meaningful to write about self-evaluation? This is the opinion of different people, I did see a lot of resume to write a self-evaluation, but in my opinion, write neither dry goods, also not convincing, as not the basis for judgment, feel more like a word, but indeed have seen some resume self-evaluation to write good, can be added points.
The hope is that as you write your resume, you’ll be able to consider what each sentence means and whether it would make more sense if you changed it to something else.
In addition to being meaningful, are you prepared to be asked questions about every sentence you write?
For example, your main technology stack is Vue, and you have participated in some development related to React in other projects. In fact, you only know some basic grammar of React, plus a little understanding of articles occasionally. Do you want to mention React in your project experience?
If I were you, I wouldn’t write a word, because maybe your interviewer knows a little bit about the React React, so he can’t ask you any in-depth questions about the React React. In fact, you don’t know much about the React React, so you end up feeling awkward about both of them, so I don’t write at all, leaving the interviewer no chance.
Of course, if the interviewer asks you a question about your React knowledge, you can say that you have been involved in a project before, and you are familiar with the basic grammar, but Vue is the most familiar with it. Compared to the interviewer, you won’t be embarrassed. It’s so much better to ask about him.
If you so gradually to streamline your resume, for the vast majority of people, you’ll soon find your resume may be even less than half a page, but it doesn’t matter, less is more, to get rid of is a kind of progress, because you get rid of those contents in the interviewer seems doesn’t make any sense, actually will not be selected on the basis of, but also spread the interviewer’s attention, It may also lead to the perception of a bad resume, causing disgust.
So what do I do when I really have nothing to write about? You can’t have a half-empty resume, can you? Seriously, it’s much more self-comforting to prepare without content, to create content that can be written on, and to fill up with meaningless content.
As a final tip, if you have done mobile work, you can print a QR code on your resume so that the interviewer can see your work directly.
To introduce myself
In Ali’s interview requirements, self-introduction is a must have the process, the interviewer can not be omitted because of the urgency of time, and self-introduction is the first step for the interviewer to directly communicate with you, you must make sure that the interviewer will ask questions in the direction you prepared.
The repeat information on the resume is needless to say, first suggestion is that after introduce yourself, directly on personal experiences, major project or technology stack, or experience of growing up in recent years, between words is best can hook up the interviewer’s questions, but don’t just list what you do, is focused on express what you do, what did I learn, harvest, It would be better if there were numbers to prove it.
The second is the introduction of the time, do not say too fluent, speed is not too fast, in the key words such as specific numbers, technology stack, it is best to pretend to think deliberately say a little slower, so that it will be more easy to attract the attention of the interviewer.
Finally the content as short as possible, it may have some common sense, because usually tell you from but actually technical interview, usually at least 40 minutes to determine whether the interviewer can pass is real a series of questions, and shorter one is don’t have to worry about time constraints, 2 it is said that the more the interviewer don’t remember, Leave the key information for the interviewer to ask questions, and the third is that it is so personality, different, did not think of it…
Answer the questions
When answering a question, don’t panic if you don’t know what to say. HMM…” Then think about whether there are relevant knowledge points to talk about, and then talk about the relevant knowledge points, to this aspect really do not know, directly admit their own deficiencies, and then talk about the direction you are good at or ready.
In fact, if you encounter a problem with implementation readiness, don’t speak too fluently, at least have a little thought and recall, there should be a lag or some.
There is also avoid to pretend to force and eager to show their own, some interviewees in order to show that they have a wide range of things, when talking about something, will pull to their own actually not familiar with the content, and then the interviewer kept asking… You don’t know what the interviewer is going to dig for, and experienced interviewers are going to ask you questions that you might not have noticed before, so try to focus on what you’re good at.
Open question
At the end of the interview, you will be asked a number of open questions, most of which are the following 14, so prepare an answer to each of the following questions. The rest is up to you.
- Your advantages
- Your shortcomings
- What books have you been reading lately? How to learn the front-end knowledge? Keep learning?
- Why work on the front end?
- Why did you leave?
- Your career plan
- Do you have any questions for me?
- One of the technical difficulties addressed by the recent project is: what pits did the project encounter? How was it solved?
- What’s the most successful sharing you’ve done recently
- What’s the coolest thing you’ve ever done
- How to understand front-end engineering?
- Front-end trends?
- Frame selection basis?
- An introduction to your team’s workflow, your position in the team, and where your skills rank
Please do not answer the above questions too truthfully, please answer with a specific case, the basic routine of the case above, can be made into an interesting joke is the best, the case can be reused in multiple questions, the real interview, please pretend as true as possible.
If you can understand these points, in fact, my interview topic is not so important, but you must be curious, so I will talk about it.
push
In fact, it is the biggest recruitment channel for Ali. We try our best to find seniors, friends and gods, and successfully promote a person at the level of P6, for example, people can get thousands of recommendation fees, so if you ask them to help with the promotion, they will generally be very happy.
But these until I come in after just know, I was push know is generally direct access to an interview, so I still get up the courage, the uneasy in zhihu sent 冴 feather greatly direct messages, because at ordinary times have focused on his blog, feel very out-going, hope can at least give me a suggestion, such as 冴 feather greatly people really good, however, not only help to modify my resume, Push in, and tell me a lot about interview skills, thank you very much.
First round of phone face
On the second day, I got a call from my interviewer at about 7 o ‘clock in the evening. Usually, the interviewer would ask if the time was right for me first. I was just going home.
So I took a glass of water, a computer, a slip of paper and a neutral pen, and found a conference room. After locking up, I began to review some systematic knowledge points written on the slip, such as performance optimization and cross-domain solutions.
At 7:32, the interviewer called. Seriously, saying 7:30 and then calling two minutes late, it’s really draining. It’s draining.
The beginning of the interview is always a self-introduction. After a word of identification, I began to introduce my project experience and the main technical stack. Then the interviewer asked me some questions and understanding about my project, and I focused on some optimization points I made based on the project and the results brought about.
Then because I had a separate “technical keyword” on my resume, they asked technical questions like
- What is a scope chain?
- The principle and application of inheritance
- Principles of the virtual DOM
Fortunately, these are some basic problems, the scope chain can see Hu yuba JavaScript in-depth series, inheritance, if you have written EventEmitter and a few native components should have experience, virtual DOM is a necessary knowledge when preparing React knowledge, Many articles can be searched directly. I had enough time to prepare, so I focused on the function of React Keys and how to calculate the specific steps from the previous array to the next array according to the operation of adding, deleting and moving an array triggered by keys. Although I was also in a daze about this algorithm, I felt that the interviewer must not have a deep understanding of this aspect, after all, this knowledge is very deep, so I spoke very decisively, I hope I was a show…
Then I asked about performance optimization. Fortunately, I was prepared.
Finally, there are some open questions, such as what else you are good at but haven’t shown, what you have learned from years of work, etc.
And finally, any questions for the interviewer? No, but I did ask, “What advice did the interviewer have for me based on my performance today?”
The evaluation given by the interviewer is “the knowledge is more systematic, but out of business”.
That’s very accurate. I almost feel ready for a second interview.
The second round of calls
If the first round was more technical, the second round was more open, mainly because interviewers move up the ranks and focus on different things.
After introducing myself, I asked questions about my technology stack. For example, I have done both mobile activity pages and BACKGROUND projects on PC. I was asked about the differences between mobile and PC and toB and toC projects. For example, when I say I wrote a set of scaffolding, do I have any secondary development? Then I talked about my experience writing plugins. Then he asked me how to promote my scaffolding to the team and stuff like that.
Then there are the open-ended questions, such as:
- 1-3 year plan
- Why did you choose to leave?
- What would you do if you stayed another year?
- How to select new technology selection?
- Front-end development Trend
- Team composition, positioning in the team, technical ranking
And finally, any questions for the interviewer? Not really, but I asked the same question again.
The advice from the interviewer was mainly on learning and technology selection, and I almost felt that I could prepare three sides.
Technical side and HR side
This time it’s the video side. Well, if there’s any advice, it’s gotta hold, gotta hold, gotta hold.
Because the interviewer not only improves the a grade, and also the industry leverage technology, for all sorts of language also has to understand, not only from the Angle of multiple languages, crushing me, but also take advantage of the interviewer forcibly returned to the topic he is good at the topic, as a result, he speak more than me, though I’m face to face the will know that I can, However, I was still out of balance, which led to my poor performance in answering HR’s questions. In short, it was a very miserable experience, and I felt angry and helpless when I looked back.
conclusion
So much for the interview, how can it be easy to get an offer from a big factory? It is necessary to summarize the study and optimize the project, and accumulate little by little to make the interview easy. But fundamentally, it is necessary to have an interest in technology and the pursuit of excellence. Only with these can those skills and methods bring into full play their value.
I recruit a cover the campaign in digging in the autumn, the autumn for full details of job searching, with a gifts | the nuggets skill in writing essay
