14 Engineering Manager Candidates in Tokyo — the 7 Steps That Ended a 5-Month Search

Engineering manager is the role Tokyo teams get wrong most expensively, and the reason is rarely the candidate market. It is that the title covers at least three different jobs, and the people hiring frequently want different ones without discovering the disagreement until someone is three months into the role. This is the method we use now, after a search that took five months and should have taken nine weeks.

Step 1 — Write down which of the three manager jobs you are hiring

The people manager owns growth, performance, retention and conflict. Their week is one-to-ones, feedback, career conversations and the difficult discussions nobody else will have.

The delivery manager owns predictability. Their week is dependencies, scope negotiation, unblocking and communicating honestly upward when a date will not hold.

The technical direction manager owns architecture and standards. Their week is design review, technical arbitration and saying no to appealing but wrong approaches.

Strong candidates usually do two of the three well. Almost nobody does all three at a high level, and a job description implying otherwise attracts people who will disappoint two of your three stakeholders. Our failed search had a CTO who wanted technical direction, a VP who wanted delivery, and a team that badly needed people management. Nobody said this aloud until candidate eleven.

Rank the three, in writing, with all decision-makers in the room. If you cannot agree on the ranking, you have discovered your actual problem and it is not a recruiting problem.

Step 2 — Source across three distinct Tokyo pools

The Tokyo engineering management market is not one pool but three, and messaging that works for one repels the others.

Bilingual Japanese managers are the smallest and most contested group, particularly those with experience in foreign-capital companies. They are typically not browsing job boards and respond to specific, respectful approaches about scope rather than to compensation-led outreach.

Foreign residents already in Japan are the most underused pool. They already hold a visa, already understand the working context, and are frequently under-levelled relative to what they did before arriving. This group produced our eventual hire.

Relocating candidates bring the widest experience and the longest timeline — add three to five months and budget for the visa process. The Highly Skilled Professional route is worth understanding properly before you promise anything, and we set out the mechanics in our guide to sponsoring the Highly Skilled Professional visa.

Step 3 — Screen for judgement, not for headcount managed

« How many engineers have you managed » is the least informative question in this process. Someone who managed twenty people through a stable year learned less than someone who managed four through a reorganisation.

« Tell me about someone you managed who was underperforming. What did you do, and how did it end? » Listen for whether they took responsibility for the diagnosis. Managers who describe underperformance as purely the individual's failing tend to produce the same outcome repeatedly.

« Describe a decision you disagreed with and had to implement. » The answer reveals how they handle the gap between their judgement and their mandate, which is most of the job in a mid-sized organisation.

« What did you stop doing when you became a manager? » Candidates who cannot answer usually have not made the transition. They are senior engineers with a management title, which is a real and valuable thing but a different hire.

Step 4 — Replace the extra interview round with a written scenario

This is the highest-value change we made. Send a one-page scenario in advance and ask for a written response of no more than a page:

« Two engineers on your team of six disagree about a database choice. The disagreement has been running for three weeks and has begun affecting other people's work. One of them is your strongest engineer. The delivery date is in five weeks. Write what you would do in your first week. »

The responses separated our fourteen candidates more sharply than any live round. Some solved the technical question — wrong instinct, that is not the manager's job here. Some escalated immediately — also wrong, it hands the problem upward. The strongest responses addressed the process failure that let a three-week disagreement continue unmanaged, and did so without humiliating either engineer.

Written form matters. A manager's work in a distributed or partly asynchronous organisation is substantially written, and a candidate who cannot structure one clear page of reasoning will not suddenly do it in a performance review.

Step 5 — Reference the direct report, not only the boss

Former managers describe outcomes. Former direct reports describe behaviour, and behaviour is what you are buying.

Ask a fixed set: « How did you find out you were doing badly at something? », « What did they do when you disagreed with them? », « Would you work for them again, and what would have to be different? »

That final clause is the important one. « Yes, absolutely » with no qualification usually means the reference has not thought hard. A considered answer with one honest caveat is a far stronger signal. Two of our fourteen candidates did not survive this step, and in both cases the pattern was the same: excellent upward management, thin support downward.

Step 6 — Fix compensation, title and visa before the offer conversation

On language, decide honestly. If the engineering team works in English but the manager must negotiate with Japanese-speaking sales, legal or executive stakeholders, business-level Japanese is a genuine requirement and the pool contracts accordingly. If the manager mainly interfaces with an English-operating organisation, requiring Japanese excludes strong candidates for no operational benefit. Write down which specific meetings require it before making it a line in the posting.

If equity forms part of the package, the mechanics are not a detail in Japan — two nominally similar grants can differ substantially after tax, as we set out in the guide to tax-qualified stock options. Regional context is worth holding too: Singapore and Dubai are bidding for the same engineering leaders, tracked by our colleagues at HireDeveloper.sg and HireDeveloper.ae.

Step 7 — Structure the first 90 days as listen, diagnose, then change

The most common way a good engineering manager fails in Tokyo is arriving with a playbook from a previous company and applying it in week two. It reads as competence to the person doing it and as disregard to everyone else.

Days 1–30: listen only. One-to-ones with everyone, attend everything, change nothing structural. The single exception is anything actively harming people.

Day 30: a written diagnosis. Two pages to their manager: what is working, what is not, what they propose to change and in what order. This document is also your first real assessment of the hire.

Days 31–90: one change at a time. Sequentially, with the reason stated to the team each time. Three changes at once cannot be attributed, and if things get worse nobody knows which one to reverse.

The search that produced this method took five months and fourteen candidates. Rebuilt around these seven steps, the two subsequent searches closed in about nine weeks each. The difference was almost entirely step one.

FAQ