Japan Has No Job Description. That’s the Job.

Nobody told me where my job ended.

Nobody could.

Japanese people are often described as having a strong sense of responsibility. That’s true. I’ve seen it. I’ve lived it.

And yet — those same people will stay silent in meetings, avoid making decisions, and find every possible way to not be the one who takes ownership of an outcome.

That’s not a contradiction. Once you understand the structure underneath, it makes complete sense.

In many Japanese companies, your job description doesn’t exist in the way foreigners expect.

In most Western countries, you are hired for a specific role. Before you start, there’s a document — a job description — that defines what you do, what you’re responsible for, and where your accountability ends. It’s not perfect, but it exists. It gives you a boundary.

In many traditional Japanese companies, especially for general-track employees, you are hired into a company. Not a role — a company. You join as 総合職 (sōgōshoku) — a general-track employee — and what you actually do is figured out after you arrive. Through observation. Through being assigned tasks. Through watching what the person before you did and doing roughly the same.

I know this because I lived it. When I started working, I didn’t know where my job ended. So I asked someone senior to me. They told me what they had done in that role. That was it. That was the answer. Not a definition — a personal history.

Everyone around me was in the same situation. Nobody had been told. Nobody could tell me, because nobody had been told either.

What happens when the boundary doesn’t exist

In Japan, there’s a saying that gets laughed at, grimly, by people who’ve been in the workforce long enough: 仕事は人につく — the work belongs to the person, not the role.

Many foreign workers recognize pieces of this — scope creep, role ambiguity, institutional knowledge — but the Japanese phrase captures it more cleanly. In their systems, work belongs to a position. When someone leaves, the position gets refilled. The work stays where it was. In Japan, it follows the person — or lands on whoever is nearby.

And there’s a particular cruelty in how this plays out. The most capable people, and the ones least able to say no, accumulate work at a rate that has nothing to do with their official role. The reward for competence or generosity is not a raise. It’s more work. The salary stays flat. The overtime climbs. The system extracts from whoever lets it.

This isn’t accidental. It’s what happens when there’s no grand design underneath. No system that says: this role exists, these are its boundaries, this is who owns it when the person changes. Just people filling gaps because gaps exist, and because no one ever drew the map.

When your responsibilities aren’t defined, several things follow.

You never know when you’re done. There’s no line to cross that means “finished.” So work expands. Hours extend. Residual tasks pile up and attach themselves to whoever is nearby, because there’s no documented reason why they shouldn’t.

When someone takes a day off, the work doesn’t stop — it moves. To someone else. And because nobody’s responsibilities are clearly defined, that someone can’t say “that’s not my job,” because technically, nothing is or isn’t anyone’s job in particular. Taking time off means imposing on colleagues. The guilt is real, and the structure created it.

When a problem arises, accountability is murky. Who owns this? Whoever spoke up about it. Which is why speaking up carries risk.

This is also one reason decisions take so long in Japanese companies. When authority is unclear, decisions do not simply move forward. They move upward, sideways, and through people who can safely share the responsibility.

This is described as a strength. It isn’t.

You’ll find articles — written by consultants, academics, business writers — that describe Japan’s lack of job descriptions as a form of organizational flexibility. “Amoeba-like adaptability,” one article called it. The idea that Japanese employees will do whatever needs doing, regardless of title or task, is held up as a virtue.

That framing ignores the people doing the work.

The flexibility is real. The cost of that flexibility — in hours, in ambiguity, in the quiet erosion of personal boundaries — is carried by individual workers. It doesn’t show up in the business case for “Japanese organizational agility.” It shows up in overtime statistics, in burnout, and in the silence of people who have learned not to raise their hand.

So why doesn’t anyone take responsibility?

Because responsibility without defined limits is terrifying.

If you speak up in a meeting and attach yourself to a position, you now own the consequences of that position — whatever they turn out to be. In a system where nobody knows exactly where their job ends, those consequences could be vast. You might find yourself responsible for outcomes three layers removed from what you originally said.

Silence is rational. It’s not laziness. It’s not a lack of care. It’s the logical response to a system that never told you how much you could lose by speaking.

Japanese people have a strong sense of responsibility precisely because of this. The weight of it is felt acutely. That’s why they avoid adding to it unnecessarily.

And that is why logic does not always win in Japanese companies. A proposal can be correct and still fail if nobody wants to become the person who owns what happens next.

Is anything changing?

At the large-company level, yes — formally. Hitachi, Fujitsu, KDDI and others have introduced job-type employment systems with written job descriptions. The Japanese government released official guidelines in 2024 encouraging the shift.

But many companies adopting job-type language are still struggling to make the reality match the announcement. The paper exists. The culture hasn’t caught up.

And there’s something subtler that doesn’t change just because a document gets written. Japan has a way of making “no” feel impossible. Not through force — through atmosphere. You arrive with boundaries. The longer you’re in the system, the harder those boundaries become to hold. Requests accumulate. Precedents form. One exception becomes the expectation.

That’s the real risk. Not that no one will write down your job description — but that even if they do, the air in the room will make it very difficult to use it.

What can you actually do?

This is a structural problem. No individual can solve it alone. But there are things worth doing.

Ask for a job description. At hire, at every role change, ask what the expectations are in writing. It may feel awkward. You may be the only one asking. Ask anyway.

Do that job well. Then, as much as you’re able, hold the line — not by refusing outright, but by making the cost visible. In Japan, the most effective boundary isn’t “that’s not my job.” It’s “if I take this on, I won’t be able to deliver on A and B, and that creates meiwaku for the team.” Use the system’s own logic. Frame the boundary as protecting the group, not defending yourself.

And know that every person who holds the line makes it slightly easier for the next one. The structure changes when the behavior changes. It won’t happen quickly. But it starts somewhere.

Nobody told me where my job ended when I started. Nobody could. But I figured out, eventually, that asking the question — even when nobody had an answer — was still worth doing.

All of the above is one Japanese person’s interpretation. Treat it accordingly.