Resignation
Resigning smoothly in Japan: the order, the timing, and the counteroffer trap
Who to tell first, how much notice the rules actually require, how to handle retention offers, and the handover that protects your reputation.
What you can use right away
- Your direct manager hears it first, in person, framed as a report — not a consultation.
- Check the notice period in your company's work rules before you schedule anything.
- Decide about counteroffers before they arrive: would more money actually fix your reason for leaving?
The order of communication is half of "smooth"
The first person to hear about your resignation must be your direct manager, face to face (or on a call if remote), in a private meeting you request without explaining the agenda. If a colleague, a peer manager, or — worst — your manager's boss hears it first through leakage, you have created the friction you were trying to avoid. Do not tell teammates, even trusted ones, before the formal conversation.
Frame matters as much as order: open with a report, not a consultation. "I have decided to resign, and I would like to discuss the timing" leaves room for scheduling but not for reversal. "I'm thinking about leaving" invites a retention process you have already decided against.
Timing: the work rules, the law, and the project calendar
Japanese civil law allows resignation with two weeks' notice, but most company work rules (shugyo kisoku) specify one to two months, and following the work rules is what keeps things smooth. Check the exact clause before your conversation, and remember the notice period starts when you formally tell your manager — not when you decided privately.
Within that constraint, sequence around reality: a project milestone, a release, the end of an evaluation period. You cannot wait for a perfect moment — there isn't one — but avoiding a resignation announcement two days before your team's biggest launch is basic professional judgment. Set your final office day and your joining date with a small buffer; a one- or two-week gap absorbs handover overruns and paperwork.
Try this checklist
- Read the resignation clause in your work rules and note the required notice period.
- Book a private meeting with your direct manager before telling anyone else.
- Build a backwards schedule from your target final day: announcement, handover, leave consumption.
The counteroffer: decide before it arrives
Expect retention attempts — a raise, a promised transfer, an appeal to loyalty. Decide your answer before the conversation, because the question to ask is not "is the counteroffer good?" but "does it fix the reason I decided to leave?" A salary bump does not change the technology you work with, the ceiling you hit, or the culture you are tired of. Industry experience is consistent: most people who accept counteroffers resume their job search within a year, now with a flagged reputation internally.
This is also why your stated reason for leaving should be something the company cannot fix — a direction change, a domain you want, a scale of challenge — rather than salary or workload, which invite exactly the counteroffer you must then argue against.
The handover is your last impression — and paid leave is part of the plan
Handover quality is what former colleagues remember, and Japanese professional networks are long-memoried. Build a handover document even if no successor is named: system knowledge, running tasks, contacts, credentials locations, the traps only you know. A good handover file protects your reputation better than a farewell speech.
Remaining paid leave is a legal right, and consuming it before your final day is standard practice — but plan it into the schedule you present rather than announcing it late. On the paperwork side, confirm you will receive your rishoku-hyo (separation notice) and gensen-choshu-hyo (withholding slip), and settle corporate DC pension and insurance transitions before your last day, not after.
Capture your work before you lose access
The day you leave, you lose the wiki, the dashboards, the repos — everything you would need to reconstruct what you achieved. The numbers that make your next shokumukeirekisho strong (latency improvements, incident reductions, project scale) live in systems you are about to be locked out of.
Before your final day, record your projects' outcomes in InterviewTrail AI's Career Memory — scale, role, stack, measurable results. Your next job change starts from an organized record instead of fading memory.