During the interview process, you can improve the success rate of the interview by using the question-and-answer session

    After the interviewer asks all the technical questions, he will usually say, "I have no problem here, what is your problem?" At this time, it enters the stage of "role switching", and you ask us to answer.

    We met a lot of people who just said there was no problem, and the interview was over. But we also met a lot of people. Through this stage, we changed our views on him, learned more points, or simply reversed the interview results. This article will describe the interview techniques of the question-and-answer session. This article is adapted from the book Java Web Lightweight Development Interview Tutorial .

    

1 By asking questions, further demonstrate your match with the position

    You can ask, which program group will I be in if I successfully apply? What technologies are needed in this project group?

    When the interviewer tells you, you can say that XX technology is something I have used before, and then talk about the details of using this technology in previous projects.

    Or the project that the interviewer said you have had similar experience with before, you can also talk about your experience.

    If the interviewer hears of similar experience and confirms that the verification finding is true, a comment of "have done similar projects before" will be added, which can be the icing on the cake and help the candidate get more salary.

    Once when we recruited for an insurance project, a candidate may be nervous at the beginning, and answering the question is very simple. We have written the words "the technology is average, it can be used or not, please consider the successor manager", But at this stage, perhaps because he talked about the aspects he was more familiar with, so it was smoother, and the knowledge points were displayed more comprehensively, so we immediately revised the comment to "The technology is OK, and I have had similar experiences". .

    The suggestion for everyone here is that before you interview, please learn about the company's projects and find a way to approximate it. You can appropriately modify your previous project experience to make it have a certain degree of similarity with the company's future projects. This effect will be better.

 

2 By asking questions, tell the highlights that you were not asked about

    It is not recommended to directly say "I actually still master XX technology, but you didn't ask just now", because it is somewhat direct, and you can still tell by asking about the project situation at this time.

    For example, you can ask, does this project use the Spring MVC framework? When you get a positive answer, you can say, "I have built frameworks with the help of project managers before, and I have XX experience."

    In other words, does a certain requirement point in your XX project involve database tuning? I had a similar experience before, and then say something. The suggestion here is that you prepare some highlights that you are sure of before the interview. The sure thing here means that you are very familiar with and understand the details, and can give examples based on the actual situation of the project, think about the starting point, and then you can find Opportunity was mentioned in the interview.

     In short, you can prepare some JVM tuning, SQL optimization or architecture-level tuning skill points, and then be sure to combine the project description. For example, you can say that in the previous XX project, we encountered a SQL running for a long time, this SQL What is it? Then I checked the problem of xx through the execution plan, and then used the method of xx to solve it. Don't talk about generalities here.

 

3 Can show some non-technical expertise

    In addition to technology, you can also ask, does your company work a lot of overtime? Who are the customers? Non-technical questions like whether the project is tight, you ask these questions for two purposes:

    ① Show that you are hard-working, good at communication, and good at dealing with more serious customers. If you go to an outsourcing company for an interview, this ability is very important.

    ②Check whether this company is a sweatshop, whether it will be running day and night, and whether it will be under too much pressure. If this is the case, you need to look at it as appropriate.

In addition, if you feel that your interview may not be successful, then you can also say the following words in the questioning stage.

    Or you can ask, is the technology used in your project the latest? If it is, it can be said that in the previous project, the technology I was exposed to was also the latest, and then I got started in a very short time to show my learning ability.

 

    

Guess you like

Origin http://43.154.161.224:23101/article/api/json?id=325068248&siteId=291194637