Resigning as a Junior Engineer: Script, Timing, What Not to Say

You got the offer. Now you have to quit, and you have never done this before. That is fine. Resigning as a junior engineer is not a negotiation, not a performance, and not a goodbye tour. It is a short, boring conversation followed by two weeks of clean handoff. Most people overthink the conversation and underthink the handoff, which is exactly backwards. This guide is the script, the timing, and the specific sentences that will get you out without torching a reference you will actually need in 18 months when a recruiter at Stripe or Ramp calls your old manager for a backchannel.

Give exactly two weeks, not three, not one

Two weeks is the US industry standard for engineers at every level below staff, and it is the standard for a reason: it is long enough to finish the ticket you are on and short enough that nobody expects you to ship anything new. If you give three weeks you will be asked to train your replacement, sit in interview loops, and write runbooks that nobody will read. If you give one week you will be remembered as the junior who left a mess. The number is two.

The one exception is if your offer start date is more than two weeks out and your current manager has been genuinely good to you. In that case, offer up to three, but only if asked. Do not volunteer four. Do not volunteer "whatever you need." You are a junior engineer; your leverage comes from being reliable on predictable terms, not from heroics.

Time the conversation for a Monday or Tuesday morning, ideally right after your 1:1. Never resign on a Friday afternoon (your manager will spend the weekend stewing) and never resign the day before a planned PTO (it looks like you are fleeing).

Tell your direct manager first, in person or on video, alone

This is the single rule you cannot break. Not Slack. Not email. Not your skip-level. Not your tech lead. Not the friend on your team you got coffee with yesterday. Your direct manager, one-on-one, synchronous, before anyone else in the building knows.

If you are remote, put a 15-minute hold on their calendar titled "quick chat" or "1:1 topic" and open with video on. If you are hybrid or in-office, ask them to grab a room. Do not attempt this over DMs. Managers remember the medium of the resignation for years, and "they quit over Slack" is a story that follows you.

Your resignation is the most controlled piece of communication you will send at this company. Write the first sentence down. Read it off the page if you need to.

Here is the exact opener, and you should use it close to word-for-word:

"I wanted to let you know in person before anyone else: I have accepted another offer, and I am giving my two weeks' notice today. My last day will be [Friday, date]. I am really grateful for what I have learned here, and I want the handoff to go smoothly."

That is it. Three sentences. Stop talking. Let them respond.

What not to say in the resignation meeting

Juniors almost always over-share in this meeting, usually out of guilt. Do not. Specifically, do not say any of the following:

• The name of the company you are going to, unless you are fully comfortable with it getting back to everyone, including people at the new company
• The comp numbers, the offer details, or how the recruiter found you
• Why your new role is "better" than your current one
• That you have been unhappy, that your TL is hard to work with, or that you wish the team shipped faster
• Anything about other teammates who are also interviewing
• A promise to "always stay in touch" that you will not keep

If your manager asks where you are going, the correct answer is: "I would rather hold off on sharing that publicly until I have started, but I am happy to tell you once I am settled." They will respect this. If they push, repeat the same sentence. Recruiters and managers talk, and a junior engineer badmouthing their previous team in a resignation meeting in 2026 will show up in a reference check in 2027.

Expect a counter-offer and plan to say no

Roughly one in three junior engineers who resigns at a company with any retention budget gets a counter-offer, and in 2026 the typical junior counter is a 10 to 18 percent bump plus a one-time retention grant of 15,000 to 30,000 dollars vesting over 12 to 18 months. Companies like Amazon, Meta, and most late-stage startups have standing playbooks for this. It will feel flattering. It is not about you.

Here is what the data actually shows: the large majority of engineers who accept counter-offers leave within 12 months anyway, usually on worse terms because the original reason they wanted to leave has not changed and now their loyalty is in question. As a junior, a counter is almost always a bad deal:

1. You accepted your current comp when you were hired, so the counter proves your employer was underpaying you on purpose
2. The counter does not fix scope, mentorship, tech stack, or manager problems, which are the actual reasons juniors leave
3. Your new employer will pull the offer the moment you renege, and the industry is small enough that future recruiters will know
4. The retention grant will vest slower than your career is moving at this stage
5. You will be first on the list in the next round of layoffs, because you have already declared you were leaving

Decide before the meeting that the answer is no. If a counter comes, say: "I appreciate you putting that together, and I thought about this carefully before I came in. I am going to move forward with the other role." Do not negotiate. Do not "think about it overnight." The decision was made when you signed the new offer.

