I may have rich experience as an interviewer among my peers. I participated in the technical interview of Java when I was an intern. Later, I interviewed many candidates in Tencent and another company, including school recruitment, social recruitment and outsourcing. Here to an interviewer’s point of view to talk to you in the interview how to leave a better impression to the interviewer, easier to get the Offer of the big factory. In order not to give away any interview questions, I will not cover any specific interview questions.
One, social recruitment and school recruitment interview focus
In fact, there are some differences between social recruitment and school recruitment. Taking Java as an example, social recruitment attaches more importance to in-depth understanding of Java technology system and the ability to solve problems. For example, the JVM, distributed, TCP/IP protocol keywords and other issues. In order to avoid leakage suspected here will not cite specific examples, specific we can search.
Social recruitment usually has a lot of project experience in the resume, the interviewer will pick one or two projects to ask more in-depth, so the project written on the resume must have a deep understanding, or in the interview when in-depth questions can not answer will be very bad.
On the other hand, school recruitment is more about basic skills and learning ability (or potential). More knowledge of Java, I will test some basic principles of the framework, not deep, data structure and algorithm, network protocol, etc., if you have reliable project/competition experience will also be the focus of investigation.
There is also the sensitive issue of educational background. Frankly speaking, if an HR/ interviewer has to sift through hundreds of resumes, he/she will not have the energy to look at them all carefully. As an important indicator, educational background is very worthy of reference. And the reality is that highly educated candidates are significantly better than less educated candidates most of the time, even though some of them have gorgeous resumes.
As for social recruitment, I happen to have this opportunity today. After more than half a year, I have compiled an architecture map, which is mainly aimed at Java developers with 2-5 years of experience. No matter in traditional industry or Internet industry, mastering these technologies will make a qualitative leap for myself.
Two, the interview process of the big factory
Generally, for large companies like Alibaba and Tencent, the interview process is one round of unified written test, three rounds of technical interview and one round of HR interview. If there is any dispute over the candidate’s level, one round of technical interview may be added. Take the spring recruitment in 2019 (intern recruitment) as an example:
- A unified written test.
- For a technical start, this is usually a round of interviews with senior colleagues on your future team
- A technical second interview is usually an interview with your prospective supervisor
- Technical crossover, usually other business division managers interview
- HR end, non-technical problem
For fresh graduates, if you want to get into one of them, you must pay attention to their internal promotion information. Internal push is generally not written, you can directly attend an interview. And the general push and unified recruitment is separate, that is, push failed still can participate in unified recruitment, more than a chance. Of course, the specific internal push will affect the unified recruitment, or let the internal push confirm.
Here I would like to talk about the spring and autumn recruitment of interns. Both spring and autumn recruitment recruit students who graduate in the second year. The difference is that the spring recruitment sign an internship Offer, while the autumn recruitment will sign a formal Offer, so we should understand the difference (spring recruitment may not be permanent).
Social recruitment is usually three or four rounds of technical interviews and one HR interview, but in many cases, there will be one round of interviews with senior people (director level).
Three, before the interview preparation
First of all, we must spend some time before the interview to prepare, especially the common typical interview questions to prepare, to avoid a long time without contact with a certain kind of knowledge in the interview, such as computer networks, common algorithms, etc.
Most interview questions can be found in the same category online, but it’s impossible to find all the original questions. Many interviewers will prepare their own questions. For example, at the beginning of every large-scale recruitment, I spend some time preparing several questions by myself.
Then the resume must be carefully written, focused, the best one page can be written. I don’t really read three or four pages. Be honest about what you write in your resume.
In at least one technical interview, the interviewer will ask you about your resume. If you write well but can’t explain it clearly, it will give the interviewer a bad impression and reduce your credibility. So if the project in your resume is from a long time ago, you’d better go back and sort it out.
Since a resume can’t be too long, what will make it particularly interesting?
- Win prizes in major competitions
- Solid project/internship experience
- Open Source Project Experience
On the other hand, one of the most annoying types of resume writing is a long list of technical terms, all of which are familiar/proficient in XXXX. It’s not that you can’t write this, it’s that you can’t write so much. No one can master all of them, and if you write this, and the interviewer picks two random questions and doesn’t answer well, you’re going to assume that you’ve mastered all of them, and the rest are definitely not that good.
Four, some advice during the interview
Interviewers and candidates are never in opposition to each other. As interviewers, they really want candidates to be excellent, and it is best to pass them directly. No one wants to constantly waste time on low-quality candidates. So the interview must be in a good state of mind, not to be difficult, but equal communication. Here are a few that I think are important:
- Be honest. If you really don’t know anything, just say that you don’t know it. Don’t pretend or make it up.
- Take the initiative to ask questions, if there are some questions or do not understand when solving a problem, you can take the initiative to ask the interviewer, generally will give you some tips. Some questions even leave an ambiguous condition that they expect you to ask. The ability to identify and ask questions is also important
- Don’t be afraid of mistakes, don’t give up, even if the last problem is completely wrong the next problem should be taken seriously
- Do not deliberately close, I am very disgusted to come up with a “brother”, or even inquire about the interviewer’s personal problems
As interviewers, the vast majority of people are generally very friendly. A lot of times when you have a difficult problem, you will first ask a relatively easy one, and then the candidate will come up with the next requirement, such as the constraints to solve the problem, or point out the problem with your implementation and ask you how to solve it. Great interview questions don’t start out particularly difficult. They don’t seem too difficult, but they get harder as the interviewer leads them along.
In many cases, it is difficult to describe a complex question clearly in one or two sentences. At this time, the interviewer may deliberately give a rough description, hoping that the candidate can find the question and ask for it when reading the question. If you feel there is ambiguity in an interview question, be sure to ask for it and make a good impression on the interviewer.
During the interview, don’t give up on yourself because you made a serious mistake on a certain topic. After the end of a topic to adjust the state of mind for the next topic. No interviewer will reject a candidate because of a certain topic. All candidates are evaluated according to their comprehensive performance after the interview. So put your mind well, even if the individual topic is wrong, the overall evaluation can still do better.
5. What should you ask at the end of the interview
At the end of an interview, the interviewer will ask you if you have any questions for them. A lot of people don’t know what to ask at this point. There are many questions you can ask, such as:
- Some of the team’s technology stack and business commitments
- If passed, what will be the main work in the future?
- Are there any brothers or sisters to take me? Does the company have any systematic training?
- You can even ask about some learning methods
But remember there is one question not to ask, is “can I pass this interview?”, this question is very inappropriate to ask here, do not pass the general is not good to say in person, can pass this round of interview generally will be other candidates comprehensive comparison, or have the next round.
6. Interview results?
After the interview, if passed, normal will reply within a week, if you wait a week did not see the reply, then it is best to ask your interviewer, although it is probably not possible. Don’t be discouraged if you don’t pass the interview. Add the interviewer’s wechat account or ask him to help you get a group. Many teams have some recruitment groups for their own sake, to be added to the next opportunity to get first-hand information.
7. What the interviewer is doing during the interview
This is interesting. In fact, technical interviewers are senior employees, and people are usually very busy. Many times, the interview is an extra task. So during the interview, in addition to communicating with the candidate, the interviewer may be doing his or her own thing at the same time. In an online programming session, for example, if a candidate is writing down a question and doesn’t say anything, I’ll sometimes do something else and come back 15 minutes later. So even when you’re writing code, it’s best to keep in touch with the interviewer, say what you think, and put forward what you don’t understand. Otherwise, the interviewer might get bored and move on to something else.
Many interviewers will ask candidates to introduce themselves at the beginning of the interview, but you should keep calm and simply say something. He is probably not listening to you and is looking at your resume. That’s why I never ask people to introduce themselves. I take two minutes to read my resume and highlight key questions before the interview begins. Even if you don’t remember, Google it.
Finally, no matter how many people say jobs are hard to find, the best people are the ones every company is after.
For technology that, in addition to myself an architecture for the map, also find friends some video recording, and collected some video, interpretation is a line of Daniel, it includes some Java distributed, micro service architecture, source code analysis, performance optimization, concurrent programming, such as video technology, this paragraph of time the interview from friends is more, There is also a set of BAT interview questions, I have shared in the web disk, divided into four stages of learning, welcome to download.
The first stage
The first stage mainly studied SVN/Git version control, Java high concurrency, JVM virtual machine, RPC architecture practice, Redis, Hadoop, high concurrency distributed project practice, Nginx, Tomcat load balancing and tuning.
The second stage
The second stage mainly studied architecture design, distributed, Niginx load balancing, ActiveMQ cluster, high availability MySQL, Storm flow, Mycat distributed architecture, distributed system case practice and so on.
The third stage
The third stage mainly focuses on architectural practice: learning from high concurrency advanced group distribution, high availability and scalability, Java high concurrency system architecture example, high concurrency database design, MySQL master-slave replication and high availability cluster, massive database architecture design and so on.
The fourth stage
In the fourth stage, I will study Internet high-concurrency solutions, Java senior architect, big data, underlying algorithms of big data, detailed explanation of distributed database architecture, etc.
= = =