12 min read
Your connection request gets accepted. Your follow-up sits unread through sprint planning. That usually means the message reads like a cover letter stuffed into chat. It doesn't mean US tech hiring stopped replying to qualified profiles.
You're not invisible. You're asking for time without giving a recruiter a ten-second reply path. Corporate tech recruiting runs on req IDs, Greenhouse scorecards, and calendar math. Your note has to snap to the same row they'd search in the ATS.
Before you send another paragraph, check your resume for free against the posting. If your best proof only lives in Skills and not under a dated employer line, no script saves a thin file.
This page gives teardown pairs you can paste tonight for software, product, data, and support tracks. You'll see what weak versions share, plus a skeleton you can reuse without sounding like a bot.
When the portal wants a letter after you message someone, don't dump your Skills block into paragraph one. Generate a cover letter that cites one metric from your resume, not a buzzword list you never shipped in production.
Job searching while your current team ships on-call rotation is draining. Good outreach shares one proof line and a light ask. You won't feel less stuck by sending ten vague notes. You'll feel progress when one thread gets a factual reply.
Recruiters aren't offended by follow-ups. They're offended by follow-ups that add zero new information. Treat each touch like an update, not a reminder that you exist.
Quick Wins
- Apply in the portal before you chase inbox replies.
- Cut drafts to four lines readable on a phone.
- Quote one stack or scope outcome from your current role.
- Ask a yes-or-no question, not a thirty-minute call.
What US tech recruiters judge in the first scroll
Readers scan for proof, req context, and a reply they can send between meetings. That's the bar from seed-stage startups to public SaaS shops running Workday. Mid-level engineers and PMs report the same symptom: accepts pile up, threads stay quiet. The resume often clears the portal screen. The inbox stays cold anyway.
Good templates are not longer. They're tighter. Personalization means one detail about their req, team, or launch, not a paragraph about their stock chart. Clarity means the reader knows which track you want without opening an attachment.
Corporate recruiting still runs through Greenhouse, Lever, Workday, and iCIMS behind the careers page. Your message is a side door to the same proof the portal will parse. If the two stories diverge, the human reader notices fast.
Edge case: you're targeting a staff-plus req with staff-level bullets. Don't message a senior title with principal scope unless your dates and scope lines support it. Recruiters flag title inflation before they forward to hiring managers.
Edge case: you're employed and searching quietly. Peer notes should ask about team rhythm or on-call load, not announce you're miserable. Referrers stall when the note sounds like a broadcast.
For how resume and profile should align before outreach, read resume vs profile: what must match and what doesn't . This page assumes your headline title is honest and focuses on the message layer.
Visa sponsorship questions belong early when the posting says no sponsorship. Don't hide work authorization in paragraph four. Recruiters would rather decline fast than discover mismatch after a final loop.
LinkedIn networking scripts for US tech recruiters: six teardown pairs
Each pair is a candidate note to a recruiter or hiring partner. Swap names and metrics with your real proof. Keep the shape.
Pair 1: Corporate recruiter after you applied (backend)
Before: Hi, I'd love to connect about engineering roles at your company. I'm passionate about building scalable systems.
After: Hi Morgan, I applied for Backend Engineer (req ENG-8842) yesterday. I own the payments API on Java and cut p99 latency on checkout by refactoring retry logic in Q2. Are you the right contact for application status?
Pair 2: Startup recruiter on a live full-stack req
Before: Hello, I'm very interested in your startup and would love to pick your brain over coffee.
After: Hi Dev, I applied for Full Stack Engineer (req FS-1190). I shipped a Next.js admin console with role-based auth for an internal ops team of twelve. Still reviewing candidates who list TypeScript on the first screen?
Pair 3: Product manager targeting B2B SaaS
Before: Hey, can you refer me to any PM roles? I'm looking for new opportunities in product.
After: Hi Priya, I applied for Product Manager, Integrations (req PM-3301). I led a Salesforce connector launch that moved activation from week three to day five for mid-market accounts. Is email better than Greenhouse messaging for status on this req?
Pair 4: Data analyst on a hybrid analytics seat
Before: Fellow data person here! Would love to connect and learn about your analytics team.
After: Hi Chris, I applied to Senior Data Analyst (req DA-5520). I built weekly churn dashboards in Looker and paired with CS on a save playbook that cut reactive tickets in one quarter. Does your team still prioritize SQL plus a BI tool on first review?
Pair 5: Customer support lead moving into CS ops
Before: Hi, I'm interested in customer roles at your company and would love to connect.
After: Hi Jordan, I applied to Customer Success Manager (req CS-7718). I managed Zendesk queues for a B2B SaaS tier with CSAT in the mid-nineties and WFM adherence in the high nineties on my last review cycle. Welcome notes from candidates with support-to-CS moves?
Pair 6: Security engineer on a compliance-heavy req
Before: Hello, I'm a security professional seeking new challenges. Let's connect!
After: Hi Alex, I applied to Security Engineer (req SEC-2044). I ran annual SOC 2 evidence collection and automated access reviews with Okta workflows for a two-hundred-person product org. Should I expect a technical screen before the hiring manager chat on this loop?
When not to send a script yet
Skip outreach when your resume still fails a plain-text paste test. If employer names shuffle in Notepad, fix the file before you tell a recruiter you applied. Skip outreach when the posting closed unless you saw a repost with a new req number. Skip outreach when you have zero proof line for the stack in the ad. Build one bullet first, then message.
Edge case: the contact is a recruiter you already emailed twice this month on different reqs. Space touches. A third identical bump on the same thread burns the relationship for roles you might fit later.
Edge case: you're messaging during a company-wide hiring freeze rumor week. One factual note is fine. Five pings across executives reads like pressure, not proof.
I've screened US tech pipelines where the candidate's message quoted Kubernetes ownership while the resume still showed ticket-queue work without container terms. The mismatch ended the thread before anyone opened the PDF.
Copy-paste block: four-line skeleton
{`Hi [First name],
[One proof line: stack, scope, or outcome tied to their req or team.]
[One sentence: why you're writing + yes-or-no question for mobile reply.]
Thanks,
[Your name]`}
Follow-up pair: one polite bump after you applied
Before: Just following up on my last message. Still interested in chatting!
After: Hi Morgan, quick bump after I applied to req ENG-8842 on Tuesday (confirmation #GH-44102). Happy to send a single-column PDF if the portal mangled formatting. Should I wait for Greenhouse status or is email better for your team?
Read how to follow up after applying timing script when you're lining up portal submissions and messages. The cadence still applies when the recruiter sits in another time zone.
Staff and principal reqs need scope language in line two. Mention systems you designed, teams you mentored, or incidents you led, not only tickets you closed. Keep dates honest.
New grad outreach should cite one internship or project with deployable output. Professors' names don't replace shipped code or customer-facing work when the req says zero to two years.
Contract-to-hire notes should ask whether the role converts and whether benefits start day one. Ambiguity burns candidates who quit contract gigs for promises that never papered.
Internal transfers sometimes require a different template. Mention your current team, tenure, and the internal req ID. External cold scripts sound odd to internal mobility partners.
Recruiter inboxes during conference week are brutal. Short notes win. If they post that they're traveling, wait until they're back unless the req closes imminently.
Don't open with apologies for bothering them. Open with context they can verify. Confidence without proof is noise. Proof without arrogance is rare.
If you lack a req number, cite the exact title from the careers page and the date you applied. Vague role names create duplicate searches and slow replies.
Emoji-heavy messages read younger than some enterprise cultures tolerate. Plain text and periods are fine. You're not texting a friend; you're asking for a routing decision.
What weak cold messages to recruiters share
Before: Candidate sends a three-paragraph career biography with no req ID and asks for any open role.
After: Candidate names one posting, one proof line, and asks whether they're in the right queue for that req.
Attaching resumes before anyone asks. Mobile readers skip attachments. Portal uploads are the source of truth. Offer a PDF only when parsing failed or the recruiter requests it.
Before: Message claims ten years of Kubernetes leadership while the profile shows one migration project as a participant.
After: Message describes the migration slice owned, team size, and rollback plan without inflating title or tenure.
Mass-blasting the same script with find-and-replace company names. Recruiters talk. Identical structure across ten firms in one week gets remembered for the wrong reason.
Asking for referrals before rapport exists. Referral asks belong after a factual exchange, not in message one to a stranger.
LinkedIn networking scripts for US tech recruiters fail when they sound like marketing copy. Strip adjectives. Keep verbs, tools, and dates.
Don't argue compensation in message one unless they invited it. Salary threads belong after screen progress or in the recruiter screen slot, not in a cold connection note.
Match resume proof before you hit send
Run the same file through parsing checks after every portal upload. Run HireFlow's ATS checker on the PDF you'll quote in message two so column breaks don't hide your best bullet.
When you're choosing which reqs deserve a personalized note, score your job match on the posting first. High overlap plus a thin message is still thin. Low overlap plus a great message wastes everyone's time.
Do this now: Apply in the portal, copy confirmation, draft four lines with one proof sentence, send once, schedule one follow-up date with new info only.
Send one tight note tonight
LinkedIn networking scripts for US tech recruiters aren't magic words. They're proof, context, and a question someone can answer without opening three tabs.
Pick one live req. Apply. Draft four lines. Send. Log the confirmation. Set a single follow-up date with new information, not the same plea.
When a thread goes quiet, improve the resume bullet you quoted, not the adjectives around it. Recruiters forward files that match the story you already told in chat.
Run a free ATS check before your next batch of messages so every proof line you cite survives parsing.
Searching while employed means every note should respect discretion. Searching while unemployed means every note should respect your energy. One good req beats ten spray-and-pray drafts.
Save templates in a notes app with blanks for req ID and proof line only. Fixed prose everywhere else keeps you fast without sounding cloned.
When someone replies, answer in the same channel with the same brevity. Long replies after a short ask feel like a different person showed up.
Track touches in a simple spreadsheet: company, req, date, proof line used, reply yes or no. Patterns emerge faster than memory after thirty applications.
Read more
Frequently asked questions
Four to six lines on a phone screen. Line one is their name. Line two is one proof sentence from your resume with employer context and a tool or outcome. Line three names the req, title, or team. Line four is a yes-or-no question they can answer between meetings. Attachments on first touch get skipped. Offer a PDF only if they ask or if the portal failed to upload.
Apply first when the req is open, then message within twenty-four hours with the confirmation number or req ID if you have it. Recruiters match threads to rows in the ATS. Messaging before you apply can still work on niche reqs, but you should say you will submit the same day so your name lands in the system they search.
Yes when the posting names them or their team publicly and your note is narrow. Lead with scope fit, not a request for coffee. Many managers forward to recruiting anyway. If they reply apply online, do it immediately and reference the thread in your cover letter. Do not cc five executives to create pressure.
Send one follow-up with new proof or the portal confirmation, not the same paragraph. Wait at least five business days unless they gave a different timeline. Two touches on the same req per month is a reasonable ceiling. Silence after that means move on or target a different req. Persistence without new information reads like spam.