CareerClimbCareerClimb
Quitting
Resignation
Career Transition
Professional Relationships
Notice Period
April 5, 20269 min read

How to Quit Without Burning Bridges

How to Quit Without Burning Bridges

I rehearsed my resignation speech in the shower for two weeks before actually doing it. I wrote bullet points on my phone. I practiced in the car. I had three different versions depending on how my manager reacted. When the moment finally came, I said about four sentences and my manager said, "Okay, I appreciate you telling me." The whole thing took less than five minutes.

The decision to leave is hard. But for a lot of engineers, the anxiety about how to leave is almost as stressful as the reasons they're leaving. You don't want to torch relationships you spent years building. You don't want your last two weeks to be awkward. You don't want to end up on someone's "never rehire" list because you handled the exit badly.

Good news: this part is more mechanical than emotional. There's a playbook. If you've already decided it's time to go, what follows is exactly how to execute the exit without damaging what you built.

Tell your manager first, and tell them live

This is the most important rule. Your manager should not hear about your resignation from Slack, email, a skip-level, or the rumor mill. They should hear it from you, in a private conversation, face-to-face or on video.

Why this matters more than you think: your manager will be asked about you for years. Reference checks, back-channel calls, internal transfers if you ever return. The way they remember your departure is disproportionately shaped by how they found out.

Request a private one-on-one. If you already have a regular 1:1, use that slot. If it's days away, send a message: "Hey, could we grab 15 minutes today? I have something I'd like to discuss." Don't say more than that. Don't put it in writing yet.

Don't ambush them in a group setting. Don't tell a trusted coworker first "just to get advice." In a company of any size, anything you tell one person will travel. Your manager deserves to process this before it becomes team knowledge.

The resignation conversation: what to actually say

This conversation does not need to be long. It does not need to be emotional. It needs to do three things: state your decision, express gratitude, and signal your willingness to help with the transition.

Here's a script that works:

"I wanted to let you know that I've decided to move on. My last day will be [date]. I want you to know how much I've valued working with you and this team. I'm committed to making the transition as smooth as possible over the next [two weeks / notice period]."

That's it. You don't need to explain where you're going (and in most cases, you shouldn't volunteer it). You don't need to justify why you're leaving. You don't need to list your grievances. This is not a feedback session. It's a notification.

What NOT to say

  • Don't trash the company, the team, or leadership. Even if they deserve it. Anything you say in this moment will be remembered as your parting message. Make it one you'd be comfortable with five years from now.
  • Don't over-explain. "I've been thinking about this for months and honestly the reorg made things worse and I just feel like my growth has stalled..." None of this helps. Your manager doesn't need your reasoning. They need your timeline and your transition plan.
  • Don't apologize excessively. You're not doing anything wrong. You're making a career decision. One "I know this creates some disruption and I want to help minimize that" is enough.

If your manager asks why

They will probably ask. Keep it brief and professional.

Good answers:

  • "I got an opportunity I couldn't pass up."
  • "I'm looking for a different kind of challenge."
  • "It's a personal decision. I'd rather focus our remaining time on a clean handoff."

Bad answers:

  • A detailed critique of company strategy
  • Salary comparisons with your new offer
  • Naming specific people or situations that drove you out

You can share honest feedback in an exit interview if the company has one. The resignation conversation is not the time.

Notice period: what's expected and what's smart

Two weeks is standard in the US. That's true at most big tech companies and nearly all startups. Some companies and roles expect more. Senior and staff engineers are sometimes asked for three to four weeks. Directors and above may negotiate 30 to 60 days.

Check your employment agreement. Some offer letters specify a notice period. If yours says two weeks, give two weeks. If it says nothing, two weeks is the default.

Offer more if you can. If you're not starting your new role immediately, offering three weeks instead of two is a low-cost way to leave goodwill behind. Your manager will remember the gesture. Don't extend so long that you lose momentum or your new employer gets impatient, but an extra week of overlap can mean the difference between a clean handoff and a scramble.

Put it in writing after the conversation. Once you've told your manager live, follow up with a brief email to your manager and HR:

"Following up on our conversation today. I'm resigning from my position effective [last day]. Thank you for the opportunity to be part of this team. I'm committed to ensuring a smooth transition during my remaining time."

Short. Professional. Creates a paper trail. That's all it needs to do.

How to handle a counteroffer

Your company may try to keep you. A raise, a title bump, a team transfer, a promise of interesting work. This is flattering. It also needs careful thinking.

The data on counteroffers is consistent. Most people who accept a counteroffer leave within 12 months anyway. The reasons you decided to leave rarely get fixed by more money. And now your employer knows you had one foot out the door.

If you're genuinely open to staying, the counteroffer needs to address the actual reason you're leaving, not just the salary. If you're leaving because of your manager, a raise doesn't fix that. If you're leaving because there's no growth path, a title bump without structural change doesn't fix that either.

If you've already committed to another company, don't entertain the counteroffer. Be gracious but firm: "I appreciate that, and it means a lot. But I've made my decision and I want to honor my commitment."

