How to Write a Two Weeks Notice Letter (With a Tech-Ready Template)
A two weeks notice letter is a short, formal document that states you are resigning, gives your exact last working day, and offers to help with the transition. That's the whole job of the letter. It follows a verbal conversation with your manager, it is not a substitute for one, and it should not carry the weight of a farewell speech, a list of grievances, or a case for better pay. This guide covers what belongs in the letter, what to cut, how it differs from the resignation conversation itself, and how tech-specific handoff norms (documentation, access, on-call coverage) change what you should mention.
What actually needs to be in a two weeks notice letter?
Four things, in order:
A clear statement that you are resigning. Not "I've been thinking about my future here." Say it directly: "I am writing to formally resign from my position as [title] at [company]."
Your exact last working day. Write the date, not "two weeks from today." A specific date removes ambiguity for payroll, benefits, and whoever is planning the handoff, and it protects you if there's ever a dispute about when notice was given.
A brief, professional tone. One or two sentences of genuine thanks are fine (a mentor, a specific project, a skill you built). You do not need a paragraph of gratitude to make the letter feel complete. Neutral and short reads as more professional than effusive.
An offer to help with the transition. A line saying you're willing to document your work, brief your replacement, or wrap up specific tasks before your last day. You don't need to spell out the full plan here, that conversation happens separately with your manager.
That's it. A two weeks notice letter that runs longer than half a page is usually doing something it doesn't need to do.
What should you leave out of the letter?
Your full reason for leaving. "I am resigning to pursue a new opportunity" or simply no reason at all is standard and sufficient. You don't owe a detailed explanation in a document that becomes part of your permanent personnel file. If you're preparing for the inevitable follow-up question in an exit interview or from a future employer, the reasoning for how much to share there is different, see why are you leaving your current job, answered for interviews for how to frame that conversation without the letter's constraints.
Grievances. Complaints about management, compensation, or team dynamics do not belong in a resignation letter, even if they're accurate and even if you're angry. The letter is a formal record, not the place to settle a score. Say what you need to say in an exit interview, if the company offers one and you want to use it.
Negotiation attempts. If your employer counters with a retention offer after you resign, that's a separate conversation, not something to angle for inside the letter itself. If you're mid-negotiation before you've decided to resign at all, that's a different fork entirely, see should you accept a counter offer in tech before you write anything formal.
Unnecessary detail about the new job. Naming your new employer, your new title, or your new comp isn't required and can create friction, particularly if the new company is a direct competitor. "I've accepted a new role" is enough if you want to mention it at all.
Is the letter the same thing as telling your manager you're quitting?
No, and treating it as a replacement for the conversation is the most common mistake. The letter is a formality that documents a decision that has already been communicated in person (or over video, for remote teams). The sequence that works:
- Tell your manager directly, in a 1:1, before anyone else on the team knows.
- Hand over or send the written letter during or immediately after that conversation.
- Let your manager control the timing of the wider team announcement, unless there's a reason you need to move faster.
Leading with an email or a Slack message instead of a conversation reads as avoidant, and it puts your manager in the position of finding out from a document instead of from you. The letter's job is to create a clean, dated record of what you've already said out loud, not to do the telling for you.
How do tech-specific handoff norms change what you write?
Two weeks is the customary minimum notice period in most of the US tech industry, though it isn't a legal requirement under at-will employment, and the right length can vary by role and company. If you own a production system, you're the only person who fully understands a piece of legacy infrastructure, or you're mid-sprint on something with hard external dependencies, offering three to four weeks (or explicitly flagging the risk in your letter or conversation) is worth considering. It's a courtesy, not an obligation, and most companies will still hold you to a standard two weeks if that's what your contract or handbook specifies.
What tech teams specifically need from a departing engineer, beyond the letter itself, usually includes documentation of systems you own, a list of pending pull requests or in-flight work, and a plan for who inherits on-call rotations or admin access. The Stack Overflow engineering blog frames the core problem well: transferring knowledge is one of the hardest parts of any developer's exit, and the fix is a deliberate transition plan, not an assumption that documentation alone will cover the gap. A short section in your resignation conversation (not the letter) covering what you're handing off, to whom, and by when, makes the actual two weeks far less chaotic for the team you're leaving. If you're job hunting while still employed and want to keep this transition clean from the other side too, job search while employed covers how to manage that without burning your current team's trust.
Access and credentials offboarding (repo permissions, production access, API keys, VPN) is usually IT's responsibility to execute, but it's worth confirming in writing when your access will be revoked, especially if you're expected to keep working through your last day. Companies vary widely here: some cut access immediately at resignation regardless of notice period, particularly for roles with sensitive data or production access, so don't assume your notice period guarantees continued system access for its full length.
Industry perspective
"The practice of giving two weeks' notice when leaving a job is outdated and inefficient, and can be a contentious and expensive problem for companies."
That critique is aimed at the custom itself, not at you for following it. Until a company tells you otherwise, two weeks (written and verbal) is still the professional default, and deviating from it without a clear reason can cost you a reference.
A short two weeks notice letter template
Subject: Resignation - [Your Name]
Dear [Manager's Name],
I am writing to formally resign from my position as [Job Title] at
[Company Name]. My last working day will be [exact date, two weeks
from today or per your notice period].
Thank you for the opportunity to work on [specific project or team];
I've valued [one genuine, specific thing].
I'm glad to help however is useful over the next two weeks, including
documenting my current work and briefing whoever takes over my
responsibilities. Please let me know how you'd like to structure the
handoff.
Best,
[Your Name]
Adjust the date line for your actual notice period, and drop the second paragraph entirely if a single sentence of thanks feels more natural than a full one.
Key takeaways
A resignation letter has four required elements and nothing else
State that you're resigning, give the exact last day, keep the tone brief and professional, and offer to help with the handoff. Anything beyond that (grievances, extended reasoning, negotiation) doesn't belong in the document.
The letter follows the conversation, it doesn't replace it
Tell your manager directly first, in person or on a call, then hand over the written letter. Leading with the document instead of the conversation reads as avoidant and creates unnecessary friction.
Two weeks is customary, not legally required, and can flex for critical handoffs
US at-will employment doesn't mandate any notice period. If you own production systems or critical infrastructure, offering more than two weeks, or flagging the risk clearly, is a reasonable courtesy rather than an obligation.
Tech handoffs need documentation and an access plan beyond the letter itself
Departing engineers should expect to document systems they own, list in-flight work, and confirm who inherits on-call and admin access. This conversation happens separately from the letter, usually with your manager and team.
Access can be cut before your notice period ends
Some companies revoke system access immediately at resignation, particularly for sensitive or production-facing roles. Don't assume your full notice period guarantees continued access, and plan your handoff documentation accordingly.
Frequently asked questions
Do I legally have to give two weeks notice?
No. In the US, employment is generally at-will, and there's no federal or state law requiring a specific notice period unless your contract says otherwise. Two weeks is a professional custom, not a legal obligation, though skipping it without good reason can affect references and rehire eligibility.
Should I email my resignation letter or hand it over in person?
Have the conversation with your manager in person or on a call first, then deliver the letter, either as a printed page, a hand signed document, or an email sent right after you talk. The letter should never be the first time your manager hears the news.
What if my company asks me to leave immediately instead of working out my notice?
This happens more often in roles with sensitive access or in industries where garden leave is common. It's usually not personal, and most companies still pay out the notice period even if they don't want you physically working it. Confirm the pay and benefits timeline in writing if this happens to you.
Do I need to explain why I'm leaving in the letter?
No. "I am resigning to pursue a new opportunity," or no reason at all, is standard and sufficient in the written letter. Save any fuller explanation for the verbal conversation or an exit interview, and only share as much as you're comfortable with there too.
How much notice should a senior engineer give versus a junior one?
There's no fixed rule, but the more critical your ownership of specific systems, the more a longer runway helps your team, and it's often reciprocated with goodwill. Two weeks remains the baseline; three to four weeks is a reasonable offer if you're the sole owner of something hard to hand off quickly.
Ready to make the move?
A clean resignation is just the last step of a job search that already went well. Find your next role, with real salary data and ATS-direct listings, at hire.monster/jobs.