A stranger replied to your cold email. That is the hard part done, and it is also the moment most job seekers waste. They say thank you, ask a vague question like "any advice for someone trying to break in?", get a two-line answer, and the conversation quietly ends. No call happens, no referral happens, and the reply turns out to have been worth nothing.
An informational interview is not a favor you cash in once someone replies. It is a specific, short conversation you have to ask for on purpose, with a real question in mind, that turns a stranger's five minutes into an actual path toward a job. Here is how to get one, what to say once it is on the calendar, and which questions are worth asking.
The reply is not the goal
Treat the reply to your first cold email as the opening of a negotiation, not the finish line. The person who replied is, at that moment, mildly interested and has done you zero favors yet. What happens next depends entirely on what you ask for.
Most replies die because the follow-up asks for nothing specific. "Thanks so much, any advice you can share would be great!" gives the other person nothing to act on, so they default to a short, generic answer and move on with their day. Compare that to: "Would you have 15 minutes this week or next for a call? I'd like to ask about how you got into the role and what the team looks for when it's hiring." That is a request with a time box, a reason, and an easy yes.
The data backs up why it is worth being this deliberate. In a survey of more than 2,200 U.S. CFOs by Accountemps, 84% said they would be likely to alert someone who impressed them during an informational interview about future job openings, and 31% said they personally field requests for informational interviews at least once a month. The conversation itself is the mechanism that gets you remembered when a role opens, not the cold email that led to it.
What an informational interview actually is
An informational interview is a short, one-on-one conversation where you ask someone about their job, their path into it, and their company, and you are explicit that you are not asking them for a job on the call. That distinction matters for two reasons.
First, it lowers the bar for a yes. Agreeing to a 15-minute call about their own career is a much smaller ask than agreeing to "look at my resume" or "pass my name along," which can feel like putting their own credibility on the line for someone they just met.
Second, it still gets you most of what a direct ask would, just in reverse order. People refer candidates they already like and trust. An informational interview is how you become that person before you ever ask for the referral, instead of asking a stranger to vouch for you on faith.
How to ask: the actual email or follow-up
Once someone has replied to your initial outreach, the ask should be short, specific, and easy to say yes to:
- Name the format and length. "15 minutes on a call" or "a quick video chat" is concrete. "Pick your brain sometime" is not.
- Give a reason that is about them, not just you. "I'd love to hear how you ended up in [role] at [company]" works because most people like talking about their own path more than they like generic career advice.
- Offer specific times, not an open-ended "whenever works." "Would Tuesday afternoon or Wednesday morning work?" gets a faster yes than "let me know when's good," which puts the scheduling work back on them.
- Make it easy to reschedule or decline. Adding "no worries if this week doesn't work" lowers the pressure of the ask and, counterintuitively, tends to raise the reply rate, because it removes the guilt cost of saying no.
If the first message already got a reply but it was noncommittal (something like "happy to help if I can"), that is still a yes. Send the specific ask with times rather than waiting for them to propose something, because most people who are willing to help will not take the extra step of structuring the call themselves.
What to say once the call happens
Open by thanking them and restating, in one sentence, what you are hoping to learn. Then get out of the way. The best informational interviews are mostly the other person talking.
A simple structure that works:
- How they got into the role — their actual path, not the official job description. This is where you learn the paths nobody writes about, like someone who moved from a support role into the one you want, or got in through a project rather than a traditional application.
- What the day-to-day actually looks like — what takes up most of their time, and what surprised them about the job once they were in it.
- What they look for when the team is hiring — skills, experience, or signals that stand out, in their own words rather than what the job posting says.
- Who else it might be worth talking to — this is the actual point of the call. A good informational interview produces a second name, not just an answer.
Close by asking directly whether they would be open to an introduction to anyone else at the company, or to keeping you in mind if something opens up. Most people will not offer this on their own; you have to ask for it, the same way you had to ask for the call itself.
The questions that actually lead somewhere
Generic questions get generic answers. "Any tips for someone trying to get into this industry?" invites a two-sentence, forgettable response. Specific questions get specific, useful ones:
- "What's one thing about this job that the posting doesn't capture?"
- "When your team last hired for this role, what made one candidate stand out from the others?"
- "Is there a project or portfolio piece that would have made you more confident hiring someone with my background?"
- "Who else on the team, or at a similar company, would you suggest I talk to?"
That last question is the one to never skip. A single informational interview that produces one more introduction compounds the same way a cold email follow-up does: most of the value comes from what happens after the first touch, not the first touch itself.
Following up afterward
Send a short thank-you within a day, specific to something they actually said, not a copy-pasted line. "Thanks again, the point about how your team weighs portfolio work over GPA was genuinely useful" shows you were listening and gives them a reason to remember you specifically.
Then stay in their inbox without becoming a burden. If they mentioned an opening might come up in a few months, a brief note then ("wanted to check in, still very interested if anything opens on your team") keeps you top of mind without asking for anything new. If they offered an introduction, follow up on it within a few days while the conversation is still fresh for them, rather than letting the thread go cold.
Doing this at scale without it feeling cold
The hard part of all of this has never really been the conversation itself. It is finding the right person to ask in the first place, especially when you don't already know anyone at the company. Most job seekers either guess at a generic "recruiting@" address that nobody reads, or give up after one unanswered LinkedIn message.
Hesper handles the part that normally stalls people before they ever get to ask for the call: you pick the role and city you're going after, it finds the companies actually hiring and the specific people there who can hire you, and it sends the first email from your own Gmail on a schedule, with follow-ups built in. The informational interview only happens after someone replies, and someone only replies if the first email reaches the right inbox. Everything above about asking well and asking for an introduction still has to happen person to person; the product's job is making sure you are never stuck wondering who to even write to.
The value of actually building that network rather than applying into a void is the whole premise here. A reply is an opening, not a result. What you do with the next ten minutes of someone's attention is what decides whether it turns into anything.
FAQ
How long should an informational interview actually be? Fifteen to twenty minutes is standard, and you should say so explicitly when you ask. A shorter, clearly time-boxed request is easier for a busy person to say yes to than an open-ended "let's grab coffee sometime."
Is it rude to ask for an introduction at the end of an informational interview? No, as long as you ask rather than hint. Most people who agree to the call are already willing to help further, but few will volunteer an introduction unprompted. Asking directly, "is there anyone else you'd suggest I talk to?", is a normal and expected close to the conversation.
Should I ask for an informational interview or just ask if they're hiring? Ask for the conversation first. Directly asking a stranger "are you hiring?" puts them in the position of either committing to help a candidate they don't know yet or saying no outright. A short conversation first lets them get comfortable with you before any ask about an actual role comes up.
What if the person never responds to the request for a call? Follow up once, a week or so later, with a short, low-pressure note. If there is still no response after that, move on. Not every reply to a cold email turns into a conversation, and that is normal; the goal is a handful of real conversations, not a reply from everyone you write to.
Can I ask for an informational interview over LinkedIn instead of email? Yes, the same approach works on either channel. The advantage of email is that it is easier to be specific and attach context (like a resume or a portfolio link) without the character limits and platform friction that LinkedIn messaging adds.
No comments yet.