It is said that the post-00s will lie flat, but there is one thing to say, the bull is still the bull.
No, some time ago, a post-00 came to the company, and he had only worked for two years, and the starting salary for job-hopping was 18K. I thought he was a young and promising technology expert, but after getting along for a month, I found that the technology is just like that.
Asked how he managed to talk to the boss about 18K, he said that he performed well in the interview, and shared some interview tips. Sure enough, he should pay attention to speaking skills during the interview. Being able to brag is also a skill.
01. Interview trilogy
A complete interview consists of the following three parts: self-introduction, project introduction, and technical questions after passing the project.
1. Self-introduction
Here I will not share how to introduce myself, speaking skills, etc. I believe everyone is familiar with the routine, here are a few details
1. When introducing yourself, you need to have the confidence. Some students are obviously very skilled, but they are nervous when they are interviewed. It's nervousness, but it's a sign that you feel incompetent, so it's important to have confidence and self-confidence.
2. When you introduce yourself, you can keep smiling and speak slowly and clearly. The interviewer can judge whether you are relaxed or nervous through your expression, tone of voice, and speaking speed. Therefore, even if you are nervous, you must find a way to stay calm. You can add some points on your face Smile and speak slowly so the interviewer can hear what you are saying.
3. The content that should be said when introducing yourself should not be too much and too complicated. If it is too complicated, it is easy to miss the key points. The general content includes: your name, work experience, what abilities or skills you have, and what achievements you have achieved (preferably with data ) and so on, the duration can be controlled within 1-2 minutes.
2. Project introduction
From several parts, first project scale, including project code scale, demand scale, use case scale, workload, progress, quality and cost;
Then there is the overall testing process , then the roles and responsibilities , and then the own characteristics in the project , such as what you do best, when you encounter the biggest difficulties (how to solve them), and where you need to improve, It is best to have corresponding data to support, and finally experience.
3. Interview questions
1. Related to career planning
What is your testing career progression?
The more testing experience, the higher the testing ability. Therefore, my career development needs time to accumulate, step by step towards senior test engineer and senior industry expert. And I also have a preliminary career plan, accumulate testing experience in the first 3 years, ask myself according to the key points of how to be a good test engineer, constantly update myself and correct myself, and do a good job in testing tasks.
Why did you choose the software testing industry?
Because I knew about the software testing industry before, I felt that the development prospects were very good.
Where is your greatest interest in testing? Why?
The greatest interest is challenging. Since I don't know where a bug might appear, I'd be happy to find one. And the test requires a lot of patience and care. I can easily find some details.
2. Personal ability (soft power, professional ability)
What specific tasks have you worked on in your previous testing jobs? Which part of the job are you best at?
I usually do web testing, build a testing environment, and conduct integration testing, system testing, regression testing, etc. for a program. Also write test cases and some documents, user manuals, functional test documents, etc. Best at functional testing.
What test case design methods are you familiar with? Please use specific examples to illustrate the application of these methods in the design of test cases.
There are two types of testing, black box and white box. Black box includes equivalence class division method, boundary analysis method, causal diagram method and error guessing method. White box has logical coverage method, loop test path selection, basic path test.
Example: In an integrity query where multiple conditions are entered at once. Using the equivalence class division rule and the boundary analysis rule, first use the equivalence division method to get one or more test cases whose results are OK, then confirm multiple NG test cases, and then use the boundary value analysis method to separate the results The test cases of OK and NG are extended and supplemented.
In your previous work, what was included in a software defect (or Bug) record? How to submit high-quality software defect (Bug) records?
Detection time, system environment, hardware environment, severity, program version, confirmer, function template, problem description, detailed operation steps, whether it will be reproduced. The problem description and detailed operation steps should be as detailed as possible. Bugs should be written in written language as much as possible, and the defects with relatively high severity should be tested in the same environment. In C\S mode, if the conditions are met, you can use the substitution method to confirm whether it is a client-side problem or a server-side problem.
What specific tasks have you worked on in your previous testing jobs? Which ones are you best at?
(The answer to this question varies from person to person. You can answer based on your own project experience. When answering, you should highlight your own advantages and achievements)
Combined with your previous study and work experience, how do you think the test should be done.
According to my previous work and study experience, I think that to do a good job, you must first have a good communication. Only when the communication is barrier-free, can there be good collaboration and better efficiency. The other thing is that the technology must pass the test , To do the test, you must have enough patience and a good working habit. If you don’t understand, you should ask, and communicate with colleagues in real time. Only in this way can you do a good job in the test.
How do developers keep making low-level mistakes?
It is necessary to formulate some coding standards in the early stage of development, which can reduce many errors caused by personal habits. At the same time, testers should not blame the developers when they find that they have made some low-level mistakes, and should patiently point out the mistakes to them. Then you can have the developers test it themselves and find out what is wrong at first glance.
The relationship between development and testing?
Development and testing are an organic whole. Before the product is released, development and testing are carried out in a cycle, and the detected defects must be modified by the developers and then continue to be tested. While developing, the test manager starts to write test cases, and the test documents should refer to the development documents, so development and testing are inseparable, and no product can be developed without either one.
Why test in a team?
Because it is difficult to know the quality of software without testing before it is released, just like ISO quality certification, testing also requires quality certification. At this time, it is necessary to carry out software testing in the team. In the process of testing, the problems in the software are found, and the developers are notified and corrected in time. When the release is about to be released, the quality of the software can be obtained from the test report.
meager strength
Finally, I would like to thank everyone who has read my article carefully. Seeing the fans’ growth and attention all the way, there is always a need for reciprocity. 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 friends who want to advance [automated testing]. This warehouse has also accompanied me through the most difficult journey, and I hope it can help you too! Everything should be done as early as possible, especially in the technical industry, we must improve our technical skills. I hope to be helpful……
