Test Engineer (QA / SDET)
Own how Tracegence catches regressions before customers do - test infrastructure, end-to-end coverage across the Django backend and Angular SPA, and the contract tests that keep the AI pipeline honest.
About the role
Tracegence ships features that span Django, Celery, Postgres + RLS, an Angular SPA, three AI tiers, and a handful of cloud services. That's a lot of places for a regression to hide. The repo has solid phase-based pytest coverage (177 tests across 12 phases at last count) plus a launch-gate test that simulates the full critical path - but the day-to-day reality is that engineers write tests as they ship and there's no dedicated owner. That's the gap. You'd own how testing works: where the existing suite has blind spots (RLS edge cases, async pipelines, multi-tenant interactions), what gets tested at the unit vs integration vs E2E level, when a Playwright or Cypress suite for the SPA is worth the maintenance cost, and how to make the AI tiers testable without burning Vertex quota on every CI run. The role is part SDET (writing the test infrastructure other engineers reuse) and part QA (catching the things tests can't - usability, edge cases in real customer data, regressions in the demo seeds that ship with every release).
What you'll do
- Own the test suite end-to-end: where it lives, how it runs, what it covers
- Build an E2E test layer for the Angular SPA that doesn't break every time the UI changes
- Tighten the mocked AI boundary: contract tests that catch a real Vertex / Document AI signature change
- Audit the RLS coverage tests - make sure new tables can never silently skip ENABLE ROW LEVEL SECURITY
- Be the person who runs the manual regression pass before every release until automation catches up
- Triage customer-reported bugs into reproductions + tests; close the loop
What we look for
- 3+ years in QA / SDET roles - not just "I ran the tests after my code"
- Deep with pytest in a real Django codebase; comfortable with Playwright or Cypress for SPAs
- Have a point of view on unit vs integration vs E2E - and when each is the wrong choice
- Can read backend Python and frontend TypeScript well enough to find the right test seam
- Comfortable being the person who blocks a release when something isn't ready
Apply for Test Engineer (QA / SDET)
Send a short note and your relevant background - we read every email.