Nail the handoff in the first three days, not the last three

The biggest mistake juniors make after the resignation meeting is treating the two weeks like a vacation. Your reference quality is set almost entirely by what you ship in the first 72 hours after the announcement. By the end of day three, you should have:

• A written handoff doc in Notion, Confluence, or the team wiki, linked in the team Slack channel
• A list of every ticket you own, with status and the next concrete step
• Credentials and access notes (but never passwords in plaintext) for anything only you have access to
• A list of recurring meetings you are in and a recommendation for who should replace you
• Open PRs either merged, closed, or reassigned with context
• A calendar invite for a 30-minute handoff walkthrough with your TL or replacement

Do not save this for week two. Week two is for follow-up questions, not original work. If you finish the handoff doc by Wednesday of week one, you look organized; if you finish it by Thursday of week two, you look like you coasted.

One specific thing juniors miss: dashboards and alerts. If you own a Datadog dashboard, a Sentry alert route, a PagerDuty schedule, or a cron, those need to be reassigned explicitly, not just mentioned in passing. These are the things that break silently three weeks after you leave and become your reputation.

Handle the exit interview like a professional, not a therapy session

Your HR business partner will schedule a 30-minute exit interview, usually in week two. In 2026 this is almost always on Zoom or Google Meet, and you will be told it is confidential. It is not confidential. Assume anything you say will be summarized in a doc that your skip-level and their skip-level will read.

This is not the place to unload. It is not the place to name names. It is not the place to explain that your TL micromanaged you or that the on-call rotation was brutal. Keep it short, keep it structural, and keep it forward-looking.

Useful things to say: the onboarding was strong or weak in specific ways, the tech stack was modern or dated, the mentorship structure worked or did not. Useful things to avoid: any sentence containing the word "toxic," any sentence naming a specific person, any sentence about compensation.

If they ask why you are leaving, the cleanest answer is some version of: "I got an offer that accelerates a specific part of my career I want to develop, and the timing worked." That is true for essentially every job change and tells them nothing actionable. You owe them professionalism, not a post-mortem.

Next steps

The next 14 days are mechanical. Do them in order.

This week: write the resignation sentence on paper. Put the meeting on your manager's calendar for Monday or Tuesday morning. Do not tell teammates, do not post anything on LinkedIn, do not update your title. Have your last-day date picked (always a Friday) before you walk in.

Day one after resigning: start the handoff doc. Share it with your manager by end of day. Merge or close every open PR you can.

Days two through five: finish handoff, do the walkthrough with your replacement or TL, reassign dashboards and alerts, document any tribal knowledge that only lives in your head. Decline any new tickets politely: "I want to make sure I do not start something I cannot finish before my last day."

Week two: be available, answer questions, attend the exit interview, be boring. Update your LinkedIn the Monday after your last day, never before. Send a short farewell message to your team Slack channel on your last day at 4 pm, no earlier. Keep it under 100 words, thank two or three specific people by name, and do not mention where you are going.

After you leave: do not poach teammates for at least six months, do not disparage the old company publicly ever, and keep the door genuinely open with your manager. The engineering world is smaller than it looks, and the manager you resign cleanly from at 23 is the VP who hires you at 31. Play the long game. This conversation is 15 minutes. Your career is 40 years.

Related guides

• Resigning as a Senior Engineer: Handoff Expectations and the Conversation — How senior engineers should resign in 2026: the conversation script, realistic handoff scope, counter-offer reality, and what your manager actually expects.
• Resigning as a Staff Engineer: Protecting Projects, Peers, Reputation — A 2026 playbook for staff engineers resigning: cross-team handoff, political fallout, protecting peers and projects, and the reputation game at L6 and above.
• The Background Check Process After an Offer in 2026 — What They Verify and Timing — Background checks after an offer usually verify identity, employment, education, criminal records, and sometimes credit or credentials. Here is what happens, how long it takes, what causes delays, and how to handle discrepancies without panic.
• Negotiating a Sign-On Bonus in 2026 — When Companies Say Yes and How to Ask — Sign-on bonuses are often the most flexible part of an offer, especially when base or equity bands are tight. Learn when companies say yes, what amounts are realistic, and the scripts that keep the ask firm but low-drama.
• Negotiating Equity Refresh Timing: Get the Next Grant Booked — How to negotiate the timing and size of your first equity refresh in 2026 — before you sign, after you sign, and what to demand in writing.