QA Engineer — Web & Mobile at Physitrack

Poland

<p><strong>QA Engineer, Web and Mobile</strong></p><p>Individual contributor. Reports to the Director of QA. No direct reports.</p><p><strong>Salary</strong>: €5000 per month </p><p><strong>Location</strong>: Poland (Fully Remote)</p><p><strong>The role</strong></p><p>You test the web application, frontend and backend, and the mobile applications on iOS and Android. That is the surface of the job.</p><p>Underneath it, the point of this role is to understand how the product actually works: the data flow, the API contracts, the places where two systems meet and produce behaviour nobody specified. That understanding is what lets you improve a specification before code is written, catch the gap nobody else noticed, and give Support, Sales, Product and Engineering an answer they can rely on.</p><p>We are looking for extreme ownership, the person who picks up the task nobody else wants because it needs doing and they can see why it matters.</p><p><strong>What you will do</strong></p><p><strong>Test the product properly.</strong> Web end to end, frontend behaviour and backend responses, not just the UI layer. Mobile on iOS and Android against an agreed device and OS matrix, with a real understanding of platform conventions and where the two diverge.</p><p><strong>Own our automated coverage on web.</strong> Extend and maintain the Playwright suite and write new tests for the features you take through. Investigate failures and fix flakiness rather than muting it, and be honest about what automation is and is not covering.</p><p><strong>Verify at the API and data layer.</strong> Requests, responses, payloads, status codes, backward compatibility for older clients. Query the database directly to confirm what actually happened, rather than what the screen says happened.</p><p><strong>Prevent bugs, not just report them.</strong> Pressure-test specifications with Product, Design and engineers before development starts: happy paths, edge cases, error states, empty states. Point out the platform that was forgotten, the API version that will break, the migration nobody planned. Asking the awkward question early is part of the job.</p><p><strong>Debug to root cause.</strong> "It doesn't work" is not a bug report. Narrow down where it breaks and what the system is actually doing, and hand the developer something they can act on.</p><p><strong>Support the wider business.</strong> Reproduce and triage customer issues that reach engineering, and keep test plans and known-issue lists current so release decisions rest on evidence.</p><p><strong>Use AI every day.</strong> Reduce your own repetitive work with it, build reusable AI skills the wider team can benefit from, make small fixes in the code yourself where that is reasonable, and bring ideas about where AI can raise our quality bar.</p><p><strong>What we are looking for</strong></p><ul><li><p>Three to five years of hands-on testing of web applications, with a demonstrated ability to find root causes rather than symptoms.</p></li><li><p>Practical test automation experience. You have written and maintained UI or API tests in Playwright, or a comparable framework, and can work in a test codebase without hand-holding.</p></li><li><p>You can read and reason about API contracts and payloads, query a database in SQL to verify data, and are comfortable with traffic and API inspection tooling, or quick to pick it up.</p></li><li><p>Mobile testing in practice. You can tell a platform convention apart from a defect, and reason about the device and OS coverage a given change actually needs.</p></li><li><p>Proven collaboration with Design and Product. You have been in the room during specification work and made it better without owning it, with examples you can talk us through.</p></li><li><p>Excellent written and spoken communication, in Polish and English, both at C2 or native level.</p></li></ul><p><strong>Nice to have</strong></p><ul><li><p>Testing in a regulated or healthcare-adjacent domain.</p></li><li><p>Device farms or cloud device labs, such as BrowserStack or Firebase Test Lab.</p></li><li><p>Triaging from crash and error monitoring, such as Sentry or Crashlytics.</p></li><li><p>Accessibility testing (WCAG).</p></li></ul>