How to Write a Resignation Letter as a Software Engineer (With Templates)
How to Write a Resignation Letter as a Software Engineer (With Templates)
The resignation letter is the last piece of code you'll write at this company. Most engineers ship it without testing it first.
You've accepted the offer. You've done the math on the equity and total comp. Now you need to tell your manager you're leaving — and put it in writing. It should take thirty minutes. Instead, most engineers either overthink it (three drafts, too many feelings) or underthink it (three sentences, no transition plan) and both versions cause problems they'll deal with for years.
Software engineers turn over at roughly 23% annually, one of the highest rates across professional occupations. That means the average engineering team is cycling through this process constantly. Your manager has seen a resignation letter before. What they haven't necessarily seen is one that makes the exit clean, professional, and reputation-preserving.
This is the guide for writing one of those.
Before You Write Anything: Read Your Employment Agreement
The most common mistake engineers make when quitting: skipping straight to the letter without reviewing what they agreed to when they started.
Pull up your employment agreement. Look for these four clauses specifically:
Non-solicitation. This restricts you from recruiting your current colleagues to join you at the new employer, or from poaching the company's clients. Non-solicitation clauses are far more commonly enforced than broad non-competes — courts will uphold them even in states that invalidate non-competes. If you're planning to hire from your current team, talk to an employment attorney before you give notice.
IP assignment. Most tech employment agreements assign inventions to the employer if they were built using company time, equipment, or confidential information — including side projects. California's Labor Code § 2870 carves out exceptions for purely personal projects built entirely on personal time with personal resources, but you must be able to document that distinction clearly. If you've been building something on the side, know where your IP ownership stands before you leave.
Non-compete. The FTC's blanket non-compete ban was blocked in federal court in August 2024 and the FTC formally abandoned its appeal in September 2025 — so there's no federal prohibition in effect. As of 2026, four states ban non-competes entirely (California, Minnesota, Oklahoma, and North Dakota) and 33 states plus D.C. impose at least some limits. If you're moving to a direct competitor and your agreement includes a non-compete, consult an attorney. California's rules apply regardless of where the contract was signed — an out-of-state employer cannot enforce a non-compete against a California-based employee.
Notice period. Your contract may specify a minimum notice period. Two weeks is the standard floor in most US tech companies, but some senior contracts or international arrangements specify four to eight weeks.
None of this requires hiring a lawyer before you resign. But knowing what you agreed to protects you from surprises — a cease-and-desist letter can arrive within days of a departure if you've triggered an enforceable clause you didn't know about.
The Conversation Comes Before the Letter
The resignation letter is not how your manager learns you're leaving. That conversation happens first.
Request a 1:1 with your manager — frame it as a general check-in if you want to avoid telegraphing anything. Tell them in person or over video before you submit anything in writing. This is professional courtesy, and it matters more than engineers typically expect. Your manager's experience of your resignation is largely determined by whether they felt blindsided by a written letter or informed in a direct conversation.
What to say in that conversation:
- State your decision clearly and early in the meeting. Don't build to it.
- Give your last day.
- Express genuine appreciation for something specific — a project, a skill you developed, a team relationship.
- Offer to help with the transition.
What to avoid:
- Explaining why your new role is better. Your manager doesn't need a comparison.
- Criticizing team dynamics, the codebase, or leadership. Save that for the exit interview if you participate in one.
- Leaving the date ambiguous ("sometime in the next few weeks").
After that conversation, the letter formalizes what was already said.
What the Letter Should Contain (and What It Shouldn't)
A resignation letter has one job: document the resignation clearly and professionally, with the exact last day on record.
Include:
- Your role title and the date the resignation is effective
- Your last working day (explicit date, not "two weeks from now")
- A brief, specific expression of gratitude — one sentence mentioning a project or skill is better than generic "I've learned so much here"
- An offer to assist with transition: documentation, handover, training your replacement
Leave out:
- Complaints about anything — management, tech debt, culture, compensation, team dysfunction. Even accurate complaints have no constructive function in a resignation letter and will follow you.
- Your new employer's name, role title, or salary. This information is not relevant to the resignation and can create friction with your manager or HR.
- Jokes, sarcasm, or emotionally charged language. The letter will go into a personnel file.
- Conditional language ("I'm resigning unless..."). You've made the decision. State it clearly.
The letter should be three to five short paragraphs. A one-pager is fine. A half-page is better.
Template 1: Standard Resignation (Taking a New Role)
Use this for the majority of departures — moving to a new company, heading to a competitor, or transitioning roles.
[Your Name] [Date]
[Manager's Name] [Title], [Company Name]
Dear [Manager's Name],
I am writing to formally resign from my position as [Your Title] at [Company Name], effective [Last Day — e.g., Friday, July 18, 2026].
Working on [specific project or team] has been genuinely valuable — [one specific thing you built, learned, or accomplished]. I'm grateful for the opportunity and for the team we built together.
I'm committed to a smooth transition. Over the next [X] weeks, I plan to [document the [system/service], complete the handover for [ongoing work], and make myself available to onboard my replacement or answer questions]. Please let me know what would be most useful.
Thank you for everything.
Sincerely, [Your Name]
Calibration notes:
- "Effective [Last Day]" establishes the date on record. Use a specific calendar date, not a relative one.
- The gratitude line should be specific enough to be credible. Generic praise reads as filler.
- The transition offer should be concrete. Vague offers ("happy to help however I can") are less reassuring than specific ones ("I'll document the deployment pipeline and write runbooks for the alert rules I own").
Template 2: Leaving for a Direct Competitor or Startup
If you're moving to a company in the same space, or to a startup in your vertical, the resignation letter doesn't change much — but your pre-departure checklist does.
Before you submit the letter:
- Do not take any code, configs, internal documents, architecture diagrams, customer lists, or proprietary data with you. Even your own code written for the company typically belongs to the employer. Removing company files before your last day is the fastest path to litigation.
- Do not recruit colleagues before you leave. Post-departure, non-solicitation clauses may restrict when and how you can reach out even then.
- Wipe your machine to the company's standards, follow any offboarding checklist your IT team provides, and get written confirmation that offboarding is complete.
The letter itself:
Dear [Manager's Name],
I'm writing to let you know that I've accepted a new position and will be resigning from [Company Name], with my last day being [Date].
My time here — especially [specific project or team] — has shaped how I think about [technical domain]. I'm grateful for the trust you placed in me and the team's partnership on [outcome or deliverable].
I want to make sure the transition is as clean as possible. I'll complete my current sprint deliverables, document the systems I own, and make myself available for questions through my last day. Let me know what you need from me in the meantime.
Thank you.
[Your Name]
Why this version is careful: It doesn't name the new employer. It doesn't signal anything about the competitive landscape. It focuses on completing work and documenting systems — both of which matter more to your legal standing and your professional reputation than anything else you could say.
Template 3: Leaving Without a New Role
Taking a break, stepping back from tech, dealing with a health situation, or leaving without a next step lined up — all of these happen, and none require you to explain your reasons in the letter.
Dear [Manager's Name],
I'm writing to formally resign from my position as [Your Title] at [Company Name], effective [Last Day].
This was not a decision I made lightly. [Company Name] has been [something specific and genuine — a challenging problem, a team that pushed me technically, a product I believed in]. I'm grateful for the experience and for your support.
I'd like to ensure a thoughtful transition — I'm happy to document what I own, help onboard someone to cover my responsibilities, and be available for any critical questions through my last day.
Thank you for everything.
Sincerely, [Your Name]
What to avoid saying: You don't owe your employer your next steps. "I'm taking some time off," "I'm stepping away from the industry for a while," and "I'm dealing with a personal matter" are all complete answers if they come up in conversation. In the letter, they're not necessary at all.
If you're leaving because of a toxic workplace, a PIP, or a management conflict — the letter is not the place to address any of it. The PIP survival and recovery guide covers how to handle that exit specifically, including how to document the situation for your own records.
The Notice Period Question
Two weeks is standard in most US tech roles. But the right notice period for your situation depends on a few things:
Factors that argue for longer notice:
- You own production services with no backup
- You're the sole expert on a legacy system or undocumented architecture
- You're mid-sprint on a high-stakes deliverable
- You have direct reports or are the primary mentor for junior engineers
- Your departure will trigger a significant recruiting effort
Three to four weeks in these situations protects your professional reputation and gives the team a genuine chance to respond. Some engineers at senior levels negotiate four to six weeks as a matter of standard practice.
Factors that argue for the standard two weeks:
- Your new employer's start date is fixed and giving more time would require negotiating with them
- You're in a team with good documentation and coverage
- Your relationship with the company or manager is strained
Most new employers will accept a delayed start date if you explain you want to give your current team proper notice. Asking for an extra week or two is more common than engineers assume and rarely costs an offer.
The one rule: whatever you agree to, show up fully through the last day. Engineers who mentally check out during their notice period consistently get worse references. The last two weeks color how the entire tenure is remembered.
Protecting Your References and Professional Reputation
Tech is a small industry. Engineering managers, CTOs, and recruiters move between companies, and reference networks overlap for years in any given technical community.
A few practices that protect your reputation through a departure:
Don't announce your new employer before your last day. Telling colleagues and posting on LinkedIn while still employed creates unnecessary social and legal friction. Wait until you've formally left.
Document what you own. A departing engineer who writes clear runbooks, hands over their on-call rotation cleanly, and records a Loom walkthrough of the systems they built earns goodwill that survives the departure. An engineer who leaves nothing behind does not.
Exit interviews are optional. If you participate, keep the feedback constructive and forward-looking. Specific, actionable feedback ("the oncall rotation had no documented escalation path") is useful. Grievances about individuals are not. You can decline to participate at all — there's no professional cost to doing so.
Leave access revocation to IT. Don't remove your own access, don't delete your Git history, and don't wipe configurations that others depend on. Let the company's standard offboarding process handle it.
Your next job search starts the moment you leave this one. The Referral Playbook covers how the professional relationships you built at each company become your most valuable recruiting asset over time.
TL;DR
- Read your employment agreement first — check for non-solicitation, IP assignment, non-compete, and notice period clauses before you give notice.
- Tell your manager in a 1:1 before submitting the letter. The written letter formalizes what the conversation already communicated.
- Keep the letter short and clean: your role, your last day, specific gratitude, concrete transition offer. Nothing else.
- Name your last working day explicitly — use a specific calendar date.
- If you're moving to a competitor: leave no data behind, don't recruit colleagues, and consult an attorney if you have a non-compete.
- The right notice period is usually two weeks, but three to four weeks is professionally warranted if you own undocumented critical systems.
- Show up fully through your last day. The last two weeks determine how a multi-year tenure is remembered.
The resignation letter is a small document with a long tail. Written well, it closes one chapter cleanly and leaves every relationship intact for the next one.
If you're evaluating the offer that's replacing your current role, The Engineer's Salary Negotiation Playbook covers how to counter effectively and the offer evaluation framework covers what to look at beyond base salary — equity, growth trajectory, team quality, and the numbers that actually matter.
And if you've received multiple competing offers and need to manage them simultaneously, the multiple-offer negotiation playbook covers the mechanics.
Your resume and career profile need to reflect where you're headed — not just where you've been. Wrok is an AI-powered platform that helps engineers translate their work history into a focused career narrative calibrated for their next role. Try Wrok free →