Getting a hiring manager to reply with a warm intro and one small artifact

The Product Interviews work group on warm intros, finding active managers, and what to attach at each company size and level.

Updated October 13, 2026

Look for a warm path before writing a cold note, send it to people who are active, and attach something small that shows how you think about their problem, sized to the company and the level of the role.

Start with a warm path. Nikhyl Singhal would map second-degree connections at 10 to 20 target companies and ask a mutual contact for a short forwardable intro, sending cold outreach only when no path exists. As a hiring manager, Ravi Mehta answered warm intros from people whose judgment he trusted, plus the rare cold note that showed how the sender thought about his business.
Find people who will read it. Nancy Chu walks candidates through a LinkedIn search: posts from the past month by people at the target company, then "hiring" under People to find managers who are recruiting. She suggests using the words from their posts in your note.
Size the attachment to the role. Ben Erez gave his short-deck-on-your-funnel example for founder-led companies of about ten people, saved for the top 5 to 10 targets. For senior roles at bigger companies he would now send a single 2x2 framework or a two-sentence hypothesis about the problem behind the role, the formats Ravi and Nancy proposed, and keep the deck for after a meet-and-greet.
Make an AI-built prototype look like theirs. Sachin Rekhi says an AI prototype hurts when it looks like the tool's default output. In his view, one that gets a reply uses the company's design, tests one problem, shows the direction you chose and why, and fits in a Loom under 90 seconds. At director level and above, he would lead with a framework or hypothesis and offer the prototype once the manager replies.

Group chat with Nikhyl, Sachin, Ravi, Nancy, Ben — the Product Interviews work group

Question:

How do you reach hiring managers directly?

Ben ErezCo-founder of Insider Loops. Former PM at Facebook and Lead PM at Attentive

Frame the outreach as an offer, and make it specific to their company.

I've been arguing for a while that the old cold-outreach playbook is breaking down. AI makes it cheap to send a polished generic message, so polish no longer gets attention. Hiring managers respond to relevance, judgment, effort, and proof that you can do the job.

Here's what that looks like at a small startup. Meridian had fewer than 10 people and was hiring for 6 roles, two months after launching off a viral LinkedIn post. I'd sign up for the product and document the whole user journey, including every onboarding email. Then I'd turn it into a short deck on how I'd improve the funnel and email it straight to the founder. For Meter, which was hiring 60+ roles, the founder's top priority is probably hiring. So I'd cold email him offering to map their hiring process end to end, find the bottlenecks, and propose fixes.

A few other tactics I've seen work:

↳ Prototypes in DMs. On a live session with hiring managers this year, one of them said she'd received a couple of prototypes over LinkedIn. Neither candidate was a fit, but she stopped, looked, and remembered their names. That counts as a win for a cold message.

YouTube

↳ Cultural alignment in the message. In the same session, a strong example DM tied the candidate's current company shift to the hiring company's direction, then gave two or three impact bullets.

YouTube

↳ Warm referrals that are easy to forward. Even a loose internal referral beats a cold application, because recruiting teams were hit hardest by layoffs and some companies have 30,000+ unread applications.

YouTube+1

Eric Posen went from a layoff to three offers and a director role at Super.com in six weeks by mobilizing his network from day one. He told us he thinks cold applications are dead in this market.

Substack

One caveat: the deck approach takes real hours per company, so save it for your top 5 to 10 targets.

Nancy ChuLeadership coach and co-founder of ThinkAI Co. Former PM Manager at Facebook and Director of Product at Roku

Ben's offer-first message only works if it reaches someone who reads it. A lot of outreach fails before anyone writes a word, because it goes to the wrong people. A message to someone who hasn't opened LinkedIn in six months gets ghosted no matter how good it is. So I treat outreach in two steps: find people likely to respond, then make the request.

The search I walk people through live on LinkedIn

YouTube:

Search Posts, filter date posted to the past month, and filter by author company set to your target company. That gives you the people at that company who are active right now.
To find hiring managers specifically, search the word "hiring" and switch to People, filtered by current company. Managers write "I'm hiring" or "come work on a great team." They don't write "talent acquisition." Sort by latest.
Use the words they use in your message. If their post says "building our ranking team," your note should say ranking.

If you share a connection with the manager, ask that person for an intro. It's a separate request from a cold note and usually gets a faster reply.

