11 min read · Target first, boards second
Why do some teams hire people you've never seen apply on a job board? Because the req went to a short list first, or the role was backfilled from a referral thread, or the manager already had your name from a peer intro. The posting was the backup plan, not the starting gun.
Boards aren't dead. They're just late and loud. If you're only refreshing listings at midnight, you're competing after the manager already has three files on their desk.
Before you send outreach tonight, check your resume for free against a target req or a similar public posting. You can't pitch proof you haven't written down yet.
This walkthrough is five steps: list, map, tailor, message, follow up. You won't need a hundred companies. You need fifteen good targets and messages that sound like you read their team page, not a template blast.
Quick Wins
- Pick fifteen targets with a real hiring signal, not random logos.
- Name one team problem and one metric in your opener.
- Follow up once, then move on.
Where jobs that are never posted actually come from
"Hidden" doesn't mean secret societies. It means the req never hit the public homepage before someone was already in process. Common paths: internal promotion backfills the old seat, a referral arrives before recruiting finishes the write-up, a contractor converts, or a manager hoards headcount until Q4 budget unlocks.
Signals beat slogans. A new product line, a leadership hire in your function, a req that closed in two days, or three alumni from your school on the same team all suggest live or upcoming headcount.
I've routed inbound notes to hiring managers in Greenhouse when the message named a team pain point and attached a parse-clean PDF. Generic "open to opportunities" notes died in the inbox.
Edge case: stealth startups. Titles on the website may lag reality. Edge case: large enterprises. The manager you want might sit two levels below the VP who posts on social. Map the team page, not the billboard.
Read how to build a US application funnel to balance outreach with portal applies. Read how to message a hiring manager with examples when you want more sample openers.
How to find jobs that are never posted in five steps
Work one employer at a time. Finish tailoring before you send the note. Batching fifty generic messages is how you get zero replies and a bad reputation in a small industry.
Step 1: Build a target company list with hiring signals
Open a spreadsheet with columns: company, signal, function, hiring manager guess, warm tie, status. Aim for fifteen rows to start, not fifty.
Signals that matter: public req on an adjacent team (shows stack and level), press about a launch you could support, a leader who joined in the last ninety days and is likely building staff, or a backfill post that disappeared fast (often means internal fill, but the team may still need your skill set elsewhere).
Before: Saved searches on three boards with no company theme.
After: Fifteen employers where your title, tools, and city or remote preference already fit.
Pass check: every row has at least one signal written in plain language, not just "good brand."
Step 2: Map the hiring manager and one peer
Find the person who owns the team output: Engineering Manager for backend, Director of Marketing for lifecycle, Operations lead for supply chain. Confirm on the company site. Cross-check with recent talks or blog posts so you don't message a recruiter by mistake.
Add one peer: a senior IC or lead who'd partner with the role. Peers sometimes forward strong notes when managers are traveling.
Before: Message sent to a VP four levels up with no team context.
After: Note addressed to the manager who owns the backlog you can solve, with a peer name in your research tab if you need a second path.
Pass check: you can state in one sentence what this team ships and how your last role connects.
Step 3: Tailor proof to one team problem
Duplicate your master resume. Rename for the employer. Move must-have tools from their public postings into Skills and bullet one under your current job. Rewrite Summary in two lines: target title, years, one metric, one tool they use.
Copy PDF text into Notepad to confirm section order. Two-column exports break when managers forward files internally.
Pass check: bullet one names a problem this team likely cares about (latency, pipeline, churn, throughput) with a number you can defend in a call.
Step 4: Send a short outreach note with one ask
Keep it under one screen. Paragraph one: why this team now. Paragraph two: one proof line with a metric. Paragraph three: a small ask (brief call, or permission to share a tailored resume). No life story.
Copy-paste outreach skeleton
Hi [Name], I saw [team signal: launch, hiring post, talk] and I've spent the last [X years] on [function] at [current or last employer]. Recently I [one metric bullet tied to their stack]. I'm exploring [title] roles on your [team name] side and would value fifteen minutes to learn how you're staffing this year. I attached a one-page resume tailored to your stack. Open to a brief call next week?
Replace bracket lines, attach the tailored PDF, and send Tuesday or Wednesday morning in their time zone. Avoid Friday afternoon pings that sink below weekend email piles.
Step 5: Apply officially and follow up once
If a close req exists on Workday or Greenhouse, submit there the same day you message. Reference the application in your follow-up so recruiting and the manager see one story.
After five to seven business days, send one follow-up with a new detail: a link to a relevant project, a short note about their latest release, or an updated bullet. Do not send a third bump without a reply.
Pass check: your tracker shows date sent, date followed up, and a next action that isn't "send again tomorrow."
Composite example: product ops lead
Before: Generic board apply to "Product Manager" with a resume that lists Jira once and no launch metrics.
After: Note to the Director of Product Ops citing their public API launch, bullet showing two releases per quarter with defect rate cut, portal apply to the adjacent PM req the same afternoon.
Outreach that gets ignored
Blasting fifty identical connection requests. Low reply rate and burned contacts in a tight industry. Quality caps beat volume fantasies.
Messaging without a tailored file attached. Managers forward PDFs. A blank profile and "let's chat" puts the work on them.
Chasing the wrong seniority. VP notes for IC roles signal you didn't read the org chart.
Skipping the portal when a req exists. Outreach opens the door. HRIS creates the official record. Do both.
Third and fourth follow-ups without news. Persistence without new proof reads as noise. Move to the next target instead.
Leading with desperation. You don't need to mention months of searching. Lead with team fit and one metric. Hiring managers hire capability, not guilt.
Score fit before you message
Tailored outreach fails when the file doesn't match the public req or team stack. Paste your resume and a similar posting into the job match score tool and fix gaps before you attach the PDF to a hiring manager note.
When you need a clean one-page file fast, the free resume builder exports a plain layout that survives forward-and-parse cycles better than design-heavy templates.
If the team asked for a letter on a public req, draft a short opener in the cover letter generator so your portal apply and your manager note tell the same story.
Run a small target batch weekly
How to find jobs that are never posted is really how to show up before the req does: target list, manager map, tailored proof, one message, one follow-up, portal apply when it fits. Boards stay in the mix. They stop being the whole mix.
- Fifteen targets with written signals beat fifty random applies.
- Attach a tailored PDF every time you reach out.
- Track dates so you don't spam the same manager.
Build three rows on your target sheet tonight, tailor one file, and run a free ATS check before you hit send. That's how you get on a desk before the posting goes live.
Read more
Frequently asked questions
Many roles fill through referrals, internal moves, or a short list before a public req goes live. That does not mean boards are useless. It means boards are one channel, often the noisiest one. Targeted outreach to hiring managers surfaces reqs that never hit the homepage.
Start from the team page, recent product launch, or req that just closed. Search the function plus company on professional networks. Confirm they own the team you want, not a peer in another division. One short note with proof beats ten generic connection requests.
Spam is annoying. A three-line note that names a team problem and one metric from your resume is not. Hiring managers forward those to recruiting when timing lines up. Keep volume low and specific.
Yes when a matching req exists. Outreach and portal apply are complements. The portal creates the official record. The message puts your file in front of the person who owns the headcount.
One polite follow-up after five to seven business days is enough. Add one new piece of proof or a link to relevant work. A third ping without news rarely helps.