This position is in Zama’s Developer Platform team

Zama recently unveiled the Zama Confidential Blockchain Protocol, which enables confidential smart contracts on top of any blockchain L1 or L2, using Fully Homomorphic Encryption (FHE). The Zama Developer Platform (ZDP) is our managed gateway that lets internal teams and external developers use the open-source Zama Protocol through simple, authenticated HTTPS endpoints. Think Infura or Alchemy, but confidential by default.

We are looking for a Senior QA Automation Engineer to build and own the prod-like end-to-end test platform and automate release qualification. You’ll make every release safe by default with deterministic environments, automated gates, and fast rollback paths, validating how real developers build with our portal, SDKs/templates, and platform APIs. You will test a polyglot system, with core services written in both TypeScript and Rust, ensuring the entire developer journey is seamless all the way through to on-chain callbacks.

What you will do

• Own the end-to-end (E2E) test platform: Design deterministic environments (local, CI, testnet) with reusable fixtures, data seeding, and mocks; exercise real developer journeys across portal + SDKs/templates → platform APIs → on-chain callbacks, spanning TypeScript and Rust services; add lightweight test hooks/shims where needed.

• Automate release qualification: Define and implement quality gates in CI (GitHub Actions), smoke/canary packs, SLO-based promotion criteria, and rollback verification; publish artifacted evidence for go/no-go while owning teams press the button.

• Reduce flakiness & non-determinism: Drive isolation, idempotency, stable timeouts/retries, and retry-/reorg-aware harnesses; keep suites fast and flake rate low.

• Performance & resilience testing: Build load/stress/soak tests (e.g., k6/Locust) for platform paths; define perf SLOs and track trends; run basic chaos experiments to harden failure modes.

• Synthetic monitoring & on-call readiness: Ship black-box checks for golden paths (key creation, relay lifecycle, decrypt callbacks) across TypeScript and Rust services wired into dashboards/paging; fold incident learnings back into automated checks.

• Quality enablement: Provide standards, libraries, and templates so feature teams own unit/integration tests while the platform validates cross-service flows.