How to Give Two Weeks Notice at a Tech Job — the actual sequence.

Most guides to quitting a job were written for a world where you'd stay at a company for eight years and never see anyone from it again. Tech is a smaller room than that. The person you resign to today runs the hiring loop you're in next year. The peer who inherits your on-call rotation this month writes the back-channel reference in your Series C due diligence. The way you exit is the way you'll be remembered — not just by your manager, but by the roughly one hundred people who will hear the story of your last two weeks in a Slack thread that Sunday.

None of this is a reason to stay somewhere you shouldn't stay. It's a reason to leave well. Below is the sequence — from before the resignation letter to after the last day — that engineers, PMs, designers, and managers use to quit cleanly without leaving equity, references, or dignity on the table.

Before You Give Notice: The Three Checks

Do not give notice until you have finished the three checks below. Skipping any of them is how good exits go sideways.

You'd be shocked how many people skip these three checks and lose real money. The single most common mistake is timing the last day one day before a quarterly vest. It's almost always accidental — someone picked a Friday because it "felt right" — and it's almost always avoidable.

The Timing: Monday or Tuesday, in the Morning

The best day to give notice is Monday morning. The second best is Tuesday morning. The worst is Friday afternoon. This is not superstition — it is your manager's calendar. Monday gives them the rest of the week to talk to HR, plan the transition, and figure out backfill. Friday gives them the weekend to stew, which turns useful energy into resentment. Time-of-day matters too: give notice early in the day, before your manager is deep in another problem. You want their attention, and you want them to have runway to react.

Avoid giving notice on the day of a launch, the day of a board meeting, the day of a big customer meeting, or the first day of a quarter. It's not that you owe the company perfect timing — it's that giving notice on those days creates real logistical damage that becomes part of the story people tell about your exit. You lose almost nothing by moving it forward or back one day. You gain a permanently better reference.

Also: do not give notice on your birthday, the day of a team offsite, or the day after your one-on-one where your manager just gave you a promotion. Yes, all three of these have happened to people we know. All three are memorable in the wrong way.

The Conversation: Fifteen Minutes, In Person or on Video

The resignation conversation should be short, direct, and calm. Book fifteen minutes with your manager for that morning. Use the calendar title "Quick chat" — not "Personal matter," not "Career discussion." You do not want them googling "what does a Quick chat calendar invite from a report mean" all weekend.

When the meeting starts, open with the news in the first sentence. Do not build up. Do not soften. Do not spend three minutes talking about your quarter before dropping the resignation. Say it clearly:

That's the whole opening. Then stop talking and let them respond. Most managers are professional enough to be gracious in the first thirty seconds — even if they're surprised or upset. Some will ask why. A short, positive framing works best: "I've been thinking about the next step in my career and this opportunity came along that matched. It was a hard call because I've learned a lot here." That is enough. Do not name the new company unless directly asked, and even then, keep it brief. Do not compare compensation. Do not enumerate grievances. Anything you say in that first conversation can end up in an internal HR note within the hour, and the details rarely help you.

If your manager asks what they could have done differently, you can be honest — but be selective. Focus on one or two things that are structural (scope, team direction, product bet) rather than personal (their behavior, a specific peer). Their next question will be about your remaining two weeks, which is a much easier conversation to have well.

The Resignation Email: Two Lines, After the Meeting

Send the written resignation email within an hour of the conversation, cc'ing HR. Its only purpose is a paper trail. It should not be emotional, retrospective, or long. Two lines is enough.

Do not include the reason for leaving. Do not include the name of the new company. Do not include a paragraph about how grateful you are — save that for a Slack post or a personal note on your last day, where it will land better and won't be forwarded to legal. This email is a document, not a valediction.

The Counter-Offer: Almost Always No

Within twenty-four hours, there is a real chance your manager will come back with a counter-offer. Sometimes it's a raise, sometimes it's a title, sometimes it's a promise of a different scope, sometimes it's all three. The counter-offer will feel flattering. It will feel like validation. It is almost always the wrong move to accept it.

The research on counter-offers has been remarkably consistent for decades: a large majority of people who accept a counter-offer leave the company within a year anyway, usually voluntarily. The reasons for that are pretty simple. If money was the only thing that made you willing to leave, you should have asked for it before you had a new offer, and now you have taught your manager that resignation letters are how you negotiate. If money was not the only thing — if it was scope, boredom, manager fit, product direction, values — then a raise doesn't fix the actual problem, and six months from now you're in the same room having the same conversation.

There is also a subtler dynamic. The moment you accept a counter-offer, you have signaled that you were willing to leave. That signal doesn't unring. Even a good manager, without meaning to, will factor it into next year's promotion decision, next quarter's key project assignment, and next month's stretch investment. Trust is not lost — it's discounted.

The clean move: thank them, take the raise as evidence you were underpaid, and go. If you genuinely believe the counter-offer represents a real change — a new manager, a real product bet, a scope that finally matches what you wanted — sleep on it for a night before accepting. But default to no.

The Two Weeks: Build the Best Handoff of Your Career

