Quality Engineer

Mission / Why This Role Exists

Ensure clinical workflows never break — ever.

You are responsible for designing automated end-to-end, API, and regression test safety nets that protect doctors, therapists, and patients from failed deployments or unintended side effects.

This role is not about pixel-perfect UI testing — it is about high-confidence validation of real healthcare operations.

Key Responsibilities

• Test Automation for Critical Clinical Scenarios
• Design and implement end-to-end automated test suites simulating real therapist + patient workflows.
• Build API-level contract testing for all mission-critical FHIR and domain endpoints.
• Validate multi-step workflows & sequencing, such as:
• Creating + modifying Care Plans
• Booking and completing appointments
• Recording clinical Observations & progress
• Uploading clinical documents
• Patient portal flows (PROMs, exercise instructions, etc.)
• Prevent Regressions via CI/CD Enforcement
• Integrate automated test execution directly into CI/CD pipeline — must block unsafe deploys.
• Maintain a clean regression pack that evolves as features expand.
• Own test data strategy — consistent, versioned, auto-resettable.
• Quality Ownership (Not Just Testing)
• Catch real-world edge case failures, not just happy paths.
• Collaborate closely with backend + frontend engineers to define testable acceptance criteria.
• Track defects back to root cause — not just “report”.

You MUST Have

• 3+ years in QA Automation (NOT manual-only testing)
• Strong experience with API-level test frameworks (REST Assured, Karate, Playwright API, etc.)
• Experience writing automation in Kotlin/Java or Python or TypeScript
• Direct CI/CD pipeline integration experience (GitHub Actions, GitLab, Jenkins, etc.)
• Experience testing mission-critical systems (healthcare, finance, gov, insurance, etc.)
• Strong understanding of state-based testing + data consistency

Nice to Have

• Experience with FHIR, HL7, or regulated environments
• Experience with Playwright / Cypress for real user flows (not just Selenium)
• Basic understanding of Kubernetes + staging deployment flows
• Familiar with Postman Collections / Insomnia / Contract Testing

Mindset / Personality Fit

• You think like a failure-mode hunter, not a checkbox tester.
• You chase “what could go wrong?” — not just “what should work?”
• You love automation, not repetitive manual testing.
• You see yourself as a guardian of safe releases, not a last-minute tester.
• You work proactively with engineers, not after something is broken.

What You Will NOT Be

• Not a manual-only UAT tester
• Not someone who tests only visual/UI correctness
• Not someone who waits passively for tickets
• Not a passive observer — you are a safety engineer