I'm a QA Engineer who investigates products end to end — from the interface down to API contracts, databases, logs, asynchronous flows and third-party integrations.
I focus testing on business risk: payments, access control, state transitions and failure recovery. My reports connect a visible symptom to technical evidence and a clear release decision.
Good testing is not about clicking through every screen.
It's about understanding what can break — and proving what actually broke.
Paid QA work on real products, with public or sanitized artifacts where publication is possible.
| Project | Scope | Evidence and outcome |
|---|---|---|
| AI SaaS Platform | AI runtime · Custom agents · HTTP/OpenAPI integrations · Generator · E2E · Responsive / real-device | 150+ manual test cases · 20+ defects · P0/P1 risk coverage · targeted retest and affected regression |
| PRTV.pro | Web · Mobile · Android TV · Billing · OAuth/POS integrations · Migration | 228-case suite · 204 completed · 45 documented defects across 18 modules |
| Telaboro | Android · Admin panel · API · PostgreSQL · Stripe · Logcat | 150+ test cases · 55 first-run + 18 retest findings · release-blocking payment/profile defects localized technically |
| Mailshade | Chrome extension · Gmail · Exploratory · UX · Localization | 19 findings · screenshots/video/CSV/locale analysis · client-accepted QA report |
More commercial QA work
- Android TV Slideshow App — playback, cache, offline USB mode, collections and scheduled streams; executed cases linked to scenario-based defects and video/runtime evidence.
Tools, techniques and product technologies tested
| Area | Tools and techniques |
|---|---|
| Testing | Functional · Exploratory · Regression · Integration · E2E · Risk-based |
| API & data | REST · Swagger/OpenAPI · Postman · SQL · PostgreSQL |
| Backend / business logic | Payments · state transitions · persistence · permissions · third-party integrations |
| Diagnostics | Chrome DevTools · Firefox DevTools · Network · Console · Kibana · Logcat · Charles Proxy · request/response analysis |
| Test management | Jira · TestRail · Allure TestOps · Confluence · Google Sheets |
| Python / automation | Python · pytest · Playwright · Bash · GitHub Actions · GitLab CI |
| Product technologies tested | Stripe · OAuth · Firebase/FCM · React Native apps · Socket.IO/WebSockets · Chrome extensions · Android TV · HTTP/OpenAPI integrations |
| Delivery | Git · Docker · Linux · CI/CD |
Current direction: Python for API checks, reusable fixtures, browser/API automation and small QA utilities.
| Project | Focus |
|---|---|
| DummyJSON API Tests | Python + pytest API checks, reusable fixtures and CI |
| QIWI API Tests | Payment-flow checks with Playwright APIRequestContext and a Postman collection |
| QA Automation Roadmap | Python fundamentals, validation logic and pytest |
Earlier engineering projects
- Monitoring Bot — marketplace integrations, pricing logic, Docker and pytest coverage.
- Orcestre — Telegram automation, scheduling, persistence and API interaction.
- Exportum Bot — Telegram workflow automation for logistics operations.
Understand the product and business risk
↓
Model critical paths and state transitions
↓
Reproduce and isolate the failing layer
↓
Collect UI, API, database and log evidence
↓
Explain impact, likely cause and release risk
Building, testing and investigating how products really work.