What you'll do Own the test strategy and coverage across the web dashboard, the Rider App, the Teams App (Android + iOS), and the backend APIs. Design, write, and maintain detailed test cases and regression suites. Run smoke and sanity checks on every new build to catch breakages early before deeper testing - essential in a fast release cycle. Build and maintain automated tests to cover critical and repetitive flows, so manual effort goes where it's actually needed. Do thorough API testing - responses, edge cases, error handling, and data correctness behind the UI. Run performance and load testing on the APIs and platform to make sure it holds up under real traffic and high-volume telemetry. Carry out security testing - checking access controls, authentication/authorisation, data isolation between tenants, and common vulnerabilities before they reach production. Do integration testing across the apps, the backend, and third-party feeds (like telematics) to make sure the pieces work together, not just in isolation. Test on real Android and iOS devices, and across browsers, catching device- and platform-specific issues before users do. Validate each release and track issues through to resolution, distinguishing a genuine bug from a spec gap. Help define and improve QA processes as the product and team scale.Must-have skills 3-5 years in QA across web and mobile products. Strong foundation in test-case design, regression testing, and bug reporting with clear severity/priority judgment. Hands-on test automation - e.g. Selenium, Cypress, Playwright, or Appium - and the judgment to know what's worth automating. Solid API testing (Postman or similar), including validating data, not just status codes. Comfortable testing on real Android and iOS devices, and across browsers and platform versions. Performance / load testing experience - e.g. JMeter, k6, Locust, or Gatling - and the ability to design realistic load scenarios and read the results. Security testing fundamentals - access control and auth testing, data isolation, and awareness of common vulnerabilities (OWASP-style); hands-on with tools like OWASP ZAP or Burp Suite is a plus. Able to verify data behind the UI - basic comfort querying a database (we use MongoDB). Clear written communication - most of your output is test documentation and bug reports. Able to work independently - set up test coverage, prioritise, and run QA with minimal direction, owning the process end to end.