Олексій

Aleksei Masenko
Aleksei Middle QA Engineer · API / Microservices / Automation track
4 yrs · 20+ services

Masenko PROFILE
Middle QA Engineer
4 years testing web services and APIs in microservices teams. At my current job I own QA for a
20+ service platform: weekly releases, 2000+ test cases in rotation, API contract validation
CONTACT
against OpenAPI specs, and daily triage of CI failures. Actively growing into automation —
@ [open contact info](look above in the "contact info" section)
completed Hillel QA Automation Python (2025, EXCELLENT), hands-on with pytest, httpx, and
# [open contact info](look above in the "contact info" section)
in linkedin/blvckcatswag GitHub Actions. I work alongside AI-assisted development: I know which defect classes
gh github/blvckcatswag LLM-generated code tends to miss — untested edge cases, negative scenarios, contract
mismatches — and I test for them by default.
LOCATION
Odesa, Ukraine WORK EXPERIENCE
+ Remote · Open to relocation
Innovation Group Aug 2022 — present · 3 yr 1 mo
LANGUAGES Middle QA Engineer Odesa · Remote
Ukrainian Native
Owned QA coverage for a 20+ microservice platform — 2,000+ test cases maintained across
Russian Native weekly release cycles.
English B1
Validated API contracts against OpenAPI specs in Postman; caught doc-vs-behaviour gaps on
COMMERCIAL STACK 10+ integrated services before they reached production.
Postman REST API OpenAPI
Triaged pytest failures in Jenkins/GitLab CI: isolated root causes per service, cut AQA team's
SQL MySQL Jira debugging loop with structured failure reports.
Jenkins GitLab CI Git MySQL test data ownership: SQL-based setup/teardown for each cycle, entity relationship
Confluence TestRail Scrum validation across service boundaries.
Python pytest Linux Tested LLM-generated code shipped by AI-assisted developers — flagged untested edge
cases, missing negative scenarios, and contract mismatches as a repeating defect class.
LEARNING & PROJECTS
httpx fixtures parametrize
Drove full Scrum loop on a team of 6 QA (Middle–Senior): grooming, planning, sprint
estimates, weekly release sign-off.
GitHub Actions CI/CD
Postman OpenAPI MySQL pytest Jenkins GitLab CI Jira Scrum
Docker PostgreSQL

Selenium PyCharm Business Solution Lab (BSL) Dec 2021 — Aug 2022 · 9 mo
Middle QA Engineer Odesa
EDUCATION
iOS and Android testing across two live products: functional, regression, smoke, and ad-hoc.
Hillel IT School EXCELLENT
QA Automation Python Built TestRail coverage from zero for new features — established the regression baseline used
2025 · certificate.ithillel.ua in all subsequent sprints.
Hillel IT School Reviewed specs and layouts pre-sprint; owned effort estimation and test results reporting to
QA Technical Pro Head of QA.
2023 TestRail Jira iOS/Android Regression Smoke testing
SNAU, Sumy
Economics & Mgmt Macron Digital Systems May 2021 — Dec 2021 · 7 mo
2016–19 QA Engineer
SOFT SKILLS Tested an internal CRM end-to-end: forms, reports, role-based access, business logic.
- Root cause analysis Regression in Postman after every release; mentored two new testers on test design and
- Test plan authoring defect reporting.
- Scrum ceremonies
Postman Jira CRM Regression Black-box testing
- Defect lifecycle mgmt
- Cross-team communication PROJECTS & AUTOMATION
- Analytical mindset
REST API Test Suite — Hillel final project github/blvckcatswag
pytest + httpx: fixtures, parametrize, conftest, setup/teardown — written by hand, not
generated.
Positive, negative, and edge case coverage; modules split by endpoint domain.
GitHub Actions CI: tests run on every push, pass/fail visible in PR status checks.
pytest httpx fixtures parametrize GitHub Actions CI/CD

AI-Assisted Test Generation — ongoing practice
Prompt LLMs for test case drafts, then manually gap-analyse and harden coverage — cuts
design time, not quality.
Built a repeatable workflow from daily work with AI-generated code: spec → draft → edge case
audit → final suite.
AI-assisted QA LLM test gen test design edge case analysis

Aleksei Masenko · Middle QA Engineer · [open contact info](look above in the "contact info" section) · [open contact info](look above in the "contact info" section)