12 min read
You found a req that fits. You don't see a name on the posting. That's normal in US corporate hiring. The person who'll say yes or no in the panel often never appears on the careers page. You still need them on your radar because recruiters sort portal rows first, and a manager nudge can move a clean file up the stack.
Before you rewrite your summary for the tenth time, check your resume for free on the PDF you will upload. Managers who reply still forward files into Workday or Greenhouse. A pretty profile with a scrambled resume ends the conversation fast.
Job searching is exhausting. This page isn't a pep talk. It's a sequence you can run in one evening: read the posting like a recruiter, submit one application, find the likely boss on the company profile, and draft a note you wouldn't be embarrassed to show a friend.
You won't need paid search tricks or a spreadsheet of five hundred names. You'll need focus on one employer, one req, and one leader who actually owns the work described in bullet one of the job ad.
When the portal asks for a letter, generate a cover letter that uses the same employer spelling and Month Year dates as your resume so nothing contradicts when the manager opens both files.
Quick Wins
- Highlight every team, product, and location string on the posting before you search.
- Apply once in the portal the same day you plan to message.
- Filter company People by current employer plus manager titles, not generic HR keywords.
- Keep note one under six sentences with one proof line, no attachment.
Who owns the hire vs who screens the pile
Recruiters move rows. Hiring managers pick teammates. In most US reqs, a Talent Acquisition partner posts the job, runs knockout questions, and keyword-searches Workday. The hiring manager runs the panel, sets the bar for skills, and often has veto power after phone screens.
Messaging only the recruiter is fine when you are unsure who leads the team. Messaging the likely manager can work when you have a tight match and a specific question about the role. Both paths still need a portal row for compliance in large employers.
A composite product analyst kept pinging HR generalists while the Engineering Manager for the billing squad sat two clicks away on the company page. The HR inbox ignored generic interest. The manager replied when the note named the revenue APIs in bullet one of the posting and cited a public GitHub repo tied to the same stack.
Titles lie sometimes. A Director of Operations might hire coordinators. A VP might delegate first screens. Read the posting reporting line. If it says you will report to the Senior Manager of Customer Success, that Senior Manager is your primary target, not the CMO three levels up.
Public posts help you sanity-check the choice. A leader who shares release notes for the same product named in the req is a stronger target than someone who only reshares company culture graphics. You're looking for proof they touch the work, not proof they have a large follower count.
And if you are tempted to skip the portal because a friend said managers hate ATS, pause. Managers still ask recruiters whether you applied. One clean upload plus a short note beats a clever workaround that leaves no row to search.
For timing after you submit, read how to follow up after applying in the US . Follow-up rules apply whether the reader is a recruiter or the hiring manager.
How to find hiring managers on LinkedIn (US method) in five passes
Work in order. Searching profiles before you understand the team string wastes an hour and produces the wrong VP.
Pass 1: Strip team clues from the posting
Copy the job description into a doc. Highlight department names, product names, tools, location, and phrases like reports to or partners with. Those strings become your People filters. If the req says Revenue Operations supporting Salesforce CPQ, you are not messaging a generic Sales Director at random.
Before: Searched hiring manager plus company and opened the first VP profile with a fancy headline.
After: Listed RevOps, CPQ, and billing squad from the posting, then searched managers in that function only.
Save the req ID or URL in the same doc. You will paste that ID into your note so the manager can find your portal row without guessing which of twelve reqs you mean.
Pass 2: Submit one portal application first
Open Workday, Greenhouse, Lever, or iCIMS from the official careers link. Upload a single-column PDF or clean DOCX. Fill skill boxes with exact tool names from the posting. Knockout answers must be honest. You want your name searchable inside the req before any human reply.
Before: Sent five connection requests with resume PDFs attached and never clicked Apply.
After: One portal submit with req ID saved, then outreach the same afternoon referencing that req.
Recruiters match notes to rows by name and req. If you only exist in an inbox attachment, you are harder to slot into the compliant pipeline. Apply first when the button exists.
Pass 3: Filter company People by title and location
On the employer profile, open People. Add filters for current company, United States location when the req is US-based, and title keywords from pass one. Try Engineering Manager, Director of Product, Head of Analytics, or whatever matches the seniority on the posting.
Scroll past recruiters temporarily. Look for leaders whose About section mentions building teams in the same product area. Mutual connections are a bonus, not a requirement. A specific question beats a warm intro that says nothing about the role.
Before: Messaged a Talent Acquisition partner who posts thirty reqs a week.
After: Messaged the Senior Manager whose team list includes engineers on the same product named in the job ad.
Pass 4: Confirm hiring manager vs recruiter vs HR partner
Recruiter headlines usually say Talent Acquisition, Recruiting, Sourcer, or HR with many open roles listed. Hiring managers show years in the department, engineer or analyst career paths, and bullets about roadmaps or P and L. HR business partners support people programs but rarely own technical bar raisers.
When two profiles look close, pick the person whose recent posts mention the product line from the posting. Still unsure? Message the recruiter with one sentence asking who leads interviews for that team. That is not weak. It is precise.
I've watched managers ignore polished pitch decks but reply to a three-line note that named the req ID and quoted one metric from the posting in plain language.
Pass 5: Send one proof-led note
Connection requests allow a short note. Use it. Name the req title or ID, cite one proof line that mirrors a must-have from the posting, and ask one question about team priorities. No resume attachment on note one. No calendar link. No paragraph about your entire career.
Before: Hi, I am passionate about your mission. Please review my background.
After: Hi [Name], I applied to Req 1842 for Senior RevOps Analyst. I built CPQ rules in Salesforce for a subscription billing team. What is the first problem this hire would own in the first ninety days?
Copy-paste connection note (edit brackets)
Hi [First name], I applied to [Job title, Req ID if you have it] today.
[Bullet-sized proof line tied to one must-have from the posting.]
Quick question: [One sentence about team priority or stack.]
Thanks for any insight you can share.
Follow up once after seven to ten days with one new fact, such as a shipped project or a certification finished since your first note. Do not resend the same block.
If the manager accepts but does not reply, do not send a second novel. Like one relevant post they wrote, then wait. Silence after two polite touches means move on to the next req instead of camping in their inbox.
Keep a simple log with company, req ID, manager name, date applied, and date messaged. When a recruiter calls weeks later, you'll remember which proof line you promised in note one and won't contradict yourself on the phone screen.
Edge case: posting lists a staffing agency
When the employer of record is a agency brand, search the end client named in the description for People filters, but apply through the agency link if that is where the contract req lives. Your note should name the client team, not pretend you already work there.
Edge case: company hides most employee profiles
Use a search engine with site:linkedin.com/in plus the company name and a title keyword from pass one. Check the corporate blog for webinar speakers in that division. Connect with one line referencing that public talk. You still complete the portal application so recruiters have a row to attach to your name.
For alignment between posting keywords and your file before managers ask for a PDF, see why your resume is not getting interviews . Proof in Experience beats a keyword cloud when a manager forwards your resume to a recruiter.
Outreach habits that get ignored fast
Mass connection blasts with no req context. Managers and recruiters read the first sentence. If it could go to any company, it goes nowhere.
Attaching a resume on note one. Wait until someone asks. Inboxes treat unexpected attachments as risk.
Conflicting titles between profile and portal. If your LinkedIn headline says Product Manager but you applied as Product Owner, humans pause. Match strings before you scale outreach.
Messaging the CEO for a mid-level req. Escalation feels clever. It usually lands in an assistant queue. Stay one to two levels above the role, not five.
Asking for an interview in note one. Questions about team stack or first-quarter priorities invite replies. Demands for calendar time read like spam even when your resume is strong.
Before: Sent the same paragraph to twelve leaders at the company in one hour.
After: Picked two likely managers tied to the posting team string and personalized the proof line for each.
This will not fix applying to roles where honest knockout answers fail. It stops qualified candidates from staying invisible because they never tied a clean portal row to a human name.
Match resume proof before you message
Run the posting and your export through score your job match before you cite a proof line in a note. If the tool flags a missing must-have, add it to a dated bullet first, then message.
After you edit bullets, run a free ATS check on the PDF you will upload and forward. Managers lose trust fast when your note promises Salesforce CPQ but the parsed file shows an empty Skills box.
Do this now: Highlight three must-haves on the posting, fix bullet one, apply once, then send one note with the req title and a single proof line.
Your ten-minute plan tonight
You do not need a hundred new contacts. You need the right leader tied to one req with a row already in the portal. Read the posting for team strings, apply once, filter People with manager titles, confirm you are not messaging a sourcer by mistake, and send the short note template with one real proof line.
- Save the req ID and three must-have tools from the description.
- Upload a parse-clean PDF to the official portal.
- Pick one likely hiring manager from the company People list.
- Send a six-sentence note with a single question.
- Log the date and follow up once with one new fact.
Open the next req on your list. Check your resume for free , fix bullet one to match the posting, apply, then send one manager note you would sign your name to.
Read more
Frequently asked questions
Apply first when the posting lists Workday, Greenhouse, Lever, or iCIMS. Compliance teams want a portal row even if a manager forwards your file later. Message the same day with the req ID or job title so your name matches the upload. Skipping the portal and cold messaging alone often leaves you off the official slate.
Hiring managers usually sit in the department on the posting with titles like Engineering Manager, Director of Marketing, or VP Sales. Recruiters list Talent Acquisition, Recruiting, or HR in the headline and post many reqs at once. HR business partners support people ops but rarely own technical screens. When in doubt, message the recruiter first and ask who leads interviews for that team.
Use the posting team name in a web search with site:linkedin.com/in and the company name. Check the company careers page for leadership quotes tied to the product line. Attend public webinars where a director speaks, then connect with one line about that session. You still need a clean portal application so your resume lands in the same ATS queue.
A short note that names the req and one proof line is normal in US corporate hiring. Long pitches, resume attachments on the first message, or repeated pings feel pushy. Keep it under six sentences, offer no demands, and accept silence. Follow up once after a week with one new fact, not a duplicate paragraph.
Yes. Managers forward PDFs into the same parsers recruiters use. A scrambled import still kills the screen. Run a plain-text paste test on the export you will send. Single-column layout, Month Year dates, and bullet one echoing tools from the posting.