QA Engineer

Що робити

Test the money, not just the screens. Design and run test cases for the calculation logic: income and expense totals, VAT, allowable expenses, tax estimates, rounding, negative amounts, refunds, part-period and tax-year-boundary cases, 5 April / 6 April transitions. Correctness of figures is the first priority in this product, above everything else.
Own release sign-off. Maintain the regression suite for critical user journeys (onboarding, bank connection, expense capture, tax summary, subscription), run it every release, and hold the go/no-go decision on quality grounds. Target: zero critical or high-severity defects escaping to production per release.
Cover the device reality. Test across an agreed iOS and Android device and OS matrix, including older devices, small screens, offline mode, flaky connectivity and interrupted background sync — the conditions our users are actually in, on site or in a van.
Test the integrations. Bank feeds / Open Banking connections, receipt scanning, App Store and Google Play subscription flows, and the API layer beneath them (Postman / REST clients) using sandbox environments and controlled test data.
Write bugs people can act on. Steps, environment, device, app version, expected vs actual, evidence, severity and priority that mean something. Track them through to verified fix and closure in Jira / Linear.

Fintech, accounting, payroll or tax software background; or personal familiarity with Self Assessment, VAT, MTD.
Experience testing subscription billing and store purchase flows (RevenueCat or similar).
Performance, accessibility or localisation testing.
SQL for verifying data directly, and any scripting (Python / JS).
CI/CD pipeline exp