How to write Software Tester resume in 2020?



Goal of Writing Software Testing resume

Are you confident that you can write a QA resume that will result in getting called for an interview session?
Recruiters are getting swamped on a daily basis with several hundreds of product testing resumes; therefore, you need
to able to write an eye-catching resume that will stop your prospective employer in his tracks and make them take a
second, look at your resume and then reach for the phone.

So keep on reading this article and it helps you to walk through writing an eye-catching QA resume process!


There is good news – structure can be arbitrary. But you should approximately follow next points:

  • Personal info
  • Objective
  • Summary
  • Skills
  • Employment history
  • Education
  • Additional information

Personal Info

Personal info should be located at the top of your resume and include next information:

  • First/Last name
  • Location, ZIP code
  • Email address
  • Cell-phone
  • Skype

Pay attention to your email address. It can’t be something like that: ‘’. I have seen once email address familiar to ‘’. It also looks weird. The best way is to use your First/Last name in your address. For instance, ‘’.

It would be great if you include links to social media (LinkedIn, GitHub) into your Personal Info.


Software testing resume objective is typically at the top of your resume and this is just one sentence of what position you are seeking because hiring managers might have several positions so you need to tell them specifically who you are.

Good example:

Objective: To obtain a QA engineer position. Looking for an interesting project where I can elaborate on my professional skills, study new technologies.

Bad example:

Objective: To get an interesting, well-paid job in the IT area with opportunities for professional growth.
Search for QA engineer, technical writer positions.


Good summary is several sentences that described your key experience & skills. In other words, it is a brief definition of your resume. Use it as the opportunity to catch the hiring manager’s eye. You shouldn’t copy your “Skills” section to the “Summary” section. Especially, with bullets. You should describe your strongest side of technical background and it should look like sentences but try to avoid using the “I” word in them.

Good example:

10+ years of experience as a software test engineer and lead test engineer in testing client/server applications.

  • Proficient in most test automation tools (Win Runner, QTP, Silk Test, etc), automation methodologies and in writing automated scripts.
  • Advanced level skills in test management tools like Quality Center (including administration)
  • Experienced in creating master test plans and detailed test cases based on off functional requirements and specifications.
  • Experienced in analysis of use cases, complex system requirements and business requirements to ensure testability of the product
Bad example:

I have over 2 year of experience in Software Testing (Web and Embedded);

I understand product development lifecycles (Waterfall, V-model, Agile/Scrum); ▪ Wide range of test methodologies, types and approaches knowledge and usage: ▪ Static and dynamic; ▪ Black-box, white-box, grey box testing; ▪ Ad-hoc, smoke, sanity, regression, functional; ▪ Performance testing using JMeter tool; ▪ Security, GUI, usability, reliability, installation, configuration, etc; Experience in financial application (web/mobile/desktop) and gambling/casino related applications (web/mobile/desktop)• Working experience in all QA activities during full software life cycle • Efficient communication in the international distributed teams • Analytical and logical reasoning capability


In this section, you should describe your technical skills.

Don’t forget about formatting (it must be list) and avoid next mistakes:

Common mistakes:

  • HTML is not a programming language.
  • MySQL is actually too. Split your skills by group or your proficiency. For instance: Software testing, Languages, RDBMS, WEB, OS, Other
  • Writing skills that you know not pretty well. “I have read about it once on Wikipedia” is not a reason to include it in your resume. Remember, you should verify your skills in the interview.


  • OS: macOS, Windows, Linux
  • Software testing: functional/ regression/ exploratory/ UI testing; testing of mobile and desktop applications; design/ redesign and execution of manual test cases; bug reporting and verifying; work with documents and technical specification;
  • Tools: Jira, Firebug, SoapUI, BareTail, SIP IP Phones;
  • DB: Mysql
  • Other: SVN, Git.

It would be a good way if you put points in front of your skills which defined your level of proficiency. It helps hiring managers to understand how good you in skill which they were interested in. In this case, you also can use infographics:

Set of skills for freshers:

  1. Main:
    • Knowledge of testing methodologies and software development;
    • Ability to prepare test documentation (test plan, test specifications, test report);
    • Finished courses on software testing in large companies;
  2. Will be a plus:
    • Knowledge of the principles of client-server applications, Web;
    • Basic understanding of HTML, CSS, PHP, JAVA, JS;
    • Basic skills in working with GIT, Jenkins, SVN and bug-tracking systems;
    • Knowledge JSON/XML
    • Understanding the database, knowledge of SQL
    • Learn to use Selenium;
    • Experience with Linux systems. The terminal, bash, etc.
  3. Bonus:
    • ISTQB entry-level certificate.

