QA Engineer
Description
Our client builds diagnostic imaging equipment used in hospitals and clinics worldwide — mammography systems, biopsy devices, and related hardware that clinicians rely on every day. Behind that hardware sits a cloud platform that keeps tens of thousands of these devices connected: collecting operational data, powering remote diagnostics so support engineers can fix problems without an on-site visit, and feeding analytics that help hospitals keep their equipment running.
We’re taking over full ownership of the system now, which means inheriting real production code, real users, and a real backlog — not starting from a blank page. For QA, that’s the job: figure out what’s actually being tested today, decide what needs automation and what doesn’t, and build a quality process that fits a medical device company’s standards from week one.
Requirements
– At least 6-8 years in QA, 3+ in a lead/strategy-owning role (not just execution).
– Hands-on test automation framework experience (not tool usage only).
– Experience testing cloud-based or connected-device systems. Experience with device connectivity or IoT fleet management testing at scale (thousands+ of connected endpoints) is a big advantage
– Experience in a regulated software environment (medical device preferred; healthcare/fintech/other compliance-driven SDLC acceptable).
– Working knowledge of CI/CD-integrated quality gates and QMS-aligned testing (traceability, V&V documentation).
– Experience taking over an existing codebase with unclear test coverage, not just greenfield.
– Comfortable presenting quality strategy and metrics directly to client stakeholders. Strong communication and presentation skills.
Job responsibilities
We’re looking for a Lead QA Engineer who can take ownership of quality across this engagement from day one — someone who thrives with autonomy, drives decisions rather than waiting for them, and is comfortable being the face of QA in front of the client. This is a senior, hands-on leadership role: you’ll set the direction, defend your calls, and be accountable for the outcomes, not just execute a plan someone else wrote. Your responsibilities will include, but not limited to
– Define and own the overall test strategy across both systems — functional, non-functional, regression, and device-connectivity testing.
– Decide what gets automated vs. tested manually, and at what level (unit/integration/E2E), based on risk and regression value; revisit this as coverage of the inherited codebase improves.
– Select test automation frameworks, CI/CD test integration, and test data tooling appropriate to the stack and team.
– Align test strategy and documentation with the client’s QMS and design-control procedures, including ownership of V&V documentation (execution only — regulatory validation/release sign-off stays with the client).
– Own defect management: triage, severity classification, and coverage/defect metrics, reported monthly with corrective action when targets are missed.
– Enforce quality gates (Definition of Done, code review, static/composition analysis) as blocking steps in the pipeline.
– Lead the QA team (manual + automation engineers) and report quality status to the client governance forum.