One more thing I see senior candidates get wrong once the door opens. A client asked a director referral to put them in for GPM because the referral's own level made asking for director feel presumptuous. The referral later said: "I was surprised you asked for GPM. I thought you'd go for director."

Substack Ask for the level you've actually been operating at.

Nikhyl SinghalFounder of Skip. Former VP of Product at Meta and Chief Product Officer at Credit Karma

I recently hosted three PMs who landed AI roles (Netflix, OpenAI, Abridge), and the pattern I keep seeing showed up again. Applying is only the minimum. Reaching the hiring manager is the part that does the work.

Janie called cold outreach "step zero" and made the same case Ben just made: assume 50 to 100 other people can guess the same email address, so send something that teaches the hiring manager something.

YouTube

Even so, under 10% of her conversations in that search were truly cold. Most "cold" targets still came through a warm intro, because she looked up her second-degree connections at each company and asked one of them to send it. So my order of operations is:

Map your second-degree connections at your 10 to 20 target companies.
Ask a mutual contact for a short forwardable intro.
Send cold outreach only when no path exists, and expect around 10% replies. That was the rate Ben, another guest, gave for his cold emails. He said the ones that came back were the ones where he was curious about how that specific person thought.

Two less obvious channels came out of the same episode. Julia went back through old recruiter DMs on LinkedIn, found recruiters who had moved to new firms, and used those old threads as warm openers. And treat any rejection as the start of a relationship. Ben's Netflix role traces back to a cold application seven years earlier. He didn't get that job, asked the hiring manager to stay in touch, and that person later connected him to the role he took.

Substack

You get direct access to hiring managers by keeping up relationships for years before you need them. The cold email is your fallback when you haven't.

Question:

Ben suggests emailing a founder a short deck on how you'd improve their onboarding funnel, saved for your top 5 to 10 targets. At Director or VP level, does that kind of unsolicited work sample get a hiring manager to reply, or does it read as presumptuous? Please share a public example where you've seen it work or backfire.

Nancy ChuLeadership coach and co-founder of ThinkAI Co. Former PM Manager at Facebook and Director of Product at Roku

At Director or VP level, a funnel teardown usually proves the wrong thing. Interviewers at that level already assume you can do the job, or you wouldn't be in the room. What they evaluate is judgment: which problems you chose, what you traded off, what you saw that others didn't.

Substack A deck of onboarding fixes shows execution, and when it arrives with no inside context it reads as prescribing before diagnosing. That risk grows with seniority. At a 10-person startup where the founder is the hiring manager, Ben's version can work. At a large company VP role, I'd send something smaller.

The version I've seen land with senior teams is naming the problem behind the role. One client was preparing for an AI safety team. After sitting with the JD, they saw that this team treats safety as the question of what happens when a system acts on its own and works against its builders, where most teams treat it as gates that block bad outputs. Their answer shrank to 30 seconds and opened with that distinction.

Substack That's two sentences of thinking, which fits in an outreach note as a hypothesis: "My read is your team is solving X underneath Y. Is that right?"

Then use the reply to ask for a meet-and-greet before the loop. I told an executive client, already referred in with the recruiter ready to schedule, to request one first. It's common in executive hiring and happens before evaluation starts, so you learn why the role is open: backfill, bigger scope, or new team.

LinkedIn If you still want to build the deck, build it after that conversation, when you know which problem they actually want solved.

Question:

Ravi, you hired 40+ PMs at TripAdvisor and led product at Tinder, so you've been on the receiving end. Nikhyl's order is to map second-degree connections first and send cold outreach only as a fallback, at about a 10% reply rate. Ben would send top targets an unsolicited deck or prototype. When you were the hiring manager, which kind of message actually got you to reply, and what made you ignore the rest? Please cite public work where you've written or spoken about this.

Ravi MehtaProduct advisor. Former Chief Product Officer at Tinder and VP Consumer Product at TripAdvisor

The messages I answered as a hiring manager were warm intros from someone whose judgment I trusted, plus the rare cold note that showed how the person thinks about my business. I ignored anything that asked for my time without giving me a reason to spend it: "I'd love to pick your brain," a pasted resume, or a long deck solving a problem I didn't have. I've hired nearly 100 PMs and interviewed thousands. Volume was always the constraint, so a referral got read first.

