QA Automation Engineer

ABOUT CITEMED CiteMed is a globally distributed team on a mission to improve clinical regulatory workflows. We move fast, we respect each other, and we trust people to own their work. If you thrive with autonomy and care about the impact of what you build, you’ll fit right in. We’re a small but growing distributed team — scrappy, fast-moving, and genuinely collaborative. There’s no bureaucracy to navigate, no waiting for permission — just smart people moving quickly toward something that matters. For the right person, this role has real room to grow. ABOUT THIS ROLE CiteMed builds Evidence Cloud — the platform medical-device manufacturers use to produce and maintain the clinical evidence regulators demand. Our QA today is 2,910 test cases run by hand in Qase. Your job is to own the shift to automation: a Playwright suite generated from those cases, running in CI, reporting every result — with video and trace — back onto its source case in Qase. The pipe is already proven end to end. Now it needs an owner to build it out, harden it, and make it the team’s source of truth. This is a greenfield build — you define the suite, the patterns, and the tooling. Every case you automate is one no human runs again. WHAT YOU’LL BUILD Phase 1 — Prove Template the loop. Stand up the Qase → Playwright → Qase round-trip on pages that are already automatable, and set the spec patterns, helpers, and CI wiring the whole suite will inherit. Phase 2 — Scale Selectors and coverage. Add durable data-testid hooks across the core CRUD pages and convert ~900 high-confidence cases into stable, non-flaky specs — the highest-leverage stretch of the project. Phase 3 — Harden The hard stuff. Workflow-level tests for our AI-driven pages: assert state and job lifecycle, mock the model, keep tests deterministic — and design the human-review gate for AI-generated clinical content. HOW THE LOOP WORKS Qase case (the manual script) → Claude reads the view and picks selectors → Playwright spec tagged to the case → CI run with video + trace → Result posted back to Qase as pass/fail on the exact case. You own everything from the second step on — and decide where a human still needs to watch the reel. THE STACK • Testing: Playwright · TypeScript · Qase TestOps • Frontend: Vue 3 • Backend: Django • CI: GitHub Actions • AI copilot: Claude Code • Project management: Jira — initiative scoped, tickets ready YOU’RE PROBABLY A GOOD FIT IF… • You have strong, hands-on Playwright experience in production — not just tutorials, real test suites • You’re fluent reading a frontend to find the right selectors and seams — you know how to make tests durable • You have strong opinions about flakiness, determinism, and what’s actually worth asserting • You’re comfortable with AI-assisted authoring and skeptical enough to catch a dumb test when you see one • You’ve worked in CI infrastructure before — GitHub Actions, reporting pipelines, test result management • You work autonomously, communicate proactively, and don’t need to be chased for updates • You’re a builder — you’ve owned a greenfield test suite before, or you’re ready to • Bonus: experience in a regulated or audited SDLC environment, or medical device software — you understand why QA where regulators and patients are downstream is different HOW WE’LL MEASURE SUCCESS • Suite coverage: ~900 high-confidence cases converted to stable, non-flaky Playwright specs • Reliability: Zero flaky tests — deterministic, trustworthy, and maintainable • CI integration: Every run posting pass/fail, video, and trace back to its Qase source case • Code quality: Clean patterns and helpers the whole team can build on • Communication: Weekly Slack update — what shipped, what’s in progress, what’s blocked