Interviews rarely tell you how to improvise, so I think this article is very important for you.
The last article covered how to do some preparation, but during the interview process, you’re bound to be asked questions you haven’t prepared for. So what happens at this point? So let me tell you a little bit about what I learned. There are still several cases:
- Programming test
- The interview
1. Programming tests
Programming testing is part of what many large companies do. Some look at algorithms, some at programming ability, some at design. It depends on what abilities the interviewer wants to test. For this kind of test, many people will ask, “This is not the same as the college entrance examination, get the question to do, not finished, and improvisation has what relationship?” . In fact, this is very different from the gaokao.
When you program a test, you’re facing the propositioner. And the propositioner often has a point he wants to examine. But the questions are written by programmers with similar language level to us. Meaning can be somewhat unclear. Then this is the time to improvise.
Finish the topic do not rush to do, first simply think about the proposition of what you want to investigate, what is the meaning of the topic. Then explain the meaning of the topic to the proposition and ask him whether the topic means this.
It doesn’t matter if you got it right or wrong, the person who got it wrong will point it out to you, it’s better than if you’ve written all the code and found out you got it wrong. Whether right or wrong, you add some points for yourself. It reflects that you are someone who understands what needs to be done before you do it. So after you understand the question, can you just write it? Fault.
For a problem, there must be a lot of ideas and methods to solve the problem. When you get your final score on the gaokao, you get a full score. But programming tests are not. Using bad ideas and methods will kill you as well. Then it’s time to wing it again!
After you know what the topic means, say “Let me think about it” first to buy yourself some time. Then let your CPU run and think about as many scenarios as possible. Then present your plan to the proposer, preferably by talking about the pros and cons of each plan.
Some people may find this difficult. In fact, in my own interview process, as well as in the communication interview with others, I found that the programming test questions can generally be done. The ones that fail are the ones that hang on methods. If the level is not too bad, at least can come up with a simple and rude method. However, if you put this in writing, you will not get an Offer. So it’s important to talk about how you think. Talk about your ideas and solutions and discuss them with the interviewer. The interviewer will often try to lead you to the right way, which increases your chances. Do it only when you’ve reached a point where the interviewer is happy, or when you can’t think of anything else and the interviewer says, “Just go with the discussion.”
Even if you don’t do it perfectly, you’re sure to leave a good impression on the interviewer.
2. The interview
With so many variables in the interview process, it’s normal to ask questions you haven’t prepared for. When it comes to what you have prepared for, a precise and correct answer is ideal. However, there is no need to directly say that you will not be prepared for a problem. There are a few “I don’t know this” moments during an interview, and the Offer is gone. So how can you make a good impression on an interviewer when you’re not?
- Ask the interviewer to repeat the question (confirm the content of the question and gain some time to think about it)
- Repeat the question (let the interviewer make sure you understand and buy time to think about it)
- Make it clear that you haven’t done any research (so your interviewer can forgive you — even the best people don’t have research questions)
- Ask for time to think (Buy time, think hard)
- After 30 seconds to a minute, discuss your ideas with the interviewer, not necessarily with an answer (state your ideas, discuss them, and the interviewer will lead you closer to the right answer).
Take an example of my Alipay interview, talking about the database table, the interviewer suddenly asked the following question:
If have a trade table, user and businessman each undertake trade can produce a record in trade table, so cent library cent table, should divide according to what kind of regulation.
This is a question I hadn’t prepared for. So I said, “I’m sorry, I didn’t quite understand your question. Could you please repeat it?” “After he repeated it, I retold the question. After receiving his approval, I said,” I haven’t studied this problem before. May I think about it now? The interviewer won’t say no.
And then it was like 30, 40 seconds. I replied, “If we split this table, we want all the data of the same user to be in one table, and all the data of the same merchant to be in one table. But any user can trade with any merchant. If A user in table A transacts with A merchant in table B, the resulting data cannot be determined in which table, so there is no such table split rule.” In fact, that’s what I was thinking about during that time, what I was thinking about when I was saying this. Then I said, “So I wonder if I can split this table by users and maintain an index table of merchants to the original data. To provide inquiries for merchants.” Then the interviewer says, “That’s fine, but it’s a hassle. It’s okay. I’m just asking.”
If you have a question that you haven’t prepared for, follow this line of thinking and finally just say a few thoughts of your own. Even if it’s not the right way to go. It’s better than saying no. After all, no one has studied the problem. At least that means you’re willing to think.
conclusion
During the interview process, it’s normal to come across questions that you haven’t prepared for. Don’t panic when you meet them, keep calm, try to gain time, and turn on your CPU at full speed to think. Finally grasp the time to avoid awkward silence. Say something if you don’t have an answer. Being right or wrong is better than saying no. Good luck with the interview. The next chapter introduces how to accumulate in daily work projects.