Two weeks notice is a courtesy, not a law. In every at-will U.S. state you can quit at any time — but skipping it costs you the rehire-eligibility checkbox, the warm reference, and the goodwill of every colleague who has to absorb your unfinished work.
The clean version: meeting with your manager (Friday afternoon, in person or on video), short scripted opening, brief reason, firm last day, immediate written letter to manager & HR, then two weeks of genuinely solid handoff work. No sub-tweets, no rage-quitting in the all-hands Slack, no "well, since I'm leaving anyway…" pyrotechnics.
Most people don't write a polished resignation script until the morning they need one. By then the adrenaline is already running, and the version that comes out of your mouth is shorter, more apologetic, and more rambling than the one you wrote in the shower. This is the page to read the week before — when the new offer is signed but the conversation hasn't happened yet.
What follows is the playbook used by most people I've watched do this well: the timing, the meeting opener, the email template, the handoff plan, the exit interview, and the nine mistakes that show up over and over in company reviews and after-the-fact career regrets.
1. Confirm everything before you tell anyone
Before you walk into the resignation meeting, the new offer should be signed, dated, and acknowledged by the new company's HR system. Not "verbally agreed." Not "they emailed me a PDF and I emailed back yes." Counter-signed, in writing, with a confirmed start date and a written offer letter that names your title, base salary, equity, and start date.
This sounds paranoid until you've watched someone resign on Monday, find out the new role got rescinded on Wednesday during a hiring freeze, and have to sheepishly walk back into their old manager's office. Rescinded offers happen — particularly in macro climates like the one the past two years have produced. Don't be the cautionary tale.
Other things to confirm before the conversation:
- Your start date is real. Background-check delays, visa transfers, and onboarding cohorts can all push it. Get a confirmed date in writing, not "within 2-3 weeks."
- Your old role's notice clause. Re-read your employment contract. Some senior or sensitive-role contracts have 4-week, 30-day, or 90-day notice. Garden-leave clauses exist. Non-competes still bind even after you give notice in some states.
- Your PTO balance and payout policy. States differ on whether unused PTO must be paid out. Look up your state law and your company policy — and screenshot the policy before HR knows you're leaving.
- Your equity vesting cliffs. If you're 12 days from a vesting milestone, the date you set as your last day can be worth thousands. Some companies will accelerate; most won't.
- Personal files. Quietly export your achievements doc, your performance review notes, and any references list off corporate systems. Once you give notice, IT access can disappear within the hour in security-sensitive companies.
2. Pick the right day and the right meeting
Most career coaches, and most managers I've talked to, agree on Friday afternoon. Tell your manager around 3pm or 4pm in a private 1:1 or impromptu meeting. That gives them the weekend to absorb the news before they have to plan coverage, talk to HR, or rewrite next week's roadmap. It also lets you walk out of the building (or close your laptop) without the rest of the day descending into watercooler conversation.
Mondays are the worst day. You set the tone for their entire week. Tuesdays through Thursdays are workable. Avoid the day before a major release, a board meeting, a customer launch, or a teammate's milestone. Even if you don't think your news is a big deal, the timing telegraphs whether you respect the people you're leaving behind.
For the meeting itself: request 15 minutes on your manager's calendar with a vague title — "quick chat" or "1:1 update" works. Don't write "resignation" in the calendar event. They'll see it before you talk and you'll lose the conversational moment. If you're remote, video on. Audio-only is a tell that something is wrong.
3. The exact words to say
Most resignation conversations go off the rails because the resigning person tries to explain too much. The script is short, complete, and rehearsed. Here's the one I'd memorize:
"Hey — thanks for the time. I wanted to let you know in person before anything else: I've accepted a new role and I'm giving my two weeks notice. My last day will be Friday, July 4th."
"This wasn't an easy decision. I've learned a lot here and I appreciate everything you've done for my career. I want to make the next two weeks as smooth as possible — I'd like to spend tomorrow putting together a handoff plan and walking you through it on Monday."
"I'm not looking to be counter-offered, and I'd rather not get into specifics on the new role until I've gotten settled there. I'm happy to answer any questions you have about timeline, projects, or how I can help with the transition."
That's the whole script. Three short paragraphs. Notice what isn't in it: no extended justification of why you're leaving, no apology for "abandoning" anyone, no negotiation hooks, no detail on the new company. Don't bring grievances into this meeting. If you want to surface systemic feedback, that's the exit interview — a different room, a different audience.
If your manager pushes for more — "where are you going?" "what's the comp?" "why didn't you tell me?" — you can deflect politely:
- Going where: "I'd rather not share the specific company yet — I'll loop you in once I've started there."
- Why now: "It came together faster than I expected. I want to focus this week on the handoff."
- Why didn't you tell me you were looking: "I wasn't actively looking — this was a one-off opportunity I felt I had to explore." (Only say this if true.)
- Can we counter-offer: "I really appreciate that, but I've already made the commitment. I want to honor it."
4. The written resignation letter
Send the written letter to your manager (and CC HR) within an hour of the verbal conversation. Same day is non-negotiable — your manager needs the paper trail to start the offboarding process, and you don't want HR hearing about your resignation from anyone but you.
Keep it short. Three or four sentences. The point of the letter is the date, not the prose.
Subject: Resignation — [Your Full Name]
To: [Manager's name] CC: [HR contact]
Hi [Manager],
This email confirms our conversation today. I'm resigning from my role as [Title] at [Company], with my last day being [Date — two weeks from today].
I'm grateful for the opportunities I've had here and for the people I've worked with. I'll spend the next two weeks documenting my projects, transferring ownership, and supporting whoever picks up my work. I'll send a draft handoff plan tomorrow.
Thank you,
[Your name]
That's the letter. No paragraph about what you learned, no list of grievances, no announcement of where you're going. The letter is going into a personnel file. Keep it bland.
5. Work the last two weeks like you actually care
This is the part most people quietly fail at. The temptation is real: you're already mentally checked out, you've stopped getting roadmap-load, your one-on-ones turn into chatty wind-downs, and a couple of "this isn't my problem anymore" thoughts cross your mind.
Resist it. The way you work the last two weeks is the way people remember you. The pattern that shows up in references, in alumni networks, and in company culture is almost never the great quarter you had in year two — it's whether you ended well or ended messy.
What a strong handoff looks like:
- Day 1-2: Write a single handoff doc. List your active projects, who they should go to, the current state, the blockers, and the next two decisions someone will need to make. Link to docs, dashboards, Slack channels, and any private Notion pages.
- Day 3-4: 30-minute walkthrough meetings with whoever inherits each project. Record them. Drop the recordings into the handoff doc.
- Day 5-7: Document the non-obvious things. The vendor contact who only responds to your email address. The Jenkins job that only you know how to restart. The PagerDuty escalation policy that has your number hardcoded. The Stripe webhook your team's never figured out how to debug.
- Day 8-10: Pair with your replacement(s). Let them drive while you watch. Answer questions. Take notes on what they don't know yet.
- Day 11-14: Buffer time. There's always one more thing. Use the last few days to close out loops, write LinkedIn recommendations for people who've earned them, and have closing 1:1s with anyone you've worked closely with.
A good handoff is the single highest-leverage thing you do for your reputation in the industry. The teammates who watched you leave well will remember it for years. They'll refer you to roles, write you references unprompted, and the manager will mark "eligible for rehire: yes" on the form they fill out the day you leave.
6. The exit interview: be honest, be vague about people
Most companies will schedule a 30-minute exit interview with HR (sometimes with your skip-level too). It's framed as a chance for the company to learn from your departure. Some of that is true. Most of it is process. Here's how to play it.
Talk about systems, not people. "The on-call rotation was unsustainable for the engineering team" is feedback HR can act on. "Sarah from the SRE team is impossible to work with" is gossip that will get back to Sarah. The first will go into a quarterly retention report. The second will burn a bridge you didn't mean to burn.
Be honest about what made you leave. If it was comp, say comp. If it was a missed promotion, say promotion. If it was your manager, frame it structurally — "I never had clarity on what would get me to the next level," not "my manager played favorites." HR has heard worse. They're not going to be shocked. They are, however, going to remember if you handled the exit gracefully or vindictively.
Decline questions you don't want to answer. "Where are you going?" "What's the comp?" "Who else is unhappy?" All fair to deflect with "I'd rather not get into specifics" or "I don't think that's mine to share." HR doesn't need to know.
If you wouldn't say it in front of the person it's about, don't say it in the exit interview. Tech is small. People move companies. The senior engineer you torched in 2026 is going to be your skip-level somewhere else by 2028. Career half-lives are real.
7. The nine mistakes that quietly burn bridges
Most people don't blow up an exit. They paper-cut it with small unforced errors. Here are the most common ones I see:
- Telling teammates before you tell your manager. Slack travels faster than you do. Your manager finding out from someone else is the single fastest way to lose the goodwill you've built.
- Resigning over email, no verbal conversation. Reads as conflict-avoidant and disrespectful. Even on remote teams, the meeting comes first.
- Sending a long, emotional resignation letter. Three or four sentences. Date, gratitude, handoff commitment. The letter is a record, not a manifesto.
- Accepting the counter-offer. Studies repeatedly show people who accept counter-offers leave within 6-12 months anyway, often on worse terms. The trust has already been signaled to be conditional.
- Trash-talking the company on your way out. Even if it's true. Even if you're right. People mostly remember the tone you left with, not the specific complaints.
- Posting about it publicly before you've left. LinkedIn announcement, Twitter "I'm so excited for what's next," celebratory Instagram — all wait until the last day. Until your last day, you still represent your current company.
- Half-doing the handoff. A bad handoff is the single most common reason a "good leaver" gets logged as a "frustrating leaver" in the back-channels. Spend the time.
- Burning the references. The senior engineers you worked with — even the difficult ones — are your most likely references for the next 5-10 years. Send the warm follow-up message. Connect on LinkedIn. Don't let the relationships go cold.
- Forgetting to back up personal artifacts. Performance review notes, achievement records, design docs you've written, screenshots of feedback you've gotten. You'll want all of it for the next promotion. Get it off corporate systems before you give notice.
8. What to do if you can't give two weeks
Sometimes the situation forces a shorter notice — a hostile manager, a workplace that's become unsafe, a new offer with a non-negotiable start date, a health emergency, or a counter-offer process that drags past your patience.
If you have to give less than two weeks, three principles still apply:
- Give something. Three days is better than zero. A weekend is better than a Slack message at midnight.
- Be honest about why. "My new start date isn't movable" is a reason. "Family health emergency requires me to step back immediately" is a reason. Vague hostility is not.
- Offer asynchronous availability. Even if you can't be on payroll, offer to take a 30-minute call from your replacement in 2 weeks if they get stuck. Costs you nothing. Saves the relationship.
If the workplace is abusive, unsafe, or has broken its end of the contract (missed payroll, rescinded promotion, hostile environment), you don't owe two weeks. Document everything, get your personal files, and leave with a one-paragraph email. Save your guilt for someone who's earned it.
9. The thirty days after you leave
The last act of a clean exit is what you do after you've left. Most people skip this and miss the easiest career-capital play available to them.
- Week 1 at new company: send a thank-you note to your old manager. Not "thanks for everything," but specific: a project they advocated for you on, a feedback conversation that stuck, an introduction that mattered.
- Week 2: connect on LinkedIn with the 5-10 closest collaborators you didn't already have. Write a recommendation for two of them.
- Week 4: the LinkedIn "new role" announcement. Tag the new company. Mention what you're excited about. Don't backhand-compliment the old one.
- Month 3: grab coffee (or a video call) with two former teammates. Not networking — just catching up. The relationships that matter at the 5-year mark are the ones you maintained in the first 90 days after they ended.
Two weeks notice isn't really about two weeks. It's about whether you treat your last 14 days as an obligation or an opportunity. The version of you that people remember a year from now is the version that closed every loop, wrote every doc, said thank you to the right people, and walked out without anyone left wondering what just happened.
If you're early in your job search — and you're reading this before you've signed the new offer — that's a healthier moment to be evaluating the next thing. Use the culture quiz to figure out what you actually want this time, browse open roles by culture fit, and read company profiles in the culture directory so you're not making the same mistake at the next stop.
Find the next role worth giving notice for
Browse thousands of open roles filtered by culture values that actually matter — work-life balance, flat hierarchy, remote-friendly, eng-driven. So the next exit conversation can be the last one for a while.
Browse Jobs by Culture → Take the Culture Quiz →