Offer Decisions
How to decline an offer or withdraw from a process without burning bridges
Declining is normal — ghosting is not. Timing rules, a message structure that works, and how to handle the special case of declining after acceptance.
What you can use right away
- Declining is a normal part of hiring; the only unforgivable move is silence.
- Decide, then tell them the same day — every day you sit on a decided decline costs the company and your reputation.
- Four sentences suffice: thanks, the decision, one honest line of reason, and an apology for their invested time.
Declining is expected — ghosting is remembered
Companies extend more offers than they can have accepted; a polite decline surprises no one and offends no one. What is remembered — and shared, because industries in Japan are smaller than they look — is the candidate who went silent. Recruiters move between companies, interviewers change employers, and the hiring manager you ghost this year may screen your application in three years.
So the rule is simple: every process you enter, you exit explicitly. A two-line withdrawal email costs one minute and keeps every door open.
Timing: same day as the decision, within the deadline at the latest
The moment your decision is actually made, communicate it — the same day. Waiting feels kinder but is the opposite: the company is holding headcount, and other candidates are waiting behind you. If you are still genuinely deciding, that is what deadline extensions are for; ask for one honestly rather than defaulting to silence.
For withdrawing mid-process — after applying but before an offer — the same logic applies, and earlier is better. Withdrawing the day before a final interview because you accepted elsewhere is fine; simply not showing up is the one move that follows you.
The message: four sentences, honest but brief
Email is acceptable for most declines; a call is a considerate upgrade when the process was long or the offer was senior. The structure: thank them for the offer and their time, state the decline clearly and finally, give one honest sentence of reason, and close with an apology for the time they invested. In Japanese business writing this fits standard keigo forms; in English it fits four plain sentences.
The reason should be true but need not be detailed. "I have decided to proceed with another company whose role is closer to the direction I want" is complete. Do not leave the decline ambiguous out of politeness — a message the company reads as "maybe" forces them to follow up and you to decline twice. If an agent sits between you, tell the agent your decision and let them deliver it; that is part of their role, and they will also absorb the company's follow-up questions.
Try this checklist
- Write and save your own decline template: thanks, decision, one-line reason, apology.
- Set yourself a 24-hour rule: decision made means message sent within a day.
- Exit every process explicitly — including the ones that went quiet on you.
The hard case: declining after you accepted
Declining after signing an acceptance (naitei shodaku) is legally possible in Japan — employment freedom is protected, and this is well established — but it is the most damaging version of a decline and should be a last resort, not a negotiation tactic. The company may have closed their search and released other candidates on the strength of your yes.
If it truly cannot be avoided, move fast and take it seriously: contact them immediately, by phone, apologize without excuses, and follow up in writing. Do not disappear into email. And upstream, protect yourself from this situation: never accept an offer as a placeholder while waiting for a preferred company — ask for the deadline extension instead.
Decide from a comparison, not from pressure
Most painful declines trace back to a rushed acceptance: an offer deadline arrived before the comparison was done. The fix is upstream — keep every process's stage visible so you can pace them to land decisions together.
InterviewTrail AI shows all your applications, rounds, and offer conditions in one pipeline, so you can see which processes to accelerate, when to ask for extensions, and make the accept/decline call once, with everything in front of you.