Position: Middle QA Engineer
Category: QA
English level: intermediate
Years of experience: 2.5


•	Having more than 2 years of software testing experience throughout the SDLC;
•	Team player with the ability to work productively in a team as well as individually;
•	Ability to work within tight deadlines, hard-working, attentive to details, responsible and results orientated;
•	Strong communication skill combined with good concentration on the project;
•	Good analytical and problem-solving skills to drive performance results, quick learner;
•	Inventive, responsible, curious, competitive, proactive, punctual, highly-motivated and friendly person.

SKILLS
•	Strong knowledge in manual software testing process and testing documentation, Defects Life Cycle; 
•	Understanding of QA theory, knowledge in Software Development Life Cycle (SDLC), Software Testing Life Cycle (STLC), test design techniques, testing principles, test levels and types;
•	Knowledge of Development Methodologies (Waterfall, V-model, Agile/Scrum, Kanban);
•	Experience in using wide range of technologies and tools: Chrome DevTools, Postman, Jira, HTML/CSS, SQL;
•	Experience in software testing: web application testing, functional testing, re-test and regression testing, positive and negative testing;
•	Experience in creating and updating QA documentation: Test Plan, Check List, Test Cases, Bug Report, Test Summary.

TECHNOLOGY
Jira, SQL, UNIX, HTML/CSS, Postman, XMind, JSON, Chrome Devtools, Sublime Text, REST/SOAP

PROFESSIONAL EXPERIENCE
Company: Sportdata
Project Name: Sportdata OMS (Organization Management System), Sportdata EMS (Event Management System), Sportdata P (Products), Sportdata RS (Referee System)
Role: Software Test Engineer

Responsibilities and Key Accomplishments: 
•	Manual software testing;
•	Web and desktop testing;
•	Analyzing requirements and software, creating/update the appropriate test documentation (Test Plan, Test Cases, Test Coverage, Checklist etc.);
•	Test Execution and bug reports creation using JIRA bug tracking system;
•	Discussion of questions and issues with Development team;
•	Cross browser testing;
•	New versions integration testing;
•	Regression testing, Re-test, Sanity testing, Smoke testing, Functional testing, Usability testing, GUI testing;
•	Compatibility testing;
•	Manual Rest API testing using Postman;
•	Daily SCRUM meetings;
•	Black Box, Grey Box testing;
•	Work with functional and non-functional requirements.