Quality Assurance Engineer in London

Why This Role Exists

Today, every client integration — including Fishka, EasyEquities, MTN, Grab, Nykaa, and YPF — runs its own ad hoc QA process. This often leads to escalations, uncertainty, and finger‑pointing when something behaves unexpectedly. This role owns end‑to‑end QA for each client account, from pre‑production TestFlight access through production rollout, campaign setup, validation of all use cases (e.g., Best Moment), and ongoing data quality assurance. Sitting within the CDA team, this person acts as the trusted QA partner for each client pod, ensuring releases are predictable, issues are identified early, and client experiences remain consistently high quality.

Core Responsibilities

• Own UAT and Release Readiness
  • Lead UAT and release readiness for every client integration.
  • Act as the final go/no‑go gate before production deployment.
  • Manage TestFlight and test‑build coverage.
  • Verify production credentials and rollout readiness.
  • Oversee gradual rollouts, including percentage‑based enablement and PNS monitoring.
  • Sign off on debug‑screen removal before production release.
• Validate Campaign Setup and Execution
  • Verify campaign configuration through the Console.
  • Test and validate:
  • Deep links
  • Audience targeting and segmentation
  • Ensure campaign outputs match expectations as audience scale increases.
  • Confirm each client's microsegment and custom microsegment setup is configured correctly for:
  • SDK version
  • Intended use case
  • Identify and resolve configuration mismatches before clients encounter issues.
• Validate SDK Data Quality
  • Verify SDK signals within the live client application.
  • Confirm data flows correctly into:
  • Jema API
  • Cross‑check internal tooling to validate active users, SDK health, and overall data integrity.
• Triage and Manage Defects
  • Investigate and route client‑reported issues efficiently.
  • Clearly distinguish between:
  • SDK/platform issues
  • Client application issues
  • Prevent routine issues from escalating into engineering fire drills.
• Drive Cross‑Client Quality Improvements
  • Ensure fixes are systematically applied across all relevant client accounts.
  • Proactively identify clients that could benefit from existing fixes.
  • Prevent any client from falling behind on known improvements.
• Maintain QA Documentation
  • Own and maintain auditable, client‑specific QA records, including:
  • Test coverage
  • Release sign‑offs
  • Promised functionality
  • Offline workarounds
  • Known blockers
  • Version‑to‑version changes

What Success Looks Like

• Every client deployment has a clearly defined QA status and documented go/no‑go decision.
• All identified issues have owners, resolution paths, and closed feedback loops.
• Client‑side regressions are caught before clients discover them.
• Cross‑client fixes are propagated proactively and consistently.
• No client remains behind on a known fix or improvement.
• CDA pods have a trusted QA partner who significantly reduces escalation volume to Engineering and Product teams.

Experience owning UAT and release quality for enterprise B2B software deployments. Exposure to mobile SDKs and campaign management, marketing, or console‑based platforms. Strong data validation skills, including SQL and monitoring/observability tooling. Ability to reason across end‑to‑end systems, including pipelines, APIs, SDKs, and customer‑facing outputs. Exceptional stakeholder management and communication skills. Calm and effective under client pressure, while remaining credible with engineering and delivery leadership teams. Strong pattern‑recognition skills, with the ability to identify recurring defect classes across accounts and drive upstream fixes.