<h2><strong>About impact.com</strong></h2> <p><a href="http://impact.com/">impact.com</a> is the world’s leading commerce partnership marketing platform, transforming the way businesses grow by enabling them to discover, manage, and scale partnerships across the entire customer journey. From affiliates and influencers to content publishers, brand ambassadors, and customer advocates,<a href="http://impact.com/"> impact.com</a> empowers brands to drive trusted, performance-based growth through authentic relationships. Its award-winning products—<strong>Performance</strong> (affiliate), <strong>Creator</strong> (influencer), and <strong>Advocate</strong> (customer referral)—unify every type of partner into one integrated platform. As consumers increasingly rely on recommendations from people and communities they trust,<a href="http://impact.com/"> impact.com</a> helps brands show up where it matters most. Today, over 5,000 global brands, including Walmart, Uber, Shopify, Lenovo, L’Oréal, and Fanatics, rely on<a href="http://impact.com/"> impact.com</a> to power more than 225,000 partnerships that deliver measurable business results.</p> <h2><strong>Your Role at</strong><a href="http://impact.com"><strong> </strong><strong>impact.com</strong></a><strong>:</strong></h2> <p>The QA Chapter Lead sets the quality bar across our IO and AI groups and makes engineering teams the owners of it. This is a leadership role built on influence rather than a separate reporting line: you raise the standard of quality by shaping how teams design, build, and ship, by coaching engineers to own testing end to end, and by building the tooling and evaluation systems that make quality the path of least resistance. You will treat quality as an engineering discipline embedded in every team, not as a downstream gate a dedicated QA person is responsible for. The role deliberately spans two very different delivery contexts. The IO group builds deterministic platform software: integrations, ETL pipelines, APIs, and the performance and security concerns that come with them. The AI group builds non-deterministic, agentic products where correctness, safety, cost, and latency are all quality dimensions and where traditional test scripts do not apply. You will build one quality discipline that works across both.</p> <h2><strong>What You'll Do:</strong></h2> <div>As a QA Lead for the platform group, you will lead a critical function focused on both the technical infrastructure and the human element of Quality Assurance. </div> <div> </div> <div>Your responsibilities will include:</div> <div> </div> <div><br><strong>1. Set the quality bar and the operating model</strong><br> <ul> <li>Define what "good" looks like across both groups, and make engineers the owners of that bar rather than the QA function.</li> <li>Shift quality upstream, from a downstream gate into how teams scope, design, and build, so that testing is part of engineering rather than a phase after it. </li> <li>Establish quality signals teams actually use to make decisions (escaped defects, mean time to detect, confidence to ship, change failure rate) over vanity metrics like raw test-case counts.</li> <li>Drive continuous improvement of how the groups engineer for quality, and retire practices that no longer earn their keep.</li> </ul> <p> </p> <strong>2. Lead the chapter, not a QA queue</strong></div> <div> <ul> <li>Grow a cross-group chapter and community of practice for quality engineering spanning IO and AI, aligning standards without centralising the work.</li> <li>Coach engineers to own testing for their own work, increasingly with agents doing the heavy lifting. Lead through standards, reviews, pairing, and reusable patterns rather than by running a separate QA backlog that work is handed off to.</li> <li>Raise the floor for everyone: onboarding, patterns, reusable harnesses, and the internal enablement that lets any engineer test well by default.</li> <li>Provide technical mentorship and feedback that grows quality capability inside the engineering teams.</li> </ul> <p> </p> </div> <div><strong>3. Quality engineering in the agentic age</strong><br> <ul> <li>Treat agents as first-class contributors to testing: generating tests, test data, and exploratory coverage, triaging failures, and widening coverage, with humans designing the harnesses, guardrails, and reviews that keep them honest.</li> <li>Build the evaluation systems for AI products: evals, regression suites for non-deterministic output, and safety, hallucination, and guardrail testing, alongside strong classic automation for the platform.</li> <li>Own the tooling, harnesses, and CI/CD guardrails that make the quality bar automatic rather than a matter of individual diligence.</li> <li>Stay ahead of where AI-assisted testing and agentic engineering are going, and bring the useful parts back into both groups.</li> </ul> <p> </p> <strong>4. Test strategy across two contexts</strong><br> <ul> <li>For the IO platform: functional, regression, integration, performance, and security testing, with strong automation and quality gates in CI/CD.</li> <li>For AI products: eval-driven testing for non-deterministic and agentic behaviour, including prompt and behaviour regression, safety, and cost and latency as first-class quality signals.</li> <li>Ensure risk