Testing of Sberbank's EFS (Unified Front-end System), full-cycle load testing. What my work consists of: ● Writing a load testing methodology (LTM). ● Creating load profiles based on data from PROD and based on data from analysts. ● Developing scripts in JMeter based on user logs from IFT or based on information from analysts. ● Developing stubs in Java or Python. ● Configuring OpenShift clusters. ● Configuring Kafka, Prometheus, and VictoriaMetrics. ● Configuring monitoring (mostly Grafana). ● Running load tests. ● Conducting tests: peak search and confirmation, minimum cluster configuration test, reliability test, failover tests, quota and burst limit search test (for EAG limits), etc. ● Preparing and analyzing test reports, preparing a load testing conclusion with recommendations for eliminating bottlenecks. ● Maintaining documentation in Confluence. ● Reading and analyzing OpenShift logs. Additionally, I have done: ● Migrating existing scripts from Vugen to JMeter. ● Optimizing scripts to eliminate out-of-memory errors when running scripts. ● Configuring Grafana dashboards using Influx and PromQL queries. ● Migrating from Influx to VictoriaMetrics. ● Reading logs and stack traces. ● Configuring Telegraf on hosts to collect system metrics. ● Migrating a Java application from Gradle to Maven. ● Migrating a Java application from JDK 1.8 to JDK 17, resolving dependency conflicts. ● Various stub reworks: adding new services to the stub or updating service response times, migrating services from MQ to REST, integrating with Kafka, adding a limiter to the stub. ● Adding features to the stub such as disabling all REST services with a button and uploading current environment parameters from the testbed database. ● Creating jobs in Jenkins (very few). ● Python automation for running scripts, a Python script for comparing environment parameters. ● Conducting destructive (chaos) testing of an application on an OpenShift cluster. ● In 2025–2026, I did a lot of automation in Python and Java.