In the interview, how to answer the questions raised by HR largely determines whether the interview can be successful.
The following are 10 questions that software testers are often asked during the interview process, and tell you how to answer them so that you will not be routinely used by the interviewer...
please introduce yourself
Mistakes:
Most people answer this question too often, just say name, age, hobbies, work experience, which are all on the resume.
Main points:
Some of the resumes can be mentioned in one or two sentences, focusing on answering the questions that the interviewer cares about, that is, whether the job seeker is qualified for the job.
Including: the strongest skills, the most deeply researched technical fields, the most positive part of personality, the most successful things done, major achievements, etc. These can have nothing to do with learning, or they can be related to learning, and the focus is good personality and ability to do things.
The time for self-introduction should not be too short, a self-introduction of tens of seconds to a minute is too thin and unconvincing; it should not be too long, and an organized three to five minutes is more appropriate.
why did you leave your original company
Mistakes:
Many people will crackle and talk about a bunch of bad things and complaints from the original company and management personnel.
Main points:
Be careful when answering this question. Saying that the original company and management personnel are not good, firstly reflects the job seeker's poor moral character and lack of confidentiality awareness, and secondly, it will bring negative emotions to the interviewer.
The best way to answer is to blame yourself for the reason for leaving, for example: the original job does not match my career plan, I want to work in the job I majored in; the original job has no room for development, and I hope to get a job. A job with more room for growth.
Answers should preferably be positive.
How much do you know about our company?
Mistakes:
Job seekers are not prepared at all during the interview, they go directly to the interview, and they don't understand the answer.
Main points:
Before the interview, check the company's establishment time, development history, main business, main achievements, and development plan on the Internet. When answering, you can briefly mention the establishment time and development history, focusing on the company's business, achievements and development plans.
If you can’t find information about the interview company, just answer directly: I’m sorry, I didn’t find more information about the company, I only know that it’s a technology company, I want to know more about the company, ask questions, and guide the interviewer to answer question
Tell me about your biggest weakness?
Mistakes:
Answer the disadvantages directly: I am utilitarian, very lazy, and have low work efficiency.
Smart answer: My biggest shortcoming is too much pursuit of perfection.
Main points:
Interviewers like job seekers to start with their own advantages, add some minor shortcomings in the middle, and finally turn the question back to the advantages and highlight the advantages. After all, everyone likes to deal with smart people.
Tell me about your views on industry and technology development trends?
Mistakes:
Talk about the IT industry, from the past twenty years to the next two decades.
Main points:
Before the interview, understand the company's main business, the technical requirements of the interview position, and the development situation. When answering, you can talk about the company's situation, and talk about industry trends and technological development according to the company's needs. You can't talk about it in general.
What do you think about overtime?
Mistakes:
I can't accept overtime, or I'm used to it, I used to work overtime every day
Main points:
I am a consistent and responsible person. I will take the initiative to work overtime when the job requires me, but at the same time I will improve work efficiency and reduce unnecessary overtime.
What do you do when you disagree with your superiors?
Mistakes:
I believe in myself and will stand up for my own opinion, or I will obey the leadership of my superiors.
Main points:
I will communicate well with my superiors, express my opinions and worries to my superiors, and obey my superiors' opinions on general issues. However, if the superior's opinion may lose the company's major interests, I hope to communicate with higher-level leaders.
Why do you want to work in our company?
Mistakes:
Several other companies are waiting for my reply, and I haven't decided whether to work here or not.
Main points:
After the preparation before the interview and the conversation during the interview, you should have a certain understanding of the interview company and be able to answer in detail.
For example: the company's technology development environment is very attractive to me; I agree with the company's development philosophy, and the company's development plan is in line with my career plan; the company's strength is strong, its development prospects are good, and it is very competitive in the same industry.
Such an answer shows that you have done some research, and it also shows that you have a more specific development plan for your future.
What are your salary requirements?
Mistakes:
Insufficient confidence, the asking price is too low, or feeling too good about yourself, asking for a high price.
Main points:
If the job seeker's salary requirements are too low, it will obviously belittle his own ability; if the salary requirements are too high, it will appear that the job seekers are too heavy, and the company cannot afford it.
1) If the job seeker really wants to work in the interviewing company, it can be said that I focus on finding the right job opportunity, so as long as the conditions are fair, I will not care too much. I believe your company will be friendly and reasonable in dealing with my problem.
2) I am very confident in my technology, so I speak with my strength. I have been trained in professional and systematic software programming. I have done XX project and mastered XX technology. I don’t need a lot of training from the company, and I am particularly interested in programming. , Self-learning ability is also very good.
Therefore, I hope that the company can give me a reasonable salary according to my situation and the level of market standards.
3) Give a specific number, which is the minimum salary you can accept, which shows that you have done industry research and know how much you are worth, and the same interviewer also probably understands your ability.
Notice:
You need to understand whether it is pre-tax or after-tax salary. Generally, pre-tax salary is discussed in interviews with companies. If you don't understand, ask for clarification.
Do you have any more questions to ask?
Mistakes:
No questions, or how long you can get a raise.
Main points:
Businesses don't like people who say "no problem", and don't like issues like salary increases and benefits.
When asking questions, it should be related to the interview position, for example: Does the company have any training programs for new recruits, can I participate? What is the company's promotion system? Which department does my position belong to, and how many people are there in the current department team?
Interviewers like this kind of question more, because it reflects your strong interest in the company and your self-motivation.
[Finally share some of my interview experience and resume]
These are the interview questions I often memorize
PS: In addition to the hundreds of thousands of words in the reference answer, not all the answers have been put up. The high-definition print version has more than 400 pages, and you can get it directly by leaving a message
1. What is your testing career development?
2. What qualities do you think testers need to have?
3. Why are you able to do this line of testing?
4. What is the purpose of the test?
5. What are the stages of the test?
6. What is the test object, purpose, test basis and test method of unit test?
7. How to deal with overtime issues
8. Combining your previous study and work experience, how do you think the test should be done.
9. Why did you choose the software testing industry?
10. Describe the software development and testing process based on your previous work or study experience, which roles are responsible, and what do you do
11. Tell me about your understanding of software testing/quality assurance based on your experience
12. What is the process of software testing?
13. What is your understanding of SQA's responsibilities and work activities (such as software measurement)?
14. Talk about your understanding of software configuration management
15. How to write test plans and test cases
16. Talk about the general situation of mainstream software engineering ideas (such as CMM, CMMI, RUP, XP, PSP, TSP, etc.) and their understanding
17. How do you ensure the quality of the software, that is to say, how do you think the quality of the software can be guaranteed to the greatest extent?
18. Based on the current national conditions in China, most companies have tight project schedules, fewer personnel, and no or very irregular requirements documents. How do you think the quality of software is guaranteed in this situation? (Most companies want to know most How do you ensure the quality of the software in the face of this difficulty, because this is generally the case for these companies-neither want to invest too much but also want to ensure quality)
19. What qualities and skills should a test engineer possess?
20. Some key points of software testing
21. Cultivation of software testers' own quality
22. Why do you need to carry out testing work in a team?
23. What types of software testing are you familiar with?
24. What do you think is the key to doing a good job in test case design
25. Please introduce the meaning of various test types in detail
26. What is the purpose of the test planning work? What are the contents of the test planning work? Which of them is the most important?
27. What do you think is the key to doing a good job in test planning?
28. When the developer says it's not a bug, how do you deal with it?
29. What do you think are the advantages of testing?
30. What is the system bottleneck?
31. What is the main content of the document test?
32. To what extent do functional test cases need to be detailed to be qualified?
33. What is the difference between configuration and compatibility testing?
34. What does software documentation testing mainly include?
35. Can black-box testing be performed without product manuals and requirements documents?
36. What is the "pesticide weirdness" in the test?
37. In the configuration test, how to judge whether the found defect is a common problem or a specific configuration problem?
38. Why try not to allow time for well-off employees to do some testing?
39. Is it possible to fully test the program?
40. Where are the main risks of software testing?
41. The more defects found, does it mean that there are more software defects?
42. Can all software defects be repaired? Should all software defects be repaired?
43. Are software testers QA?
44. How to reduce the losses caused by testers’ job-hopping?
45. What is the difference between test product and test project?
46. What are the points for attention in joint testing with users (UAT testing)?
47. How to write a test report submitted to the user?
48. What is the status of testing tools in testing work?
49. What are the common test case design methods? Please use specific examples to illustrate the application of these methods in the test case design work.
50. What do you think is the key to doing a good job in test case design?
51. Describe in detail the complete process of a test activity.
52. Have you ever engaged in performance testing work before? Please describe the complete process of your previous performance testing work in as much detail as possible.
53. In your previous work, what was included in a software defect (or bug) record? How to submit a high-quality software defect (bug) record?
54. Have you ever used some testing tools when you were engaged in performance testing? If so, please describe the working principle of the tool, and describe how the tool is applied in actual work with a specific working example.
55. What do you think is the purpose of performance testing? What is the key to doing a good job in performance testing?
……
This post ends here, and finally, I hope that friends who read this post can gain something.
I have prepared all the interview questions in the article, please reply to [Interview Questions] to get them for free if you need them.
If you think the article is not bad, please like, share, and leave a message, because this will be the strongest motivation for me to continue to output more high-quality articles!