Position: Automation QA Engineer (Java)
Category: QA Automation
English level: intermediate
Years of experience: 3

On commercial projects:
     1.  Brought into use OOP-like Page Object pattern with incapsulating page business logic inside respective page methods (instead of having a lot of duplicated code and low level web element actions in tests that is time consuming in support and more error prone). Result: test steps are named as precise business actions, that are understandable to any stakeholder from test run report; decreased time for supporting existing tests and adding new tests. Applied on 2 projects.
     2. Setup test logging and test reporting based on AspectJ (instead of more verbose and more time consuming annotation based approach). Result: less efforts to support existing logging, almost zero efforts to log newly added tests. Applied on 2 projects.
     3. Managed to refine requirements with the client and avoid drawbacks in new feature design and implementation. Result: less time on communication with dev team, feature implementation and testing appllied on 1 project
 
     Self education. Completed trainings:
     1. "Backend automation". Gained knowledge: 
          - principle of work of message queue Kafka
          - test automation approach for backend transactions .
     2. "JDBI for test automation". Gained knowledge:
          - creating extensible and reusable interfaces for interaction with data base on top of JDBI library
     3. "Java Script for beginners", "Java script basics". Gained knowledge: 
         - basic language syntax and conceptions. Going to lean test automation with JS.
# Project in health care domain, AQA (Java).
Activities:
- creating functional automated tests (UI: Selenide, Selenoid; API: RestAssured; TestNG, jUnit5, Java 11, Java17, AssertJ, Maven, PostgreSQL);
- setup logging (log4j2) and reporting(Allure) via AspectJ;
- configuring running UI tests in parallel mode on test environment.

# Project is enterprise terminal operation system, Java SDET.
Activities:
- analysis failed test results in Kibana, Report Portal to find root cause of integration issue and report it to appropriate team;
- automated integration tests support/creating new  (Java 11, TestNG, Junit5, AssertJ, RestAssured, Selenide, Maven, Jenkins, Git, PostgreSQL, Spring, Dependency Injection, Kafka, ActiveMQ).

# Project is ERP system for IT company, AQA  (Java).
Activities:
- setting up test automation project from scratch for one of the subsystems and creating functional tests on UI and API level (Java 8, TestNG, AssertJ, RestAssured, Selenide, Selenoid, Allure, Maven, Jenkins, MS SQL, JDBI, AspectJ);
- automated tests support on another project subsystem (Java 8, TestNG, AssertJ, RestAssured, Selenium, Allure, Maven, Jenkins, PostgreSQL).

# Project is a product for DBAs, system admins to collect, monitor and analyze data base and operation systems metrics, AQA (Java)
Activities:
- implementing test automation on project from scratch and adding new tests (Java 8, TestNG, Selenide, Selenoid, Allure, Maven, Git Lab, PostgreSQL);
- data base migration testing (using developed by Company desktop tool).

#Project is an application for trading activities by prominent banks around the world, General QA.
Activities:
- communication with business owner to refine, analyze, specify requirements;
- preparing test strategy, test cases, checklists;
- functional testing;
 - smoke, regression, exploratory, shift-left testing;
- acceptance testing;
- support existing/add new automated tests (PHP, Selenium, Codeception, Behat, Selenium Grid).

#Magento based web stores, manual QA.
Activities:
- preparing test cases(Zyphyr)
- functional, regression, cross-browser, exploratory testing;
- bug reporting/tracking/verification
- interviewing QA applicants

Started working as manual QA in 2016, as AQA in 2019, with Java in 2020.
I'd like to participate in project as Automation QA Engineer to automate functional tests on API and UI level. Ideally, if there is project where test automation project should be setup from scratch. Also I'm ready to work on automation of integration tests with more mature AQA in this area.
One more interesting topic for me is take a part in BE automation (testing business logic on the level of message service such as Kafka). Even for now I don't have commercial experience in this area,  I have some basic knowledge from respective training.  
Ideally, if my business with test automation activities is going to be around 100%. Some manual testing is acceptable for me, but no more, then 5-10 %.
Working with BDD frameworks like cucumber, JBehave is unwelcomed for me.