愿你我相遇，皆有所获！ 欢迎关注微信公众号：【伤心的辣条】 免费领取一份216页软件测试工程师面试宝典文档资料。以及相对应的视频学习教程免费分享！
As the saying goes: "resume is that you can enter a company stepping stone" . The interviewer will only give you a chance to interview if he sees a quality resume.
Many people will have this question. Why did I submit so many resumes without receiving an interview notice? Is there no HR to contact me by phone? Is my ability really bad? No one wants it in the society?
Not really.
As an HR, at least dozens or even hundreds of resumes must be screened every day. The average residence time of each resume is only 15 seconds, and even only 5 seconds when recruiting is busy.
If your resume cannot "prescribe the right medicine", you will not get the opportunity to communicate with HR and interviewers!
Today, let’s not talk about the fictitious, take a few minutes to teach you to write an excellent software test resume!
First of all, we need to know what content should be included in a standard resume, which is also the content that interviewers pay most attention to:
personal information
Personal professional skills
work experience
Project experience
Overall format
01 Basic personal information
At the beginning of the resume is personal information. Everyone has no objection to this, right? However, everyone understands differently what personal information should contain. My suggestion is:
1. To include: name, gender, education, working years, phone number, email address;
2. Does not include: photos (except for those who are particularly confident of oneself), graduate school (except for those who are particularly well-known), majors (except for those who are particularly proud);
the reason:
We are a technical post, and everything is given priority to technology;
If the school and major are the advantages, of course it is encouraged to put it first, and you can even write down briefly the awards won during the school. This is a bonus item. If not, please let the person who screens your resume see your advantage as soon as possible;
02 Personal professional skills
As a technical position, your personal skills are one of the most important points for interviewers. As a software testing position, if you want an ideal salary, skills should not be too thin.
Since it is a professional skill, remember to write something that you took out and apply for a test engineer. What does it matter if you say you are proficient in using office documents?
What's more tragic is that just being familiar with the method of writing test cases, is it supposed to have better test skills, but not as good as office use?
My suggestions for this part are:
1. Don't write "proficient" casually, especially for operating systems and programming languages. If you are really "proficient", when I didn't say it;
2. If the recruitment needs have clear skill requirements, please provide your own corresponding skill proficiency according to the priority;
3. To highlight your personal characteristics, you must write what you are best at first. Sometimes HR is really impatient to finish reading, focusing on up to 3 lines;
4. Resume is for others to see, to attract others' attention, provide content that others care about, and don't put your own proud but irrelevant specialties on the list; (summary of 2 and 3)
5. Personal abilities are written in familiarity and mastery, and even understanding. For HR, mastering means being able to use it, being familiar means having used it, and understanding means not being able. For the technology you really master, you can boldly write "proficient", and the skills that can be mastered must be the result of deep learning and accumulated experience.
6. The core of the resume is "personal ability". First of all, make sure to show the skills you have mastered, and you must be good at it, otherwise it will be embarrassing to ask three questions in the interview.
03Work experience
Work experience can simply list one's own experience in different companies, generally only need to provide time interval, company name, job title.
A few notes:
1. Don't write company introduction, don't care;
2. Do not write a job introduction, as there is project experience;
3. Each company should only occupy one row as much as possible, so as not to attract too much attention here;
4. If there are more companies that have stayed, it is recommended to adjust the position to the back of the project experience;
04Project experience
Now all companies attach great importance to project experience in addition to actual work experience.
And project experience is the most space in the resume, so you must write with great care.
The description of the project experience, on the one hand, is the basic information about the project, such as what the project does, what architecture is used, which core modules are included, and so on.
You need to explain your project on a technical level, on the other hand is the description of your personal responsibilities.
This must be organized and clear. The conventional format is: XX tools/technologies are used to implement (function, performance, automation) testing of XX modules, etc.
Please keep the project description as short as possible . Let's look at an example:
Project description: Transaction fund custody service means that the bank provides credit intermediary for both parties (or parties) who need to trade goods or services or have funds custody. One party deposits the funds in the bank and temporarily freezes it, and the other party provides the goods agreed by both parties For services or other matters agreed by both parties, the bank will assist in completing the transfer of funds in accordance with the agreement; if the two parties fail to reach a transaction or other matters agreed by both parties, the bank will return the transaction funds according to the agreement. If both parties to the transaction need the bank to hand over the warrants, the bank will assist in completing the exchange of relevant equity certificates according to the agreement.
If you see this description in your resume, what is your first impression?
My first feeling is that this person is too irresponsible to himself, and the project description is not his own summary, just copy and paste at first glance.
The second is that this person may not pay enough attention to the priority of the problem, such as such a long project description, what information do you want to tell the interviewer? Explain that your project is huge? outstanding? and then? What does it have to do with you who wrote this resume?
Since it is our own resume, I think all the descriptions must be made to highlight our abilities, contributions, attitudes, etc. Any content that does not reflect our strengths needs to be streamlined or even deleted.
So when writing projects and work experience, we can follow the STAR rule to write
S scenario: In what context is the project made and under what circumstances will it be completed?
For example: In order for users to have a better experience of xxxx, the company has developed xxxx. This project is mainly for xx users. It is composed of xxx and xxx systems or architectures and written in what language;
T task: What is the main responsibility in this project, for example: there are xx members participating in the module test, I am mainly responsible for xxx, and I am responsible for xxx use cases and report design and review organization speeches, etc. ；
Action A: What did you do in this task. For example: use xx to manage the writing of use cases, manage code and version through xx, what is done with xx tools, I use xx technology for the work of this module, etc.;
R result: What results have been obtained through this action, for example: xx use cases were written, xx bugs were found, and xx lines of code were written. Using the xx tool to make conclusions—stress test results, or test results, development results, etc., through the above I got some of the impact of the project on me.
Let's see how this project description is changed to this:
Project description: The system is a fund custody service platform. There are ten modules in the system. I lead three small partners to test the functions and performance of five of the main modules. After the project was released, there was no serious problem feedback.
how about it? How did you feel after watching it? Is it clear at a glance? Knowing the general function of the project, but also understanding the role of the candidate in the project.
Several considerations for project experience:
1. Write in reverse chronological order, that is, the most recent project is written to the top;
2. Pick a few typical projects and list them, which are projects that can reflect their own capabilities;
3. The project introduction should be concise, and the language should be refined by yourself. Don't copy and paste a large section of content that you don't read from other places, just highlight the importance of the modules you are responsible for;
4. The professional skills written above should be reflected in the work responsibilities of a typical project. If you write professional skills, you will have a lot of automation tools. As a result, the project is all manual testing, which is obviously problematic;
5. In the job responsibilities, select the typical parts that can reflect your professional skills and write them, and other content abbreviations that are the same as those done by others;
05 Overall format
First of all, this resume looks clean and tidy, organized, and pleasing to the eye, which is a plus.
Don’t have traces of copy and paste. Let me tell you a little secret. If it is a docx file and the system turns on Dousha Green, it is easy to see what is copied and pasted.
Secondly, the personal skills are very rich and fully meet the current market needs. Whether it is the theoretical basis, or the function, performance, and automation, it is reflected. The skills involved in any company can be used.
You have to understand that although a good-looking resume can open doors for you to interview, the interviewer will investigate you in the end, or whether the skill points reflected in your resume are genuine, and you have the knowledge points. And the degree of understanding, whether you can clearly describe the projects you have done, etc.
Even if you have only learned some knowledge points, but have not actually used them, it will be a bonus if you can describe them clearly.
Finally, we must remember that the most important thing to write a resume is to use your heart. If you don’t care about your stepping stone, how can you be sure that you really want to come in?
Finally: benefits given to testers
In the technology industry, you must improve your technical skills and enrich your practical experience in automation projects. This will be very helpful for your career planning in the next few years and the depth of your testing technology.
In the interview season of the Golden 9th and the Silver 10th, the job-hopping season, organizing interview questions has become my habit for many years! The following is my collection and sorting in recent years, the whole is organized around [software testing], the main content includes: python automation test exclusive video, Python automation details, a full set of interview questions and other knowledge content.
For software testing friends, it should be the most comprehensive and complete interview preparation warehouse. In order to better organize each module, I also refer to many high-quality blog posts and projects on the Internet, and strive not to miss every knowledge point. Friends relied on these contents to review and got offers from big factories such as BATJ. This warehouse has also helped many learners of software testing, and I hope it can help you too!
May you and I meet and you will find something! Welcome to follow the WeChat public account: [Sad Spicy Article] Receive a 216-page software test engineer interview book for free. And the corresponding video learning tutorials are free to share!
