Talk about the interview that Zhou Gong understands

Because the company has been hiring a lot recently, there have been a lot of interviews recently, and many of my colleagues have had tight projects, so I had some technical interviews. I cannot remember the number of interviews I have participated in since I took part in my job as an interviewer or candidate. So I want to talk about my interview experience and feelings from the perspective of the interviewer and the applicant.

As an interviewer

As things last week were relatively close, I will start with my recent interview. My company has four rounds of interviews. The first two rounds are technical interviews, and the third round is English interviews (because they are foreign companies, they have relatively high requirements for English ), the fourth round is the personnel interview, because the candidates are widely distributed, so our interview is dominated by telephone interviews. Because I am a technician, I will only participate in the first two rounds of interviews.

First, the company's recruiting staff will collect information about candidates in related technical fields from the recruitment website. Here we will perform some preliminary filtering, such as education, working life, and work experience, the filtering here does not involve any technical personnel. I am not involved in this step, and I do not know the details. After filtering your resume, you will be notified by phone to confirm whether you are interested in your work.

After filtering your resume, you will enter the formal interview process, that is, the first round of technical interview. This round of technical interviews is a bit like the "Supergirl" audition. In this round, we will conduct a comprehensive test on the technical breadth and depth of candidates. For technicians, I personally think that the depth of technology is a sufficient condition for determining whether to hire, and the breadth of technology is a sufficient condition for determining your salary. Note that the words I use here are adequate, not mandatory or necessary, because some geeks and geeks are not in this case, it is necessary to work hard on the depth and breadth of technology. It is best to follow the process of depth first and then breadth. Therefore, in the first round of technical interviews, we will first learn the breadth of the skills that the candidates have mastered through some basic questions, then, you can use some basic questions to test the depth of your skills. If the applicant meets our deep requirements in some aspects, they will enter the next round of interview.

Different from the first round of interview, the second round of interview questions will not be so wide, however, based on the outstanding performance of the applicant in the previous round, the depth of the technology he has mastered will be thoroughly understood and tested. In addition, there may be some problems to test his thinking ability, for example, for a framework that has already been implemented, the applicant must try another implementation, such as how to write a web server or a framework, here, the applicant is not required to implement such a function, but to determine his thinking ability to respond to unfamiliar problems. If you have passed this round of interview, you have passed the technical interview.

Here I want to correct some incorrect ideas.

The first point is that many junior and intermediate developers often think about the basic usage of some classes. They can get the answer by checking the help manual or searching the Internet. Why do they still ask such a question? This is incorrect. I admit that many questions can be answered by searching for help manuals or searching online, but it is necessary for developers to master some basic knowledge. Just as we can read all the books through Dictionary lookup, but which of the following words have you ever heard? A developer is a creator. If there is no basic knowledge in his mind, how can he think about this problem and use the method of that class to implement it? This is why all interviews with Junior and intermediate technical personnel must have basic knowledge. For the implementation of the same function, there may be different implementations in the class library. The differences between these implementations I don't think are as ridiculous as the pedanky style of the word ", on the contrary, they may be used in different scenarios.

The second point is that many candidates always feel that the interviewer must be difficult for them to obtain psychological pleasure. Maybe there are such interviewers, but most interviewers do not have this mentality. Sometimes, some questions may be raised, such as drill-down and remote issues, which are necessary to understand the breadth of the technologies mastered by candidates. In most cases, it doesn't matter if you cannot answer some questions. No one expects you to get a full score.-Of course, if you get a full score, when you talk to HR about salary, you will be more active and confident. In some cases, the interviewer may go deep into a project somewhere. For example, if you want to recruit someone to develop a project in the future, the project has high requirements for some fields.

