Fullstack QA Engineer (Client App)
About the role We are looking for a Fullstack QA Engineer who can own quality across mobile applications, backend services, and end-to-end product flows. This role is not limited to manual testing. We expect QA to think like an engineer: understand product risks, work with mobile and backend systems, analyze logs and API behavior, contribute to automation, use AI tools thoughtfully, and help the team improve quality processes. You will work closely with mobile engineers, backend engineers, product managers, designers, and other QA engineers to ensure that new features are released with the right level of quality. What you'll work on Native mobile applications for iOS and Android. Backend services and APIs that support mobile product flows. End-to-end customer journeys across mobile client, backend, data, and third-party integrations. Product features developed by cross-functional teams of mobile, backend, product, and design specialists. Test coverage across manual, exploratory, API, mobile, and automation layers. QA processes related to feature testing, regression, release quality, and production issue analysis. What you'll be responsible for Own end-to-end quality for your product area across mobile applications and backend services. Analyze new features from a product, technical, and user-risk perspective. Design and maintain test coverage for new and existing features. Investigate complex issues using logs, crash reports, analytics, traffic analysis tools, API tools, and system data. Contribute to automation strategy: define what should be automated, at which level, and why. Write, maintain, or review automated tests where relevant. Use scripts, tools, API clients, or AI-assisted workflows to reduce repetitive manual work. Participate in test planning, regression scope definition, release risk assessment, and quality process improvements. Clearly communicate risks, trade-offs, and coverage gaps to engineers, product managers, and stakeholders. What we need 3+ years of experience in QA / software testing, preferably with strong mobile product experience. Understanding of mobile-specific behavior: app lifecycle, permissions, push notifications, deeplinks, device matrix, app updates, network conditions, and platform differences. Experience testing REST APIs and backend-driven product flows. Ability to analyze client-server interaction. Basic understanding of backend behavior. Ability to read and write basic code or scripts. Strong experience with at least one programming language such as Kotlin, Swift, Java, Python, JavaScript, TypeScript, or similar. Understanding of automated test structure, assertions, test data, setup / teardown, flaky tests, and CI test runs. Ability to reason about what should be automated and what should remain manual. Strong bug investigation skills: logs, crash reports, reproduction steps, affected users, severity, priority, and root cause hypotheses. Ability to work independently in a fast-moving environment with incomplete requirements and changing priorities. Good to have Experience testing native mobile applications on iOS and Android. Experience with mobile automation frameworks such as XCTest / XCUITest, Kaspresso, Espresso, Appium or similar. Experience with native mobile stacks: Swift / iOS or Kotlin / Android. Experience building or maintaining automated API regression tests. Experience with CI/CD pipelines and test execution in CI. Experience with device farms or mobile testing infrastructure. Experience with log analysis, crash reporting, or monitoring tools. Experience testing financial, banking, lending, payment, marketplace, or other high-risk product flows. Experience using AI tools to improve test design, analyze logs, review tests, generate test data, or speed up QA workflows. Experience improving QA processes, reducing regression time, or decreasing defect leakage. What we value We are looking for a QA engineer who can go beyond checking tickets. A strong candidate: thinks in terms of product quality and business risk; understands that Figma shows only part of the system; asks good questions before testing; can reason about mobile client, backend, data, and configuration together; does not blindly automate everything, but chooses the right level of coverage; can use AI tools critically and responsibly; communicates risks clearly and constructively; can challenge a process without creating unnecessary conflict; takes ownership of quality in their product area.