Notice Periods in Europe: Why Your New Hire Starts in Q3

If you hire a senior engineer in Germany, the Netherlands, Poland or the Czech Republic, assume they will start two to three months after they sign. In Turkey, Spain, Portugal or Romania, assume four to eight weeks. In the UK the statutory minimum is almost irrelevant — what matters is the clause in their current contract, which for senior people is usually one to three months. Notice periods are the single most underestimated variable in cross-border hiring plans, and they are the reason a role you "closed" in March does not produce working code until July.

This post covers what the typical ranges look like, why the legal minimum is almost never the number you should plan against, and the handful of levers that genuinely compress the gap.

The statutory minimum is the floor, not the forecast

Every European labor code sets a minimum notice period, usually scaled by tenure. Almost every employment contract for a mid-level or senior professional extends it. Employers do this deliberately: a longer notice period is cheap insurance against losing a key engineer with two weeks' warning.

So when you ask a candidate "what's your notice period?" and they say "I think it's one month, that's the law here", treat that as a hypothesis. Ask them to open their contract and read you the clause. In our experience the gap between what candidates believe and what their contract says is one of the most common causes of a slipped start date — and it surfaces late, after the offer is signed, when you have already told the board when the team will be at full strength.

Two other things sit on top of the contractual clause:

• Accrued vacation. In several markets it is normal to run unused leave concurrently with notice, which shortens the effective gap. In others the employer pays it out instead and the candidate works the full term. This is negotiable and often worth more to the candidate than a signing bonus.
• Resignation timing rules. Germany is the clearest example: notice commonly runs to the 15th or the end of a calendar month, so resigning on the 16th can cost two extra weeks. If a candidate signs on a Friday and resigns on Monday, that detail decides whether they start on the 1st or the 15th.

Rough ranges by market

These are typical patterns for professional and engineering roles, not legal advice — statutory rules change, collective agreements override them in some sectors, and the individual contract usually wins. Verify before you commit to a date.

• Germany — statutory minimum around four weeks for employees, extending with tenure on the employer's side; senior contracts frequently specify one to three months, tied to month-end. Probationary periods carry much shorter notice, often two weeks.
• Netherlands — employee notice is typically one month unless the contract extends it, usually to month-end. Employer notice grows with service.
• Poland — scaled by tenure: roughly two weeks under six months, one month up to three years, three months beyond that. Three-month notice is the default reality for experienced engineers.
• Czech Republic and Slovakia — two months is standard, running from the start of the following month. Plan for ten weeks, not eight.
• Romania — up to twenty working days for non-management roles and significantly longer for management positions. In practice, four to six weeks.
• Turkey — statutory notice scales from two weeks under six months of service up to eight weeks beyond three years. Contracts rarely extend it much for individual contributors, so four to eight weeks is a reliable planning assumption.
• Spain and Portugal — commonly fifteen to thirty days for employees under general rules, with longer terms for senior and fixed-term arrangements.
• United Kingdom — statutory employee notice is one week, which almost nobody actually serves. Contractual notice of one month for mid-level and three months for senior and leadership roles is the norm, and garden leave is common.
• Nordics — one month is a common baseline for employees, extending with tenure and collective agreements; senior roles often sit at three months.

The pattern worth internalizing: Central Europe is slow, Southern Europe and Turkey are faster, and seniority stretches everything. If your engineering plan assumes a uniform six-week ramp across markets, it is wrong in at least two directions.

Leadership hires are a different timeline entirely

Director, VP and C-level contracts routinely carry three to six months of notice, sometimes with non-compete tails on top. A CTO search that takes three months to shortlist and offer can easily mean nine months between the decision to hire and the first board meeting with that person in the room.

That changes how you sequence the work. You cannot run a leadership search as a reaction to a departure and expect continuity — you need the search to start while the incumbent is still in place, or you need an interim arrangement. It is also the reason executive search for director and C-level roles is planned around a calendar rather than a requisition: the notice period is a fixed cost of hiring senior people in Europe, and the only way to absorb it is to start earlier.

The levers that actually work

Most attempts to shorten notice fail because they ask the wrong party. The candidate's current employer has no incentive to help you. What does work:

• Negotiated early release. Many employers release people early once a handover is complete, particularly if the departing person is not client-facing. Encourage the candidate to propose a specific handover plan and an early date rather than asking "can I leave sooner?"
• Buying out the notice. In some markets a candidate can pay compensation in lieu of serving notice, and some employers reimburse it. This is a real tool for critical hires, but it needs to be checked against local law and the specific contract.
• Unused vacation. Often the cheapest two weeks you will ever buy. Ask the candidate how much leave they have accrued before you fix a start date.
• Start-date staggering with part-time onboarding. Pre-start access to documentation, a laptop, and asynchronous onboarding material does not shorten notice but it shortens ramp. A person who has read the architecture docs during their last month elsewhere is productive in week one.
• Hiring in parallel across markets. If the same role can be filled in Istanbul, Lisbon or Warsaw, notice periods become a tiebreaker rather than a constraint. This is one of the quieter advantages of running technical and specialist hiring across several countries at once instead of one.

What does not work: pressuring the candidate to breach their contract. It damages their references, exposes them to claims in several jurisdictions, and tells you something about how they will treat your own notice clause later.

Build the delay into the plan, not the apology

The practical fix is to run the timeline backwards from the date you need the person working, not forwards from the date you open the role. For a senior engineer in Poland or Germany: three months of notice, plus four to eight weeks of search and interviews, plus a week or two of offer negotiation. That is roughly five months. If you need the capacity sooner than that, hiring is not the mechanism — bridging the gap with a dedicated team you can stand up quickly is, and you backfill it with permanent hires as they arrive.

The second fix is to ask about the notice clause in the first screening call, not at offer stage. It costs thirty seconds, it occasionally changes which candidate you prioritize, and it stops the single most predictable surprise in European hiring from being a surprise at all.

If you are planning headcount across several of these markets and want a realistic calendar before you commit to one, talk to us about the timeline.