The third point is about the technical superiority of the interviewer and the candidate. Many people think that the interviewer must be more technical than the candidate, but it is not necessarily. Of course, this is probably the case in most cases. I have seen that someone wrote in the interview writing experience that I once asked the interviewer a question. The result is that the interviewer's answer is not ideal, so I came to the conclusion that the interviewer is not technically competent, it may even be said that the interview company's conclusion is not technically sound. In fact, this conclusion may not be correct. The so-called technical specialization means that the knowledge you possess may not necessarily be required by others. If you win at a certain point, it may not mean that you have exceeded all aspects. Of course, there are also reasons why you have really won someone else on a certain level-this is probably why someone else wants to recruit you. In short, the interviewer is not always better than you. He can interview you on behalf of the company. Maybe he is outstanding in other aspects that you are not good at, so he entered the company and came to interview you on behalf of the company.

As a candidate

Previously, Zhou Gong said that he has been an interviewer and a candidate. Here, Zhou Gong also talked about his experiences and feelings as a candidate, in my resume, my job is from C # Senior Programmer to project manager and Technical Director. To avoid unnecessary troubles, the company names listed in the following description are all random code names. Please do not sit on the phone.

After returning to Wuhan, Hubei Province from Taiyuan, Shanxi Province, Zhou Gong worked in WSW, a Taiwan-funded enterprise with a US capital flag (the most typical representative of a Taiwan-funded enterprise is that it is, the most distinctive feature of the platform is that all windows have security nets), such Taiwan-funded enterprises include WC and Qs. Due to the abnormal management system and no welfare measures of Taiwan-funded enterprises, Zhou Gong went to some software companies in Wuhan for an interview at that company. Here, Zhou Gong will talk about some impressive interviews.

The first company with a better impression is Qs. This is also the same as WSW. It is also a software company that implements Management of Taiwan enterprises under the banner of US capital. There are many measures that do not violate laws and regulations but make people feel uncomfortable, one of them is to let you take the salaries of the second-and third-tier cities to the first-tier cities for business trips (some Taiwanese companies, such as WSW, are even worse than they are, in the name of "training", let you go on a business trip, this saves travel expenses ). I was asked many technical and management questions in this company. Most of them answered well, so I was not impressed. I still remember a unit test question. The question is: there is a unit test for a large project, there are 0.16 million all test cases, and it takes about 8 hours to complete all tests. The current situation is that if all tests are performed at a time, the test case test fails. If only half of the test is passed (the first 1/2 or the last 1/2), you can pass the test and ask how to solve the problem. To be honest, I had no idea about this problem at the time. Generally, developers will not encounter such a number of unit test cases in projects, my idea at that time was to test the first 1/4 to 3/4 cases to see if they would all pass, or continue to look at the problem through computer-based troubleshooting Division (that is, through Segmentation, however, it is still rejected. So far, I still haven't come up with a better solution (this is why I still haven't forgotten it). Now I think of whether there are resources in the unit test that have not been released in time, it does not appear in a few test cases, in a large number of test cases, it will be caused by release without time (for example, a large number of accesses to the database lead to no available connections in the database connection pool, resulting in wait timeout, etc ).

The second company is in Hankou. After I went there, I was told that my company is headquartered in Shenzhen, and that the Wuhan Branch was established soon. Now there are no technicians. The only general manager who understands the technology was on a business trip. Before the business trip, the general manager left a set of questions. After HR took this set of questions, I was dumb at first glance! This 8-page question is filled with questions. The programming languages involved include Delphi, C \ c ++, Java, C #, and PHP, the databases involved include SQL Server, MySQL, and Oracle. In addition, there are some algorithm questions, such as gray algorithms. To be honest, I have used these programming languages and databases (the breadth is acceptable, of course, some are just for my spare time ), but it won't be possible to reach the same depth in every programming language and database. It took me two and a half hours to submit what I could do. Afterwards, I felt that I had met many companies with a wide range and depth of requirements during the application process, but this was the first time in my life, in the end, I don't know what the company mainly uses for language development.

