Things to notice during the interview

Since I learned and applied JAVA in my previous job, I have been contacted by many companies. The work content is all about JAVA development. I would like to thank the previous company for the cultivation.

During the interview, it is common to be asked several common questions, such as why you left the previous company, introduce the projects you have done, expected salary, etc. In addition, there are technical questions, and this is the key point.

In addition to introducing previously used technologies, the interviewing engineering executive will also ask technical questions about the company's expectations of the candidate's level, possibly situational questions (ex: ...how would you handle/design this situation? What is the cost consideration? Are there idle resources?), or knowledge of the underlying knowledge of the programming language (ex: if you declare a global or local variable, will it exist in memory or register? This question was asked and I was dumbfounded. Reply)

The above question about programming language is not and don’t need to be particularly nervous. After the interview, think carefully about the non-undergraduate supervisor and colleagues of the former company. If you don’t know that this kind of thing can survive in the industry, there is no problem, just like the interviewer himself. He said, "There is no need to apologize for this kind of thing. It is different for everyone. I just want to know how much the interviewee knows about the tools they use. The interview is such a process."

In addition, I would like to express my special thanks to the personnel of the first interview company during this period. They gave a lot of advice on expressing themselves in interviews. I would like to share them here: "It is suggested that self-introduction can be more substantial, and don't be too simple. Like You said that the service is on the cloud, so what functions have been used in the development process, what services have been used, and what are your experiences... Telling them all can make people more impressive. Because you may have poor interview experience There are too many, so it’s inevitable that I don’t know how to say it, but I’ll mention it to you as soon as I see it.”

My interview process lasted about two weeks, because most of the companies I interviewed were online, so they could be arranged intensively, and there was even a record of three interviews in one afternoon. In this cycle of constant introduction, questioning, and being asked questions, I found a big problem: my grasp of knowledge is not as solid as I originally thought.

Every time my development process is a complete requirement, new data types in the database, related business logic checks for planning and writing, api interface structure design open to the outside world, and other single-execution programs. Accidentally, you will feel that you have done such a thing. If you can explain the principle and the process of implementation, it means you have learned it. However, in the parts that you have not seen, there are actually many leftovers from predecessors, and the trivial and repeated parts will be dealt with first. , let the team develop the common part more smoothly, when one day try to reproduce the function by yourself, you may hit a wall.

In addition to the size of the school project and the industry project, in addition to the scale and the need to consider the actual use situation to the degree of detail, I think the biggest difference is that it is usually not involved from scratch, thus reducing the difficulty of the team's development, but it may also be Learned a lot less.

Some people say "don't make your own wheels." This is because other people's wheels are better. Unless your business is to design wheels, you can save the R&D cost of wheels and make good products. Why not do it? ?

So why do schools teach the wheel how to do it? Don't you have to do it yourself?
Not having to make your own wheels and not being able to make your own wheels are two different things. The latter can't go to other fields, so if no one builds the wheels first, they can only avoid it? The former has more options.

My situation may be a bit like this, but it's too late to prepare during the interview.

Therefore, after finding the problem, it is expected that the interviewer may ask what questions and how to answer them, so as to truly show their level. If there is no part, just say no, and the interview company will judge whether it is suitable.

At the same time, the resumes that were published on the Internet were also closed. The interviewees are good for these companies for the time being. If they are not ideal, they will spend a month to make up for their lack of skills and start again.

I made this decision around 2021.9.22.