I have an interview for a software testing job tomorrow, what can I do now?

First of all, time does not allow you to conduct a large-scale professional review, so you should make preparations for immediate results :

1. Organize your instruments.

Go for a haircut first to make yourself look more energetic, especially for boys. Arranging your hair and trimming your sideburns can quickly create a better impression of yourself.

Girls put on some light makeup before going out, and boys can also apply some cream or body lotion. Don’t believe that boys will be very girly when they use cosmetics. A boy who smells like sweat and a boy who emits a faint fragrance will give people a closeness The feeling is different. Because girls pay more attention to this aspect, they don't talk more about it.

During the interview, hold your head up and make eye contact with the interviewer. Many testers are not in good shape, and there are not a few of them hunched over. If they are familiar with each other, there is no big problem, but for those who meet for the first time, they will give people a feeling of laxity and unsteady will.

2. Understand the basic situation and corporate culture of the company

At least you need to remember the name of the company and the company's main business. If you really can't remember it, don't talk nonsense. Mispronouncing the company name will directly reduce your impression score to 0.

There are also some small tips. It is best to know the name of the founder or chairman of the company. If you have published a book, you can read it. Some companies are more obsessed with their founders than you might imagine.

It is also necessary to understand the company's corporate culture, which determines what personality the company prefers to hire. Sometimes you will encounter some interview questions like: what do you think is your most precious quality, and what do you like most about yourself can be answered more specifically.

3. Find out if you understand the company's interview process in the local network resources

Some companies have a slightly more complicated interview process. If you haven't contacted them before, you may be nervous, so you can ask in advance. If you haven't established a network of contacts locally, you can start preparing now.

Next, the interview questions that are most likely to be asked are predicted :

1. Self-introduction (should be a must)

It mainly examines your overall quality and professional skills. Self-introductions must be prepared in advance to reflect your professional ability and learning ability, and don't wait until all the content is thought of on the spot.

2. How do you usually learn technical or professional knowledge?

It mainly examines your learning ability, and you can talk about the ways of learning, such as reading books, videos, forums, blogs, etc. To be more specific, persuasion will skyrocket. For example, the books I often read include "The Way of Google Software Testing", "The Art of Software Testing"...

3. Tell me about your company’s testing process

It mainly examines whether you are really familiar with software testing, and usually needs to add some company-specific implementation conditions to the standard software testing process.

4. How do you deal with frequent changes in requirements? What do you do when something goes wrong online?

It mainly examines whether you are heavily involved in project release, and whether you can summarize experience and lessons from previous work.

5. Coverage of automated tests

It mainly examines whether you have experience in automated testing and your understanding of automated testing.

If you don't have enough time to prepare, it is very necessary to prioritize these interview questions that are most likely to be asked. However, the test-related interview questions are very, very extensive, and basically impossible to list exhaustively. The knowledge reserves you need to prepare in an interview are mainly divided into:

1. The technical points mentioned on the resume, these will be asked first;

2. Test theory related

3. Network knowledge related

4. Related to automated testing

5. Operating system related

6. Programming language related

7. Other

Here are some common interview questions, you can look at them according to your schedule:

test theory

1. How to write a test plan?

2. What are the common black box testing methods? and use one of the methods as an example

3. List some test points of the login function?

4. What is the difference between web testing and app testing?

5. How to deal with bugs with low recurrence rate?

6. What is stability test?

network related

1. What are the three-way handshake and four-way wave?

2. What happens when you enter url in the browser address bar?

3. The OSI seven-layer model of the network

4. The difference between GET request and POST request

5. The difference between session and token

6. The difference between session and cookie

7. What are the common status codes?

automated test

1. What is PO mode and why should I use it?

2. What projects are suitable for automated testing

3. What are the stability factors that affect the operation of ui automated test scripts?

4. If an element cannot be positioned, what reasons do you generally consider?

5. How selenium works

operating system

1. What is multi-process

2. What is multithreading

3. How to terminate the process

4. How to check CPU usage?

5. How to check system performance?

programming language (Python)

1. What is the difference between unittest and pytest?

2. What is a decorator

3. The difference between instance method and class method

4. The difference between dictionaries and tuples

5. What technology stack do you use for automated testing

other

  • Tell me about your understanding of performance testing, load testing, and stress testing
  • How to use jmeter to find out the maximum number of concurrent users of a certain interface?
  • The principle of bubble sort
  • What is cache avalanche?
  • What is cache penetration?
  • What are the benefits of database indexes?
  • Why are there sub-databases and sub-tables?

The interview is a systematic inspection of the skills you have mastered. Some companies will be very comprehensive, and some companies will be more one-sided. review.

Of course, systematic and comprehensive knowledge mastery is the most important. If you always collect various interview questions before the interview, it is likely that the previous related skills have not reached the level of systematic mastery, so you should pay more attention learned.

Good luck with your interview.

Guess you like

Origin blog.csdn.net/Androidyuexia/article/details/132169055