Gennadii Nikitin
EN RU

Gennadii Nikitin

QA Engineer (Senior) · 8+ years · Manual + Automation + API

LATAM, Asunción, Paraguay · Remote (UTC-3), overlapping CET and EST · relocation considered · available immediately
Contract: B2B, EOR or direct — negotiable.

Download

FormatWhat it is
PDF 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

2 days → 2 h Regression cut from 2 working days for 2 testers to ~2 hours for 1 tester (Python + PyAutoGUI, image-recognition locators).
30% of L1 requests closed by an AI chatbot on prepared documentation, never reaching the team; tracked per channel and project.
5 + ~10 projects on the automation template I co-designed: five of my own, about ten more in adjacent teams.
QA-owned performance testing: dedicated environment, k6 benchmark / stability / maxperf, Grafana; methodology now reused.
Release gate Automated suites were a release admission check: a red pipeline held the release until we knew why. Roughly 70/30 — tests lagging deliberate changes vs. real defects — at about one red run a week.
Daily CI Visual regression (screenshot tests) on daily CI runs, reports delivered to the corporate messenger.
2 mentees Mentored a backend developer on probation and an intern PM while running daily standups; the project launched on schedule despite staffing gaps.

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)

April 2023 – September 2026

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

May 2018 – April 2023 · Test Specialist → Test Engineer → Quality Engineer · team of 3 testers, 6 developers

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

Education & languages