Shulou(Shulou.com)06/03 Report--

A few days ago, I talked about some points for attention in writing a resume in "3 key points to move people on my resume" and "3 questions not to appear in my resume". Today, I want to talk about how to better reflect my real strength during the interview process.

In interviews, I often start with the following three questions:

1. Please introduce yourself briefly.

two。 Briefly introduce a project in which you are highly involved and your responsibilities in the project.

3. Briefly describe the most fulfilling Bug you found in the project.

Below, I would like to explain these three problems one by one.

1. Please introduce yourself briefly.

The advice given by most chicken soup articles or noodles may be as follows:

Hello, interviewer, my name is Zhang San, born on August 31, 2018, female, a dog, I like climbing, reading, swimming, running, playing chess, writing code, doing tests, I am very happy to get today's interview, thank you.

Well, is that good? yes, there's nothing wrong with it, but there seems to be something missing, what is missing? Without the information I need, the interview is not a chat, and there is a purpose between questions and answers, so my suggested answer can be as follows:

Hello, interviewer, my name is Zhang San, graduated in 2016, the most recent job is in Tesla Company, the most recent project is Tesla coil test, I play the role of test leader in the project. This change of job is because of the company's business adjustment, ready to invest resources to do super high-speed rail, cut off Tesla coil business, this time want to find a team atmosphere, more technically challenging job.

The reasons why I am satisfied with this answer are as follows:

Taking the initiative to give some necessary information, such as company and project information, such as the reasons for changing jobs, as well as personal expectations, reduces the time for the interviewer to answer questions, and at the same time makes the interviewer feel that the person is more considerate. Or there's something in the eye. Although the answer is, but in the leading topic, or creating topics, such as he mentioned the company and the project, but did not elaborate on his role as test leader, so I will certainly continue to ask.

Interviewers who can create topics for the interviewer are good interviewers (but don't bring yourself into the ditch). If you make a good impression on the interviewer on the first question, it will be very helpful for later communication.

If it were you, what would you say?

two。 Briefly introduce a project in which you are highly involved and your responsibilities in the project.

If the first question, the interviewer did not take the initiative to tell these contents, the second question I will take the initiative to ask.

In response to this question, some students will miss the key points, for example, they will spend a lot of time to introduce the details of their projects:

I recently participated in an App test, which has a home page module, a friend module, a core transport module and a personal center module, and is divided into IOS and Android, and Android is divided into domestic and overseas versions. I am mainly responsible for testing the domestic version of Android.

Look, having said so much and answered only part of the project information, I still don't know exactly what you have done, so I need to ask this question again.

Note that the key point in the interview process is the interviewer himself, the project information is background information, and the main information should be what the interviewer does, so you only need to highlight the areas that can set off the interviewer's abilities, such as:

I recently participated in an App test, the cycle is two weeks, a total of 10 developers and 4 tests participated, I am mainly responsible for leading the other 3 testers to ensure the quality of all versions of the project. My main work includes requirements review, use case writing, test division, and automated scripting.

In that case, will the information be much richer at once? Providing more personnel information will help the interviewer understand his or her position in the team, especially when he or she plays a key role, and provide specific work content so that further communication can be carried out.

For example, the requirements review, use case writing and automated scripting in this topic are all what I want to expand. Again, the interviewees who can create topics for the interviewer are all good interviewers, but remember, don't dig holes for yourself. For example, automated scripting mentioned above will only change the configuration parameters, and there is no technical content, so you will be very disappointed to ask.

So the previous sentence can be improved: the interviewees who take the initiative to lead the topic to their own advantages are good interviewees.

If it were you, what would you say?

3. Briefly describe the most fulfilling Bug you found in the project.

This question should not be my patent, and it will be mentioned in almost every scripture, so many interviewers prepare in advance, so let me first tell you some points for attention:

What you want is found by yourself, not by others; similarly, don't name what others find on your head, it's easy to make flaws; it's better not to be the Bug that appears in the execution of regular use cases.

Let's first look at an example:

"one project added a local search function. When I took special characters as input, the program crashed, then debugged and located with windbg with the developer, and finally found that the program did not handle the exception. "

"isn't special character input covered by a regular use case? In that case, anyone can find out, right? "

"well, it was discovered during the execution of the use case. "

"windbg debugging needs pdb, this is only the development, so it is actually the development to locate it? "

"well, for developer positioning, I am providing a reproduction environment and dump files. "

We think that most people can take into account all the key points mentioned above and the test points that can be covered by conventional use cases. in this case, it should not be a very fulfilling thing to find such a Bug, is it?

Let's look at another example:

"because of a requirement, the business needs to intercept the injection operation. After the development and testing, it does meet the requirement scenario. After communicating with the developer, we understand that the implementation logic handles the call of API SetWinEventHook. However, it is found that API SetWindowsHookExW can also achieve the same effect, but the development does not handle it. In view of the low cost of bypassing another API, the development added the processing of this SetWindowsHookExW. "

"how did you come up with this test site? "

"there are a lot of API in Windows system, and it is complicated, so we are very careful when we encounter it. We have always had the habit of checking MSDN before, so we found this test point when studying the specific implementation method, and there are many other similar situations. "

"is the test tool written by the developer? "

"No, I wrote it myself. "

In this example:

The problems found by yourself; not the scope covered by conventional use cases, figuring out the detailed logic of development, and doing targeted and comprehensive testing, not everyone can do it; another point is that the problem positioning process is completely completed by yourself.

If you were an interviewer, who would you choose in the face of these two interviewers?

Well, that's all I have to say. Wait a minute. I think I heard a classmate have a problem.

"I know all the above, but I really don't have anything to sell. What should I do? "

What else can I do? go back and make it up.

Remember, the process of doing each project is the process of our growth and harvest.

By the way, if you share this article first, and then make it up, the effect will be better.

This article was first posted on the official account "sylan215", ten years to test the original practical information of veterans, follow me, rise posture!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.