By Peter Miller · Published March 24, 2026 · Last updated: September 15, 2026
11 min read · Copy a script, edit three brackets, send
You don't need a clever opener. You need a connection note short enough to read on a phone, one line that proves you read the spec, and a follow-up that gives the recruiter something to paste into Greenhouse or their CRM. Senior engineers, architects, and platform leads with ten-plus years often lose the thread here. The CV is fine. The message reads like a cover letter stuffed into a 300-character box, or it never mentions the system design proof the posting leads with.
Before you send note one, check your resume for free against the same posting. If bullet one on your CV does not name Kubernetes, AWS, or whatever the spec leads with, fix that first. UK recruiters won't chase a strong note when your profile and CV tell different stories.
Job searching at senior level in the UK is already draining. You're qualified. You're also competing with internal moves, contractor benches, and referral stacks. A tight script won't replace a fit gap, but it'll stop you from getting ignored for tone alone. These connection request templates are built for UK corporate tech hiring: agency recruiters, in-house talent partners, and engineering directors who skim on mobile between stand-ups.
You don't need twenty variants. You'll need four connection scripts, two follow-ups, and the judgment to know which one matches a live req, a cold team, or a director you met at a meetup. That's what the sections below walk through.
If the portal already asked for a letter, don't paste your About section into paragraph one. Generate a cover letter that cites the same architecture line you'll use in script two, then stop rewriting.
Send these three pieces first
- Connection request: seniority + one architecture line + connect ask. No CV attachment.
- First follow-up: req link or application reference plus one metric from bullet one.
- Profile headline matches your CV title and primary stack before you hit send.
Why UK recruiters skip the long connection pitch
The symptom looks like ghosting. You sent ten connection requests last week. Two accepted. Nobody replied to your follow-up. So you assume networking does not work for senior IT professionals at your level in the UK market.
Most skipped notes fail on length and proof placement, not on qualifications.
Recruiters and hiring managers open LinkedIn between interviews and stakeholder calls. They are not sitting down to read a mini application in the connection box. A principal engineer who lists every framework since 2008 in note one gets treated like spam even when the delivery record is real. The same person with one line on a cloud migration they led and a clean follow-up after accept often gets a short screen booking.
There is a second failure mode common at senior level: the note is short but hides the architecture proof in paragraph three of your About section. Hi, I am passionate about your company reads empty when twelve other candidates sent the same sentence. You need one object from the posting: team name, platform stack, regulatory domain, or req reference. That object is what makes the message feel like it belongs in their inbox instead of a blast list.
UK hiring adds a third wrinkle. Agency recruiters often represent the same candidate to multiple clients. They need a stack line they can forward without editing. Internal talent partners need a note that matches what Greenhouse or Workday already parsed from your CV upload. When your LinkedIn headline says Head of Engineering but your CV title still says Senior Developer, the note dies in review.
For how recruiters search profiles after you connect, see Greenhouse ATS optimisation for UK IT CVs . The short version: they ctrl-f the stack, then scan tenure and scope. Your note should point them to the same words your CV already uses.
Edge case: you met the hiring manager at a conference or internal tech talk. Lead with that context in sentence one. Do not pretend it is a cold reach when it is not.
Edge case: you are a senior contractor on a notice period. Name the timeline in a follow-up, not the connection request. Urgency in note one reads like desperation even when the deadline is real. IR35 status belongs on the application, not in a 300-character invite.
LinkedIn networking scripts for UK senior IT professionals: connection request templates
Pick the script that matches your situation. Replace every bracket. Keep the body under 300 characters for connection requests. Follow-ups can run slightly longer because they land in a direct message thread after accept.
Script 1: Agency or in-house recruiter, live req you have not applied to yet
Use when the posting is on the careers site and you want a warm path before you upload. Name the req title or reference if it is visible.
Hi [Recruiter First Name], senior [platform/architecture] engineer, [12+] yrs, [Java/Python/Go] on [AWS/Azure]. Your [Req Title / ref] matches the [K8s/data mesh/event] work I led at [Current Employer]. Open to connecting?
Script 2: Recruiter, you already applied in the portal
Use after Greenhouse or Workday shows submitted. The goal is to attach a human face to the application reference.
Hi [Recruiter First Name], applied to [Req Title] yesterday via Greenhouse. Background: [architecture line from bullet one]. Happy to connect and share context if useful for the screen.
Script 3: Engineering director or head of, team-specific hook
Use when you can point to a blog post, talk, or product area they own. Do not use this to bypass HR on a company that routes all inbound through recruiters unless the director invited open DMs.
{`Hi [Director First Name], I lead [platform/domain] at [Employer], mostly [stack] on [product]. Your piece on [topic] matched how we handled [specific problem]. I'd value connecting if senior [role type] opens on your team.`}
Script 4: Informational, no live req
Use for target employers without an open posting. Ask for insight, not a job, in the connection note.
Hi [Name], senior [discipline] engineer in [city/remote UK], focused on [stack]. Researching how [Company] structures [platform/data/SRE] teams. Open to a brief connect? No ask beyond learning.
Follow-up 1: After they accept, no reply yet
Send five to seven business days after accept. Add one new fact they can forward.
{`Thanks for connecting, [Name]. Quick context: at [Employer] I [owned/designed] [scope] on [stack]; [metric] in [quarter/year]. Interested in [Req Title / team] if you're the right contact. CV on request or via the portal.`}
Follow-up 2: Gentle second nudge
One week after follow-up 1. Shorter. Acknowledge they are busy. Close the loop yourself if needed.
{`Hi [Name], circling back once on [Req / team]. If timing isn't right, no worries. I'll stay applied in the portal. Thanks either way.`}
I've screened thousands of inbound LinkedIn threads beside Greenhouse queues for UK tech roles, and the note that moves is the one where I can paste your architecture line and req reference into a hiring manager chat without editing your grammar first.
Copy-paste fill-in sheet (edit every bracket)
CONNECTION (max 300 chars):
Hi [Name], senior [role], [years] yrs, [language] + [cloud].
[Hook: req ref / team / talk]. Open to connecting?
FOLLOW-UP (after accept):
Thanks for connecting. At [Employer] I [designed/led] [scope] on [stack]; [metric].
Targeting [Req / team]. Applied via [portal] on [date] if relevant.
SUBJECT LINE (if InMail):
[Req Title], senior [stack] engineer, applied [date]
Copy-paste the sheet above, then swap brackets for your real stack and req before you send anything.
Read UK CV vs US resume formats when you are also applying to US parents of UK entities. The LinkedIn note stays the same. The CV file you attach in the portal may need a format swap.
Notes that stall before a screen
Even strong candidates lose momentum when the message fights the medium. These pairs show the pattern UK recruiters see most on senior IT outreach.
Connection request: job application vs architecture proof
Before: Hi, I am a highly motivated senior IT professional with a passion for innovative solutions. I would love to pick your brain about opportunities at your company. Please review my CV attached.
After: Hi Priya, senior platform engineer, twelve years Java on AWS. Your Principal Engineer ref (PE-4421) matches the EKS migration I led at Meridian Systems. Open to connecting?
Follow-up: pressure vs context
Before: Any update? I really need this role. Please let me know ASAP. I sent my CV last week.
After: Hi Priya, circling back on Principal Engineer PE-4421. I applied in Greenhouse on Tuesday. At Meridian Systems I cut deploy failures 22% after moving fourteen services to EKS. Happy to share more if you are the right contact.
Director note: vague vs specific
Before: I admire your leadership and would love to join your world-class team. I am a fast learner and team player with extensive experience.
After: Hi James, I own payments platform APIs at Northwind UK, mostly Java and Kafka. Your post on idempotent checkout matched a rollout we shipped in Q2. I'd value connecting if senior backend roles open on Payments.
Profile mismatch: headline vs CV
Before: Headline says Head of Platform Engineering. CV title says Senior Software Engineer with delivery-heavy bullets and no team-scope proof on dated lines.
After: Headline: Head of Platform Engineering · Java · AWS · Kubernetes. About opens with the same migration metric from bullet one. Recruiter sees one story in ten seconds.
Edge case: internal referral already submitted. Tell the recruiter in note one so they do not search twice. Mention the referrer by first name only if they approved it.
Edge case: contract ending in thirty days. You can name the timeline in a follow-up, not the connection request. Urgency in note one reads like desperation even when the deadline is real.
Avoid attaching a PDF in the connection request. Many UK recruiters will not open files from unknown senders on mobile. Save the CV for follow-up or the portal upload they already trust.
Do not send the same script to the recruiter and the hiring manager on the same req the same morning. They compare notes. Pick the entry point that matches how the company routes inbound.
Senior candidates sometimes bury contractor day rates in note one. UK agencies will ask rate and IR35 status after fit is clear. Leading with numbers before stack proof filters you out for the wrong reason.
Align the message with a forwardable CV
A clean note dies if the recruiter opens your profile and cannot find the architecture line you promised. Upload the same file you would send in Greenhouse and run a free ATS check on the posting. Confirm Java, Kubernetes, or the lead requirement shows inside extracted experience text, not only in your About section.
Fix bullet one before you network. The message should point at a line the parser can read.
When you are choosing which reqs deserve an hour of outreach tonight, score your job match on the posting first. A 90-character note cannot fix a skill gap on a principal platform req if your last three years were frontend-heavy.
Send one note tonight
Open the strongest req on your list. Copy script one or two. Replace the brackets with your real stack, employer, and req title. Send the connection request without attaching a file.
Set a calendar reminder for five business days out with follow-up one drafted. If they accept sooner, send it that afternoon with one metric from bullet one. Stop after two unanswered follow-ups on the same thread.
Job searching is already hard at senior level. You do not need a personality rewrite. You need a short note that matches the CV a recruiter can forward. When the wording on the file still feels off, check your resume for free against the same posting before you paste the architecture line into script two.
Frequently asked questions
Stay under 300 characters in the connection request box. Lead with seniority, one architecture or platform line from your CV, and a hook tied to their posting or team. Save the CV ask for after they accept. UK agency recruiters often triage on mobile between calls. A wall of text in the invite gets skipped even when your tenure is real.
Message the recruiter when the role is live on the careers site or you already applied through Greenhouse or Workday. Message the hiring manager when you have a specific team hook, a referral, or a talk they gave that matches your delivery work. Do not send the same script to both on the same day. UK employers route inbound differently. Pick one entry point.
No on the connection request. Answer contract status and right to work accurately on the application or when the recruiter asks. Mention remote or hybrid only when the posting or profile makes location a clear filter. Senior contractors lose momentum when note one reads like a rate card before anyone knows the stack fit.
Yes. Headline, current title, and the first two lines of your About section should mirror bullet one on your CV. UK recruiters open your profile within seconds of a decent note. If your headline says Head of Platform but your CV leads with hands-on Java delivery, they pause. Align the files before you send script one.
Wait five to seven business days after they accept the connection, or seven to ten days after an InMail if they never accepted. Send one follow-up with a new fact: req number, a migration you led, or a metric from bullet one on your CV. A second follow-up a week later is fine. Stop after two unanswered notes on the same thread.