Overview We’re looking for a senior QA engineer to quickly bring our healthcare platform (Software as a Medical Device – SaMD) to pilot-ready quality. Our system includes: • A web-based clinician dashboard (React, Java backend, Kafka, mongo, sql) • A cross-platform mobile app (Flutter) • The two work in tandem — workflows are initiated on the web and executed on mobile, with results reflected back in the web dashboard We currently have QA support, but we need someone who can introduce structure, define coverage, and systematically identify issues — not just exploratory “click testing.” This is a short-term, high-impact engagement to ensure we can safely deploy to real users. ⸻ What you’ll do 1. Establish QA structure (quickly) • Review the product and identify core workflows and high-risk areas • Create a lightweight test plan / coverage checklist • Define clear “pilot readiness” criteria 2. End-to-end functional testing (primary focus) • Test workflows across web → mobile (Flutter) → backend → back to web • Validate: • Task assignment and completion flows • Data consistency across systems • User roles and permissions • Error handling and edge cases • State changes (statuses, alerts, visibility, sync behavior) 3. Structured bug reporting and triage • Log bugs with: • Clear reproduction steps • Expected vs actual behavior • Screenshots or screen recordings • Severity classification (blocker / critical / minor) • Identify likely root causes of issues (e.g., UI vs API vs data sync vs workflow logic) to help accelerate debugging and resolution. 4. Prioritize for pilot readiness • Help categorize: • Pilot blockers (must fix before release) • Important but non-blocking issues • Nice-to-have improvements 5. Regression and release confidence • Create a repeatable regression checklist • Verify fixes and prevent regressions in core workflows ⸻ Deliverables • Test coverage checklist (what’s covered vs gaps) • Core E2E test cases for key workflows • Structured bug backlog with severity/priority • Pilot readiness summary (blockers, risks, recommendations) ⸻ What we’re looking for • Strong experience testing multi-system applications (web + mobile or distributed systems) • Experience with Flutter app testing (or similar cross-platform frameworks) • Ability to quickly bring structure to unclear or undocumented systems • Strong bug reporting and prioritization skills • Comfortable working independently and moving fast ⸻ Nice to have (not required) • Experience in healthcare / regulated environments (SaMD, risk-based testing mindset) • API testing (Postman or similar) • Experience testing async/sync workflows (delays, retries, data sync issues) • Basic automation knowledge (for future phases) ⸻ Scope & Timeline • Immediate start • Initial engagement: 1–2 weeks (intensive testing + triage) • Potential for ongoing support through pilot phase ⸻ How to apply Please include: 1. A brief example of a project where you tested end-to-end workflows across web and mobile 2. Your approach when there is little or no existing test documentation 3. How you define and classify bug severity (blocker vs non-blocker) 4. Your availability over the next 1–2 weeks ⸻ Questions for You 1. Have you tested workflows that span web and mobile apps working together? Briefly describe. 2. How do you quickly build a test plan when documentation is limited? 3. How do you determine if a bug is a pilot blocker vs non-blocker? 4. What tools do you use for bug tracking and evidence capture? 5. Are you comfortable testing Flutter-based mobile apps?