QA Chapter Lead
at Impact
Cape Town, 5+ years
posted 11 Sept 2026
- Test automation
- Docker
- Playwright
- CI/CD
- Agents
- TestRail
- Selenium
- LLM
- MCPs
- ETL pipelines
- API testing
About the role
Posted: 2026-09-11
About impact.com
impact.com 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, impact.com empowers brands to drive trusted, performance-based growth through authentic relationships. Its award-winning products—Performance (affiliate), Creator (influencer), and Advocate (customer referral)—unify every type of partner into one integrated platform. As consumers increasingly rely on recommendations from people and communities they trust, impact.com 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 impact.com to power more than 225,000 partnerships that deliver measurable business results.
Your Role at impact.com:
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.
What you would do
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.
1. Set the quality bar and the operating model
- Define what "good" looks like across both groups, and make engineers the owners of that bar rather than the QA function.
- 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.
Read from job-boards.greenhouse.io, last seen 2d ago.