Not an automation role. A digital bank in Tokyo is looking for a senior QA who works inside the Scrum squad: risk-based testing, requirement review, test strategy across levels. JSTQB/ISTQB concepts, working Japanese. Must already live in Japan.

Risk-Based Testing / Requirement & Design Review / Test Strategy (unit/API/integration/E2E) / JSTQB / ISTQB / Scrum / Agile Quality / Jira / Xray

Location requirement

You must already be living in Japan with valid work authorization. We are not sponsoring relocation or visa transfers from overseas for this role. Applications from outside Japan will not be considered.

Context

Our client is building a new digital bank in Tokyo, backed by established players in Japanese finance. The bank has not launched yet: the immediate goal is to go live with a deliberately minimal scope, then hold quality as the product grows. You join the QA function at the moment where the practices are still being set.

The role: quality inside the Scrum team, not test automation

Read this part carefully, because it is what makes this role unusual. Test automation is owned by a separate, dedicated team. What this client needs is a QA engineer who works inside the Scrum squad and catches risk, ambiguity and quality gaps early — during refinement and design, not at the end during a test phase.

The QA manager framed the job around four areas. Nobody is expected to be strong in all four.

1. Risk-based testing — identify the key risks from business impact and likelihood of failure, and prioritise testing accordingly.
2. Requirement and design review — review user stories, acceptance criteria and design documents to surface ambiguity, missing information and gaps before implementation starts.
3. Test strategy and approach — define the right test approach across levels (unit, API, integration, E2E) based on the characteristics and risks of each feature.