Gennadii Nikitin
QA Engineer (Senior) · 8+ years · Manual + Automation + API
Download
| Format | What it is |
|---|---|
| 35 KB · the same text, two pages, print-ready | |
| DOCX | 42 KB · for ATS systems that reject PDFs |
| Markdown | plain text, no layout |
| JSON Resume | JSON Resume 1.0.0, for agents and scripts |
Summary
QA engineer with 8+ years on desktop, web and mobile client-server products in high-traffic consumer promos and gamification — prize games, seasonal campaigns, loyalty mechanics — including a prize promotion with up to 3M+ unique monthly users. I own the full SDLC on my projects: requirements and testability before development, test design, functional / regression / API / integration testing, and automation where it pays off — TypeScript on an in-house Playwright framework, plus k6 load testing on two products. I leave documentation and processes a team can pick up and reuse.
Key achievements
Core skills
- Testing
- Functional, regression, integration, system, UI, API, cross-browser, performance/load, visual regression.
- Test design & analysis
- Boundary value analysis, equivalence partitioning, state transition diagrams, requirements analysis, three-amigo sessions, testability review.
- Automation
- TypeScript on eva.io (Selenium, then Playwright), Playwright, Python (PyAutoGUI, image recognition), parameterized tests, visual regression, Allure TestOps, Qase, reusable module/page structure.
- API & data
- Postman, Insomnia, Swagger/OpenAPI, Charles, Fiddler, OWASP, SQL (SELECT, JOIN, GROUP BY, subqueries, INSERT/UPDATE), MSSQL replication verification.
- Performance
- k6 (benchmark, stability, maxperf), load profiles built from production logs, Grafana, internal metrics service.
- Platforms & infrastructure
- Docker, BrowserStack, real iOS/Android devices, Android Studio, Chrome and Firefox DevTools.
- AI in testing
- LLM-assisted checklists and test scenarios, prompt iteration, in-IDE coding agents for test code; shared the practice with the team.
- QA process
- Test strategy, test plans and test cases, shift-left (requirements and testability review before development), release criteria and quality gates, defect lifecycle and triage, test documentation, QA metrics; Agile — Scrumban (Scrum/Kanban).
- Tools & CI/CD
- Git, GitLab CI with daily scheduled runs, Jira, Confluence, Allure TestOps, Redmine, Kafka topic integrations.
Experience
Quality Engineer — T-Bank (ex Tinkoff)
Web and webview apps inside Android/iOS apps: promo mechanics that grew into products, including a prize game with up to 3M+ unique monthly users. Sole QA for two years, then one of two QA engineers; owned the test strategy of my projects. Release cycle: 3–7 months on staging, one release day, then daily-to-weekly follow-ups. On-call for support and alerts: QA triages first, then routes.
- Department automation template (eva.io, TypeScript): auth via internal test environment, execution and Allure TestOps reporting, repo structure, deployment guide; code review and contributions; adopted across teams.
- Game Center: built the testing process from scratch — plans, reports, FAQ and knowledge base; system, UI, API and integration testing; screenshot visual regression in CI; handed over with documentation.
- Test pyramid and TestOps: unit, integration, e2e and screenshot layers kept separate, all reporting into TestOps. A contract sweep and field validation of the API caught a broken contract and an unvalidated field.
- Shift-left by default: co-wrote functional requirements in three-amigo sessions, followed the department RFC on early testing, kept an open-questions page during design.
- Support load: AI chatbot in the corporate messenger answering from documentation; dashboard showed 30% of inquiries resolved without the team.
- Performance testing: with SRE, set up a dedicated environment; k6 benchmark, stability and maxperf scenarios. Runs exposed database saturation (slow queries, lock contention), fixed before launch. Wrote the approved methodology, template and quickstart.
- Mentoring and ownership (Pushkin 225 Years): daily standups, Kafka integration research, launch readiness with the Lead PM; mentored a backend developer and an intern PM.
- Cross-team relief: twice covered a neighbouring team’s QA gap for 1–2 months and handed back with documentation.
Quality Engineer — Tillypad
Client-server restaurant automation: desktop apps for waitstaff, bartenders, cooks and managers, later mobile and web; MSSQL with replication to head office / cloud.
- Full-cycle manual testing: test plans and cases; unit, integration, system, regression; API checks in Postman and Swagger; traffic analysis in Charles and Fiddler; defects in Redmine.
- UI automation: Python + PyAutoGUI with image recognition; regression from 2 days (2 testers) to ~2 hours (1 tester).
- MSSQL replication testing: SQL scripts to insert/update/delete source data and verify the target held everything it should and nothing it shouldn’t. About ten high-severity defects in three years.
- Support and onboarding: troubleshooting with support; trained new team members.
Selected projects
- hecho-demo / hecho-e2e — public demo of the full QA cycle: React 19 + NestJS + PostgreSQL app, Playwright e2e suite, Qase catalogue.
- Prizopoly 2.0 — prize promotion, up to 3M+ unique monthly users; k6 coverage of every critical endpoint, three scenarios distilled into one, load-testing ownership moved from backend to QA.
- Stickermania with Vkusno i Tochka — parameterised tests, auth module added to the shared template; R&D showed layout automation by parameterisation had a high false-positive rate, so it was not adopted; the approach was scaled to functional tests instead, cutting duplication.
- New Year 2024 — gamified promo; Kafka and deep-link testing across app versions; real app-version usage from logs decided which versions to test first.
- Birthday 4.0 — prize-giveaway service grown from a promo into a product; testing from scratch, automation, then two years as the team’s testing point of contact.
- UserAgent Redirect — user-agent research for a fallback page; ADR, usage guide, automated tests over large value lists, department knowledge-sharing session.
- TShop — merchandise store in the mobile app; order-fulfilment integrations, sole QA.
Education & languages
- St. Petersburg College of Technology — Programming (secondary vocational), 2023 – 2027 (expected).
- St. Petersburg State Transport University (PGUPS) — Mechanical Engineering, 2007 – 2011, incomplete higher education.
- Internal courses: end-to-end automation on eva.io, load testing with k6. No external certifications.
- Russian — native. English — B2, working proficiency.