Middle QA Engineer

Що робити

Test a funnel end to end as a user would: landing, registration, confirmation, onboarding, paywall, payment, renewal. Then do it again on the device and in the country where it is most likely to fail.
Own payment testing together with the PSP Account Specialist: successful charges, declines and their retry logic, 3-D Secure challenges, currency and amount correctness, cancellation, refund, and the recurring charge on the right date.
Build and maintain the test matrix: which GEOs, devices, browsers and payment methods actually need coverage, and which combinations are noise. A working funnel runs in 5 to 12 countries at once, so choosing well matters more than testing everything.
Verify that tracking survives the funnel: the events fire, the parameters stay intact, and the tracker, the ad account and BI agree on what happened.
Reproduce production incidents on request. When a buyer reports that conversions dropped this morning, you are the person who establishes whether the funnel broke or the traffic changed.

2 to 3 years of hands-on QA on web products, with at least one of them on a funnel that took real payments.
Payment flow testing experience: you know what a decline code is, why a retry can succeed where the first attempt failed, and how a recurring charge differs from a one-off one.
Confident cross-browser and cross-device testing, including real mobile devices rather than emulators only.
Fluent use of DevTools: Network, Console, request parameters, cookies, redirect chains.
The judgment to build a test matrix instead of a list of every possible combination.

Experience in subscription products, dating, or any vertical that lives on recurring billing.
Familiarity with a tracker such as Keitaro or Binom, and with conversion postbacks.
Postman or an equivalent for checking API responses by hand.
Basic SQL for pulling a number yourself instead of asking the analyst.
Any exposure to automation, even if you have not owned a suite.