Senior QA Engineer

ROIcamp is a media buying team in the dating vertical. They are looking for a Senior QA Engineer to build automated regression suites, synthetic monitoring, and API testing, with a focus on mobile and attribution. The role is fully remote and reports to the Tech Lead.

• 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.

• 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.
• 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.
• Nice to have: Experience with subscription or recurring billing products.
• Nice to have: Familiarity with trackers, conversion postbacks and server-side event delivery.
• Nice to have: SQL beyond the basics, enough to validate data rather than only read it.
• Nice to have: Load or performance testing, particularly on landing pages under traffic spikes.
• Nice to have: Any prior mentoring or informal leadership of other engineers.

• 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.