QA resume. Basic advice and some specific

Your resume is the absolute initial phase in any request for the employment process. It’s a chance to promote yourself and show that you are the best individual for the accessible position. Getting a meeting call relies upon how you present your aptitudes in your resume or CV.

The Software Testing market is getting serious and landing the position is much increasingly troublesome. For a QA Specialist position, Head recruiters are getting a bunch of Quality Assurance Tester resumes.

In case you’re a good Software Quality Assurance Specialist searching for a new position, take a look at how can you create your resume.

Sections to be preferably included in any resume

There are things that must be in every qa tester resume: they are about common sense, not about the specifics of roles and spheres of activity.


It is best to leave a few ways to communicate with you: for example, mail and Skype. If you don’t mind calling, but rarely use Skype – please state your phone number. Be sure to check your contact details: you can receive a CV with incorrectly specified mail and have not the opportunity to provide feedback. The same works on your side.


Behind every open position lies an unsolved problem. The employer is primarily interested in your essential skills. Give a recruiter / Team Lead / a PM/ QA manager the opportunity to quickly orient themself in your hard skills. The more important the information (in order for the company to decide on your candidacy), the higher it is worth posting. Therefore, describe skills by second or third item: after contact information and summary (if you decide to add it to the resume).

Your experience

is the one that presents you as a professional. It allowed you to master your hard skills, develop them, face many challenges, come up with solutions, offer ideas, improve your soft skills and solve more than one problem. For more information on your experience, please see below.


For some companies, the education of testers, developers and other technicians is important, so it is better to indicate your academic education briefly and clearly – university, faculty, speciality, obtained level and years of study.

Useful, but not necessary sections of the resume


This section, which goes after contacts, is relevant for those who already have experience behind their shoulders. A summary is like a review of your software tester resume. Here you should briefly describe your strongest skills, achievements, attention to detail skills, fields and domain areas in which you work, qa degrees and perhaps also your career goals. Two or three sentences are enough. A summary is your opportunity to present yourself not just as a “tester with 3 years of experience”, but as a Quality Assurance engineer with special experience and with certain achievements (for example, “who put the process of testing automation on three projects”).


IT is a globalized sphere, and relocation in is not uncommon. If you are ready to move to other countries and cities, or if you are considering also remote possibilities of cooperation, it is worth mentioning this along with contact information. If you are looking for a job in the office only in your town, this paragraph is not mandatory.

Additional education and certification

Have you already completed 10 online courses? Or maybe have you studied at the Academy at a large IT company? Do you have Oracle – or ISTQB – certification? Notice that in your resume. First, for some companies, certificates may be mandatory, and second, the company will see that you are a person for whom learning is not just a word.  

Experience outside of main activity

If you have your pet projects (participated in hackathons, helped in the development of social or state projects), add this experience to your resume. Companies pay attention to this: people who care about the life around them and who are willing to spend their own time studying new technology or developing pet projects are sure to love their business sincerely.


How to describe technical skills in a resume?

The most convenient format is the list of hard skills divided by groups. For example, it can be programming languages, frameworks, QA tools, bug reporting systems etc. Specify the skills that you really know, not those you’ve just read or heard about. Knowledge of the theory is essential, but each technical specialist performs tasks due to hard skills.
What to do with technologies that you haven’t already possessed at a sufficient level, but that’s your goal? Specify them in Summary or Linkedin. If you have not-for-profit experience with them (for example, used only in pet project), but you are interested in working with them in the future, add this to your qa engineer resume too: the HR will navigate easier.

How to describe the technical experience in the resume?

Of course, the most important is what tasks were in your area of responsibility and what your personal achievements were. But keep in mind: companies are usually interested in knowing not only what you were doing, but also what team you were working on (5 people or 100), what technologies were generally in the project (not only the ones you worked with), what the project was about (in a nutshell) and how long have you worked in every company and every office.
Often HRs can see in the description of the experience of the answer to the question “What you did”?: developed functionality, wrote automatic tests and so on. This list usually coincides with what companies indicate in the job description. So, it is also worth adding paragraphs that respond to the question “What have you did”? – that is, to describe your achievements. For example: “Taught three juniors who have now become middle QA specialists”, “Developed the architecture of two test projects”, “Put the process of automatic testing on Java and wrote the framework”.

What additional links should be added to the resume?

Speeches and articles of your authorship

If you write articles for a company’s blog, perform inside a team or at open events, publish your texts on the websites of the IT community or have a record of your speech on Youtube – add this to your resume.

Technical accounts

Links to your accounts in Github, Stackoverflow can tell even more about you as a technical specialist than the resume and your accompanying sheet. If you are an active member of any of the technical online communities, add a link to these accounts in the list of contact information. In addition, you can add a link to the Linkedin profile: there is an opportunity to ask for feedback from colleagues from the previous team, for example.


QA resume sample