Position: Senior QA Engineer
Category: QA Automation
English level: upper
Years of experience: 7

1. Introducing performance testing for a team.
Deployed a full cycle of a performance testing using Jmeter, Grafana, InfluxDB, bash and Docker for it.
That was a regression tests which I was running in the end of each sprint and before release.
Results: Discovered a list of issues which provided a tangible impact on a product. Sharing reports of the run between teams.

2. Discovered a list of security issues in a product.
Results: Issues were hotfixed on production and covered for future development process.
Also, working with security team for internal reporting.

3. Improved internal QA processes, documentation and reporting.
Results: Covering with manual test sets takes less time, documentation became clearer, an example of a bug reporting ticket introduced as a standard.
I was working in large it-companies in QA teams. A few years were dedicated for embedded projects (hardware, software and networking testing).
Then I switched the domain to Web (front-end, back-end, performance, security testing).

My current position is a Senior QA in a back-end team. 

Main responsibilities:
- Cover back-end features with manual testing (Postman);
- Cover back-end features with C# (NUnit) e2e automation tests;
- Participating in performance testing;
- Production deploying;
- On call duties.

Working with next tools: Postman, Visual Studio, JMeter, Burp Suite, Docker, Git, Kibana, Grafana.

I'm continue developing myself as an automation qa to be more professional in coding.

Also, my hobbies is security testing, I dedicated a lot of free time with pleasure on it, as a result I have a rewarded bug on HackerOne platform. I'm continue developing myself in this area.

I always have time slots for trainings, I attended performance testing, and security testing offline courses, also learning these topics on courses platforms.