Once notice is given, the game becomes reputation. You have two weeks to leave behind a handoff so clean that your teammates remember you as the person who cared enough to do it right. This is not corporate politeness — it is the single most durable thing you can do for your career. The story your teammates tell about your last two weeks is the story your reference will tell for the next ten years.

The core deliverables of a great two-week handoff:

• A running handoff doc. One document that lists every project you own, its current state, next steps, key stakeholders, and where the code / spec / assets live. Update it every day, share it with your manager on day one of notice, and treat it as the source of truth.
• Ownership transfers, on paper. Every project, on-call rotation, JIRA queue, and customer relationship gets a new named owner before your last day. Send a short email to each affected stakeholder introducing the new owner. Do not leave "the team" as the owner of anything — orphaned work rots.
• Recorded walkthroughs. For anything gnarly — a legacy service, an unusual customer setup, a fragile deploy path — record a short Loom walkthrough. Ten minutes of video saves your successor ten hours of confusion, and future you gets remembered as thoughtful.
• A calendar audit. Go through every recurring meeting on your calendar. Cancel the ones that were only useful because of you. Reassign the ones that need to keep happening. This is one of the highest-signal moves in a good handoff and almost nobody does it.
• A short list of "watch-outs." Things you know about the codebase, the team, the customer, or the roadmap that aren't documented anywhere. This is the memo your successor will thank you for six months later — and the memo your manager will remember when they're asked for a reference.

Do not use the two weeks to coast, litigate old grievances, or try to influence decisions you won't be around for. Coasting reads to your peers as validation that they should coast too. Litigating old grievances turns a graceful exit into a messy one. And weighing in on decisions after you're already leaving usually just tells the room you never really left the ego at the door.

Also: do not, under any circumstances, take company data with you. Do not fork the repo. Do not copy the Notion workspace. Do not export the customer list. The moral case is obvious; the practical case is that this is one of the fastest ways to get a phone call from a lawyer six months into your next job.

The Last Day: Say Thank You, Then Go

On your last day, send one short Slack message to the team channels you care about. Keep it under six sentences. Say what you learned, thank a few specific people, share a personal email or LinkedIn where you can be reached, and wish them well on the next chapter. That's it. No manifestos. No last-day roasts of the exec team. No "I want to be honest about why I'm leaving" posts. Those posts read like personal courage in the moment and read like something else entirely on Monday.

Then hand back the laptop, revoke your own SSO access if it's still active, delete the personal photos out of Slack DMs, and go. Take a week off between jobs if you can afford it. The new job will be there.

The Common Failure Patterns

The way most tech resignations go wrong is not dramatic. It's small, avoidable, and repeated:

• Resigning on a verbal offer. The single most damaging mistake. Wait for the countersigned letter.
• Telling one peer before your manager. The peer tells someone. That someone Slacks someone. Your manager hears it from HR. Every future conversation with that manager, forever, will carry the memory of finding out that way.
• Giving notice by Slack. Even in fully remote companies, this is read as disrespect. If you can't be in the same room, be on the same video call.
• Naming the new company unprompted. If the new company is a competitor or a customer, this creates political complications you did not sign up to manage. Say it only if asked, and even then, keep it simple.
• Trashing anyone in the exit interview. Exit interview feedback is confidential in exactly the way company all-hands are confidential. It gets around.
• Working past your last day out of guilt. Do not do a week of "just a few emails" from the beach. It signals you have no boundaries and it teaches your former manager that resignation dates are negotiable.
• Ghosting the handoff. Skipping the handoff doc costs you the reference forever. Two weeks of good work is a genuinely low price for a decade of "yeah, they were great, I'd hire them again."

What About Longer Notice?

If you are a senior IC on a critical rotation, a tech lead, an eng manager with reports, or a founder-level exec, two weeks is often not enough. Three to four weeks is more graceful, better for your reference, and usually better for you — because the two weeks after resignation are always harder than the previous six months of thinking about it. Offering four weeks and letting your manager pick the actual date is a strong move: it signals seriousness, it's a real gift to the team, and it almost never costs you the new start date, because most new companies will happily flex an extra week or two if the reason is a graceful handoff at your current one.

The one place longer notice can backfire is at companies where handing in notice triggers an immediate walk-out. Some finance-adjacent tech companies, and a handful of paranoid startups, will escort you to the door the day you resign. If that's a real risk at your company, don't offer more than two weeks — you'll lose the paycheck and the equity clock will start ticking. Ask a former colleague who has resigned recently what the norm is, quietly, before you commit to a date.

The Bottom Line

Two weeks notice at a tech job is a small window with an outsized shadow. Two weeks of good work — clean handoffs, a short calm resignation letter, no counter-offer drama, no all-hands manifesto on the way out — buys you a reference that will still be paying dividends when the company you're joining next month has been acquired, renamed, and half its founders have moved on to their next thing. The room is small. The stakes are long. Leave well.

The rest — the new role, the new team, the next culture question — starts the Monday after next. If you're not sure the next company is actually the right fit, spend an afternoon reading a few culture profiles before your first day. Better to find out what you're walking into now than after your first sprint.