Position: Senior QA Engineer
Category: QA Automation
English level: upper
Years of experience: 11

I was part of various consulting groups in multiple projects - all projects are leading in their niches. 
Here are some not covered by NDA: 
-	unian.ua  -  37 million visits per month
-	glavred.info  -  4 million
-	zakupka.com  -  2.4 million
-	www.poptop.uk.com  -  253.9K

I have Microsoft, Linux and Coaching certificates

- Improved CI/CD pipeline speed from hours to minutes
- Good in full-stack performance analysis in finding bottlenecks and performance issues
- Built E2E testing frameworks with unique features and elegant design which has proven good with years of use
- Found critical code execution vulnerabilities, XSS and data-corruption bugs, breached client's infrastructure in security testing
- Implemented GDPR and FEDRAMP testing requirements in our projects
- Mentored other developers to share the knowledge and ensure high-quality standards
I am QA Automation Architect and Software Development Engineer in Test (SDET) with 15+ years of experience, possessing strong full-stack development capabilities. 
My unique approach to end-to-end (E2E) testing differentiates me in the industry. 

My philosophy and techniques revolve around the following key areas:
1. Parallel Testing Design:
- Emphasizing parallel testing, I increase the testing speed by executing multiple tests simultaneously, reducing the overall runtime to the duration of the longest individual test.
2. Simplicity and Reliability:
- My code is characterized by its simplicity and reliability, with all complexities hidden away, enabling other developers to update and maintain tests with ease.
3. Contemporary Frameworks:
- I prefer utilizing modern frameworks such as CypressJS, Playwright, or NightwatchJS, ensuring cutting-edge techniques in E2E testing.
4. Backend integration:
- For optimized speed and compatibility, I create APIs to integrate the backend with E2E tests using a shared codebase, resulting in a developer-friendly way to extend tests.
5. Page Object Model or Component Model:
- In relevant projects, I adopt the Page Object model or Component Model to encapsulate information about the elements on the application page, promoting maintainability and reusability.
6. CI/CD Pipeline and Containerization:
- I build efficient CI/CD pipelines using Docker, fostering a reproducible application testing environment.
7. Technology Selection:
- My technology decisions are driven by genuine project requirements rather than personal preferences, ensuring alignment with organizational goals.
8. Quality and Collaboration:
- I value readable, well-written code, dependable tests, and instructive error messages.
- I design user-friendly tests that empower Product Managers, Release Managers, manual testers, and developers to run tests autonomously, streamlining their respective workflows.
- I actively foster communication, collaboration and respect within the team, find proper contacts within the company to give or get help with issues

Projects
- Medical Accounting Software
- House Insurance CRM
- Legal Case Search Engine 
- Financial Accounting Software
- Crypto Payment Gateway 
- Trucking Company Software
- Used Car Shipping Software
I want to work in a product Company in a 100% QA Automation position.

I can refactor old code into up-to-date technologies.
Cucumber because it is an obsolete approach
Capybara, Robot Framework, and other older Selenium-based technologies are already outdated. 
Java+Selenium - is a time/money-burning machine