QA Lead

Що робити

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.

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.

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.