Position: Software Testing Engineer
Category: QA
English level: intermediate
Years of experience: 1.5


I have worked at EPAM for over 1.5 years, and spent most of my time on a single project, but in several different teams.

The first team was quite large, with approximately 30 people, including 5 manual QAs and 4 automation specialists. For the client, we worked on creating a product sample management system. Testing involved verifying the functionality of the user interface according to the Zeplin mockups, the backend according to the specification in SwaggerHUB. Most requirements described as user stories in Jira. The overall specification was laid out in Confluence, where requirement analysis and clarification took place. Test cases were written with consideration of BDD in Gherkin notation for further simplified automation.

Later, I moved to a neighboring team of 5 people, where I was the only tester. The team was responsible for developing and improving a common landing page for several applications, one of which was the one I worked on before. Additionally, the team was responsible for functionality common to all these applications and integrating them into a single system. My responsibility included creating regression reports and collecting various metrics on demand. The work also required checking the quality of data exchange between applications, so the focus was on working with SQL queries in Apache Kafka, through which data was transmitted, and databases for data storage. I participated in the setup and verification of monitoring and logging systems Kibana, Matomo, and Instana.

I successfully passed the assessment for the role of a middle QA engineer.

From the new year, the client reduced cooperation, and I moved to the bench, where I initially worked on crowd testing at Test.io, which gave me experience in testing different projects with different approaches to writing test cases and experience in mobile testing.

At the same time, I joined an internal project for developing a financial application for mobile platforms and the web. On this project, in addition to working directly with GUI and API testing, I actively participated in changes to the Jira workflow and process optimization.

In the end, I faced massive layoffs, and now I'm here.

I want to continue my path in IT, and I am learning Java in parallel while planning to develop in the direction of automation.
Looking for Middle QA Engineer position in a friendly team with the ability of professional growth. Also interested in developing automation testing skills.