Set of experienced testers skills:

  • Analyze test results
  • Ability to code automated tests
  • Create test plans
  • Experience with an agile development process
  • Experience with web-based testing applications
  • Perform manual and automated testing
  • Record test progress and results
  • Research and analyze product features being tested
  • Research new tools, technologies, and testing processes
  • Capable of using source code repositories
  • Communicate with technical and non-technical Resources
  • Identify areas of improvement
  • Identify, isolate and track bugs throughout testing
  • Identify potential problems users may encounter
  • Perform and document risk analysis
  • Perform manual and automated testing
  • Record test progress and results

Employment history

It is a custom to write about experience in reverse order. In this part of a resume follow the next structure:

  • Years
  • Company
  • Position
  • Role description
  • Project description
  • Tools and technologies

You shouldn’t detail describe your irrelevant jobs. And If you have one try to define previous job responsibilities more matching to position which you are applying for. Or describe your irrelevant position in several sentences to show the hiring manager that you don’t have gaps and do focus on courses which you’ve taken etc. Describe what problems you solved in your projects, how you impacted and improved the testing process (all others processes).

Good example:

Sep 2005/Current-Lead Test Engineer Centric Consulting

Client: Nationwide Insurance

Role: Lead Test Engineer 09/05 – Present
Project: Nationwide: Office of Investments

Nationwide Office of Investment is building an investment data infrastructure foundation with an integrated hub.


  • Develop test strategies, master test plans and test cases.
  • Main contact between the development team and the test team.
  • Communicate the test team’s expectations and strategies to the rest of the team and project manager.
  • Write extensive SQL queries and execute test cases.
  • Gather and maintain/load test data to execute test cases.
  • Coordinate the testing activities: prioritizing, scheduling, assigning work.

Web: HTML/CSS, PHP, JavaScript DB: Oracle, MySQL, Postgre, Cassandra, Mongo Task tracking: Jira, Redmine, Pivotal Test management: TestRail, Zephyr Test automation: Robot framework(Python), jMeter, Selenium IDE, Protractor, Cucumber Integration: Jenkins, Bamboo, Karaf, Docker

Bad example:

Junior Manual Test Engineer. Project: websites (Jan 2015 – Aug 2015)

12.2010 – 03.2012 LLC ” Poultry Bashtansky»
Purchasing Manager. -control quality materials procurement Wrote reports about purchased products -planning and control costs for the purchase -responsibility for the quality of the finished feed (purchase of all components + standard test).

11.2008 – 05.2010
Main department of statistics
Leading Specialist. and the accept audit on the investments in the logic and completeness -Search and error correction, after making statements to the database Summarizing on the basis of the data and reporting to management.


What should include in the Education section of a software tester resume?

  • First, list your highest level of education and name. If you’ve earned a bachelor’s degree or higher, do not include your high school information.
  • Include your GPA only if it is higher than 3.0 and it’s been less than three years since you graduated.
  • If you recently graduated and don’t have any experience you can mention appropriate academic honors or extracurricular leadership roles to your future job. Mention relevant modules/subjects you studied.
    For software testing positions candidates having computer networking and system administration skills are preferred. If you studied any subject or completed any course related to computer networking and system administration or Linux/Unix operating system knowledge, then add it in your resume.
  • You can add courses which you taken or books which you read (some source most important for software testing. You shouldn’t list all courses)

2007 Master of Science in Information Technology
Georgia Institute of Technology, Atlanta, GA
GPA: 3.75

Other Training:

  • Courses in Project Management: Project management essentials and Project management & team leadership.
  • Formal training in test tools: SilkTest, TestDirector, WinRunner. Testing Methodologies.
  • Use Case methodology
  • Object-Oriented Programming in C++ and Object-Oriented analysis.

Additional information (optional)

There is the section for the next data:

  • Languages
  • Marital status
  • Interesting hobbies
  • Any information is important to learn by an employer in the context of a particular job

How to write a fresher’s resume? Software tester resume sample for freshers

