QA-Driven Technical Product Owner

Faifly, до $5000

Що робити

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.

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.

Знайдено через trackr.help/jobs · Канал: @trackrhelp · Бот для персональних сповіщень: @trackrhelpBot