A resume is a knocking stone, but what kind of material it is is a matter of opinion. So what makes a resume a good knocker? Here are some personal insights that I hope will help test engineers who are or are looking for a better career opportunity.
First, for those who have been enlightened in the testing industry: highlight the advantages of project experience.
To the extent the company allows, give a brief description of the projects you worked on. For example, the architecture of the project you are involved in, the implementation technology, etc., these things can show the extent of your knowledge of the test project, and thus can show the extent of your experience.
For example, we can tell each other about our 4-tier architecture in our project introduction: Database, middleware, web service, the client, the use of the c/s mode, and so on, if you think you can, we used our databases are what, what middleware is and so on, after briefly describe the project, you can be very honest to tell you to apply for a job by the company, in this project is mainly responsible for you, For example, which level of testing is the main responsibility, whether the main responsibility is test execution or test involvement, etc.
Two, for the new test: remember the “principle of honesty”.
Some people may not attract attention to the degree, graduated from colleges and universities, but please generous write out, bold to tell you the company, only you recognize yourself, to hope that others recognize you, if you join the company, you can also be tough work.
Degree and college can be a bit of an obstacle in your interview process, but degree and college can only prove your past, not your future. Nowadays, most companies recognize a person’s ability, education background, the university you graduated from is just a little bit out of the place.
Three, some general principles.
1. Description of test ability.
This is a lot of people like to list, in fact, in my opinion this is a big no-no. General listing usually does not reflect a person’s ability, some people go is the test management line, he is good at the process of control ability; Some people are taking the performance test route, he is skilled in the use of a specific or certain tools. Never describe yourself as an omnipotent person, which, in my opinion, is often a person with no special skills.
2. Add some unique testing insights if you can.
What I don’t like very much is that once I ask anything, it is all a set of things from the book. In fact, there is a big difference between the book and the reality sometimes. To show your unique insight at the right time can prove that you are a person who learns and applies flexibly, and such a person is very popular in any unit.
3. Testing is actually a process of applying computer technology and industry knowledge to carry out a strict test on software products.
Imagine testing a database if you don’t know anything about it. If you test a bank’s business system and you don’t know the business knowledge, how do you test it? Even as a beginner tester, without understanding the business, can you tell if the results of a use case run are correct or wrong? If all is judged by the expected results in the test case, the overall effectiveness of the test depends entirely on the level of the person writing the test case.
4. For software testing, we should first be familiar with the functions and background knowledge of the tested products, so as to carry out comprehensive verification and quality control of the tested software.
Testing tools and testing methods are just a skill that must be mastered in order to better test software, just like developers must be able to use JAVA and document writing must be able to use Word.
Below to prepare for you a inside test resources