QA Lead

About the role

ROIcamp is building a QA function from a standing start. Today testing is spread across a few engineers and a tech lead who has other work; tomorrow it needs to be a team of five or six with a strategy behind it, because the money at risk has outgrown the ad hoc arrangement. This role is the person who does that building.

The scope is everything between a change and live traffic: what gets tested, by whom, how deeply, with which tools, and who says yes. A dating funnel that takes recurring payments across a dozen countries has more failure modes than any one person can hold, so the job is to turn that into a strategy other people can execute.

The company has worked in the dating vertical since 2011. You report to the Tech Lead.

What you’ll do

• Own the test strategy: a coverage map across funnels, payments, tracking and mobile, with an explicit and defensible position on what is not covered and why.
• Build the team. Two engineers are being hired now and four more positions are open. You interview everyone who joins after you, onboard them, and set what good work looks like.
• Own the release gate. Your team’s sign-off decides when a landing goes live or a product release ships, and you are responsible for making that gate fast enough that nobody wants to route around it.
• Decide the automation boundary: what the suite covers, what stays manual, and when the cost of maintaining a test exceeds what it protects.
• Run the metrics that matter and drop the ones that do not. Defects reaching production, time from report to fix, and money protected are worth tracking. Test case counts are not.
• Handle the incidents: when a funnel breaks under live traffic, you coordinate the response, then run the review that turns it into a permanent check.
• Work across teams: with the Tech Lead on tracking infrastructure, with the analyst when the numbers disagree, and with the buying leads whose campaigns your gate can hold up.
• Stay hands-on about a third of the time, on the riskiest areas rather than on whatever is left over.

Requirements

• 5 or more years in QA, including at least 2 leading a team of three or more engineers with real responsibility for their output.
• A track record of building a test strategy from scratch rather than inheriting and maintaining one.
• Strong technical depth: you can read the automation suite, judge whether it is well built, and argue with an engineer about it on equal terms.
• Experience owning a release process and the authority that comes with it, including the harder half, which is saying no to a release that people want shipped.
• Hiring experience: you have interviewed QA engineers and can tell competence from vocabulary.
• The judgment to prioritise by risk and money rather than by coverage percentage.
• Clear written communication, since a remote team runs on what you write down.
• English at a level that supports working with vendors and documentation.

Nice to have

• Experience in subscription products, dating, or another vertical built on recurring billing.
• Familiarity with paid traffic: what a buyer does, and why a broken funnel costs money by the hour.
• Experience introducing automation to a team that did not have it before.
• Mobile and attribution background.
• Any experience defending a headcount or tooling budget to leadership.

What we offer

• A function to build rather than one to maintain. Almost nothing is fixed yet, and the shape of QA here will be the shape you give it.
• Real authority: the release gate is yours, and it is not overruled casually.
• A company where the cost of a defect is measured in spend rather than in story points, which makes the value of your work unusually easy to argue for.
• No manager layer above the function, so your decisions are not re-litigated one floor up.
• Fully remote work, a fixed payout date, and a salary review at six months.

Growth path

From here the track widens rather than climbs: quality across the whole dating direction, compliance included, as the function grows past one team. If the organisational route does not appeal, the alternative is the deep technical one toward tracking and infrastructure architecture. We discuss both at the six-month review and measure them by results rather than by tenure.

Compensation

$2,200 to $3,200 base, depending on the size of the team you have led and how much of a test strategy you have built yourself. Salary review after six months. Payouts on a fixed date each month.

Hiring process

A 30-minute screening call, then an interview with the Tech Lead on technical depth, then a working session where you sketch a test strategy for one of our real funnels and defend what you would leave uncovered, then a conversation about team building and hiring, then an offer. The whole process takes up to 12 business days.