Last month we introduced an internship program for our Sofia office. However, due to the pandemic outbreak, we had to postpone it. However, we decided that we will do a few interviews directly with some of the candidates for our Junior positions. For only a week, we received more than 50 resumes.
I want to give you a few DOS and DON’TS for improving your CV and increasing your chances drastically to receive a call for an interview. Also, at the end of the article, I will share a list of resources and books that can be used to gain even more knowledge in the field of QA and Automated Testing.
I want to emphasize that some of the tips are highly opinionated and based on my preference and experience. However, I think all of them are valid. I heard similar pieces of advice from the HR professionals I have had the chance to talk to regarding the matter.
Be sure that we spent the time read all emails and CVs in detail, trying to see beyond the “subjective” look.
However, I believe not all employers will spend the time doing it, nor will they send feedback about what was wrong.
DOS and DON’TS for Writing a Great QA Resume
Dos and Donts
-
Explain what you are searching for and why this is the case. For example, clearly state the desired direction- manual or automation, why this is the case.
-
Search more info about the company and explain why you want to work for this particular company.
-
There are many proven platforms for the creation of beautiful CVs- you can use one of them, for example- Enhancecv. I liked some of the custom CVs that you designed. However, some were hard to read. Usually, the CV needs to be easy to be scanned fast.
-
Export the CV as PDF.
-
The best practice for the name of the CV file should be- firstName-lastName-CV.pdf (it is easier this way to search in a folder containing many CVs)
-
Especially if you are applying for a Junior position- your CV should be short- 1 page long. Do not write a resume more than 3 pages unless you are applying for the team lead or managerial positions.
-
I highly recommend getting certified. The bare minimum is to have a relevant QA course or programming one in case of test automation. About the certification- I mean ISTQB Foundation- it is a big plus.
-
Add up-to-date representative photo of you not just cropped from one lying on the beach.
-
The most crucial info is to mention the related courses you have completed and maybe saying the score.
-
It is valuable to add projects you have worked on- links to GitHub.
-
Apply all these tips to your LinkedIn profile. If you don’t have one, you should definitely create.
-
If you want to get more practical experience while waiting to get hired somewhere, you can try freelance QA platforms such as uTest.
-
If you haven’t worked something related before and don’t have a technical university degree, I believe the first thing you have to do is to participate in a QA fundamentals course. The next step may be to take some relevant online courses in Udemy or Pluralsight and mentioning this in your CV. Like the ISTQB certificate, this will mean a lot when we see it.
-
You can specify some related technical books you have read.
-
Just send an empty email. Even if there isn’t a requirement for a cover letter, more or less, the email is this. It should be personalized for the company and position you are applying to.
-
I would suggest not to use the general EU CV Word template (some companies HRs won’t read them or ignore them). My subjective opinion is that this does not apply to all types of works, but it is essential for IT specialists. (formating sometimes will be remembered and make the impression that you have spent the time to prepare yourself which show other qualities which companies are usually looking for)
-
There isn’t much value to add many long paragraphs explaining your duties in non-related past jobs. We usually just look at the field and type of work. The more technical it was, the better. In some cases, work with people is also a plus. (customer service, teaching, etc.
-
Write how much experience you have in logging bugs or test cases- if you even haven’t worked as Junior. It is much more valuable to add the places where you regularly educate yourself about the field.
-
The next tip is maybe just my subjective opinion. Feel free to ignore it: Add only relevant to the position information in the CV. It is not essential that you have a driving license or can repair bikes. Mentioning your interests is another thing since this is something we consider whether you will fit in the current team (will you have topics to talk about with others during lunch)
-
It is better to use the official channels of communication. For example, I gave an official email address. It is OK to ask questions, mainly if something is not explained in the description (you are decreasing your chances if you are asking me something that is written and you haven’t spent the time to read the whole post). I will respond at the same speed using the email than pinging me in Messenger. A much better channel might be LinkedIn. I consider Messenger to be too personal for such communication even when the post is from my account. Again asking for feedback and results should be addressed first via email, not directly asking in Messenger. As we said, we promised to contact everyone, so creating pressure won’t help.
-
Do not mention technologies and tools (skills) that you have only seen for a few minutes on a lecture or course, but you haven’t tried much yourself.
-
Single spelling error is sufficient to reject your resume. Spell check twice.
-
Make sure you write your name, email address and phone number on top of the resume.
-
Make sure you write your name, email address and phone number on top of the resume.
-
Attach/add links to any related recommendations (by lecturers or previous employer). You can even ask your QA course trainer to give you one if you were an exceptional student. Even this small thing will differentiate you from the rest.
I believe that following these tips and tricks will increase your chances to receive an interview call. To prepare for the interview you can check my related articles- 78 Interview Questions for .NET Software Developer in Test and Interview Questions: How to Test a Login Form- 110 Test Cases
Below you can find a list of few resources for gaining more QA and technical knowledge. Also, at the end of the post, you can check my full list of recommended literature.
Sample Manual QA Job Offer
Main Responsibilities
Understand the business objectives of the company’s software product line. Have a critical eye for detail and be motivated to explore our products in pursuit of identifying problems that will be important for our customers.
Day-to-Day Duties Time Distribution
50% define test plans, create and execute test cases;
20% take part in software design discussions, reviews, planning and strategy sessions;
20% analyze product requirements and take part in design of test strategies;
10% compile and communicate test status reports;
Core Requirements
Additional Resources for Gaining QA Knowledge
Here is a list of the few resources I gave before to people just finishing QA academies.
List of My Favorite Programming, Testing and Automated Testing Books
And of course, if you are more into the Automated Testing, you can check my newly released book- Design Patterns for High-Quality Automated Tests: High-Quality Test Attributes and Best Practices (#1 New Release on Amazon).
Be healthy and safe. Good luck!
