“This is the 7th day of my participation in the Gwen Challenge in November. Check out the details: The Last Gwen Challenge in 2021.”
After the initial introduction to one of the previous projects, your interviewer has a sense of your entire project, your skills, and your fishing experience.
This will be followed by questions from the interviewer. Generally speaking, when the interviewer asks you a specific question, there will always be your first ideas and methods to solve the problem.
Therefore, the interviewer will ask you, during the presentation of some of the projects that you have just done, what are some of the difficult problems that you encountered when you actually developed the project, and how did you solve them?
When asked this question, the interviewer is trying to gauge your experience and how you approach the problem.
You don’t really have to worry about the definition of such a difficult problem. Because if you are in the process of interviewing blindly pursue I want to play me some of it is very difficult to solve a lot of partial door problem, and told the interviewer how I through some complex query methods to solve these problems, to find the answer, in fact is not necessarily can highlight you correspond to the real one bright spot and strength.
Therefore, first of all, you need to refine some difficult points in the process of your project before the interview. First let’s look at what a hard problem is.
What kind of problems are hard to solve
Generally speaking, difficult problems can be divided into four dimensions, which are common problems, door deviation problems, normal problems and pit problems.
Do we need to think about whether I’m going to talk about a common problem, or whether I’m going to talk about a different problem? In fact, there is no very clear answer to this question. Generally speaking, common problems are often encountered in the process of Internet research and development. Although the problem is common, it does not mean that it is difficult to solve. For example, some GC configuration problems, although it is a common problem, but in fact, there is a certain technical content, and multi-performance optimization when we have to bear these problems. For some partial categories of problems, most of the cases we belong to some specific fields will encounter some problems.
For example, we have developed a corresponding digital calculator, and we need some special solutions to verify some digital computing capabilities. A side-door question like this may have nothing to do with the position you are interviewing for. So in my experience, what you need to be prepared for are some common, but technically deep, internet-specific problems.
What we need to consider is whether I should do some normal questions or a reply to some trampling problems. That for some normal general, we are and common problems are the same, are some fixed a routine pattern to solve these problems.
For the pit problem, it is often said that we found some pit in the source code of Spring Boot. I investigated for a long time and finally found some such problems through debugging the source code.
For this kind of situation, there is no standard answer, it must be to say which is better, but more to say that the technical depth of your corresponding problem, as well as a means of solving the problem, thinking about the problem, whether to meet the requirements of the interviewer for your position.
So a question-and-answer question asks you what difficult problem you solved and how you did it. In fact, the interviewer is mainly looking for your content and in-depth practical experience, as well as some of your thinking and means to solve problems.