Reneging on an accepted offer to take a counteroffer burns bridges in a different direction. The tech industry is small. The recruiter who placed you, the hiring manager who went to bat for you, the team that cleared their calendar for your onboarding. Those people remember.

Your transition plan: the thing that separates good exits from great ones

The single most effective thing you can do during your notice period is make it easy for the people who stay. That's it. That's the whole strategy.

Write a handoff document

Before anyone asks you to, create a document that covers:

  • Active projects with current status, next steps, and who should own each one
  • Recurring responsibilities with instructions and relevant links
  • Key contacts for anything that requires institutional knowledge
  • Known issues that are in progress or need attention
  • Where things live. Documentation links, repo locations, access permissions, dashboards

This document doesn't need to be perfect. It needs to exist. Most departing engineers leave behind a gap that takes weeks to fill because nobody wrote anything down. Being the person who did is remembered.

Do knowledge transfer sessions

Don't just hand someone a document. Sit down with whoever is inheriting your work and walk through it. Let them ask questions. Record the session if your company allows it. This is the highest-value use of your remaining time.

Tie up loose ends

  • Close or reassign your open pull requests
  • Update your tickets with clear status notes
  • Remove yourself from on-call rotations and update escalation paths
  • Cancel or transfer any recurring meetings you own

What NOT to do during your notice period

Your last two weeks set the final impression. People will remember this stretch more than you expect.

Don't slack off. The temptation is real. You've mentally checked out. The work doesn't matter to you anymore. But it matters to the people around you. Showing up and delivering through your last day is a signal of character. It costs you nothing and buys lasting goodwill.

Don't badmouth the company. Not to coworkers, not in Slack channels, not in exit interviews you treat as therapy sessions. Every negative thing you say during your notice period will travel and get attributed to you. Some of it will get distorted. None of it will help you.

Don't recruit your teammates. Even if your new company would love them. Even if they've mentioned they're unhappy. Actively recruiting from your current team during your notice period is one of the fastest ways to turn a clean exit into a messy one. If a coworker asks about your new company, you can share factual information. But don't initiate.

Don't skip the goodbye. Send a brief farewell message to the team or broader org on your last day. Thank people by name where it's genuine. Share your personal email or LinkedIn for staying in touch. Make it warm, make it short, make it real.

Maintaining relationships after you leave

The exit is one moment. The relationship is ongoing. Tech is a small industry that runs on referrals, back-channels, and alumni networks.

The alumni network effect

Engineers at big tech companies underestimate how often their paths will cross again. The person on your team today could be your hiring manager in three years. Your skip-level could end up at a startup you want to join. Your peer could be the one who refers you to the role that changes your career.

This is not theoretical. On Team Blind and in engineering communities, the same pattern surfaces repeatedly: people who left well get pulled back into opportunities. People who left badly get quietly excluded.

Stay in touch without being weird about it

You don't need to maintain deep friendships with everyone. But a few small gestures go a long way:

  • Connect on LinkedIn before you leave, not after
  • Check in occasionally. A message every few months is enough. "Saw your team shipped X, congrats" takes 30 seconds and keeps the connection alive
  • Be a resource. If someone from your old team reaches out for advice, help them. If you hear about an opportunity that fits a former colleague, pass it along
  • Attend the occasional team event if you're invited and it's genuine

The people who build real allies don't stop building them when they change jobs. The best professional relationships survive company changes because they were never just about the company.

If you're leaving a bad situation

Some exits happen under difficult circumstances. A toxic manager. A PIP you disagree with. A reorg that gutted your team. A culture that made you miserable.

The temptation to burn it all down on the way out is understandable. Don't do it. Not because they don't deserve it. Because it doesn't help you.

Your resignation letter is not a manifesto. Keep it standard. The three-sentence version works regardless of how you feel.

Your exit interview is optional. If you choose to do one, share constructive feedback about systems and processes, not personal attacks on individuals. Be honest, not vindictive. If you can't do that yet, it's perfectly fine to skip the exit interview entirely.

Process your feelings somewhere else. With a partner, a friend, a therapist. Not with your coworkers during your notice period. Not in a Glassdoor review written from a place of raw anger. You can write that review later, when you've had distance and can be fair.

The goal is not to pretend everything was fine. The goal is to leave cleanly so that the bad situation doesn't follow you to the next thing.

The conversation with your manager one more time

If you take one thing from this article, let it be this: the relationship with your manager is the most consequential relationship to protect during your exit. Not because your manager is always right, or always good, but because they're the person most likely to be asked about you in the future.

Have the conversation live. Keep it brief. Be grateful where gratitude is honest. Offer a clean transition. Then execute the transition well.

That's the whole playbook. Everything else is detail.


CareerClimb helps you build a strong career case wherever you go. Your wins follow you. The evidence you collect, the impact you document, the case you build. None of it disappears when you change jobs. Start documenting from day one at your next role.

Frequently Asked Questions

Related Articles