Basics
What an informational interview is
A clear definition of informational interviews, how they differ from job interviews, and a worked example of a useful thirty-minute conversation.

An informational interview is a short conversation where you learn about a field, a role, or a workplace from someone already there. It is not a hidden job interview, and it is not a request for a referral on first contact.
This Mentorwick guide explains what the meeting is for, what it is not for, and how one reader used a thirty-minute chat to map a career path without asking for a job. Mentorwick publishes information only; it does not arrange introductions.
Paper is enough.
A learning meeting, not a hiring screen
You ask for time to understand how the work actually goes: daily tasks, skills that matter, common entry paths, and culture signals. The other person shares experience. You leave with notes, not an offer.
Treating it like a stealth application usually backfires. People can tell when the conversation is only a funnel to 'are you hiring?' Keep the ask honest: learning first.
Thirty minutes is a common length. Come with five strong questions and leave room for follow-ups the other person finds interesting.
Keep the frame honest when you describe the meeting to friends too. Calling it networking is fine; calling it a backdoor interview sets the wrong expectation for you and for them.
If someone offers unsolicited hiring help, you can thank them and still keep the first meeting about learning. Accepting kindness is not the same as opening with a job ask.
Write down what success looks like before you request time: two or three answers you still lack after your own research. That list keeps the conversation from drifting into biography hour.
What you can reasonably hope to learn
Day-in-the-life detail you cannot get from a posting. Which skills are taught on the job versus required on day one. How people in that field found their first role. Which books, communities, or projects are respected.
You may also learn what to avoid: burnout patterns, credential myths, or titles that sound better than they feel.
Write notes the same day. Capture phrases they used; those words often help later applications sound grounded.
Keep a running glossary of terms they use. Field jargon often becomes the difference between a generic application and one that sounds lived-in.
If time runs short, skip your least important prepared question rather than talking faster. Rushed closings feel disrespectful.
Worked example: Alex maps a UX path
Alex wanted to move from retail management into UX research. She asked a researcher for thirty minutes to understand portfolio expectations. She did not ask for a job.
In the meeting she learned which three portfolio pieces mattered most, which certificate was optional, and which meetup actually helped newcomers. She left with a reading list and a clearer six-month plan.
Two months later she sent a short thank-you with a portfolio link — only after building the pieces they had discussed. The researcher offered informal feedback. The first meeting stayed a learning meeting.
The lasting value was not a single tip. It was a clearer map of what good work looked like in that world, written in someone else's plain words.
Ethics and boundaries in learning conversations
Do not record without permission. Notes in your own words are enough for most goals.
Do not publish their private advice as a quote without asking. Paraphrase lessons into your own plan.
Do not turn a courtesy meeting into a sales pitch for your services. If they ask what you do, answer briefly and return to learning.
If the conversation reveals hiring needs, you may ask how openings are posted. That is different from demanding a referral.
End on time even if the chat is going well. Respect for the clock is part of your reputation.
Checklist: is this an informational interview?
- Is my primary goal learning, not landing a job today?
- Can I explain the ask in one honest sentence?
- Do I have five questions that are not answerable by a quick web search?
- Am I prepared to end on time and send a short thank-you?
- Have I avoided asking for a referral in the first conversation?
- Will I write notes the same day?
Quick reference: interview types
| Type | Goal | You ask for | You should not |
|---|---|---|---|
| Informational | Learn about field/role | Time + insight | A job on first contact |
| Job interview | Evaluate fit for a role | Consideration for hiring | Pretending it is casual chat |
| Referral ask | Introduction to a hiring manager | Warm intro after trust | Demanding one immediately |
| Mentorship | Ongoing guidance | Periodic advice | Unlimited access |
Key terms
- Informational interview
- A short learning conversation with someone in a field you want to understand.
- Day-in-the-life
- Concrete detail about how work actually unfolds.
- Soft ask
- A request for learning time without a hiring demand.
- Thank-you note
- A short follow-up that names one specific thing you learned.
- Portfolio signal
- Evidence that shows skill without requiring a job ask.
Questions to ask
- What do I most need to understand about this field?
- Who is close enough to the work to answer well?
- What can I learn on my own before I ask for time?
- How will I keep the first meeting about learning?
- What will I do with the notes afterward?