You found someone doing exactly the work you want to do. You opened a blank email to ask them for a conversation, typed "Hi," and froze, because everything you can think of sounds either desperate or like a sales pitch.
Here is the good news: informational interview requests get accepted far more often than people expect, when they are built the right way. This guide gives you the exact structure, an 80-word template you can adapt in five minutes, the three questions actually worth asking, and the one rule that protects the whole thing.
Why people say yes (and why they say no)
Understanding the psychology makes the email almost write itself. People say yes to requests that are:
- Specific. "Could I ask you about how clinical data teams are structured at mid-size hospitals" beats "I would love to pick your brain."
- Bounded. Twenty minutes with a clear time window feels safe. An open-ended "chat sometime" feels like a chore with no edges.
- Flattering, but true. People can smell generic flattery instantly. "Your talk at the June meetup changed how I think about onboarding" works because it is verifiably real. "I am a huge admirer of your work" works on no one.
- Free of hidden agendas. The moment a request smells like a job ask in a trench coat, the yes evaporates.
And people say no, or just never reply, when the email is long, vague, about the sender rather than the conversation, or clearly copy-pasted. Every choice below flows from this.
The 80-word request template
Here is the skeleton. Adapt the details, keep the proportions.
Subject: Quick question about clinical data work at Meridian
>
Hi Dana,
>
I am a data analyst moving toward healthcare after five years in retail analytics. I found your name through the Women in Health Data group, and your post about messy EHR exports was the most honest thing I have read on the topic. Could I ask for 20 minutes, any time in the next two weeks, to hear how you made your path into this field? Happy to work around your schedule.
>
Thanks either way,
Sam
Why each piece earns its place:
- The subject line names a topic, not a favor. "Quick question about X" outperforms "Coffee chat?" because it tells them what they are agreeing to.
- One line of who you are. Enough context to answer, not your life story.
- One specific, true compliment that proves you actually read or heard their work. This is the flattering-but-true engine of the whole email.
- A bounded ask with a window. Twenty minutes, two weeks, their schedule. You have made saying yes nearly effortless.
- "Thanks either way." A graceful exit ramp lowers the pressure and, paradoxically, raises the yes rate.
If you have no connection to this person at all, the same principles hold but with extra care, and networking messages to strangers walks through that colder version. If the person is someone you used to work with, you have an even warmer path, covered in reconnecting with old coworkers.
The cardinal rule: never ambush the chat with a job ask
This rule deserves its own section because breaking it destroys everything the email built.
The person said yes to sharing their perspective. If, fifteen minutes in, you pivot to "so, are you hiring?" or slide your resume across the table unprompted, you have changed the terms of an agreement they made in good faith. It feels like a bait and switch because it is one. They will end the call politely and never help you again.
Here is what to do instead:
- Trust the mechanism. If they like you and know of a fit, they can raise it themselves: "You know, we actually have an opening on our team." You cannot count on that, which is exactly why you do not ask.
- You may leave one light door open, at the very end. Something like: "This has been really helpful. If you ever hear of roles where someone with my background would fit, I would love to know." That is a signal, not an ask, and it respects the frame.
- If they say "send me your resume," that is your green light. They opened the door. Walk through it promptly and gracefully.
The discipline is hard when you need income. But the informational interview is a long game that pays off precisely because you did not force it.
Three questions worth asking (and two that waste the call)
You get maybe six or seven real questions in twenty minutes. Make them count.
Worth asking:
- "What does a typical week actually look like in your role?" Job postings describe fantasy jobs. This question gets you the real one, and the answer often changes what people decide to pursue.
- "What separates the people who do well here from the people who struggle?" This is the question that surfaces what the company truly values, which no careers page will tell you.
- "Knowing what you know now, what would you tell someone entering this field today?" People love this question, it produces their most honest advice, and it positions you as someone thinking seriously rather than fishing for a referral.
Skip these:
- Anything you could have Googled. "What does your company do?" tells them you did not prepare, and preparation is the whole way you show respect for their time.
- "Are you hiring?" See the cardinal rule. This question converts a generous conversation into an awkward screening call.
Take notes. Ask follow-ups. Let it be a conversation, not an interrogation, and end on time even if it is going well. Ending on time is how you get invited back.
After the call: the follow-through most people skip
The email got you the meeting. The follow-through turns it into a relationship.
- Send a thank-you within a day. Two or three sentences, referencing one specific thing they said that changed your thinking. Specificity proves you listened.
- Act on their advice, then tell them. If they suggested a certification, a person to meet, or a company to watch, do the thing and report back in a few weeks. "I took your advice and X happened" is the single most relationship-building message in networking, because almost nobody sends it.
- Keep the connection warm. Send them an article relevant to something they mentioned. Congratulate them on work anniversaries or launches. Small, genuine, occasional.
If the conversation goes well and you want to approach the hiring manager at their company directly later, do it as its own respectful outreach, and cold emails to hiring managers covers how to do that without leaning on your contact's name more than they offered.
Get your resume ready before they ask for it
Informational interviews have a predictable happy ending: "send me your resume and I will pass it along." It happens more often than you would guess, and it usually happens fast, at the end of the call, while you are still saying thank you.
That means the time to fix your resume is before the conversation, not after. Because here is the unglamorous truth: even a hand-carried referral usually gets uploaded into the company's applicant tracking system, the same software that screens every other applicant. If that software misreads your dates, mangles your titles, or drops a whole section, your new advocate is forwarding a scrambled version of you.
The free scan at careerbounce.io shows you exactly what the hiring software will read from your resume. It runs entirely on your device, so your resume never leaves your computer, and it flags what parsed cleanly and what did not. Run it before your next informational interview so that when someone says "send it over," you are ready in minutes.
Nobody can promise that a twenty-minute conversation leads to a job, and this article will not pretend otherwise. But a specific, bounded, honest request gets conversations, conversations build a real map of where you fit, and a clean resume makes sure that when a door opens, you fit through it.