Funnel QA Specialist, DTC E-Commerce (Checkout & Tracking)

About HarZa Group

HarZa Group builds and scales direct-to-consumer health and wellness brands. Our flagship brand is Rejuvacare, with RejuvaKnee as our hero product in chronic pain relief, and we are actively launching new brands across the portfolio. We run entirely on paid digital channels, ship primarily into the United States, and have grown twelve times in a single year with close to 150 people across more than 15 countries. We are remote-first by design and async-first by default.

The Role

Every funnel we publish carries paid traffic from the moment it goes live. When something breaks here, it does not break quietly in a staging environment. It breaks while we are spending money on it.

The expensive failures in this business are rarely the obvious ones. A page that looks perfect but records the order under the wrong offer. An upsell that charges correctly and then sends the customer to a blank screen. A purchase event that fires twice and quietly corrupts the numbers the media buyer is optimizing against. A downsell path nobody walked, because everybody tested the version where the customer says yes.

We are hiring a Funnel QA Specialist to be the person who walks those paths.

You will test complete customer journeys rather than pages, inside Checkout Champ and across the funnels built on top of it. You will place test orders, follow every branch including the ones where the customer declines, verify that tracking fires correctly and only once, check the experience on mobile first because that is where our traffic is, and confirm that what went live matches what was approved.

And you will do the part that matters more than any individual bug: when the same defect appears for the third time, you stop logging it as a new ticket and change the thing that keeps producing it.

What You'll Do

Test the full journey, not the page

• Walk complete funnels end to end before launch: advertorials, landing pages, VSL pages, quizzes, product pages, order forms, checkouts, upsells, downsells, declines and post-purchase flows.
• Place test orders in Checkout Champ and validate pricing, offer configuration, order records, confirmation pages and what the customer actually receives.
• Test the paths nobody volunteers to test: declined cards, abandoned flows, downsell branches, back-button behaviour, refreshes mid-checkout.
• Test mobile first, then desktop, across the browsers our traffic actually uses.

Validate tracking as seriously as you validate checkout

• Confirm page view, add to cart, initiate checkout, purchase and custom events fire, fire once, and carry the correct values.
• Use GTM preview, tag assistant and browser network inspection to verify rather than assume.
• Flag tracking discrepancies early, because broken tracking corrupts decisions downstream before anyone notices the data is wrong.

Hold the line on quality

• Verify that live pages match approved copy, claims, pricing, imagery and brand standards.
• Validate A/B test variations before launch, confirming both variants work and track cleanly.
• Run regression checks on high-performing funnels whenever something is deployed near them.
• Return work that has not been self-tested by the developer. Developer self-QA is a prerequisite here, and you are the second line of defence, not the first.

Make defects stop repeating

• Log defects with reproduction steps, severity, environment and evidence, clear enough that a developer can act without asking you a single question.
• Verify fixes rather than assuming them.
• Categorize recurring defects and their root causes, and push the change where it belongs: into the checklist, the template or the reusable component.
• Build and maintain QC checklists for each page and funnel type, so quality becomes a property of the system rather than a property of your attention.

What Success Looks Like

In your first 30 days, you know our funnels and offer structures, you are testing launches independently, and your defect reports are being acted on without follow-up questions.

By day 90, we expect [X]% of launches going out with a complete journey check, escaped defects reduced to fewer than [X] per month, median time from defect reported to fix verified under [X], and the first set of standardized QC checklists live and in use.

Beyond that, the measure is simple. The same defect should stop appearing, and the team should be able to ship faster because quality is built into the process rather than inspected at the end.