Prepare Your First Informational Interview: Questions and Example

Prepare your first informational interview by choosing one career question, researching the person's work, and agreeing on a short conversation. Ask about specific work they have done, leave room for follow-up questions, and finish by recording what you learned and what you will test next. A useful outcome can be a clearer reason to explore a role further, or a reason to reconsider it.

An informational interview is a conversation to learn about someone's work. Berkeley Career Engagement describes it as typically 20–30 minutes and distinguishes it from a hiring interview. Be clear about that purpose when asking for time. The person has agreed to share their experience, not to assess you for a vacancy.

Kognivu can help you plan the research, question preparation, and follow-up as daily quests around your available time. Plan your career-exploration sessions in Kognivu, then review the proposed tasks against the actual conversation you have arranged. Keep contact details and conversation notes in your own files; the app does not arrange the meeting or verify someone's career advice.

Pick a question a conversation can answer

“Should I change careers?” is too broad for one person to settle. Start with an uncertainty that affects your next choice:

I enjoy making spreadsheets. How much of an entry-level operations analyst's work involves understanding unclear requests, rather than building reports from ready-made instructions?

That question gives you something to listen for. It also leaves room for an answer you might not like. If you only ask how to enter the field, you can miss whether the everyday work interests you.

Read the person's public role description and a little about their organization. Note what you already know, what you are assuming, and what only their experience could help clarify. Choose someone whose recent work is relevant to your question. A senior leader's career history may be interesting while telling you little about the junior role you are considering.

If you need a broad transition plan afterward, the career-change roadmap covers the longer sequence. This conversation has a smaller finish line: enough specific information to choose your next exploration step.

Make a small, honest request

A request should explain why you chose this person, what you hope to learn, and how much time you are asking for. Yale's Office of Career Strategy recommends stating the purpose and meeting length, being flexible about scheduling, and confirming the arrangement.

Here is an invented example to adapt only when the details are true:

Hello, I'm exploring operations analyst roles after doing reporting tasks in an administrative job. I saw your public description of supporting a logistics team. Would you be open to a 20-minute call about how you turn an unclear request into a useful report? I'm trying to understand the day-to-day work before choosing a practice project. I can work around your availability, and I understand if you cannot make time.

Remove the role or connection if it does not apply to you. Do not imply that a mutual contact referred you when they did not, or hide an application request inside a conversation about learning.

An unanswered message remains unanswered. It does not establish anything about your suitability for the career. You can continue public research and approach another relevant person respectfully. Do not mark “complete informational interview” as done because you sent a request.

Prepare questions that reveal the work

For the analyst example, keep a few questions that each serve a different purpose:

Question to adapt	What you are trying to learn
Could you walk me through a recent request, without sharing confidential details?	What work actually starts with
What was unclear, and how did you decide what to ask before building anything?	How much interpretation the role requires
What did the person using the report need to do differently afterward?	How the output gets used
Which part could a beginner practice with public or invented data?	A safe, realistic next experiment
Which parts of your experience depend on this team or industry?	Where the account may not generalize

These are original practice questions for the scenario, not a compulsory script. Replace them when your uncertainty concerns fieldwork, collaboration, writing, or another kind of work. Yale's guidance also recommends open questions and prompts that invite concrete stories. Ask a follow-up about an answer that matters instead of rushing to finish the list.

Questions about a typical week can help, but a specific recent task gives you details to examine. Avoid requesting customer records, internal dashboards, or private hiring information. A person can explain how they worked without handing over the underlying material.

Give the agreed time a simple shape

For an agreed 20-minute call, this is one possible agenda:

First 2 minutes: thank them, explain your question, and check the time limit.
Next 12 minutes: explore a recent example and ask relevant follow-ups.
Next 4 minutes: discuss what you could practice and what remains unclear.
Last 2 minutes: summarize what you heard, allow corrections, and close.

The allocation totals 20 minutes. It is a planning aid, not a reason to interrupt a useful answer at an exact second. If the example takes longer, drop a lower-priority question. Near the end, check the time rather than assuming that a friendly conversation means an extension is available.

Keep brief notes if the person is comfortable with that. Ask permission before recording; written notes are enough for this exercise. Finish with your interpretation in plain language: “I heard that clarifying the request took longer than building the chart in this case. Have I understood that correctly?” Their correction may be more useful than another prepared question.

Turn one account into a test, not a verdict

Consider this fictional conversation outcome. An analyst describes a delivery report where “late” could mean arriving after the promised date or after the customer's preferred date. They had to agree on the definition before calculating anything. You had expected analyst work to start with a clean question and a ready-to-use dataset.

Your note could read:

Question: Would I enjoy clarifying a reporting request?
What I heard: In this person's delivery-report example, agreeing on
the meaning of "late" was necessary before building the chart.
My interpretation: I need to try defining the measure, not just plotting it.
Limits: One person's example from one team; not a survey of analyst jobs.
Still unknown: How often this happens and how beginners get support.
Next test: Use a small invented delivery table. Write two definitions
of late, calculate each result, and explain why the counts differ.
Next conversation: Ask a person in a different team about a recent request.

Suppose your invented table has ten deliveries. Two arrived after the promised date, while four arrived after the preferred date. The rates are 2/10 = 20% and 4/10 = 40%. Both calculations can be correct for their respective definitions. Your practice output should state the definition and denominator before suggesting what someone should do with the result.

These numbers are fictional exercise inputs. They are neither the interviewee's data nor evidence about an employer. The useful test is whether you can explain the ambiguity and choose the next question to ask. The first data-analysis project guide helps extend that exercise into a checkable report.

One conversation may change your working hypothesis. It cannot establish what every employer requires, whether you will enjoy every part of the role, or whether someone will hire you. Preserve disagreements between sources instead of blending them into a confident general claim.

Budget the work you control

You might protect three 25-minute sessions: research the person and draft the request; select questions after a meeting is confirmed; then write the decision note and follow-up. That is 75 minutes of your own preparation and review, plus the agreed conversation and any travel. The waiting time for a reply is a dependency, not a task you can complete by working harder.

If the conversation moves to next week, keep the research and update the questions. If your preparation session disappears, shorten the background reading while preserving the main question and time agreement. If you already have a hiring interview scheduled, use the separate behavioral interview preparation guide for explaining your own experience.

Berkeley recommends a thank-you within one or two days. Mention a specific useful point without turning the note into an unagreed favor request. Record any permission to keep in touch, and follow through on a next step you actually chose.

You have finished this exploration step when your note distinguishes what the person said, what you infer, what remains unknown, and the small test you will do next. “We had a nice call” can be true while leaving the career question untouched.

Build my career-exploration goal in Kognivu with your current question, available sessions, and meeting date if one is confirmed. Check the generated path and first quest. Keep the conversation evidence and your decision note alongside the work.