Hero

Senior QA Engineer / SDET

QA systems that make shipping safer.

I build practical quality systems for backend, platform, fintech and crypto products: risk-based testing, API coverage, CI/CD release checks, Allure reporting and clear signals teams can trust.

Download CV Book an interview

Reliability Snapshot

A concise read on where I create release value.

Role Senior QA Engineer / SDET

Experience 4+ years

Stack API, Playwright, CI/CD, Allure

Domains Backend, platform, fintech, crypto

Work Type Strategy, automation, metrics, mentoring

Quality System

Testing is a release instrument, not a checklist.

I connect test design, automation, CI/CD and reporting into a system that exposes product risk early and keeps the team aligned before release.

Risk model

Map product behavior, data flows, integrations and failure cost before choosing coverage.

Automation architecture

Separate stable regression checks from exploratory work, smoke checks and service-level API suites.

CI/CD gates

Put fast release signals in pipelines and reserve slower checks for the moments where they matter.

Evidence reporting

Use Allure, dashboards, logs and defect patterns to make quality visible without noise.

Selected Impact

Evidence from product teams and platform work.

QA strategy Defined QA strategy from scratch as the sole QA engineer in a cross-functional product team.

Regression Automated checks for a mission-critical service to improve release speed and confidence.

Visibility Built a department-wide quality metrics dashboard for 1,000+ employees.

Allure coverage 1,500+ test cases created for crypto-fintech services

API surface 900+ Postman endpoints expanded across collections

Defect work 300+ reported defects across product releases

Case Files

Selected work, framed by problem, action and result.

T-Bank / Product team

Building QA from zero in a cross-functional team

Problem: Quality process had to be defined while the team kept shipping.
Action: Created test strategy, release checks, regression priorities and shared risk signals.
Result: Team gained a repeatable release rhythm and clearer confidence before production.

Scalable Solutions / Crypto-fintech

Testing backend systems across 30+ microservices

Problem: Service behavior, integrations and API coverage were spread across a large platform.
Action: Expanded API collections, Allure coverage and CI-integrated regression checks.
Result: Coverage became easier to repeat, inspect and evolve with product releases.

Quality metrics / Department level

Making release signals visible beyond one team

Problem: Quality status needed a clearer operating view across a large engineering group.
Action: Built a metrics dashboard and connected quality data to delivery conversations.
Result: Managers and engineers could discuss quality with shared evidence.

Stack & Methods

Automation

Playwright, Java smoke tests, Postman automation, API collections, regression suites.

Testing layers

REST API, backend services, microservices, SQL, message queues, performance checks.

Reporting

Allure, Jira, Confluence, dashboards, defect lifecycle, quality metrics.

Pipelines

Jenkins, GitLab CI/CD, Git, smoke gates, release checks and practical feedback loops.

Observability

ELK log analysis, Prometheus, Grafana, alerting context and defect investigation.

Collaboration

Scrum, Kanban, SDLC, STLC, mentoring engineers and speaking about testing and AI.

Final CTA

Interview Signal

Need a QA engineer who can turn release risk into structure?

I am ready to discuss product quality, backend testing, automation strategy, release gates and the systems that make teams ship with confidence.