We are building and operating a fintech and BNPL platform that includes mobile applications, web applications, backend APIs, batch processes, databases, and integrations with banks, merchants, and other external partners.
Our Product Managers, Business Analysts, architects, designers, and engineers define the business requirements and system designs. We are looking for a Senior Quality Engineer who can translate those requirements and designs into an effective quality strategy and continuous automated verification.
You will own product quality and drive quality improvements across the organization. This does not mean that you must personally implement every test or perform every quality-related task. You will work with engineers and other product members to determine what must be verified, what should be automated, what technical components are needed, and how those components should be combined into reliable quality-control flows.
This role covers the entire product—not only UI testing, but also mobile applications, web applications, APIs, batch processes, databases, and cross-system business flows.
-
Review business requirements, acceptance criteria, UI/UX designs, API specifications, and technical designs prepared by Product Managers, Business Analysts, architects, designers, and engineers.
-
Translate expected product behavior into test conditions, test scenarios, and automated verification.
-
Identify unclear, inconsistent, incomplete, or difficult-to-test requirements and proactively clarify them with the appropriate owner.
-
Define a risk-based quality strategy, including test coverage, quality gates, release criteria, and regression policies.
-
Determine the appropriate combination of unit, integration, contract, end-to-end, regression, smoke, exploratory, and manual testing.
-
Design scenarios covering successful paths, failures, retries, timeouts, recovery flows, boundary conditions, and data inconsistencies.
-
Communicate quality risks and coverage gaps clearly and help teams prevent defects during requirements, design, and development—not only detect them after implementation.
-
Incorporate defined security, compliance, auditability, and traceability requirements into test scenarios, automated verification, quality gates, and release evidence.
-
Design, implement, maintain, and improve automated verification across mobile applications, web applications, APIs, batch processes, and databases.
-
Build or improve reliable and maintainable automation frameworks.
-
Automate critical end-to-end business flows spanning multiple applications, services, and backend systems.
-
Implement mobile and web automation testing using appropriate tools such as Maestro, Appium, Playwright, Cypress, Selenium, or equivalent frameworks.
-
Implement API and contract testing using OpenAPI specifications, schema validation, Schemathesis, Postman/Newman, REST Assured, Pact, or equivalent solutions.
-
Create automated flows that execute and verify batch processes, smoke tests, API responses, system states, and data consistency.
-
Define the data and system conditions that must be verified and collaborate with engineers to prepare the necessary queries, scripts, APIs, test hooks, or other technical components.
-
Combine tests, scripts, queries, APIs, and other verification components into repeatable automated quality-control flows.
-
Investigate failures and distinguish between product defects, environment issues, test-data problems, integration issues, and unstable test implementation.
-
Continuously improve test reliability, execution speed, maintainability, observability, and coverage.
-
Define which automated checks should run at each stage of development and release, including pull requests, merges, deployments, scheduled executions, and releases.
-
Integrate automated verification and quality gates into the existing CI/CD process.
-
Define clear pass, fail, warning, escalation, and exception conditions based on product risk.
-
Work with engineers to implement or modify CI/CD workflows when additional technical support is required.
-
Ensure that test results and quality-gate failures provide clear and actionable feedback.
-
Prevent unreliable or unnecessarily slow tests from blocking development while maintaining sufficient release confidence.
-
Work closely with Product Managers, Business Analysts, designers, architects, and engineers to improve quality across the product.
-
Coordinate quality activities across teams and systems while involving the appropriate specialists in implementation.
-
Raise quality concerns with clear evidence, including affected requirements, business flows, system behavior, test results, and potential impact.
-
Support manual testing and investigation when necessary, particularly for new, complex, or high-risk product areas.
-
Explore practical uses of AI in requirement comparison, test generation, coverage analysis, regression-impact analysis, and automated-test maintenance.
-
Promote a culture in which quality is considered throughout the product-development lifecycle and owned by the entire product team.
During your initial months, we expect you to:
-
Understand the existing architecture, repositories, CI/CD workflows, product flows, specifications, and testing processes.
-
Map critical product flows to existing tests and identify important coverage and automation gaps.
-
Assess current quality risks and automation maturity across mobile, web, API, batch, and database layers.
-
Propose a prioritized quality strategy and automation roadmap.
-
Implement or improve automated verification for selected high-risk areas and establish the appropriate quality gates.
We are looking for a quality-minded Product Builder who wants to improve quality across the whole product.
-
Strong Automation Mindset: You can build automated verification and want to expand automation beyond individual screens.
-
Product-Wide Perspective: You consider mobile apps, web applications, APIs, batch processes, databases, and system integrations as parts of one product.
-
Proactive Communication: When requirements or designs are unclear, you actively consult the relevant person instead of making unsupported assumptions.
-
Technical Curiosity: You are comfortable working with APIs, CI/CD, logs, system data, and distributed workflows, and can independently learn unfamiliar tools.
-
Risk-Based Pragmatism: You prioritize testing based on business impact and technical risk and understand when to implement something yourself or involve another engineer.
-
Ownership and Integrity: You take responsibility for product quality and communicate risks and test results honestly and transparently.