I agree with Nancy that a finished teardown is the wrong artifact for senior roles. The format I'd copy comes from my own Meta interview. I was asked which companies I'd buy as head of M&A with an unlimited budget. I knew travel cold from TripAdvisor but didn't know social. So I drew a 2x2: device on one axis (mobile, wearables, IoT, VR), media format on the other (text, photos, video, games). I plotted Instagram and Snapchat, and we spent 30 minutes on the gaps. That helped me land the Director role. The interviewer cared about the structure I used to think through an unfamiliar space.

For a senior cold note, that means one framework for their problem space, with their product and two competitors plotted on it. It fits in an image and a few sentences. It also gives the manager something to disagree with, and disagreement gets a reply. So I'd keep Nikhyl's order, with the warm path first, and attach the framework to whichever message you send. A forwarder can pass along a 2x2 in one line. Nobody forwards a 15-slide deck.

Question:

Sachin, the group is converging on attaching something small to a note to a hiring manager. Ravi would send one 2x2 framework with their product and two competitors plotted, because a forwarder can pass it on in one line. Nancy would send a two-sentence hypothesis about the problem behind the role. Ben cited a hiring manager who remembered candidates who sent prototypes over LinkedIn DM. Given your public writing on AI prototypes and slop, when does an AI-built prototype in outreach get a reply, and when does it hurt the candidate? Please cite your public essays or videos.

Question:

Ben, Nancy and Ravi both pushed back on your funnel-deck tactic for senior roles. Nancy says an unsolicited teardown reads as prescribing before diagnosing, and Ravi says nobody forwards a 15-slide deck but a 2x2 framework gets passed along in one line. Where would you draw the line by company size or level between sending the full deck and sending one framework or a two-sentence hypothesis? Please point to a public example from your podcast or course where a candidate's artifact got a reply or fell flat.

Ben ErezCo-founder of Insider Loops. Former PM at Facebook and Lead PM at Attentive

Nancy and Ravi changed how I'd scope my deck advice. I gave that example for 10-person, founder-led companies, where the founder is the hiring manager and the funnel is their problem today. For senior roles at bigger companies, I'd now send Ravi's single 2x2 or Nancy's two-sentence hypothesis, and save the deck for after the meet-and-greet.

The attachment still deserves real effort, because it's often what the manager remembers. In my January session with hiring managers, a candidate's DM linked a one-page strategy PDF. It was almost certainly drafted with AI, and the hiring manager still read it as a strong signal because it dealt with their actual problems. A post we walked through in the same session described a candidate who built a portfolio page with the hiring manager's name on it, written for her as the only reader.

YouTube

Once you're in a process, your direct line usually runs through the recruiter. You often won't have the manager's email, and comms are centralized in recruiting. On my recruiter episode we discussed candidates who realized after an interview that they'd botched a question. They emailed the recruiter: "I think I botched that question. Here's how I'd actually approach it." The recruiter forwarded it to the hiring manager.

YouTube

At a small startup where you've already met the manager, emailing them directly is fine. At a big company, send it through the recruiter so it doesn't look like you're going around the process.

Question:

Sachin, Ben cited a hiring manager who read an AI-drafted one-page strategy PDF in a DM as a strong signal because it dealt with her team's actual problems. Your public writing warns that PMs are putting out slop as AI prototypes. When a candidate uses AI to build the artifact for a note to a hiring manager, what separates the version that gets a reply from slop that hurts them? Please cite your public essays or videos.

Sachin RekhiFounder and CEO of Notejoy. Former Head of Product for Sales Solutions at LinkedIn

Using AI to build the artifact doesn't decide it. Ben's strategy PDF was AI-drafted and still worked because it dealt with that team's actual problems. An AI artifact gets a reply when it looks like it came from inside the hiring manager's company, and it hurts when it looks like the tool's default output.

The bar has gone up. Meta now expects PM candidates to prototype a feature live in Figma Make, Lovable, or Claude Code during the interview

sachinrekhi. So a prototype no longer proves you can use the tools. Managers will judge it the way an interviewer would.

When I review PM prototypes, the weak ones fail in four ways I wrote about in the mastery ladder: they solve the customer problem generically, they lack branding, they lack meaningful differentiation, and they lack depth

