November 16, 2026

Underperforming senior engineer: UK, Dutch and German plans

A tenured senior engineer is underperforming. Check the setup, then run a written plan that fits UK, Dutch and German law, and cover the work meanwhile.

Guide

Tech

For an underperforming senior engineer past probation, check the setup before the person, then run a written plan with measurable standards and a dated review. We'd plan about 12 weeks. After a failed plan, expect roughly two more months in Germany, a court or settlement in the Netherlands, and contract notice in the UK. Keep their scope covered meanwhile, and don't backfill their role.

Is it the setup or the person for an engineer who used to perform?

If they were good two years ago, something changed, and it's often on your side. Look for role drift, a new manager or a reorg, heavy on-call load, a review queue that stalls their work, or AI-tool expectations nobody wrote down. Fix what you find, then restart the clock. For the audit itself, the 10-day audit for a new hire works for a tenured engineer too. That article also covers the probation case. If the person is a vendor's contractor, the contractor case runs on different terms.

Rule out illness next. Dutch law excludes inability caused by illness from the underperformance ground, and Acas says an employer can't dismiss or discipline someone just because they're disabled, and must do all it reasonably can to support the person first. If health is in play, this stops being a capability case.

We'd also assume their last good reviews and any raise will be read against you. The setup check protects you as much as it helps them.

What evidence counts for an engineer, and against whom do you compare?

Use outcomes you can show: scope delivered against what was agreed, review turnaround, incidents they owned, commitments missed. Leave out commit counts and similar volume numbers, which say little about a senior engineer (why token counts are not a performance standard makes the case). Write down what good means in this person's role before the plan starts. If you can't write it, you aren't ready to hold anyone to it.

If the cause is a second job or work that isn't happening for other reasons, it's a conduct case, not a capability case.

Germany adds a comparison problem: the court test is output against comparable colleagues, covered under Germany below. If the engineer is one of only two backend engineers, there's barely an average to fall under. Build the plan on a written standard and a comparison, not on a percentage.

What does a fair capability plan look like in the UK, the Netherlands and Germany?

CountryWhat the law asksWhat the plan needsMain trap
UKA fair procedure per the Acas CodeObjectives, timeline, support, written recordSkipping your own capability procedure
NetherlandsNotice of the shortfall, real chance to improveDated feedback, training, redeployment checkGaps caused by your training or conditions
GermanyOutput clearly below comparable colleaguesA written standard, a measured gapToo few comparable colleagues

United Kingdom

Capability is a fair reason for dismissal in the UK, but only after a fair procedure that follows the Acas Code. If you have your own capability procedure, follow that too. Start with an informal talk. If that doesn't work, write a performance improvement plan with objectives, a reasonable timeline and further support or training. Discuss it with the engineer and share a written record.

Keep records throughout: regular, fair reviews that show consistent issues, and evidence of the support you gave. A final written warning, then dismissal if the issue continues, is a possible outcome. The timeline can be extended, and dismissal stays a last resort.

Netherlands

Tell the engineer about the shortfall in good time, give them enough chance to improve, and check the shortfall isn't down to your own lack of training or poor working conditions (article 7:669(3)(d) of the Dutch Civil Code). Also check whether another suitable role is possible, with training if needed (article 7:669(1)).

If the plan fails, the route is a request to the kantonrechter (the subdistrict court) to dissolve the contract, under article 7:671b. The alternative is an agreed exit, a vaststellingsovereenkomst. So a Dutch plan is a file you build for a judge, and it also strengthens your hand in any settlement talk.

Germany

Build a file that shows output clearly behind comparable colleagues, not a percentage. In a 2003 judgment (2 AZR 667/02), the Federal Labour Court (BAG) said the employer meets its burden by showing output clearly behind comparable employees, well under the average. The employee then has to explain why the low output is still their full effort. On those facts a long-term shortfall of well over a third was enough, but the court refused to treat about a third as a fixed line.

German law sorts dismissals into behaviour (verhaltensbedingt) and person (personenbedingt). Low output can justify the first when the employee isn't using their capacity reasonably. The second needs no fault: it asks whether the gap is so large that you can't fairly be expected to keep the contract as it is.

In the 2003 case the employer had talked to the employee twice and issued two written warnings that compared their output with the department average and demanded a minimum level. It also informed the works council (Betriebsrat) before giving notice. The BAG set aside the lower court's ruling for the employee and sent the case back for a new hearing, so even that file hadn't yet won. Ask counsel what your works council must be told and when.

The Dismissal Protection Act (KSchG) section 23 applies where a business regularly employs more than ten people, for staff hired after 2003. A 12-person team, like the one in the example below, is over that line, so the Act applies. Part-timers count in part, so check the real headcount.

