Alexander P.

Senior QA Automation Engineer with 10+ years in software testing, including roles as a QA Lead. I build test automation that teams keep using after I leave — not a demo that falls apart in six months. Most automation fails for the same reason: it is written to show that it works, not to be maintained by someone else. I design suites around the team that will own them — clear structure, stable test data, meaningful assertions, and a CI run that gives a useful signal in minutes instead of an hour. What I usually do: • Build a framework from scratch — Python with Playwright, or TypeScript with Playwright/Cypress, depending on your stack. • Take over an existing suite — review it, fix what is fragile, document it so your team can work with it. • API testing — REST and GraphQL, schema and contract validation, wired into CI. • CI/CD — GitHub Actions, GitLab CI, Jenkins. Test runs fast enough to execute on every commit. • Test strategy — what is worth automating, what is not, and where manual testing is still the right answer. Stack: Python, PyTest, Playwright, Selenium WebDriver, Cypress, TypeScript, JavaScript. REST and GraphQL API testing. PostgreSQL, MSSQL, Oracle, DB2. Docker, Linux, Git... you name it :D I have worked both as an individual contributor and as a lead responsible for a QA team's direction, so I am comfortable writing tests and deciding what should be tested at all. I also use AI tools in test design and maintenance, and I am honest about where they help and where they do not. If you need automation built, rebuilt, or taken off your team's hands — send me a short note about your stack and what is not working, and I will tell you how I would approach it.