You’ll lead quality engineering for a new shared platform that lets Money Forward product teams add approval and document-submission workflows without building those capabilities from scratch. Working across REST APIs, Kafka-based events, micro-frontends, and multi-tenant infrastructure, you’ll build confidence in the behaviours no single component team can validate alone - including service contracts, end-to-end workflows, failure recovery, performance, and reliability.
You’ll join the QA team as a Staff IC, reporting to the QA Manager and working across the teams that build and integrate the platform. Your initial focus will be taking the platform from its first staging release through hardening and production launch. You’ll work hands-on alongside developers and component QA engineers: identifying systemic risks, improving testability and observability, automating critical validation, and turning evidence into clear release-readiness recommendations. Beyond launch, you’ll establish the quality architecture and engineering practices that allow the platform to evolve safely.
Technology Stack
- Backend: Kotlin (Spring)
- Frontend: React
- Platform: AWS, Kubernetes, Terraform
Responsibilities
- Define and evolve a risk-based quality strategy for the platform, covering service contracts, cross-service workflows, tenant isolation, failure recovery, performance, and reliability.
- Design and implement automated validation at the layers where it provides the most confidence, including API and event contracts, service integration, and critical end-to-end workflows.
- Lead performance and resilience testing to expose capacity limits, latency risks, unsafe retry behaviour, and failure modes before they affect production.
- Work with developers to improve the platform’s testability and observability, including useful telemetry, controllable test environments, and reliable test data.
- Bring together evidence from component teams and system-level testing, clearly communicate residual risk, and make release-readiness recommendations.
- Coach component QA engineers and developers in platform quality practices, and create reusable approaches that allow teams to validate their own changes effectively.
Requirements
- Quality engineering for a shared platform. You’ve been technically responsible for quality for a production platform or shared service used by multiple products or engineering teams. You can show how you identified and addressed risks between the platform and its consumers - for example, contract compatibility, integration behaviour, tenant isolation, or coordinated changes across systems.
- Hands-on test and software engineering. You’ve designed and implemented maintainable automated tests and supporting tools for production systems, including APIs, service integrations, and end-to-end workflows. You’re comfortable reading application code, debugging failures across system boundaries, and contributing improvements directly.
- Performance and resilience engineering. You’ve designed and run load, stress, or failure-recovery tests for production systems. You can interpret application, infrastructure, database, and messaging telemetry to find bottlenecks and failure modes, then work with engineers to address them.
- Technical leadership across teams. You’ve led a quality initiative involving multiple engineering teams without relying on line-management authority - for example, aligning teams on risk, establishing shared practices, coaching engineers, and communicating evidence clearly enough to support release decisions.
- DevOps & CI/CD ecosystems. Basic proficiency with DevOps and CI/CD tools (e.g., CircleCI, GitHub Actions, ArgoCD) to support high-frequency platform delivery.
- Scalable automation architecture. Experience architecting robust, scalable test automation frameworks that integrate seamlessly into CI/CD pipelines and handle multi-tenant complexity.
- English Language Requirement: Professional communication in English. You can discuss technical designs, write clear quality and risk assessments, and explain release-readiness evidence to engineers and stakeholders in English.
Nice to haves
While not specifically required, tell us if you have any of the following.
- Distributed and event-driven systems. Experience testing production systems made up of multiple independently deployed services, including API and message contracts, partial failures, schema compatibility, delivery semantics, ordering, retries, and idempotency.
- Micro-frontend integration testing. Experience validating embedded web components and their interactions with host applications, ideally using browser-automation tools such as Playwright.
- Cloud-native performance analysis. Experience combining load-testing results with metrics, logs, and traces from Kubernetes-based systems to isolate application, database, or messaging bottlenecks.
- Workflow or financial-software experience. Experience testing systems involving approval routing, delegation, permissions, auditable state transitions, or financial data.
- Experience in AI development and/or experience in using AI tools to improve development processes.
- Money Forward is at a major turning point, shifting “from Cloud to AI.” We are currently driving “AX (AI Transformation)”—the next step beyond DX—with the goal of providing “Digital Workers,” where AI agents autonomously execute tasks. As we enter a phase of evolving into Japan’s No. 1 back-office AI company by integrating AI agents into all of our products in the future, we are looking for individuals who can contribute to AI-driven development and value creation.
- The ability to collaborate with Japanese-speaking colleagues or read Japanese product documentation is helpful, but Japanese is not required for this role.
Compensation
¥10,008,000 ~ ¥15,000,000 annually.
