QA Lead

ROIcamp is building a QA function from scratch for its dating vertical. The QA Lead will own test strategy, build the team, own the release gate, and stay hands-on about a third of the time. The role reports to the Tech Lead and has a growth path to QA Manager.

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

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

• 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.
• The QA Manager position above you, which we would rather fill from within.
• Fully remote work, a fixed payout date, and a salary review at six months.