Short answer

Give two weeks if you're an IC, three to four if you're senior or in a critical seat. Tell your manager first, in person or on video — not Slack. Write a three-paragraph resignation letter that names the last day and offers help with the transition. Skip the grievances. Spend your final weeks documenting, training a replacement, and finishing what you can. The way you leave matters more than the way you arrived.

The tech industry is small in the way that matters. The person you ghosted in your last two weeks is the person who quietly tells a recruiter "don't bother" three years from now. The team you abandoned mid-launch is the team your future skip-level used to manage. Reputations in tech don't get rebuilt — they get inherited, copied between Slack groups, and remembered for a long time.

This guide is the resignation playbook for tech workers leaving in 2026, whether you're heading to one of the 118 companies in our culture directory, going independent, or taking a break. The mechanics matter, but the bigger point is this: how you leave is the last thing your colleagues remember about working with you. Make it count.

Step 1: Decide before you talk

The most common mistake people make is having the resignation conversation before they've truly decided. They go in floating a maybe — looking for their manager to either talk them out of it or push them out the door. This is a trap. Once you've started the conversation, you've already changed the dynamic at work. Your manager now knows you have one foot out. Even if you stay, the trust takes months to rebuild, and you'll likely get passed over for the next interesting project.

Before you say a word, decide. Sign the offer. Confirm the start date in writing. Confirm your equity vesting cliff has cleared (or accept that it hasn't). If you're using the resignation as leverage, that's a different conversation entirely — and one we'd argue you should have before putting in notice, not after. If you're comparing offers, finish that comparison first. Don't let the resignation moment force the decision.

Step 2: Pick the right notice period

Two weeks is the floor in US tech. It's still the most common practice for individual contributors, and most employment contracts don't require more. But "two weeks" became the cultural default in a different era, when engineers handed off well-documented systems to teammates with overlapping knowledge. Modern roles often don't work that way — you might be the only person who knows how a service works, or the only PM on a critical workstream.

Here's how to think about it:

Whatever you pick, commit to it in writing. The biggest source of post-resignation friction is a date that "drifts" because no one wrote it down. Put a hard last day in the letter and the calendar. If your next employer wants you earlier, negotiate that before you give notice — most companies are flexible on start dates if asked early, much less so once you've already committed to a date.

Step 3: Tell your manager first, in person

This is the single most important interaction in the entire process. Your manager finds out from you, in person or on video — not from a Slack message, not from HR, not from a calendar invite titled "Quick chat" that they'll spend the morning dreading.

Schedule a 1:1, ideally at the start of their day. Open with a clear sentence:

You

"I want to let you know I'm resigning. My last day will be Friday, June 26. I've accepted a role that's a strong fit for where I want to grow, and I wanted to tell you in person before anything else."

That's it. Don't fill the silence. Don't apologize. Don't list grievances. The shorter and clearer you are, the more in control of the moment you'll feel.

Your manager will likely follow with three reactions, often in this order: surprise, an attempt to understand why, and an early hint at a counter-offer. Prepare for all three.

If they ask why

Give the truthful, neutral version. "It's a role that pushes me into [X area] and I've been thinking about that direction for a while." Or: "It's a chance to work on [problem space] at a stage I haven't done before." If the real reason is something more pointed — a manager you don't trust, a project getting deprioritized, comp that hasn't moved — the resignation conversation is not the place to relitigate it. The exit interview is. Save it for then, and even there, keep the framing about systems and processes, not specific people.

If they hint at a counter-offer

Be ready for this. Many managers will float the idea of a retention offer — sometimes in the first conversation, sometimes in a follow-up over the next 24 hours. Industry analyses (Workplace Trends, Korn Ferry, and others over the past decade) have consistently found that the majority of people who accept counter-offers leave within a year anyway. The underlying reasons that drove the search — scope, manager, trajectory, culture — rarely resolve just because comp moved.

If you're determined to leave, say so cleanly:

You

"I appreciate that, and I want to be straightforward — this isn't a compensation conversation. I've made the decision and I want to spend my remaining time here doing the handoff well."

If you're genuinely open to staying for the right counter, say that — but understand that you've now flagged yourself as a flight risk for the next review cycle. There are companies that handle this well. Most don't.

Step 4: Send the letter

After the conversation with your manager, send a brief written resignation. The letter exists for two reasons: it creates the legal/HR paper trail your employer needs, and it gives you a record you'll want when you negotiate things like equity vesting, accrued PTO payout, or COBRA timing.

The letter is three short paragraphs. Don't write a memoir.

Subject: Resignation — [Your Name] [Manager's Name], I'm writing to formally resign from my position as [Role] at [Company]. My last day will be Friday, June 26, 2026. Thank you for the opportunity to be part of the team. I'm committed to making this transition as smooth as possible — I'll spend the next [N] weeks documenting my projects and supporting any handoff you'd like to set up. Please let me know how you'd like to handle the announcement and what I can do to make this easier. Best, [Your Name]

That's the whole template. If your relationship with the company is positive and you genuinely want to say something warmer, you can add one specific line — "I'm especially grateful for the work we did on [project] and the trust you placed in me on [thing]." Avoid blanket praise; it reads as performative. Avoid grievances entirely; they belong in the exit interview, if anywhere.

Send it to your manager first. CC HR (or your People partner) only after the conversation has happened. Sending the letter to HR before talking to your manager is the kind of mistake people remember.

Step 5: Run a real four-week handoff

If you only do one thing well during this whole process, do this. The handoff is the difference between a clean exit that people quietly respect and a messy one that follows you around. The work isn't glamorous, but it compounds.

Week 1

Inventory and document

Write down everything you own. Services, repositories, dashboards, customer relationships, recurring meetings, projects in flight, on-call rotations, vendor contacts, internal docs you maintain. Put it all in one document. Mark each item as either "needs owner," "needs handoff session," or "can be deprecated." This document alone is worth four weeks of goodwill.

Week 2

Decide owners, schedule handoffs

Work with your manager to assign every item to a teammate. For complex services, schedule 45-minute pairing sessions where you walk someone through how it actually works — what breaks, what to check first when it does, who to ping. Record these. Write follow-up docs immediately after. Don't assume people will remember a Loom from six weeks ago.

Week 3

Finish what you can, hand off what you can't

Pick the in-flight projects you can realistically wrap up by your last day and finish them properly. For everything else, write the handoff doc as if you're being hit by a bus — what's the current state, what's the next decision, what are the open questions, what are the dependencies you were tracking in your head. Make it possible for someone else to pick up where you stopped without a meeting with you.

Week 4

Goodbye, gracefully

Last week is for goodbyes. Coffee chats with people who shaped your time there. A short message to your team that thanks them without melodrama. Make sure your contact info is in the company directory or a Notion page so people can find you later. Return the laptop. Sign whatever HR sends. Don't take what isn't yours — confidential docs, customer lists, internal IP. The temptation to "back up" things is high. Don't.

If you've done weeks 1-3 well, week 4 is mostly social. If you haven't, week 4 is chaos. The investment in the first three is what protects you in the fourth.

Step 6: Mind the legal and money details

A surprising number of people lose money or expose themselves legally by skipping this section. The boring stuff matters.

If you're at a private company with meaningful equity and you're considering exercising, the 90-day window is genuinely the most expensive thing on this list. Don't let it lapse by accident.

Already mid-search?

Browse roles at companies that publish their culture transparently — engineering-driven teams, flat orgs, learning cultures, and more across our directory.

Browse Open Roles → See Culture Directory →

Step 7: The exit interview is not therapy

HR will schedule an exit interview, usually in your final week. Many people treat it as a chance to finally unload — to name the manager who held them back, the product decision they disagreed with, the comp gap that pushed them out. Resist the urge.

The exit interview goes into a file. Anything specific you say about a named person can come back. Anything specific you say about a strategic decision can be relayed. And the value of the catharsis is roughly zero — you're leaving anyway.

What's useful in an exit interview is constructive, systemic, and forward-looking. "Our onboarding for senior hires didn't set expectations clearly, and three of the last four senior engineers who joined struggled in the first quarter for the same reason." That's a critique that helps. "My manager was bad" is not.

If you have nothing constructive to say, say nothing. "It was a good experience and I'm grateful for the time" is a complete and honest answer.

Step 8: Plan the social moves

The handoff covers the work. The social layer covers the relationships, which are what actually carry forward.

Step 9: The week after

You probably have a few days between roles. Don't fill them with work. Decompress. Tech transitions are emotionally draining even when they're net-positive, and starting a new role with residual frustration from the old one is a bad way to make a first impression.

If you're heading into a new role at a culture you can research, do the research. Read your new company's profile in our culture directory, look at the values they emphasize, prep questions for your first 1:1. If you don't know where you're going yet, take longer than a weekend. The market has thousands of roles open right now across learning-focused, flat-hierarchy, and engineering-driven cultures — there's no rush to take the first thing.

The principle behind all of this

The mechanics in this guide — the letter template, the four-week handoff, the 90-day option window — are the tactics. But the principle is simpler: the way you leave is the last thing your colleagues will remember about you. They will forget the launches and the late nights and the Slack debates. They will remember whether you left them better or worse off than they were the day before you resigned.

Tech is small. The PM you trained in your last two weeks becomes a director at a company you want to join in 2029. The engineer who covered your on-call shift recommends you for a staff role at a startup you didn't know existed. The manager you walked out cleanly from writes a one-line LinkedIn endorsement that closes the loop on a deal years later.

Quit well. The compounding is real.

"Two weeks isn't a number. It's a posture. The number is whatever your team needs. The posture is: I leave better than I came."

Frequently Asked Questions

How much notice should I give when quitting a tech job in 2026?+
Two weeks is the floor and the most common practice for individual contributors. Senior engineers and engineering managers should plan on three to four weeks because the handoff is genuinely larger. If you're on a critical project or on-call rotation, signal that you can flex up to four weeks — but commit to one specific last day in writing, otherwise the conversation drifts. See how notice periods vary by country if you're outside the US.
Should I tell my manager why I'm leaving?+
Give the truthful, neutral version: you're taking a role that fits where you want to grow. Don't list grievances, don't trash the company, don't get into a debate about pay. The exit interview with HR is the right venue for constructive systemic feedback — and even there, keep it about processes and systems, not specific people.
How do I write a tech-job resignation letter?+
Three short paragraphs. Paragraph 1: you're resigning, your last day is X. Paragraph 2: you're committed to a smooth transition and will use the next N weeks to document and hand off. Paragraph 3: ask how they want to handle the announcement. Skip the praise. Send it to your manager first, then to HR after the conversation. Keep a copy for your records — you'll want it for equity, PTO, and reference checks later.
Should I accept a counter-offer?+
In most cases, no. Industry data has consistently shown that most people who accept counter-offers leave within a year anyway, because the underlying reasons (scope, trajectory, manager, culture) rarely change just because comp moved. The exception is if comp was genuinely the only reason you were leaving — and even then, you've flagged yourself as a flight risk for the next review cycle.
Can my employer revoke my equity if I quit?+
Vested equity is yours. Unvested equity is gone the day you leave. Standard ISO option grants have a 90-day post-termination exercise window — if you have ISOs and don't exercise within 90 days of your last day, they expire. Some companies have historically extended this window (Pinterest, Coinbase, Stripe at one point); most haven't. Read your grant agreement before you give notice.
Will quitting hurt my references for future roles?+
Not if you do the handoff properly. Most modern reference checks happen through informal mutual connections on LinkedIn rather than formal calls — your peers and skip-level often matter more than your direct manager. How you spend your final two to four weeks (documenting, training a replacement, finishing what you can) is what people remember a year later when a recruiter calls them about you.
Should I tell my team before or after the official announcement?+
After. Your manager owns the announcement timing — typically a same-day or next-day note to the team or department once HR has acknowledged the resignation. Don't pre-announce to peers, even close ones. Information travels fast inside companies, and your manager hearing about your departure from a Slack channel rather than from you is the fastest way to sour the goodwill you're trying to preserve.

Already lined up your next move?

Browse 13,799+ open roles across 118 companies — each with culture context, Glassdoor ratings, and the values they actually live by.

Browse Jobs → Evaluate Culture First →