The third company was originally located in central South China. After entering the course, I also sent a bunch of interview questions, including Chinese descriptions that require Chinese answers, English descriptions that require English answers, and technical and logical thinking, you may also require personal privacy information. In the technical interview, I tested compilation principles and assembly languages. Although I did not study computer courses, I have learned this knowledge to broaden my horizons, most of the questions were barely answered, but I didn't finish all the questions, because I saw a lot of design privacy questions in the questions, for example, whether hepatitis B has been obtained (it seems that the country prohibits employers from inquiring about and rejecting candidates), and whether there have been major diseases and ancestral investigations in the past three years, in addition, the company said that the company would be dismissed immediately if it did not answer the truth. Considering that such a company could not respect its employees, I decided to leave the company halfway (afterwards, I went to this company with a colleague, it fully proves my speculation ).

The fourth company is located on lingyu Road, and its headquarters is also located in Shenzhen. In the winter of a university, I went to this company for an interview. The first time I met someone who poured a cup of water (I really wanted to have a cup of hot water to warm up, especially when I knew that the entire interview process lasted for three and a half hours ). This company's interview questions are also very thick. The first half is a non-technical test, and the questions are similar to the logic reasoning questions of the Civil Servant Examination (Zhou Gong once had a civil servant examination experience). The second half is a technical question, all that surprised me was the C and C ++ questions. I am not familiar with C and C ++. I can only answer a part of my questions. Finally, a technician chatted with me. We talked about the level at which the number of records of various databases should be measured by cluster or Server Load balancer, all the time later will focus on database knowledge. After the event, Zhou Gong felt that the company's HR staff may regard C # As c ++ because they want to recruit senior C ++ developers instead of C #, it is estimated that all of them have C, so I thought it was almost the same.

The Fifth Company, this is the last company before I entered the current company. This is an entrepreneurial company, so it has high technical requirements. In this company, the interview process is basically centered around C # and ASP.. net. I had a comparison between Java and C #. I have been using Java and C # and I am also paying attention to the technical trend. So I answered the question smoothly. Two questions are quite impressive. One method is to execute 1000 times in the C # loop and 1000 times in Java (ignoring the syntax difference ), there is no difference between them even when they are running; another problem is that they are in ASP.. Net implements URL rewriting. Is this process prior to or after user identity authentication? After three months in the company, I finally left, in addition, the current company has known colleagues who have worked in the same company before (I sat in the position of this guy right after I went in ), the feeling is that this company is very labor intensive, and it can only work for six days a week. It still works for more than 12 hours a day.

Finally, let's talk about my interview with me. Before I went in, I had four rounds of interviews. The first two rounds were also technical interviews. During the technical interviews, I asked about the differences between IIS versions, naming pipelines, and ASP. NET page lifecycle, Asp. net1.1 and ASP. differences between net2.0 (there are differences between the ASPX page, the frontend is extends, the last bit is partial, and the compilation process is different) and so on to investigate the breadth and depth issues. Finally, I joined the company after passing the interview.

Before joining the current company, I was also recommended by the headhunting staff to contact a mobile internet company in Shanghai. I applied for a position as technical director, during interviews with this company, I mainly talked about handling problems under high concurrency, such as how to use Server Load balancer, how to use memached and other third-party tools. I still have some experience in this regard, the other party also took a fancy to my technical and management experience, but the people around me did not agree that I would leave Wuhan again, so I had to leave. To be honest, I felt a little sorry, but I had to give up for my parents and family.

Feelings and experiences

During the interview, you don't have to worry too much about questions that you cannot answer. Especially when the interviewer examines the breadth of your skills, the most taboo is that one or two questions cannot be answered, this affects the performance of individual abilities. For individuals, we must try our best to work in depth to expand the breadth of the product while meeting the needs of the depth. (logical thinking can be used to draw the opposite picture ). Finally, the mentality is very important. You have the right to choose a company, and the company has the right to examine your abilities through various means, if privacy is not involved or personal welfare is affected, try to answer the question as much as possible. If you can get in, you will naturally be happy. If you cannot start a job, you do not have to abandon yourself. You can continue to find the right company or prepare for the next interview.

Zhou Gong

2011-08-15

If you have this problem, you can leave a message below the blog or asynchronously to Zhou Gong's Weibo (http://weibo.com/zhoufoxcn) to participate in the discussion.