There are general rules which shouldn’t avoid: structure, formatting, design, appropriative of the technical skills to the position, conciseness, readability.

The key idea of writing freshers software tester resume is focusing on your technical skills and relevant courses, open-source projects, any volunteer work. You must show a hiring manager despite a lack of work experience you were ready for free work to get some relevant experience.

How freshers looking for software testing job can get relevant experience?

  1. Get some experience by working on dummy projects that available on the internet. Search for online dummy projects (e.g. Inventory management software) and download test software and all available documents. Follow the complete testing process like:
    • Requirements analysis
    • Writing test cases
    • Executing test cases
    • Preparing test reports
  2. By adding dummy projects learned from software testing courses:
    If you have joined any software testing course to learn manual testing and automation tools then you can put this dummy project experience in your resume.

How to write a software test lead resume?

To see the article
“How to write software test lead QA Engineer resume” + Software test lead QA Engineer resume samples
follow this link

Agile QA Tester Resume Samples



Highly skilled Agile QA Tester has excellent technical ability and a sound understanding of software debugging and testing. Has extensive knowledge of multiple computer programming languages and is very detail-oriented and focused. Has excellent communication skills with a Bachelor’s Degree in Computer Programming and over six years working as an Agile QA Tester.

Set of highlights for Agile QA Tester Resume

  • Excellent collaboration with all stakeholders in development projects
  • Strong testing and debugging abilities
  • Good time-management and organizational skills
  • Able to work well with minimal supervision while also functioning as a vital team member
  • Highly responsive to client needs and changing software requirements
  • Works well with developers, programmers, computer engineers, project managers, and clients
  • Excellent functional and analytical technical abilities
  • Highly detail-focused

Agile QA Tester work experience


Agile QA Tester 6/1/2012 – 9/1/2014
Business Applications Technology Solutions LLCNew Cityland, CA

  • Collaborated with all stakeholders in every project.
  • Completed quality assurance testing of developed applications and identified code areas that needed improvements.
  • Streamlined projects to make them meet changing needs.
  • Was highly responsive to the team and clients.

Agile QA Tester 6/1/2008 – 5/1/2012
Corporate Insurance Technologies Inc.New Cityland, CA

  • Collaborated with all stakeholders in the quality assurance and development process.
  • Tested and debugged code sections and adapted to meet the needs of clients.
  • Met with teams weekly in meetings for planning purposes.
  • Met all deadlines for projects.

Healthcare QA Tester Resume Samples

To see the article

follow this link

20 Tips about writing the best quality assurance resume

  • Ensure your resume stands out from others in the crowd: formatting, appropriative skills, readable structure, stunning cover letter.
  • Ensure your key information on the first half-page of your resume because the first page of your resume is crucial
  • Make sure you read the contents of the job opening thoroughly.
  • Next, you might need to rephrase your resume (for instance, add some skills) to become more appropriate to the position. You make sure your skills maximally match to the job.
  • pay attention to the needs of your employer.
  • Write a clear objective at the top of your QA resume. Don’t write irrelevant clichés, but keep the objectives as short as possible; one or two lines being the best.
  • Let your on-the-job accomplishments also be on the first page.
  • Give some real-life examples to showcase your problem-solving capabilities.
  • Do not write about the non-relevant job, responsibilities a lot of.
  • Save your doc with an appropriate name. Typically, “Name_Role/tile_years of experience.doc- (Name-QA_Analyst-8 Years.doc)” is recommended.
  • Keep resume short – no more than 2 pages unless you are applying for a team lead or managerial positions.
  • Check for spelling, grammar mistakes.
  • Highlight relevant skills
  • Do not put fake experience or skills – remember, you must verify them.
  • Focus on the employer’s needs and prepare your resume with relevant skills.
  • Avoid table structure. It is old-school.
  • Do not write ‘CV’ or ‘Resume’ word at the top of your resume. It is obvious.
  • Do not use “I” while describing your responsibilities: instead of, “I wrote test cases” use, “Wrote test cases” or “test cases writing”)
  • Don’t download your resume from LinkedIn. It looks unprofessionally. You can stick to this template. But it also isn’t perfect

Software testing resume format

software testing resume format should be DOC or PDF.
Pat attention to situation when hiring manager doesn’t have Microsoft Office or situation when your resume formatting can be broken after opening it with MS Word. So I recommend to use PDF format. In this case you can save your right resume formatting.