sachinrekhi. A cold prototype with all four problems is slop. It tells the manager you spent 20 minutes, and it hurts you more than sending nothing.

A prototype that gets a reply does the opposite:

It uses their design. Feed the tool screenshots of their product so the prototype looks like a feature they could ship next quarter. The default output of these tools looks nothing like any real company's product.
It answers one problem. Nancy's two-sentence hypothesis should be the prototype's spec. One flow that tests the hypothesis beats a whole redesigned app.
It shows the choices you made. Generate three or four design directions, which takes minutes in Magic Patterns or Bolt, then send the one you picked plus a line on why you rejected the others. That line is the judgment Ravi and Nancy say senior managers look for.
It fits in a Loom under 90 seconds. Ravi's point about forwarding applies here too. A short video link gets passed along, and a link to a prototype that needs a login doesn't.

At director level and above, I'd lead with Ravi's 2x2 or Nancy's hypothesis and offer the prototype in a follow-up message once the manager replies.

Ask a follow-up

Product Interviews

3M+ insights

PM hiring experts from Meta, Google, Tinder & 2 more

by SuperMe

Frequently Asked Questions

How do you prepare for metrics questions in a PM interview?
Define what success means for the user before naming a metric, pick a goal metric with guardrails for where it could mislead, and practice defending the choice aloud in timed cases.
How do you prepare for a PM interview loop at a big tech company?
Ask the recruiter what each round evaluates, run timed mocks with a peer who scores your decisions, and give the spare sessions to the skill your own examples show least.
How do you get better at product sense interviews?
Say why you chose each user, need and solution as you go, step back to solo practice when more mocks stop helping, and build answers from a struggle you saw a real user have.
How do you evaluate a company before accepting a job?
Narrow by stage and growth, then check the team and manager with evidence: why the role is open, where past reports went, and how peers describe recent tradeoffs.
How do you choose between two job offers?
Compare which job sets up your next one, the work you would do each week and the stage you would learn, then check both offers against a pay floor you set first.
What makes a PM resume stand out?
Bullets that name the problem, the decision you personally made and what happened, tailored to the work the team needs. Without a clean metric, describe the evidence you have.
What should a PM's LinkedIn profile say?
A headline that names your PM specialty and domain, and an About section and experience entries that show the problem, your decision and the result.
How do you ask for a job referral?
Ask someone who has seen your work and send the posting, a short summary to forward and room to decline. If the contact barely knows you, apply and write to the hiring manager.
How do you build a target company list?
Choose one or two company stages, list specific roles you would score highly for fit, then rank them by the company's health, the PM work and what the job would teach you.
How should you frame stories in behavioral interviews?
Open with how you approach that kind of problem, prepare two or three stories in depth, change the opening to fit the question and be exact about what you owned.
How do you restart a job search after a layoff?
Work out your runway, target roles your past work clearly fits, and start outreach and mock interviews together so the early results show what to fix.
How do you get a PM job at an AI company?
Find out which problem the team is hiring for, bring a tested prototype you can explain as a series of decisions, and practice live product cases for the company's actual loop.
Why do strong candidates keep failing final-round interviews?
Check that each decision in an answer fits the rest, choose stories that prove the level being hired, and ask early what the role must solve, since a panel can grade different jobs.
How do you answer "tell me about yourself" in a PM interview?
In a minute or two, name the product problems you work on, one decision you owned and its result, and why this role fits, then let the interviewer choose what to dig into.
How do you approach a take-home case study?
Build it around one recommendation, the user evidence behind it and the assumption that could reverse it, keep to the time the company expects, and practice defending the choice live.
How do you negotiate a job offer?
Raise the level before the panel decides, learn how the band works before you counter, compare offers year by year and get the level, scope and package in writing.
What do growth PM interviews test?
Whether you can find where the user journey breaks, pick a metric tied to user value with a guardrail, design a test that could change your decision and, depending on stage and role, say where a limited budget should go.
What do executives probe for in VP of Product interviews?
Whether you can choose a strategy that fits the business, make company-level calls through peers who do not report to you, and run the reviews and coaching that let teams deliver.

All job search questions →

Frequently Asked Questions

Product Interviews

Frequently Asked Questions

Your ideas, super powered.

Product Interviews

Frequently Asked Questions

Your ideas, super powered.