11 min read
Put your job title, contractual notice, and calendar last day in the first paragraph as plain text. That's what UK HR teams file when payroll closes and references get updated. Mid-level engineers and product folks often send warm Slack goodbyes and forget the dated record people ops actually searches later.
You're not writing for a job-application parser. You're writing so an admin can copy dates into Workday, Personio, or BambooHR without opening a thread to ask which Friday you meant. Graceful exits start with boring clarity, and you won't regret being the person who made payroll's job easy.
If your contract's notice clause feels fuzzy, don't guess in the letter. Ask people ops for the calendar end date before you tell the team. It's slower by one day and faster by a month when nobody disputes what you meant.
If you're already updating your CV for the next search, check your resume for free while notice runs. Leaving clean and landing clean often happen in the same month.
Below: why plain structure matters in UK tech offboarding, the exceptions that change notice, what to do this week, templates you can paste, and mistakes that burn references after you've already decided to go.
You don't need legal Latin or a signature stamp unless HR asks. You do need a date your manager and payroll can repeat without guessing. That's the whole bar for mid-level tech exits in London, Manchester, Edinburgh, and remote UK contracts alike.
Quick Wins
- Last day as Friday, 17 October 2026, not in two weeks.
- Notice length in words plus dates: one month's notice ending …
- Manager conversation first, identical text to HR email second.
- Single-column DOCX or email body; skip letterhead graphics.
Why UK tech teams need machine-readable resignation text
Offboarding in UK tech still runs through people teams who tag leavers, freeze access, and confirm P45 timing. When your resignation arrives as a screenshot or a decorative PDF, someone retypes the dates. Typos become payroll disputes. References stall because HR notes never matched what your manager heard.
Plain text is the ATS-friendly part. Not keyword stuffing. Predictable labels: Name, Role, Notice, Last working day, Transition. Those strings paste into HRIS comment fields and survive forward searches when a future employer verifies tenure.
Mid-level ICs sit in the messy middle. You're not exec-level with lawyers drafting garden leave. You're not junior with a same-day walkout. You own repos, on-call rotations, and sprint commitments. A clear letter sets the handoff window managers need.
Contract notice beats politeness. If your agreement says one month, the letter should say one month and show the calendar end date that satisfies it. Statutory minimums matter when contracts are silent, but most UK tech contracts are not silent.
Read resignation letter templates for US employees only if you're comparing tone. UK letters stay shorter and date-forward. US at-will framing does not apply.
Equity and unvested grants don't belong in resignation prose unless legal already sent you wording. Mid-level tech staff often panic and overshare in paragraph two. Keep paragraph two about tickets and access, not cap tables.
Hybrid workers: list your primary work location country in the letter header if HR templates ask for it. Remote doesn't mean dateless. It means your dates still anchor payroll in the entity that employs you.
ATS-friendly resignation letters UK mid-level tech: field order
Use this order so HR can skim top to bottom without hunting. Each line is one idea. No bullet grids in the PDF you attach.
- Statement of resignation with exact job title.
- Notice period in words tied to contract.
- Calendar last working day (weekday, day month year).
- One sentence offering transition and documentation.
- One gratitude line. Close with your name.
Template A: one-month notice (common)
Before: "Hey team, moving on soon, thanks for everything, let's chat."
After: "I am resigning from my position as Backend Engineer. I am giving one month's notice in line with my contract. My last working day will be Friday, 28 November 2026. I will document open tickets and pair on handoff during notice."
Template B: shorter notice by agreement
Before: "I'd like to leave ASAP; hope that's OK."
After: "Following our conversation today, I confirm resignation from my role as Product Designer. We agreed two weeks' notice; my last working day is Friday, 3 October 2026. I will finish the checkout redesign spec and transfer Figma ownership before then."
Copy-paste block: UK tech resignation email to HR
{`Subject: Resignation – [Your Name] – [Job Title]
Dear [HR or People Team],
I am writing to confirm my resignation from the position of [Job Title]
at [Company], effective with one month's notice per my contract.
My last working day will be [Weekday], [Day] [Month] [Year].
I will work with [Manager Name] to hand over [systems/repos/on-call]
and document open work before that date.
Thank you for the opportunity to contribute to the team.
Kind regards,
[Your Name]`}
Exceptions that change the letter
Garden leave or payment in lieu: only include language HR or legal already approved. Don't invent PILON in the letter without written agreement.
Visa or sponsorship ties: follow people-team guidance on timing. The letter still needs dates; the conversation may need to precede the email.
Redundancy or settlement talks: use HR-drafted wording. This page is for standard voluntary resignations by mid-level tech staff.
I've seen reference checks drag because HR stored a vague "end of month" line while the manager remembered a different Friday. The employee wasn't difficult. The letter left room to argue.
Remote UK roles with EU colleagues: still use UK date format in the letter HR files locally. Slack timezone jokes don't replace dated text in the people record.
Template C: on-call and production handoff
Mid-level SRE and platform engineers should name on-call rotation end date in the transition sentence. Don't assume HR knows your pager schedule.
Before: "I'll wrap things up before I go."
After: "I will complete on-call through Sunday, 12 October 2026, document runbooks for payments alerts, and transfer admin access to [Name] by my last working day, Friday, 17 October 2026."
What to do during notice week by week
Week one: send the dated letter, confirm HR received it, list repos and credentials you'll transfer. Week two: finish documentation tickets before you announce side projects. Final week: return kit, export personal files per policy, and don't ghost standups because you're mentally gone.
Managers remember who made handoff easy. That memory becomes the reference sentence when your next employer calls. The letter sets the tone; your ticket hygiene proves it.
Keep resignation email subject lines boring: Resignation, your name, job title. HR inboxes search those strings. Creative subjects delay filing.
If you're on probation, notice may be shorter. Say so explicitly: "I am resigning during probation with one week's notice per my contract." Probation exits still deserve dates, not vibes.
Where graceful UK tech exits turn messy
Resigning only in chat. Managers forget dates. HR never gets a searchable record.
Decorative PDFs with logos and columns. They look professional and paste poorly into HRIS notes.
Negative storytelling. Grievances in writing follow you. Keep venting for trusted peers offline.
Announcing before you have a calendar last day. Teams plan sprints around fiction until you name a date.
Before: resignation email lists every frustration with leadership.
After: same facts as Template A with one neutral gratitude line.
This won't fix a toxic team or rewrite a bad notice clause in your contract. It stops your exit record from being the thing that slows payroll and weakens the reference your next hiring manager requests.
Read how to follow up when you applied via Lever US when you're job hunting during notice. Different channel, same rule: dated, plain language wins.
Before: resignation sent only to manager on WhatsApp.
After: manager conversation, then identical text to people@company with manager on CC and calendar invite for handoff checkpoints.
Stock options, bonus windows, and unused holiday payout vary by employer. The letter doesn't negotiate those items. It triggers the process. Follow HR's calculator email without debating in the resignation paragraph.
If you're union-covered or have collective terms, use rep-approved wording. This guide targets standard UK tech employment contracts for individual contributors.
Equipment returns matter for mid-level staff with test devices and YubiKeys. Mention you'll return kit in the transition sentence so security doesn't chase you on your last afternoon. That's not ATS parsing. It's the operational half of a graceful leave.
Open-source maintainers: note whether you'll transfer repo admin in the handoff line. Companies care about continuity when your GitHub handle owns a public SDK they depend on.
Prep your next application file
After you send the letter, refresh your CV in a single-column layout and run a free ATS check on the export you'll use for UK and remote reqs during notice.
If a posting asks for a short cover note, generate a cover letter from the job description while your handoff docs are top of mind. Keep resignation tone out of application tone.
Send checklist
ATS-friendly resignation letters for UK tech mid-level staff are short, dated, and identical in the manager talk and the HR email. That's the whole trick.
- Confirm notice length in your contract.
- Calculate calendar last day before you speak to your manager.
- Paste Template A or B, adjust brackets, read once aloud.
- Email HR with the same text the same day.
Name the Friday on paper first. Then plan the handoff like the professional you want referenced next quarter.
Archive a copy of the sent email outside company mail before access shuts off. You'll need exact dates for the next background form, and memory lies about which October Friday you picked.
Update your CV end date to match the letter the same evening. Mismatched end months between CV and HR record confuse recruiters six months later when they verify tenure.
And if you're nervous about the manager conversation, script two sentences aloud: why you're leaving at a high level, and the calendar last day. The letter can stay warmer than the speech, but the dates must match.
Read more
Frequently asked questions
Job-application ATS parsers are not the same stack that stores offboarding, but many UK employers attach resignation PDFs to HRIS employee records. Plain headings, one column, and explicit dates help HR admins tag leavers correctly. A messy layout does not block your exit; it slows payroll and reference updates while someone retypes your dates.
Follow your contract first. One month is common in UK tech; some startups ask for two weeks, others for three months for senior ICs. Statutory minimum notice depends on length of service. Name the calendar last working day that matches your contractual notice, not a vague soon.
Tell your line manager in a live conversation when you can. Send the same text by email to HR or people ops with your manager copied if policy asks. The email body should match the letter: title, notice length, last day, transition offer. Attach a simple PDF only if HR requests a signed copy.
You don't need to. UK letters work best with role, notice, last day, and handoff. If you mention a new company, keep it one neutral line. Save negotiation about garden leave or equipment return for HR, not paragraph two.
Use standard section labels, left-aligned text, no tables or logos, and dates written as day month year. Include employee name, job title, department if helpful, notice period in words and dates, and a single transition sentence. That structure copies cleanly into HRIS notes and searchable employee files.