After moving from India to Kazakhstan, I took a position as QA Analyst/QA Engineer in the integrationstream on the Danish project NuuDay, where I worked for a year.I studied integration testing, supported SIT testing for phase 2.1, and directly conducted SIT testingfor phase 2.1.1.Then, I transitioned to the same role on a completely new company project to implement the IVoE(Integration Validation over E2E) approach. This cross-stream position required an understanding ofthe business, end-to-end scenarios, integrations, and the entire system as a whole.The main idea behind the IVoE approach is automatic integration testing through automated tests:- A significant amount of work with RegExp for creating templates;- A large number of conditions and interrelations;- Extensive analysis.As a result, the IVoE team (focused on integration testing), consisting of three people, identified acomparable number of defects as the five-person E2E team within the same timeframe. Additionally,we often found blocker defects earlier than others due to the speed of our automated testing, as wellas uncovered numerous design gaps before they were detected in SIT testing.

As part of supporting business continuity, I was relocated to India to maintain the Japanese projectRakuten. From that moment on, every workday was conducted entirely in English, starting fromsync-ups to meetings with clients to confirm testing results or clarify details.I also tried my hand at writing complete end-to-end test cases, gathering all the details from variousparts of the design. I successfully completed the task but realized that writing cases was less appealing to me than solving technical problems, so I requested a transfer to a new projectAfter stabilizing the project, I was transferred to a new Danish cloud project for the company -NuuDay - where for the next six months, I focused on building logging for the QA team, triagingdefects, and studying the cloud solution.

I worked with new services on the "Cloud Platform" project, such as Airflow, Spark, and Hadoop (amonolithic solution on 7 virtual machines), executing the entire testing cycle for these services.During this time, I worked extensively with Linux virtual machines, with most installations performedthrough CI/CD processes; where such an approach was lacking, I implemented it.At the same time, I began to support the automated tests for my "old" services, got acquainted withRobot Framework, and successfully continued developing automated tests for RabbitMQ, Mistral, andAirflow.Later, I was transferred to the Japanese project Rakuten, where I started learning about end-to-endtesting and delving into the company's business and analytical processes.

I worked on an internal project called "Cloud Platform."I conducted a complete testing cycle for the cloud microservices Mistral, RabbitMQ, Zipkin, and Jaggerin two environments: Kubernetes and OpenShift.When I say a complete cycle, I mean:- analyzing user stories;- writing test cases;- testing installation (deployment);- functional testing;- integration testing (with other microservices);- regression testing;- automated testing coverage;- executing automated tests and analyzing results.During this period, I gained foundational skills working as a QA engineer.