Interview preparation guide
Informational Interview Questions: Learn About a Career and Choose a Next Step
Good informational interview questions help you investigate a career before committing to it. They invite someone to describe work they know, rather than asking them to predict whether you will be hired. Use the original fictional exchanges below to practice listening, following up and turning one conversation into a small, testable career decision.
Agree on a learning conversation
Berkeley Career Engagement distinguishes an informational interview from an interview for an opening. Its purpose is to learn. Research the person’s work first, explain your interest briefly and respect the time they agree to give. Do not disguise a request for a job as a request for advice.
Our fictional scenario is a customer-support professional exploring operations analysis. The contact is an operations analyst at a fictional service organization. Their answers illustrate possible follow-ups; they are not evidence that all analysts work this way.
A specific request you can adapt
“I work in customer support and am exploring operations-analysis roles. I would like to understand how analysts turn service problems into useful recommendations. If you have 20 minutes available, would you be open to a conversation about your day-to-day work and how you entered the field?”
Prepare an opening: “Thank you for making time. I have a few questions about the work, and I will watch the time. May I take brief notes for my own career research?”
1. What did you actually work on this week?
A concrete period can reveal more than a general list of responsibilities. Ask about an ordinary piece of work and what made it difficult. Avoid requesting confidential customer details or internal documents.
Fictional exchange: daily work
Question: “Could you walk me through a recent task, from the initial request to what you delivered?”
Contact: “A team wanted to know why its queue kept growing. I checked how requests were categorized, clarified what counted as open and compared the patterns with the team’s workflow.”
Follow-up: “Which part required the most discussion with colleagues, and which part was analysis you could do independently?”
What to record: the work involves agreeing on definitions before comparing numbers. Do not conclude from this one account that every analyst role has the same balance of meetings and analysis.
2. What does useful work look like to the people receiving it?
Job titles can conceal different expectations. Ask how the output is used, what decisions it informs and what happens when someone cannot act on it.
Fictional exchange: quality and impact
Question: “How do you know a report has been useful?”
Contact: “We discuss whether it answered the original decision. Sometimes a shorter explanation is more useful than an elaborate dashboard.”
Follow-up: “Can you describe a time when you changed the format after hearing what the team needed?”
What to record: communication and problem definition deserve practice alongside software. A possible next step is to explain a small public-data analysis to a nontechnical friend and ask what decision it supports.
3. Which entry skills matter, and how could I demonstrate them?
Ask about a realistic starting point for someone with your background. Separate the person’s own entry route from a requirement that every employer follows.
Fictional exchange: entry path
Question: “For someone moving from customer support, which skills would you look for in a first analysis project?”
Contact: “I would want to understand the question, see how the data was checked and read a clear explanation of the limitations.”
Follow-up: “Would a small project using public data be useful practice, and what would make it difficult to evaluate?”
Contact: “It would help if the question were narrow and the source were clear. A polished chart without an explanation would tell me less.”
What to record: this is one practitioner’s view, not a hiring promise. Compare it with actual entry-level vacancies and another conversation before choosing a course or large project.
4. What should I investigate before choosing this path?
Invite the less visible parts of the job without asking the person to criticize named colleagues. A neutral question about tradeoffs can reveal whether your interests fit the work.
Fictional exchange: fit and next questions
Question: “What part of this work surprised you when you started?”
Contact: “I expected more time building reports. I spend substantial time checking what people mean by the question.”
Follow-up: “What helps someone enjoy that part of the work?”
Closing question: “What kind of role or public resource would give me another perspective on this field?”
If they suggest a person, ask whether an introduction would be appropriate. Do not treat a name as permission to imply that the contact endorsed you.
Turn notes into a decision worksheet
Keep observations, your interpretation and your next action separate. This prevents a friendly conversation from becoming certainty about a whole industry. Thank the person with one specific lesson and, if appropriate, a brief update after taking the action.
Completed fictional note worksheet
Observation: This contact described checking definitions before comparing service queues.
Interpretation to test: I may enjoy the investigative and communication parts of operations analysis.
Next action: Use a public dataset to write a one-page analysis with a question, checks, finding and limitation.
Cross-check: Read several current vacancies and speak to someone in a different organization about the balance of technical and coordination work.
Decision after the exercise: Identify which tasks I enjoyed and which skills I need to practice before investing in a longer course.
Questions, answered
Should I send my resume before an informational interview?
Only when it is requested or clearly useful to the agreed conversation. A short description of your background is usually enough to explain what you hope to learn.
What if the contact gives advice that conflicts with another conversation?
Record the context: organization, role, seniority and type of work. Differences can reveal variation in the field. Compare the advice with vacancies and your own practice rather than choosing the most reassuring answer.
Sources and examples
ResumizeAI team. Examples are fictional teaching material, not customer results. Replace sample details with your own facts.
Your experience. A complete resume.
Build in Resumize with ATS-friendly templates, guided editing and a live preview. Start free, then upgrade when you need more.
Free account required. Free-plan PDF exports include a watermark.