Experience Sharing of Software Test Engineers

A few days ago, a friend went to interview for the position of software testing engineer, and when he came back, he told me about his interview experience with confidence. However, in the end the interview went down the drain. In fact, I have already expected it...

In the interview process, if many details are not handled well, it will be cold in the end, no matter how good your software testing skills are.

In fact, the interview is nothing more than three parts: self-introduction, interviewer's questions, and salary. Today, I will talk to you about the software testing interview.

In the interview process, if many details are not handled well, it will be cold in the end, no matter how good your software testing skills are.

1. Self-introduction

A concise and informative opening statement is the beginning of leaving a good first impression on the interviewer. When making self-introduction, the following points must be paid attention to.

· When introducing yourself, mention your basic personal information, try to maximize your strengths and avoid your weaknesses.

For example: if you are too old or too young, don’t report your age frankly;

·  If you switch to a software test engineer across majors, avoid actively mentioning the wrong major, and reduce the probability of HR's careful investigation.

If you mentioned it in the self-introduction and were interrupted by the interviewer to ask for details, then you have to guide the interviewer to ask about the projects you have done (if you just finished software testing, then take out the content of the practical class for emergency) . This makes it easier to win favor;

·  When introducing yourself, try to highlight your work experience, and avoid mentioning if you have no work experience.

For example: if you are too old or too young, don’t report your age frankly;

·  Highlight your skills.

Especially those related to the description of the job itself, or those that are more valued by the industry. The more you know the following points, the more likely you will be successful in the interview.

1) Have done 1-3 large-scale projects;

2) Ability to write test requirements analysis;

3) Proficient in one of linux system, windows system and MAC system;

4) Skilled use of mainstream databases such as Mysql/Oracle;

5) Skilled use of 1-3 mainstream programming languages;

6) Automated testing;

7) Performance testing;

8) Safety testing;

Finally, I will give you a summary self-introduction for your reference (if you have no work experience, replace the underlined part with the content of the practical class):

"Hello interviewer, my name is **** and I come from ***. I have been doing software testing for 3 years. During this period, I have done a lot of projects and accumulated a lot of testing experience. Currently I have been able to complete software testing independently. Before, I mainly did functional testing, app-specific testing and interface testing. I am also familiar with the application of linux, database, fiddler, and jmeter. I have also done it with jmeter Some performance tests, I have also done automated tests recently, mainly using the python+selenium framework. In addition, I usually like reading books and playing basketball. The above is my personal situation. You see, I still need to do it here Anything to add?"

Second, the interviewer's questions

In this link, you will usually encounter some routine questions, such as: What is your work goal? What skills do you have? What have you gained and experienced in the previous company? What is the reason for your resignation? etc. All you have to do is answer according to your personal situation. A reminder to everyone, do your homework in advance before going to the interview to avoid being unable to answer due to nervousness. Here are some common interview questions we have compiled for you:

1. Common sense questions.

Generally, the interviewer will ask a few questions, try not to make mistakes, and avoid meaningless deductions.

For example: What is the difference between HTTP and HTTPS?

Answer: The data transmitted by the HTTP protocol is unencrypted, that is, in plain text, so it is very insecure to use the HTTP protocol to transmit private information. In order to ensure that data can be transmitted encrypted, HTTPS was born. To put it simply, the HTTP protocol is a network protocol built with the SSL+HTTP protocol that can perform encrypted transmission and identity authentication, which is safer than the HTTP protocol.

2. Technical issues.

Generally, according to the position you are applying for, you will ask detailed questions about a certain section of the test section. To give you some directions for preparing answers, you can refer to the directions for preparing your own interviews. example:

1) How does Charles work? How to capture Https web pages, what special attention should be paid to IOS?

2) What are the commonly used ADB commands?

3) What are the commonly used Linux commands?

4) What is the difference between mobile Android and IOS systems? What should I do when a crash test occurs in the APP? etc.

3. Questions about work experience.

The most common are broadly divided into three blocks:

1) What is your company's testing process?

It is recommended to combine the orthodox process and the relevant situation of the former company to express the testing process of a certain project more fully.

2) specific project details.

Generally, the interviewer will ask questions based on the content of your resume. For the project you write about, you must be familiar with it (preferably proficient), at least you must be able to stand up to questions, and avoid writing about areas that you don't understand at all.

3) What is the most difficult bug you have ever solved?

When answering, you should not only describe what the bug is, describe the difficulty, but also describe the solution suggestions, preferably at the code level (this will add points for yourself).

Third, the salary part

In terms of salary communication, many small partners are discouraged when talking about salary. The subjective reason may be that you are not confident enough about yourself. You feel that there are many people who are better than you. If you ask for a higher salary, will the interviewer choose you? But in fact, understanding the salary standard of the company's recruitment is an important reference standard for judging your own salary. If during the interview process, you underreport your salary out of timidity, you will be the one who suffers in the end.

Therefore, when negotiating salary, we should pay attention to the following points:

1. If the interviewer does not clearly want to hire you, please do not raise your salary first.

If you rashly put forward your salary floor first, it may cause the following results:

①Bad impression (for the money? Just want to dawdle?);

② Get a salary that is lower than what the recruiter actually wants to give (for example, if the company plans to recruit employees with a monthly salary of 10K, and you propose that you want 9K, then in the end, you can only say that you have saved costs for the company);

2. Constantly dig out the highest salary standard for enterprise employment.

During the interview, the interviewer will also practice Tai Chi, and most of them are unwilling to disclose the salary standard. At this time, you must put forward the specific content and explore the salary standard of the other party. For example, I am a software test engineer who has been working in automated testing for two years. Then, you can ask the interviewer like this:

①Professional fields you are familiar with:

"I personally have done a lot of projects in automated testing, and I am familiar with this field. Your company's current work content is biased toward automated testing or manual testing?"

Tips: Judge according to the interviewer's answer. For example, if you tend to recruit manual testing, then the salary standard is often not too high.

②Fields not familiar to me:

"I was mainly engaged in automation testing before, and I have a certain understanding of the security testing field recruited by your company, but I don't have enough practical experience. Is this position that your company recruited only responsible for security testing? Or does it also involve some automation? The content of the test?"

Tips: According to the interviewer's answer, judge the salary standard you can get. For example, if you only need to be able to test security, then your salary will only be a little more than that of Xiaobai; if you need both, then there is room for a price increase.

3. When the other party expresses that they want to hire you, raise your salary.

There will be one round, two rounds, and three rounds of interviews in many interviews. No matter how many rounds the company has to interview, once they confirm that they want to hire you, they will definitely mention salary. At this time, you can reasonably propose a salary.

4. What if you have to set a salary standard during the initial test?

Please start playing Tai Chi, lead the chat with the interviewer to the second point, and finally give your expected salary that you think is reasonable.

In fact, negotiating salary with the interviewer is not terrible. What is terrible is that you do not understand the market and market conditions, and you have lost the standard of judgment.

To sum up, the interview is part of what you have to go through after you learn software testing or when you change jobs. Successful application is also an affirmation of one's own learning achievements and experience accumulation. A good horse with a good saddle, a good you and a little interview skills can make the interviewer discover you as a shining star faster.
 

Finally, I would like to thank everyone who has read my article carefully. Reciprocity is always necessary. Although it is not a very valuable thing, you can take it away if you need it:

These materials should be the most comprehensive and complete preparation warehouse for [software testing] friends. This warehouse has also accompanied tens of thousands of test engineers through the most difficult journey, and I hope it can help you! Partners can click the small card below to receive 

 

Guess you like

Origin blog.csdn.net/OKCRoss/article/details/131398697