- Wrote and maintained tests in the Playwright + TypeScript automation suite, writing Cucumber/Gherkin scenarios and page objects on a Page Object Model structure, covering around 250 scenarios across three environments.
- Wrote page objects and Cucumber scenarios covering back-office modules such as role management, bank account configuration and daily balance monitoring.
- Tested APIs and backend flows, verifying request/response headers and event data across microservices through Kibana logs, and validated the resulting records with SQL queries against the database.
- Tested financial and banking features in a large-scale back-office platform, covering deposits, withdrawals and payment provider flows.
- Worked with the GitLab CI/CD pipeline and release workflows, with branching and merge request reviews in Git.
- Tested release branches on staging before handover to UAT, then acted as the QA point of contact through UAT and go-live, resolving issues in real time so stakeholders were never blocked.
- Worked in Scrum ceremonies - two-week sprint planning, refinement and retrospectives - with cross-functional teams across several time zones on a globally scaled, microservice-based system.
- Managed test cases in TestRail and tracked defects in Jira, writing reproducible, technically precise bug reports.
- Wrote how-to guides and test documentation in Confluence for the team and for other departments, so new QA colleagues could learn the application and the test process.
About
QA engineer with 11 years in software testing, the last four automating a fintech back-office platform with Playwright, Cucumber.js and TypeScript.
I wrote and maintained tests in an existing Playwright framework, covering back-office modules such as role management, bank account configuration and daily balance monitoring, with page objects and Cucumber scenarios. Work spans UI, API and backend testing across microservices, with request tracing in Kibana when something does not add up.
Through UAT and go-live I was the QA point of contact, solving issues in real time so releases were not blocked. I worked in distributed Agile teams across several time zones, in Scrum with two-week sprints.
Outside work I built my own E2E framework from scratch for a production website, 110+ scenarios running daily in GitHub Actions.
I use AI tools daily in my QA work: test design, log analysis, and writing and reviewing test code. I treat the output as a first draft, not an answer.
Experience
- Functional, integration, system, regression, exploratory and load testing of online casino games against customer, jurisdictional, regulatory and functional specifications.
- Reviewed product documentation and release packages for conformance and release readiness.
- Created, maintained and executed detailed test plans, test cases and test documentation with effort estimations, across system, integration and regression cycles.
- Documented and tracked defects in Jira, performed root cause analysis with the development team and proposed corrective action.
- Contributed to defining internal test standards and procedures, reported progress and quality status to stakeholders, and mentored new hires on the test process.
- Administered network maintenance and server administration.
- Provided technical support for workstations, operating systems, and cash registers.
- Installed and maintained automatic measurements in fixed storage tanks.
- Provided technical support to employees, troubleshooting daily workstation issues.
- Assisted in software installations, system updates, and ensured smooth operation of hardware and network resources.
- Conducted interventions and installations of POS terminals for Komercijalna Banka.
- Provided technical support and training for customers.
Achievements
Education
Skills
Strengths
Personal Projects
Built a Playwright + TypeScript + Cucumber (BDD) framework from scratch, with Allure reporting, for my own production website, with 110+ scenarios covering navigation, product catalog, ordering rules, blog and SEO metadata.
- CI in GitHub Actions on every push and on a daily schedule, with lint, type check and tests as quality gates, and email alerts with screenshots on failure.
- Runs safely against production: read-only, analytics blocked, form requests mocked, so no test can touch real data.
- Added data-testid attributes to the site itself instead of relying on fragile locators.
- AI-assisted test authoring on a protected branch workflow: agent-written batches go through PR review and CI before merge.
I run a small furniture studio in Belgrade, designing and building industrial-style pieces in metal and wood, from cutting and welding to finishing and delivery. eye4artstudio.com