Engineer to EM in Japan: What Employers Look For

When a company in Japan hires an engineering manager, the question it most wants answered is whether this person will let go of the work. Technical depth gets you into the interview. The habit that made you the strongest engineer on the team, fixing things yourself because it is faster, is the one the interview is designed to catch.

Why the best engineer is often not the best EM

Promotions reward performance in the current job, and managing is a different job.

The cleanest evidence comes from sales, not engineering. Alan Benson, Danielle Li and Kelly Shue studied sales workers at 214 firms in "Promotions and the Peter Principle," published in the Quarterly Journal of Economics in 2019. According to the National Bureau of Economic Research (NBER) summary, doubling a salesperson's sales raised their chance of promotion by 14.3%. After promotion, the sales of each of their subordinates fell by 7.5%. Firms were promoting on current performance and passing over traits that better predicted who would manage well.

I would not apply those numbers to engineers directly. The mechanism transfers, though. A strong engineer is fast, has high standards and catches details. Carry those habits unchanged into management and the team becomes one expert with a few assistants.

People often call this a personality problem. I think more often nobody told the new manager what the new job is actually testing.

What hiring managers check

EM interviews in Japan are commonly described as clustering around delegation, trade-offs and talking to the business. That is a general pattern, not a survey result.

Delegation. Will you hand over work you could do better yourself? A common question: tell me about the last time you gave someone a task you could have done. How many times did you step in? It is a hard question to fake.

Trade-offs. Can you say what the team will not do? Engineers want to build it right and build all of it. An EM decides every week what gets pushed back, then explains that to the person who asked for it.

Talking to the business. Can you turn a technical problem into a business cost? Saying tech debt is dangerous gets nowhere. Saying "if we leave this, next quarter's feature ships two weeks late and we push a customer release" gets a decision.

In my four-layer model these sit on different layers. Willingness to let go is tied to the Core layer, to what drives a person. Someone driven above all by mastery finds handing off work painful. Grabbing the code back under deadline pressure is a derailer on the Patterns layer. One-on-ones, estimates and writing reviews are equipment, and equipment can be learned.

Employers worry most about the first two layers. Equipment can be trained. A mismatch in Core or Patterns rarely gets fixed by a course.

Do engineering managers in Japan still write code?

Usually, yes. Japanese management roles are mostly player-manager roles.

In its 2023 survey of section managers at listed companies with 300 or more employees, the Sanno University Institute for Management Research collected 809 responses from managers with at least one direct report. In a January 2026 release citing that survey, the institute put the share with no hands-on work of their own at just 5.1%. The survey covers all functions. I see no reason to expect engineering to be the exception.

So Japanese employers often ask how much you plan to code and who covers that code when something breaks. Code too much and you cannot delegate. Code nothing and the team stops trusting your technical calls. There is no correct ratio, but a candidate who has no answer rarely gets to the next round.

There is also the paperwork. EMs in Japanese companies usually write appraisals, sit in calibration meetings and help HR set grades, all in written Japanese. Engineers who are fine in technical meetings sometimes stall here.

Promote from inside or hire from outside?

Both carry a cost. Which one an employer picks depends on which mistake it fears more.

An internal promotion comes with known context. The team trusts the person, and so does the business side. The risk is the Peter Principle itself: the person chosen is usually the strongest current performer, who may not be the strongest leader. In Japan, undoing the appointment is awkward for both face and pay, so a bad call tends to stay in place.

An external hire comes with visible evidence. They have managed a team before, and you can check how it went. The risk moves to context. They may have done well because their old boss gave them room, the team was mature and the pace suited them. Put the same person in a three-person Japan office managed closely from overseas and they may struggle.

So experienced interviewers ask external EM candidates about the setting, not only the results. How did your manager handle you on the team that went best? Have you worked under someone with the opposite style?

For internal candidates, some companies run a trial. The engineer leads a small project with one or two people as a tech lead for three to six months, without the title. If it works, the appointment follows. If it does not, they go back with no loss of face. It is slower, and in a Japanese workplace I think the slowness is worth it.

If you want the move, collect evidence now

Employers look for what you have done, more than for what you say you want.

You can build that record in your current job. Onboarding a new hire. Leading a technology choice and explaining the trade-off to the business side. Turning down a request on behalf of the team and being proven right later. Told as specific events, these carry more weight in an interview than any theory of leadership.

EM is also not the only path up. Some companies run an expert track that reaches the same grades as management. Managers step down for reasons they did not choose more often than people expect, which I wrote about in A third of ex-managers in Japan stepped down unexpectedly. The same trap catches salespeople, as I argued in Don't promote your best salesperson to country manager.

For anyone hiring an EM, a useful first request is a list. What did you hand off, what did you refuse, and what did you keep for yourself. That list says more about a future manager than any line on the resume about the stack.