Your Senior Engineer Just Resigned: A 30-Day Plan to Cover the Gap Without a Panic Hire
A resignation starts a clock you did not choose. Here are the notice rules in five countries, what to hand over while the engineer is still there, why Gallup finds 52% of voluntary leavers say something could have been done, and a day-by-day 30-day plan with an option to bridge with external engineers.
What Should You Do in the First 48 Hours After an Engineer Resigns?
Protect the roadmap, not the org chart. Confirm the last working day in writing, list what only this person knows or owns in production, and start a written handoff while they are still willing to help. Do not promise the team, the board or a customer a replacement date yet.
Tell the team yourself, before rumor does, and say who covers what in the meantime, even provisionally. Then open two tracks at once: a search for the permanent replacement, and a plan for delivery capacity until that person arrives.
Key Takeaways
- Confirm the last working day in writing
- List what only this person knows and what they own in production
- Tell the team before rumor does, and promise no replacement date
- Open the permanent search and a cover plan in parallel
How Long Is the Notice Window in the US, UK, Germany, the Netherlands and Poland?
Different in every country, and usually shorter than your search. The statutory rule is a floor, not necessarily your window, so read the employment contract first because it can set a longer period. This summarizes public sources and is not legal advice.
In the Netherlands, the government business portal says an employee who resigns gives one month unless a different period was agreed beforehand and stated in the contract, with a maximum of 6 months. For Poland's statutory notice tiers, the Eurofound legislation database lists two weeks under six months' service, one month from six months, and three months from three years. That page is written from the side of notice given to employees and does not say in so many words that a resignation follows the same tiers, so confirm the period with counsel.
Germany's section 622 of the civil code sets four weeks to the 15th or the end of a calendar month. The UK's GOV.UK guidance sets at least one week after the first month in a job. Our in-house hiring timeline covers both from the new-hire side. In the US, SHRM guidance from 2018 notes that most states follow employment at will, so an employer can request advance notice but should not call it a requirement, and an employee can still leave immediately.
| Country | Statutory rule | What to check |
|---|---|---|
| Netherlands | One month unless a different period was agreed in the contract; maximum 6 months | The period stated in the contract |
| Poland | Two weeks under six months' service, one month from six months, three months from three years | The leaver's length of service, and with counsel that the same tiers apply to a resignation |
| Germany | Four weeks to the 15th or the end of a calendar month | Which calendar date the notice lands on, since the real last day may fall later than four weeks out |
| UK | At least one week after the first month in the job | Whether the contract requires longer notice or notice in writing |
| US | Employment at will in most states; an employer can request notice but should not call it a requirement | Any notice clause in the employment contract |
What Should the Notice Window Be Spent On?
A written handoff of what only this person knows. Five areas cover most of the risk: how to deploy and roll back each service; which secrets, accounts and access they hold and how to rotate them; on-call history and past incidents; business rules that live in their head or in old tickets; and which areas of code and which pull requests they review.
Ask for recorded walkthroughs instead of long documents, because a short screen recording of a rollback is faster to make and easier to follow than a page of prose. Have a colleague pair on every open pull request so someone else can finish it. A handoff nobody has used is only a draft, so ask a teammate to run a deploy from the notes while the leaver can still correct them.
Adding engineers to a roadmap like this? Spec your team in a minute.
Is It Worth Asking What Would Change Their Mind?
Ask, but do not bet the plan on it. Gallup reports that 52% of voluntarily exiting employees say their manager or organization could have done something to keep them. The figure covers the general workforce, not engineers, and the page names no study, so read it as a reason to have the conversation, not a forecast.
Ask what changed, listen, and decide quickly whether any change is within your power. If it is, offer it once, and keep the handoff and the cover plan running either way.
How Big Is the Gap, and When Does It Start?
The gap starts on the last working day and ends when the replacement is productive, not when they sign. For illustration only, assume the last day is 28 days away and you open the search today. SHRM's recruiting benchmarking data puts the median time to fill a nonexecutive role at 39 calendar days, which lands 11 days after the last day. The Employ hiring benchmarks, reported by HR Dive, put the average at 63.5 days in 2025, which lands 35.5 days after it. Both are across all roles, not engineers, and the new hire's own notice comes on top.
To price the empty seat, use the open seat cost calculator.
Should You Backfill In-House or Bridge With External Engineers First?
Usually both, because they answer different questions. Hire permanently when the role owns a core system or product direction for years. Bridge when the problem is delivery capacity against a date.
| Situation | Better first move |
|---|---|
| The leaver owned a core system and its architecture decisions | Hire a permanent owner, and bridge so delivery does not stop during the search |
| A customer or board is watching a date | Bridge now and run the search in parallel |
| The work was mostly steady feature or maintenance work | A bridge engineer may be enough; decide after the trial |
| The leaver was your only reviewer | Bridge for review and delivery, and plan how to rebuild review capacity |
What Should a Bridge Arrangement Contain?
Engineers can typically start within one to two weeks of first contact; a full team usually takes two to four weeks. As arithmetic only, if the notice runs 28 days and you make first contact in the first days, a start within one to two weeks could leave part of the window for the leaver and a bridge engineer to work side by side. It is not a promise of a date: fit is confirmed in a 15-minute intro call, a 60-minute discovery call if there is a fit, and then the trial.
Two StepTo practices help a handoff in particular. Engineers work in your repository and tools from day one and you own the code, so the handoff goes straight into the system you already run. And a written handover is produced whenever an engineer is replaced or the engagement ends, so a later permanent hire inherits notes and not memories. Both are on the engineering practices page.
Terms and success criteria written down before anyone starts. StepTo staff augmentation starts from $4,500 per developer per month, with a 3-month minimum and then 30 days notice. The first two weeks are a paid trial, and a replacement within the first 30 days is free. The details are on the pricing page.
Write the trial criteria before the first day: which open pull requests or tickets, what review turnaround, and which items on the handoff list the bridge engineer must be able to operate by the last day. The two-week trial plan has a template.
What Does the 30-Day Cover Plan Look Like, Day by Day?
This is a plan for you to run, assuming notice of about 30 days. Compress it if your notice is shorter.
| When | What you do |
|---|---|
| Days 1 to 2 | Confirm the last day, list unique knowledge and production ownership, tell the team and anyone who depends on the date, promise no replacement date |
| Week 1 | Start the handoff list, inventory every account and secret the leaver holds, write the brief for a bridge engineer, open the permanent search in parallel |
| Weeks 2 to 3 | Pair on open pull requests, record walkthroughs, have the bridge engineer work alongside the leaver, run a deploy from the notes |
| Last week | Rotate secrets and access, name an owner for every service, review the trial against the written criteria |
| After the last day | Hold a first read-out on what broke or slowed down, then decide whether to extend the bridge, hire, or both |
What Protects the Roadmap Before the Last Day?
A written handoff, a named owner for every service and delivery capacity that starts before the leaver walks out. None of it needs a panic hire, only the first 48 hours used well and a plan that runs in parallel with the search. Tell us the role, the stack and the leaver's last day on our contact page and book a 15-minute intro call; if there is a fit, a 60-minute discovery call follows.
Building a team in Eastern Europe?
StepTo builds dedicated nearshore engineering teams in Belgrade, Serbia. Engineers can typically start within one to two weeks of first contact; a full team usually takes two to four weeks. Two-week paid trial, from $4,500 per developer per month.
Related: Open seat calculator · Write your trial exit criteria
