Recent interview experience

I have interviewed several companies recently. Let's sum up. These companies include (but are not limited to ^_^) Firestone, codoon, and duoplay, as well as two companies dedicated to providing back-end business system solutions for Telecom (mobile, Unicom, and other carriers. In addition to Firestone, other companies are very lucky to contact me. I was not prepared before the interview. I am very familiar with it. Don't get it like a college entrance examination.

Let's start with a feeling: a cup of water. In fact, a cup of water is not that difficult for a company, but it is very important for a job seeker. Imagine how much water is important for a person who runs away from the company for at least two hours. This glass of water also reflects the degree of human nature of the company, which is better for some small companies. Dear HR, the interviewer should pay attention to this issue.

Let's talk about the technical interview. The first is the question. There are three types of questions: one is about theoretical knowledge and work experience. That is to say, you do not have to clearly describe the implementation steps of a certain knowledge point, however, you must know the role of this knowledge point. The abstract point is that your head should store an index pointing to this knowledge point, which may point to a book or a webpage. This type of questions is related to the breadth, and it is not difficult for me.

The second type is, since you know the role of a knowledge point, do you know its principles. For example, do you understand the principle of static assert in mpl? What is the principle of KMP mode matching? What is the principle of IOCP port completion? (I understand all of these. Here is just an example.) These kinds of problems are deeply related. Even if you have mastered their principles before, you will be asked again a few years later, you may have only one impression. For example, the technical director of one of the companies asked me how to implement C ++'s front ++ and back ++. I'm dizzy. If I were five years ago, this was definitely not a problem. However, in my five years of work experience, there were very few and very vague impressions to use custom ++ operators. If I want to write a ++ operator, see <C ++ Primer>, <C ++ Primer> it is a reference book at the beginning. For such questions, I can only talk about luck. If I have a deep impression on the questions I asked, I will be able to roll back. If I only have the impression of Ding (I am rarely touched by my work ), can I answer this question, please refer to XX?

Category 3: Take the interviewer as the front-end of the C ++ compiler. These questions are especially disgusting to me. I usually refuse to answer these questions. I think the people who come up with such questions are dumb. These people are still thinking at the stage where the C language examination questions were taken on behalf of the University 10 years ago. And now the University will not come out with such questions!

Next, let's talk about the interviewees. In general, there are two types of interviewees: chat and technical exchanges. This type of communication is relatively easy.

The other type is people who take you as the front-end of the compiler and constantly seek out the details of uncommon and strange languages to show their advantages. I cannot communicate with such people.

I have also worked as an interviewer (two years) to interview C ++ and Java applicants. I generally start from the candidate's project experience, test whether the technologies used by the applicant in the project are mastered, especially the design pattern, reconstruction, and some such technologies as program framework. I will ask the following question: Why is this technology used? (Check whether the applicant uses the new technology to use IT) What are the advantages and disadvantages of this technology (the role of the new technology ), what is the difference from not using this technology (any new technology is built on the old technology, this question mainly checks whether the candidates know the relationship between the old and new technologies, and studies these relationships, can open up people's thinking space ). If the applicant is able to speak about the xuanjicang, it will basically be qualified. I will never explain the details of the language, because niche things do not help ordinary work. Of course, I do not disagree with your personal interests.

Finally, let's talk about the questions of these companies and the types of interviewers. The Firestone test has two parts: an online test. This is an in-depth test. I have read the <C ++ Primer>, <More Effective tive C ++>. The written test is relatively simple, basically all of which are of the breadth type. The interviewees also focus on technical exchanges. Of course, there will also be two in-depth questions. Let's look at luck. I asked a question about the plus and minus ++ and HASH algorithms, and I was not sure about the plus and minus ++, hash I still have an impression on the data structure. I passed Firestone's technology and personnel, and finally it was because of my career orientation.

Cool, a written test (made on a computer), is also simple. Although it is a deep type, most of my impressions are not difficult (but some problems are like the order of the stack, I said that I had mastered the software five years ago, but I forgot it now ). After the test is completed, let's take a machine test and make a calculation file bit 1 number. It is not difficult to show the progress bar. The algorithms used to calculate the number of bits 1 are available on CSDN. The interviewees are mainly engaged in technical exchanges.

It is interesting to play more. The questions belong to the deep type and are very biased. For example, C ++ handles UTF8 and so on. I'm dizzy. It's okay if you want to use Java for processing. I also asked me what the UTF8 memory format is, and I was dizzy. UTF8 was actually used before. It was a year ago when the company's Java program was excluded from garbled code, but now I have only a few impressions. I can't decide. Can I ask for a wiki? The interview is also interesting. The first person asked some simple questions, for example, what is thread, will it be win32 programming? I'm dizzy. Do you think I just graduated? I fooled him about the Observer mode, and then I pulled it to AOP (one of the capabilities of AOP is to implement observer, he said that AOP is AOP, and the design mode is the design mode. It has nothing to do with the two. At first glance, TM will know that you are just a beginner. Next I came to the second person. This person is even more interesting. He keeps learning the details of the language. This is my father !!! There is also a question about the CRT heap, that is, the difference between the creation of the CRT heap during static and dynamic connections. I have also studied this question. I directly said that I have also studied it. When I answered the question, I made some mistakes. Indeed, his belief began to be uncertain. In general, the interview for multiple games is quite a failure. I cannot understand the behavior of these people and naturally cannot communicate with them.

The other two are engaged in business systems, one of which is UNIX and does not understand. The other has UNIX But windows, and they also give me an adaptation period to familiarize myself with the UNIX environment, the condition is also the best, but it is still the problem of career orientation.

To sum up, the interviewees in some companies really cannot understand their thinking. Do your company really want to recruit some Compiler Front-ends? The design pattern and refactoring have been popular for many years, and parallel computing will become the next growth point. You are still at the NLP syntax stage. Do you have a future? Where is your future?