Senior QA Engineer

About the role

Right now, when a funnel breaks in production, the first person to notice is usually a buyer looking at a conversion chart that stopped climbing. By then the loss is measured in hours of spend. That detection gap is the problem this role exists to close.

The work is building the systems that watch the funnel continuously: a regression suite that runs on every release, and synthetic checks that walk the live funnel around the clock and raise an alert when a step stops behaving. Add to that the parts of testing that need the most engineering, which here means mobile builds, deeplinks and attribution.

ROIcamp has worked in the dating vertical since 2011. You report to the Tech Lead, work alongside the tracking infrastructure engineer, and set the technical standard for the QA engineers below you.

What you’ll do

• Build and own the automated regression suite in Playwright, covering the funnels that carry the most spend first rather than chasing coverage percentages.
• Set up synthetic monitoring against live funnels: a scripted user walks the flow on a schedule, and a failed step pages someone instead of waiting to be noticed.
• Wire the suite into CI so it gates every landing and product release, and keep it fast enough that nobody is tempted to skip it.
• Own API-level testing of the tracker, the postback endpoints and the Conversion API integrations, where a browser test cannot reach.
• Take mobile: store builds, deeplink behaviour after install, and attribution through the mobile measurement partner, confirming an install and a subscription land on the right campaign.
• Investigate the failures that nobody else can reproduce, including the ones that only appear on a specific GEO, carrier or device.
• Review bug reports and test plans from the junior and middle engineers, and mentor them toward the standard rather than rewriting their work.
• Keep the suite honest: a test that fails intermittently and gets ignored is worse than no test, so flaky checks get fixed or deleted.

Requirements

• 4 or more years in QA, with at least 2 spent building and maintaining an automated suite that other people relied on.
• Strong automation practice in Playwright, Cypress or Selenium, with JavaScript or TypeScript at a level where you write the framework rather than only the tests.
• API testing experience: request construction, authentication, response validation, and testing integrations you do not control.
• CI experience: you have put a suite into a pipeline and dealt with what happens when it starts blocking releases.
• The judgment to decide what should be automated and what should not. Automating a rarely changing flow while a payment step stays manual is the mistake we are trying to avoid.
• Comfort working without a spec, since a funnel is often the only documentation that exists.
• English sufficient for reading documentation and vendor support threads.

Nice to have

• Mobile testing and experience with an MMP such as AppsFlyer, Adjust or Branch.
• Experience with subscription or recurring billing products.
• Familiarity with trackers, conversion postbacks and server-side event delivery.
• SQL beyond the basics, enough to validate data rather than only read it.
• Load or performance testing, particularly on landing pages under traffic spikes.
• Any prior mentoring or informal leadership of other engineers.

What we offer

• A blank page on automation: no legacy suite to inherit, no framework someone else abandoned, and the authority to choose the approach.
• Problems that are genuinely hard rather than merely large: attribution, recurring billing and cross-GEO behaviour under real traffic.
• A direct line to the Tech Lead and the analyst, so decisions get made in a conversation rather than a process.
• The QA Lead position ahead of you, which we intend to fill from within.
• Fully remote work, a fixed payout date, and a salary review at six months.

Growth path

The intended next step is QA Lead, which adds the team, the strategy and the hiring to what you already do technically. If leading people is not what you want, the alternative is the deep technical track alongside the tracking infrastructure engineer, where the work moves from testing the pipeline to designing it. Both are discussed at the six-month review and measured by results rather than by tenure.

Compensation

$1,600 to $2,600 base, depending on the depth of your automation practice and whether you have run a suite in production before. Salary review after six months. Payouts on a fixed date each month.

Hiring process

A 30-minute screening call, then a technical interview with the Tech Lead covering your automation decisions and their trade-offs, then a practical task where you design the monitoring for a described funnel and justify what you would not automate (up to four hours, reviewed together), then an offer. The whole process takes up to 10 business days.