Let me tell you something first, if you were an interviewer, what kind of person would you like to recruit?

If this question is clarified, then it can be said that the interview for the test position becomes very easy.

According to general practice, the interviewer will ask you to introduce yourself, introduce your project experience, and ask about your technical ability. These are all routine questions.

I won't talk about fixed templates or anything. I'll take my previous interviews with other people as an example, and specifically talk about the cunning of the interviewers, where they will set up pitfalls for you, and how you should deal with a tricky question.

A real interview process:
1. It must be a self-introduction when you come up

Self-introduction is an essential link in any interview process, and it can be said to be the most important link, because every interviewer needs to use the shortest time to get to know you, what you have done before, how many years of experience you have, and what projects you have done. It can be said that through a short self-introduction, the interviewer already has 50% of his mind to decide whether to want you or not.

2. Ask about the testing process of your previous company

If you don’t have a company, stop making trouble. Are you planning to interview interns? Let’s interview formally when you come up. If you have reached the technical level, why let work experience limit you.

So, the interviewer asked this question, on the one hand, to know whether the testing process of the previous company and this company are close, and there must be a comparison. In fact, these are not the most important, the main thing is to examine whether you are clear about the entire testing process. The interviewer will check your mastery of the complete test process by asking about the previous test process. So, this is the first pitfall. If you don’t speak well, or if you say it casually, you will lose a chance to show your ability, and you will fall into the first "trap" set by the interviewer.

As an aside, let's expand on how to answer this question if the interviewer asks it.

First of all, the first thing in the testing process of a formal company is to get the requirements document, the user will say what they want, and the product personnel will record it and convert it into a requirements document.

Afterwards, our testers and developers conduct a requirements review after the product personnel take out the requirements documents. We need to know what functions the users want and what software they talk about. During the review process, it is necessary to analyze the requirements to see if there is any ambiguous content and if there is any inaccurate description.

This is the first thing, needs review.

Then after our requirements review is passed, our testers need to write a test plan by the test team leader and manager.

After the test plan is written, all testers are called together for a meeting to review the test plan.

What is the content of the review? Is the arrangement reasonable? Is the time schedule really enough? Including whether the risks inside have been avoided, and our test machine preparations, etc.

After the review is passed, let's write test cases, divide the labor, and then review the test cases after writing the test cases. If there are no missing points, after the review is passed, the test cases will be executed, then the first round of testing, the second testing, the third testing iteration, until the acceptance test, and then publish and write our test report.

The whole process is over.

Combining this process with the items in your resume to answer is definitely a perfect answer. As an interviewer, you will think that you are very, very clear about the testing process of the previous unit!

This is a question that the interviewer hopes to hear you answer perfectly, and it is also a question that can measure whether you have really worked.

3. What kind of business are you mainly responsible for?

Notice! Send a proposition!

For example, let’s take an e-commerce project as an example. Because if you don’t have work experience, you dare not answer this topic, just say that you are only responsible for registering the login module. If you answer this way, well, you have been shot dead in the interviewer’s heart.

Because of what, because the test manager will only assign the registration module to interns, and will never give this module to a person with strong technical ability. If you are only responsible for this module, it can only be said that your leader is not optimistic about you.

Or how to answer this "send proposition"?

Boldly say that you are responsible for the testing of a process, and I am responsible for the order process, or the payment process, or the refund process. These are more logical. Then these processes involve the front-end and back-end, because it involves the review process, which involves the database, so if you answer in this way, it means that the work you do is relatively technical, and your technical level is no problem.

4. What testing methods did you use?

You said that you should test a business with strong logic, and then the interviewer will definitely ask, what testing methods did you use, all of which are to verify the authenticity of the previous question. The test method is not listed, it is too long.

5. What is the most logical BUG you encountered during testing?

Send a proposition! Knock on the blackboard! I use this routine often!

What is the purpose of asking this question? The purpose is whether you have actually tested it. If you made up this resume, if you lied to the interviewer, you will be stuck in this link, because you were on the spot at the time, and you would never have imagined what a logical BUG you found at the beginning. You couldn't figure it out at the time. This is a small way to verify that the item is actually real.

There are also interviewers who are very cunning and will deliberately say something wrong.

In the past, when I was interviewing for advanced tests, I would often use this method. For example, when talking about loadrunner or jmeter, I deliberately said something wrong, and then I looked at your reaction. If there is no response or nodding, then I can be sure that you do not know this tool. The "familiarity" or "proficiency" written in your resume contains water, so the interviewer may not ask you directly when examining your tool usage.

The most important points in the interview:

1. The image must be neat, decent and reasonable.

2. The tone is a little humble, not too proud (of course, when talking about the bug that impressed me the most, I want my eyes to shine).

3. The voice must be moderate, don't be timid, don't be afraid that the other party is also human, you are strangers. Don't worry, it's still unknown whether I can be a colleague after my interview today.

4. Nervous? It doesn't matter, then speak slowly, which can ease your tension.

5. Don't look at your eyes randomly, especially for men. If your appearance is still good, if the interviewer is a woman, you must look at the other person's eyes without distracting thoughts to answer questions. Showing the charm of a man is an absolute plus.

What? You are a girl, what should you do if you are embarrassed? That's simple, it's okay if you don't get used to looking at the other person's nose or eyebrows.

6. Try to blurt out the answers to the questions, of course the questions and experiences you are familiar with. If you really don’t know how to do it, then answer modestly, “I’m sorry, I haven’t touched on this issue of the manager. Can you explain it to me. People in the IT industry are very weird. They always think they know a lot, so they will explain it to you with vanity (of course there are weird people).

7. If your ability is not very outstanding, you can consider expressing that my best friend is also doing this business, and I will also ask him for advice. This can give the manager who interviews you an illusion that you can learn one more way, and they can invest less. But, good friends are just me bragging...

8. You must have an advance plan for your future development. Even if you don’t know how to compile, you have to compile a set, but don’t say that I want to be a test manager in 3 to 5 years. . . Usually, this manager is the one who meets you. Where will I sit when you come up? Pack up and leave?

9. Be sure to know whether the other party is the boss of HR or testing or the position of the manager. You need to know the position of the other party, otherwise you will not be able to play cards in a targeted manner.

10. Try not to mention that I can learn. The company does not have the resources to find someone to teach you. What you want to mention is that I am also self-studying, reading xxxx books, my learning ability is very strong, and I am also very adaptable, so I will be able to quickly integrate into the environment.

11. For other things, you should be confident and firm, so that the interviewer will feel that although your business may not be the best, you are still reliable. After all, business ability can be improved, but the quality of people is not what they want to cultivate.