QA Engineer

Faifly5k USD

format:Remotetype:Full-timecompany:Outsource

rest-apisqllog analysisdata modelingapi testing

test automationemr

test task:yes

englishB2

domainHealthTech

> full description

Location: Remote — 5+ hours of overlap with US Eastern hours Position
Type: Full-time, long-term
Seniority Level:Middle+ / Senior (Strong QA / Technical PO)
Domain: Digital Health — Remote Patient Monitoring, Chronic Care Management, Billing

About the Project

A US-based digital health platform for Remote Patient Monitoring (RPM) and Chronic Care Management (CCM). It integrates with a broad range of FDA-approved medical devices — blood-pressure cuffs, glucometers, scales, pulse oximeters, and more — and with leading EHR systems, helping providers and care teams monitor patients at home and run their RPM and CCM programs, including billing.

About the Role

A hands-on technical product role built for someone with a strong Technical QA background, not a management role.

If you are the QA Engineer who always spots missing edge cases during grooming, digs into SQL, APIs, and logsbefore filing a bug, and ends up rewriting tickets so developers actually know what to build — this role is your next step.

Reporting to the Lead Technical PO, you will turn epics from PMs and the Head of Product into precise specs that engineers can build and QA can test without follow-up questions — inspecting APIs, querying data, reading logs, and tracing logic in code yourself.

It is a long-term track toward Lead Technical PO, not a path to a roadmap Product Manager or Project Manager. If you want to own a high-level roadmap or manage people, this role is not for you.

Responsibilities

Turn epics into precise, testable requirements: define data and API behavior, dependencies, edge cases, and acceptance criteria that leave nothing to interpretation.
Prevent bugs before code is written: challenge implementation assumptions with engineers and work with design when edge cases or constraints change the UX.
Run the grooming loop with the Lead Technical PO: make sure every technical and UX change agreed upon with engineers and design reaches the final ticket before sprint start.
Investigate production issues yourself: reproduce bugs, isolate the problem using logs, SQL queries, and API payloads, and write the ticket that fixes the root cause.
Own post-deployment verification: validate releases in production on real data and workflows, catch regressions before clients do, and drive the fixes.
Work with two leads: product priorities from one, technical PO craft standards from another.

Requirements

Strong hands-on background in Technical QA (Middle+ / Senior QA, QA Lead, or a Technical PO / BA who grew out of QA).
Deep understanding of how systems work under the hood: you comfortably work with REST APIs, data models, relational databases (SQL), and logs, and can read code / PRs to trace business logic.
Extremely detailed technical writing in English (Upper-Intermediate / B2+ or higher): you naturally think in state transitions, negative scenarios, and unambiguous acceptance criteria.
A working day of roughly 12:00–21:00 Kyiv time: a local team meeting at 12:00, the daily stand-up with the US team at 16:00 Kyiv (9:00 ET), and at least 5–6 hours of overlap with US Eastern business hours (occasionally more — e.g., for a release).
Occasional release windows in the US evening — night in Europe.
Genuine interest in the Technical PO craft as a long-term career path.

Nice to Have

Senior QA Engineer who has already been writing specs, grooming tickets, or acting as a Proxy PO / BA.
Strong SQL fluency on complex, production-shaped data.
Formal grooming and refinement experience with engineering teams.
Experience with test automation or reading/writing scripts.
Healthcare, RCM, claims, billing, or another regulated domain with complex business rules.
EHR/EMR, medical devices, or third-party API integrations experience.