Position: General QA Engineer
Category: QA Automation
English level: upper
Years of experience: 7

- Was the only QA on the mobile project with 300K+ active users and a high overall rating in stores (Appstore 4.5, GooglePlay 4.8). This app was featured  twice by AppStore in the "Education" category 

- Junior QA, who was mentored by myself, became a Middle QA in 4 months and a Middle BA further in 6 months after onboarding.

- With the whole QA team transferred the API regression suite to the automation basement instead of manual execution. We achieved  65 % coverage for all our endpoints. A team wrote more than 250 tests and I wrote at least 30%.
- 7 years in QA area( 4 years as GeneralQA/AQA as well);
- Experience with TMS(Jira, TFS);
- Good understanding of SDLC, STLC;
- Ability to estimate QA activities required for the project;
- Experience in writing QA documentation: Check List, Test Cases, Test Plan, Test Specification, Bug report, Test summary;
- Experienced with software development methodologies: Waterfall, Agile (Scrum, Kanban);
- Strong theoretical and practical knowledge in manual testing;
- Ability to work with HTML/CSS;
- Working knowledge of SQL using DataGrip;
- Mobile-client testing toolset: Android Studio, Xcode, Firebase App Distribution, TestFlight, Fiddler, Charles, Crashlytics;
- Understanding CI/CD concepts, working with Jenkins+Bitbucket, Gitlab CI;
- Experience in API testing via Postman, Swagger;
- Ability to work with debugging tools: Chrome Developer Tools, Firefox Developer Tools;
- Programming knowledge: Python is mainly used for work, JS : basic knowledge( wrote few tests via Playwright+TypeScript stack);
I want to continue improving my skills as an AQA.

As was mentioned in my experience -  I was the only QA on the team and didn`t afraid of such type cases at all. 
But while I compare my experiences with every single place of work I understand that working in a team with several QA`s gives me much more points for growing as a professional. 

The possibility of working as a team is definitely important for me. Testing is a part of all development, not the science behind the scenes, so testing issues should be resolved collectively as in development, marketing, etc.