Middle QA Engineer

ROIcamp is a media buying team in the dating vertical. They are hiring a Middle QA Engineer to own the testing of the subscription funnel from ad click to payment and renewal. The role involves end-to-end testing, payment flow testing, and release gating.

• 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.
• Write bug reports precise enough that an engineer reproduces the issue on the first read, then verify the fix and check what it broke nearby.
• Run the regression pass before every landing and product release, and keep the checklist growing with each bug that got through.
• Gate releases: your sign-off is what says a funnel is ready for traffic.

• 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.
• Bug reports that are reproducible without a follow-up conversation.
• Consistency: the regression pass gets completed even when the release looks harmless.
• 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.
• English sufficient for reading platform and payment provider documentation.

• One funnel that is genuinely yours, with the authority to stop a release rather than only report on it.
• Payment and subscription expertise that transfers to fintech, e-commerce and any subscription product, built on real volume rather than a test sandbox.
• Direct contact with the people whose budget depends on your work, so the value of a catch is never abstract.
• A team where QA is a separate function with its own growth ladder, not a duty attached to a developer.
• Fully remote work, a fixed payout date, and a salary review at six months.