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

Since 2011 I have successfully developed many application components, helped to improve quality assurance processes, and transformed customer requirements into a set of various automation tests, including UI, restful web services API and load tests.
I am a Software Engineer in Test with over 10 years of hands-on experience with Java, JavaScript and thorough knowledge of tools and frameworks used not only for testing, but also for building, and designing web applications. My practical experience in test automation allows me to cover the functionality with various flavors of Integration, End-to-End, performance & load, security and contract tests, conducting black\gray\white-box testing, and thus ensure the highest quality.


TESTING Technologies
 • Selenium, REST Assured, Spring Framework Testing, Allure, XPath, Protractor, Junit 5, Mockito.

---------------------------------------------

GENERAL Technologies
 • Java, Spring Boot
 • JavaScript, Angular
 • RESTfull web services
 • JPA, SQL
 • AWS, Docker, Kubernetes, Apache Kaffka 

Software Design
 • GoF Patterns, SOLID, GRASP, 
 • Microservices, 12-factor apps, reactive streams, 
 • Front Controller, DTO, DAO, Repository 

Security
 • OWASP top 10, Spring Security, OAuth 2, JWT

Web Technologies and Frameworks
 • Angular
 • TypeScript, CSS, semantic HTML5
 • JSP, Servlets, JSTL, 
 • Spring MVC

Integration
 • Web services (REST, JSON, XML, XSD, Jackson, JAXB),
 • gRPC (protobuf)

Application Servers
 • Apache Tomcat, JBoss

Databases
 • PostgreSQL, HSQLDB, MySQL

Network Tools
 • Wireshark, Postman

Version Control Tools
 • Git, Mercurial

Virtualization & Orchestration Tools
 • Docker, Kubernetes
 • VMWare

Build Servers
 • Gitlab CI, codefresh.io

Test and Bug Tracking Tools
 • Jira, Confluence

Software Design Tools
 • UML (Class/Sequence/Activity in Sparx EA 12)
The ideal working environment would have 
0. access rights to the labs\envs\repos\DBs;
1. friendly collaborative team of professionals
2. no bureaucracy
4. a reduced amount of inefficient group meetings if possible, on-demand 1-to-1 with team member(-s) for collecting details of issues and etc. could be more productive in my experience;
5. a great plus would be to have the already written manual scenarios to automate and documentation, however, the exploratory manual testing also works for me;
6. nice to always have enough details to incident\bugs reproduction.