How long does each route take, and what does it cost?

The law gives "reasonable" for the improvement period, not a number. We'd use 8-12 weeks for a senior scope. Take Kasia, a senior backend engineer with seven years' service on a 12-person team, paid an assumed EUR 7,000 a month. Her plan starts in week 0, has a review in week 6, and ends in week 12.

CountryNotice at 7 yearsAfter a failed planAgreed exit
UKPer your contractWeek 12 plus noticeSettlement agreement
NetherlandsTwo months on the scaleCourt decision, then paymentVaststellingsovereenkomst
GermanyTwo months, to month-endWeek 12 plus about two monthsAufhebungsvertrag

Germany's Civil Code section 622(2) scales employer notice by years served. Seven years puts Kasia in the two-month band, so she'd be gone roughly five months from day one, and you carry the gap that whole time.

In the Netherlands, article 7:672(2) also gives two months for five to under ten years. The transition payment under article 7:673 is a third of the monthly wage for each year of service. For Kasia that's 7 x 1/3 x 7,000, or EUR 16,333. The maximum is adjusted each 1 January, so recheck it when you start.

For UK notice, read the contract. In every country, ask counsel for the current court wait before you start the clock.

How do you cover the work while the plan runs?

While the plan runs, Kasia is still at work, so you're covering part of her load rather than an absence. Don't hire into her role during the plan. It tells her, and a judge or tribunal, that the outcome was decided. Instead:

  1. Leave her 100% of a named scope with targets she can reach.
  2. Move her unrelated review load to two other engineers.
  3. Cut one scope item the team can live without.
  4. Put a time-boxed outside engineer on a named piece of work outside her role, if the gap still hurts.

Don't change her targets mid-plan because the team around her changed. A moving standard is the quickest way to lose the record you're building. The mechanics of redistribution, fixed-term cover and interim contractors are the same as in covering for an engineer who is signed off, without the sick-pay rules.

What this means for your improve, move or exit decision

You have three outcomes, and the plan should leave all three open until the week-12 review. Improve: the standard is met, you close the plan in writing, and you tell the engineer so. Move: they're strong in one area and failing in another, so you re-scope with new targets and a new date. Exit: the record is complete, and you choose with counsel between a settlement and the formal route before any notice clock starts.

Do three things this week. Write the standard in one page that a peer would recognise as fair. Put the review dates in the calendar, with the decision at the last one. And fix the cover plan now, because once notice runs you're paying for the gap in both salary and delivery.

For the rest of the people decisions around this one, see engineering management guides for CTOs and VPs of Engineering.

Frequently asked questions

Can you dismiss a senior engineer for poor performance in the UK?

Yes, Acas treats capability as a fair reason. But you can only dismiss if you follow a fair procedure in line with the Acas Code and any capability procedure of your own. Expect informal talks first, then a performance improvement plan with support, written records, and a final written warning before dismissal. Dismissal should be a last resort.

How long should an improvement plan run?

No statute in the three countries gives a number. Acas says a reasonable timeline, Dutch article 7:669(3)(d) says enough opportunity, and the BAG looks at output compared with colleagues. For a senior scope, we'd plan 8-12 weeks with a review at the halfway point.

Can you fire an underperforming engineer without a plan in the Netherlands?

Not on the underperformance ground. Article 7:669(3)(d) requires that you told the engineer in good time and gave them enough opportunity to improve, and the ground goes to the kantonrechter under article 7:671b. The alternative is an agreed exit through a vaststellingsovereenkomst.

Does a German employer need to prove how far below average the engineer is?

The employer has to show output clearly below comparable employees, in the BAG's words well under the average. There's no fixed percentage. The Dismissal Protection Act applies where a business regularly has more than ten employees, for staff hired after 2003. On a small team, ask counsel who counts as comparable.

What happens if the engineer fails the plan?

In the UK, a final written warning, then dismissal if the issue continues. In the Netherlands, a court dissolution request, with the transition payment due, or an agreed exit on negotiated terms. In Germany, notice on the section 622(2) scale, with the employer carrying the burden of proof.

Sources

Share this article

Author Image

HighCircl Editorial Team

The HighCircl editorial team writes about hiring software engineers, nearshore development, and engineering team building. Our articles draw on direct experience sourcing and placing senior developers across Poland, Hungary, Slovakia, Serbia, Slovenia, Romania, and Spain — and on candid conversations with the CTOs and engineering leads who hire them.

HighCircl is a nearshore engineering network that delivers matched candidate shortlists in 72 hours. Every piece of content we publish is informed by real engagement data: actual developer rates, real hiring timelines, and what separates engineering teams that scale cleanly from those that stall.

Take Me to the Experts

Access our network of industry-leading software engineers.

Start Now