By Peter Miller · Published August 10, 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 req, and a follow-up that gives the recruiter something to paste into Greenhouse or Workday. Mid-level engineers with four to seven years of backend, platform, or full stack work often lose the thread here. The resume is fine. The message reads like a cover letter stuffed into a 300-character box, or it never mentions the stack the posting leads with.
Before you send note one, check your resume for free against the same posting. If bullet one does not name Python, AWS, or whatever the req leads with, fix that first. Recruiters will not chase a strong note when the profile and resume tell different stories.
Job searching at mid level is already draining. You're qualified. You're also competing with internal transfers and referral stacks. A tight script won't replace a fit gap, but it'll stop you from getting ignored for tone alone. These templates are built for US corporate tech hiring: agency recruiters, in-house talent partners, and engineering managers who skim on mobile between meetings.
And 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 manager 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 stack line you'll use in script two, then stop rewriting.
Send these three pieces first
- Connection request: role + one stack line + connect ask. No resume attachment.
- First follow-up: req link or application ID plus one metric from bullet one.
- Profile headline matches your resume title and primary stack before you hit send.
Why 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 software engineers at your level.
Most skipped notes fail on length and timing, not on qualifications.
Recruiters and hiring managers open LinkedIn between interviews. They are not sitting down to read a mini cover letter in the connection box. A mid-level backend engineer who lists every framework since college in note one gets treated like spam even when the tenure is real. The same person with one line on Kubernetes cost work and a clean follow-up after accept often gets a five-minute screen booking.
There is a second failure mode: the note is short but generic. 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, cloud stack, product surface, or req number. That object is what makes the message feel like it belongs in their inbox instead of a blast list.
For how recruiters actually search profiles after you connect, see why your resume is not making the shortlist . The short version: they ctrl-f the stack, then scan tenure. Your note should point them to the same words your resume 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: the recruiter posted the req on LinkedIn but the apply button goes to Workday. Mention you plan to apply through the portal and ask if they prefer a heads-up with the req ID. That saves them from searching your name twice.
LinkedIn networking scripts for software engineers: connection and follow-up 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: 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 number if it is visible.
{`Hi [Recruiter First Name], I'm a mid-level [backend/platform] engineer with [4-6] years in [Python/Go/Java] and [AWS/GCP]. Your [Req Title / #12345] lines up with the [Kubernetes/ECS] work I shipped at [Current Company]. Open to connecting?`}
Script 2: Recruiter, you already applied in the portal
Use after Workday or Greenhouse shows submitted. The goal is to attach a human face to the application ID.
Hi [Recruiter First Name], I applied to [Req Title] yesterday (application #[ID] if you have it). Background: [stack line from bullet one]. Happy to connect and share context if useful for the screen.
Script 3: Hiring manager, 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 manager invited open DMs.
{`Hi [Manager First Name], I lead [scope] at [Company], mostly [stack] on [product surface]. Your piece on [topic] matched how we handled [specific problem]. I'd value connecting in case a [role type] opens on your team.`}
Script 4: Informational, no live req
Use for target companies without an open posting. Ask for insight, not a job, in the connection note.
{`Hi [Name], mid-level [discipline] engineer in [city/remote], focused on [stack]. I'm researching how [Company] structures [platform/data/mobile] teams. Would you be open to a 15-minute 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 [Company] I [verb] [scope] on [stack]; [metric] in [quarter/year]. I'm interested in [Req Title / team] if you're the right contact. Resume attached here only if you want it. Otherwise I'll keep everything in 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, and the note that moves is the one where I can paste your stack line and req number into a hiring manager chat without editing your grammar first.
Copy-paste fill-in sheet (edit every bracket)
CONNECTION (max 300 chars):
Hi [Name], mid-level [role], [years] yrs, [language] + [cloud].
[Hook: req # / team / talk]. Open to connecting?
FOLLOW-UP (after accept):
Thanks for connecting. At [Company] I [built/owned] [scope] on [stack]; [metric].
Targeting [Req / team]. Applied via [portal] on [date] if relevant.
SUBJECT LINE (if InMail):
[Req Title], [stack] engineer, applied [date]
Copy-paste the sheet above, then swap brackets for your real stack and req before you send anything.
Read how to network without feeling awkward when you need a lighter tone for alumni or former coworkers. The structure stays the same. The opener gets warmer.
Notes that stall before a screen
Even strong candidates lose momentum when the message fights the medium. These pairs show the pattern recruiters see most on mid-level engineering outreach.
Connection request: pitch vs proof
Before: Hi, I am a highly motivated software engineer with a passion for innovative solutions. I would love to pick your brain about opportunities at your company. Please review my resume attached.
After: Hi Maya, mid-level backend engineer, five years Python on AWS. Your Platform Engineer req (#8842) matches the EKS work I shipped at Cedar Labs. Open to connecting?
Follow-up: pressure vs context
Before: Any update? I really need this role. Please let me know ASAP. I sent my resume last week.
After: Hi Maya, circling back on Platform Engineer #8842. I applied in Greenhouse on Tuesday. At Cedar Labs I cut deploy failures 22% after moving fourteen services to EKS. Happy to share more if you are the right contact.
Hiring manager 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.
After: Hi James, I own payments APIs at Northwind, mostly Java and Kafka. Your post on idempotent checkout matched a rollout we shipped in Q2. I'd value connecting if backend roles open on Payments.
Profile mismatch: headline vs resume
Before: Headline says Senior Full Stack Engineer. Resume title says Software Engineer II with backend-heavy bullets and no React proof on dated lines.
After: Headline: Software Engineer II · Python · AWS · Kubernetes. About opens with the same 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 recruiters will not open files from unknown senders on mobile. Save the resume 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.
Align the message with a forwardable resume
A clean note dies if the recruiter opens your profile and cannot find the stack you promised. Upload the same file you would send in Greenhouse and run a free ATS check on the posting. Confirm Python, Go, 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 staff-level platform req if your last three years were frontend-heavy.
For project proof US tech recruiters actually click on, see full stack resume projects that US recruiters like . Link one repo in follow-up only when the readme shows the same stack as the req.
Send one note tonight
Open the strongest req on your list. Copy script one or two. Replace the brackets with your real stack, company, 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 mid level. You do not need a personality rewrite. You need a short note that matches the resume 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 stack line into script two.
Frequently asked questions
Stay under 300 characters in the connection request box. Lead with role fit and one stack line tied to their company or posting. Save the resume ask for after they accept. Long pitches in the invite get skipped because recruiters cannot forward a wall of text to a hiring manager from a phone.
Message the recruiter when a req is live on the careers site or you already applied in Greenhouse or Workday. Message the hiring manager when you have a specific team hook, a referral, or you applied and want context on stack scope. Do not send the same script to both on the same day. Pick one entry point.
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 shipped feature, or a metric from bullet one on your resume. A second follow-up a week later is fine. Stop after two unanswered notes on the same thread.
No on the connection request. Recruiters filter those in the ATS after you apply. If work authorization is a hard gate for the role, answer it accurately on the application. Mention remote or relocation only when the posting or their profile makes location a clear filter.
Yes. Headline, current title, and the first two lines of your About section should mirror bullet one on your resume. Recruiters open your profile within seconds of a decent note. If your headline says full stack but your resume leads with platform work, they pause. Align the files before you send script one.