Two and a half years working as a QA Engineer. Worked on various web and desktop projects. Most of the work is manual testing. Last half of a year working on testing automation for about 20% of working time.I have basic Java knowledge, learning UI testing autimation using Selenide framework and api testing automation with Rest Assured. Did an interesting task of making CI process with Jenkins.Worked with Postman, organized CI process in the following way: TestIT(TMS) sends Webhook to Jenkins, Jenkins connects via ssh to testing machine, machine launches newman(Postman) autotests, when autotests done Allure report is generated and results are sent to TMS. It was very interesting process to make this pipeline. Also worth mention that generate Allure report from newman results and sending this results to TMS was not an easy task because of bug in newman-reporter-allure, generated allure files missed some values in Json of successful tests. Did some research of a bug, submitted steps to reproduce and bug details to allure-js git, and after two weeks was happy to see everything working.Participated in solving an interesting task of load testing project made with Vaadin. In this project there is no Rest hosts, so i experimented with UI testing parallelization, i used JUnit's dynamic tests and some build.gradle magic to make possible launch of tests on a remote machine with ability to set maximum parallel tests and count of iterations to each testing thread as a parameter to "gradle test".Also i have some SQL knowledge, can make basic queries, Join and nested queries.