Position: Senior QA Engineer
Category: QA
Experience: 9 years | English: upper

- Reduced Defect Rate: on one of projects, where we as a backend team were struggling from plenty of defects being found both by me during system test and by frontend team during BE - FE integration, I proposed extending dev testing, which resulted in significant reduction of critical+ bugs in ‘ready for QA’ stories, and implementing and sharing to FE team sort of an ‘API design doc’ before BE work on a story started, which made early review by FE team possible.
- Streamlined Testing Cycles: on one project we got regression autotests set that were very slow due to a lot of unnecessary UI interactions (a company's proprietary AT tool with access to UI (xpath/jsonpath) and DB), so I found out how the tool works and rewrote the tests - replaced redundant UI interactions with DB ones which reduced time of a single run by four times, that made it possible to deliver fixes more frequently.
- Team Recognition: there were a couple of projects which I as a person who knew a solution the best was asked to return to in order to analyze an impact of new CRs (i.e. the final GO/NO GO solution regarding the CRs was on me) 
- Mentored and Developed Junior QA Team Members: there were a lot of projects that initially were staffed with me as a single QA and later extended with several newcomers, who at first required constant attention but eventually grew up into fledged professionals. I successfully led several of my subordinates to the point where they could be able to substitute me for the project stream/QA lead position. There also was a project where I had a team of four newcomers that came right from their QA courses, all of them have successfully developed into solid QA engineers, one of them substituted me when I left the project and later was named the most productive QA of the project (that was a huge one with 50+ QAs)
- Collaborated with Cross-Functional Teams: there was a case when my team was constantly getting complaints stating that ‘nothing works because QA don’t find any bugs’. Since I’m always trying to keep all my Jira stuff in order (everything is linked/labeled/aligned in terms of statuses/etc) it was not a problem to find out that the functionality was actually well tested and a lot of bugs were found and waiting for the fix. Engaging a simple Time To Fix metric exposed the fact that the DEV team was so overloaded and focused on new features so it was not even able to notice a huge list of critical+ defects related to already implemented ones.
- 9+ years of QA experience
- testing of complex business logic / data migration (a lot of SQL usage) / API / mobile apps
- business trips to customer's offices (Japan)
- onsite UAT support experience
- project QA team management and mentoring (up to 6 members) 
- little automation experience (API regression and test data creation (postman/JS) + a company's proprietary AT tool with access to UI (xpath/jsonpath) and DB)
- I have been involved in projects that sizewise vary from 1 QA to 50+
- project QA lead / Stream lead experience
- It would be great to use SQL in my work
- I feel ok about growing in test automation direction.
- I'd prefer not to be involved in things like making trainings or conducting interviews.