!Submit applications only in English!
Role summary:
We’re hiring a QA Team Lead to own end-to-end quality for a multi-tenant automation backend: API contracts, Celery task reliability, account health correctness, browser/proxy stacks, and release gating for `dev` → production Docker deploys.
You’ll set the quality bar, build automation where it matters, and make sure releases are safe, especially when data correctness and async workflows are on the line.
Today the system is production-critical but under-tested. Your job is to change that: clear standards, reliable smoke/regression coverage, and a team that catches issues before customers do.
What you’ll do
- Own QA strategy, release criteria, and go/no-go decisions for backend and worker deploys
- Lead and mentor the QA team; define bug severity, repro standards, and reporting cadence
- Build and grow automated coverage (API contract, data integrity, selective E2E) and make CI a real gate
- Validate async job pipelines end-to-end (enqueue → worker → result → monitoring)
- Treat dashboard/KPI correctness as a first-class concern — reconcile UI numbers with underlying data
- Partner with engineering on staging setups, flaky environments (browser-based workers), and migration risk
- Prioritize by impact: wrong metrics, stuck jobs, permission leaks, and infra regressions
What we’re looking for
**Must-have**
- 5+ years in QA / SDET, including 2+ years leading QA or owning quality for a complex backend product
- Strong REST API testing (auth, permissions, negative cases, async polling)
- Experience with background job systems (Celery or equivalent)
- Solid PostgreSQL / SQL skills (joins, views, reconciling counts and statuses)
- Comfortable reading Python and writing pytest (or similar)
- Proven track record turning weak/manual QA into structured automation and CI gates
- Clear written communication and crisp bug reports
**Nice-to-have**
- Browser automation (Playwright / Selenium) in Dockerized or antidetect-style environments
- Multi-tenant SaaS isolation testing
- Docker + GitHub Actions (or similar) release pipelines
- Dashboard / analytics QA experience
- Familiarity with Jira as the defect source of truth