The informational interview
that actually leads somewhere

There's a version of the informational interview that's taught in every career workshop: ask someone for thirty minutes, be curious, don't ask for a job. Then you send a thank-you note and... nothing happens. You told yourself you were "building your network." You were, in a sense. The network just isn't going to do anything.

The version that actually leads somewhere looks slightly different. Not aggressive: aggressive is worse than useless. Just specific. Here's what specific means.

Why most informational interviews go nowhere

The person on the other end wants to help. Humans mostly do. The problem is they don't know how to help you, because you didn't tell them.

A typical thirty-minute call goes like this: fifteen minutes of you asking about their career path, ten minutes of them asking about yours, five minutes of "let me know if I can ever be useful!", and then they close the laptop and forget. You weren't memorable in a way that activates a future action. They have no idea what you'd take from them if they offered it.

The call has to produce one of three concrete outcomes, and you have to engineer one of them, because the other person won't.

The three outcomes worth engineering

A referral. The most direct: they forward your resume to a hiring manager, or introduce you to someone hiring.

A second introduction. They don't have a role, but they know someone at a different company who might, and they'll make the warm intro.

A standing invitation. No immediate action, but explicit permission to come back. "send me a note when you're actively looking" is very different from "let me know if I can help" because it names a trigger.

Anything less than one of these three is a pleasant conversation with no load-bearing output. That's fine once. It's a failure mode if it's happening thirty times.

What makes the ask legible

The difference between "can I pick your brain" and an ask that converts is specificity of the thing you want the person to think about after the call ends.

Compare:

I'd love to learn more about your path into product management.

With:

I'm a senior engineer looking to move into PM in the next six months. I'm most interested in infrastructure or developer tools companies at Series B or later. I'd love thirty minutes to ask how you thought about the transition, and (if it turns out to be a fit) whether you'd be willing to introduce me to one or two people in your network.

The second version does something the first doesn't: it tells the person what a successful outcome looks like, so they can evaluate it during the conversation. They spend the call pattern-matching you against their network. The first version gives them nothing to match against.

The ask doesn't have to be in the initial message: it can be the thing you build toward by the twenty-minute mark. But if it never arrives, neither does the outcome.

The structure of the call itself

Thirty minutes, roughly:

Minutes 0–5. Context. Who you are, what you're doing, what triggered the outreach. Be specific about why you reached out to them: "I saw your talk at Railsconf" is better than "I found you on LinkedIn." People remember being remembered.

Minutes 5–20. Their story, but with specific questions. Not "tell me about your career." Questions like: what made you leave X for Y, how did you evaluate the tradeoff, what's surprised you about Y that you didn't see coming. These produce actual signal. The generic version produces a rehearsed script.

Minutes 20–28. Your ask, framed as a fit check. "Given what you've described, does my situation sound like something that'd be a match for [your company / your network / roles you've seen recently]?" This invites them to volunteer a lead without your having to ask directly. Half the time they do.

Minutes 28–30. One concrete next step. Not "I'll stay in touch." Something like: "I'll send you the two companies I'm prioritizing this month, if anyone at either rings a bell, I'd be grateful." Gives them a specific prompt to match against.

What to do after the call

Most candidates send a generic thank-you and it goes straight to the archive pile. A better follow-up closes a loop:

• Reference something specific from the conversation ("your point about how PM interviews at Series-B differ from big-tech was the single most useful thing I've heard this month").
• If they offered to introduce you to someone, remind them in two sentences and attach your resume, so forwarding takes one click instead of eight minutes of composing.
• If they didn't offer anything but the call was warm, ask one specific, small follow-up question in writing a week later. This converts "nice person I chatted with once" into "person I'm in light ongoing contact with" which is the category that actually produces referrals six months from now.

The people who get jobs through networking aren't people with bigger networks. They're people who converted more calls into loops that stayed open.

The volume question

You will sometimes read that you should do thirty of these in a quarter. You probably shouldn't.

Ten well-chosen conversations (people at companies you actually want to work for, in roles you can articulate wanting, asked for with a specific and honest framing) outperform thirty scattershot ones. The asymmetry is similar to cold applications: selectivity compounds, volume dilutes.

A reasonable cadence is two to three per week during an active search, selected by target-company list, not by whoever accepts the invitation first. If nobody's accepting, that's information, likely about how the outreach message is written, not about your candidacy.

On the "don't ask for a job" rule

Taken literally this rule is bad advice. What it's trying to say is: don't open with the job ask, because that repositions the entire conversation as transactional, and people are worse at helping transactionally than relationally.

But you also can't close without any ask. The middle path (spend the first two-thirds of the call building genuine context and understanding, then surface what you're looking for once rapport exists) is how experienced networkers operate, and it's what separates the conversations that move your search forward from the ones that don't.

Curiosity and ask aren't opposites. You need both.

The long arc

The uncomfortable truth about informational interviews is that the individual call rarely produces the job. What produces the job is the fourth conversation with someone you first met two years ago, because a role opened at their new company and they remembered you existed.

Which means the real work isn't any one call. It's staying in light, honest, non-transactional contact with a slowly growing list of people whose work you genuinely find interesting, so that when timing aligns, you're top-of-mind.

That takes longer than most candidates want to hear. It also works better than every other channel, which is why every senior person you know insists on it despite how slow it sounds. For how to set up the LinkedIn presence that makes these outreach messages actually produce replies, see the LinkedIn profile that actually gets you found.

If the time cost of researching target companies and warming up outreach is what stalls a networking push, Jobiz does the structural part so the thirty minutes on the call goes into the conversation itself, not into the prep.