Manual Tester Client-Facing – Food Compliance SaaS

Who we're looking for?

• 2–4 years in manual testing / QA on a software product — ideally somewhere you also had direct contact with clients (application support, technical customer success, or implementation on a B2B product)
• Strong manual testing skills — you can systematically break a feature, design test cases from both the requirements and how clients really use the product, and write a bug up so clearly that anyone can reproduce it
• A sharp troubleshooting instinct — when something looks wrong, you work out whether it's a bug, a data problem, a config issue or a misunderstanding, rather than guessing
• Comfortable being client-facing — you can explain a technical issue to a non-technical client clearly and calmly, in excellent written English
• Comfortable with Jira/Zendesk-type tooling, reading logs, basic Postman and spreadsheets
• A natural sense of ownership — you follow things through without being chased

Nice to have: a food/FMCG or compliance background, basic SQL, or experience with multi-tenant SaaS.

About GFcomply

GFcomply is a SaaS platform delivering compliance and labelling solutions for the food industry. Our Data Team collects, structures and maintains regulatory data from official sources worldwide — the trusted foundation that powers the compliance and labelling services our customers rely on.

The team runs an automated ETL (Extract / Transform / Load) pipeline built around Claude AI, turning regulations from many geographies, languages and frameworks into a structured, searchable database. As a Manual Tester on this team, you'll be the person who keeps that product reliable — testing every release, safeguarding data quality, and being the calm, clear voice clients hear when something needs fixing.

,[Run manual test cycles before every release on new features, fixes and regressions, so problems get caught before clients ever see them. You'll design test cases from both the requirements and how clients actually use the product, verify the fixes, and close the loop with whoever reported the issue., Own the quality bar — every row and every workflow must be traceable and correct. You'll deliberately try to break things, cover the edge cases, and make sure nothing broken slips through to production., Take client and supplier queries by email and ticket, dig into what's really going on (a bug? data? config? just a misunderstanding?), and reply clearly. For the trickier cases, you'll hop on a call. When something's genuinely broken, you'll write it up properly for engineering — then translate their answer back into plain language for the client., Keep clients in the loop during incidents and after releases, so they never feel left in the dark.] Requirements: Manual Testing, Jira, Test Case Design, QA, Zendesk, SQL, SaaS