Run an informational interview that changes your next step

Before choosing whom to contact, write down what you do not yet understand. Perhaps you are comparing two occupations, testing whether a career change makes sense, or trying to learn which skills a junior role uses most often. A narrow uncertainty helps you find someone whose experience is relevant. It also keeps the conversation from becoming a broad request for life advice.

CareerOneStop distinguishes an informational interview from a hiring interview: its purpose is learning about work and organizations. That distinction shapes the request. You can mention that you are exploring opportunities, but do not disguise a request for a job as an innocent question. A clear purpose lets the other person decide whether they can help and prepares them for the kind of conversation you want.

For a fictional example, Pavel is considering a move from museum visitor services to learning program coordination. He wants to know whether the work is primarily planning, facilitation, or administration. That question is specific enough to investigate. Asking whether he should leave his current job would require the other person to judge personal circumstances they do not know and a decision they cannot make for him.

Look for professional experience related to your uncertainty. A person currently doing the work may explain daily tasks. A recent entrant may remember the learning curve. A manager may explain team expectations. None has a complete view of the field. Choose deliberately and remain aware of the perspective you are receiving rather than treating one conversation as a representative survey.

You can start with existing professional or educational connections, public events, alumni networks, or people who share their work publicly. Use appropriate contact channels and respect stated preferences. Research enough to avoid asking questions already answered in the person’s public profile. You do not need to collect personal details or manufacture similarities. A genuine work-related reason for contacting them is sufficient.

Pavel chooses a fictional coordinator who moved from front-of-house work into program operations because that transition resembles his question. He also plans, later, to speak with someone who entered directly from education. The second perspective may reveal what is specific to the first person’s route. The goal is not to find someone who confirms Pavel’s preferred answer; it is to understand the work more accurately.

A good request says who you are, why this person’s experience is relevant, what you hope to learn, and what form of conversation you are proposing. Keep the scope manageable. You can offer flexibility about format and timing. Do not send a long autobiography or a list of twenty questions with the first message. The recipient needs enough context to decide, not the full preparation document.

Here is a fictional request: Hello Morgan, I work in visitor services at a local museum and am exploring learning program coordination. I noticed your move from public-facing work into program operations. I would value a short conversation about how the day-to-day responsibilities changed, particularly planning and administration. If a brief call is convenient in the coming weeks, I would be grateful; a short written response would also help.

The recipient can understand the purpose and decide whether they have time for the conversation. If the person declines or does not respond, respect that boundary. A restrained follow-up may be appropriate depending on the channel and context, but repeated messages do not improve the underlying fit. Continue your research through other sources and people rather than making one contact the gatekeeper for your entire exploration.

Build questions around a recent example. What did your last program require from first planning meeting to delivery? Where did coordination become difficult? Which decisions could you make yourself, and which needed approval? These prompts are more likely to reveal a process than broad questions about whether the career is enjoyable. They also allow the person to choose an example they can discuss appropriately.

Ask about variation. A typical day can be hard to describe when work changes across seasons or projects. You might ask how a launch week differs from a planning week, or what changes when a program is small versus large. This helps you avoid mistaking one vivid story for the whole role. Pay attention to which tasks recur and which appear only under unusual conditions.

Include questions about learning and tradeoffs. What took longer to learn than expected? What does a beginner tend to underestimate? Which part of the work do outsiders rarely notice? Avoid requesting confidential information about colleagues, customers, hiring decisions, or internal problems. You can learn a great deal about the structure of work without asking someone to disclose details they should not share.

Begin by confirming the available time and the purpose of the conversation. Give a brief introduction, then let the person talk. You can take notes with their awareness, but avoid recording without explicit permission. Your preparation is a guide, not a questionnaire that must be completed. If an unexpected answer addresses a more important uncertainty, follow it thoughtfully.

Distinguish description from advice. The person may describe how their organization works, explain their own preferences, and suggest what you should do. Those are different kinds of information. A statement such as I learned best by supporting a senior coordinator is a personal experience, not proof that everyone should follow that route. Ask what made it useful and which conditions mattered.

In the fictional conversation, Pavel learns that program coordination includes much more participant data checking than he expected. He asks what kinds of errors are common and how the team prevents them. That follow-up reveals a practical task he can test through a volunteer project. The conversation has become valuable because it changed his understanding, not because it made the career sound uniformly appealing.

It is reasonable to ask how people enter the work and what evidence helps a beginner demonstrate readiness. Keep the question about patterns the person has observed, not a demand that they secure your entry. Ask which tasks a new colleague usually handles first, what training is available, or what sample of work would help explain a transferable skill.

If the conversation naturally turns to openings, be transparent about your interest. You can ask where suitable roles are normally advertised or whether there is a published process you should follow. Let the person decide whether to offer a referral or introduction. Do not assume that giving you time creates an obligation to advocate for you, and do not name them in an application without permission.

Pavel asks which experience would make his visitor-services background easier for a hiring team to understand. The fictional coordinator suggests showing a planning example and a careful administrative process. Pavel treats that as one informed perspective. He compares it with actual job descriptions before changing his documents. A conversation can guide his attention without replacing the employer’s stated requirements or his own judgment.

As the agreed time approaches, identify one or two points that changed your understanding. A brief summary lets the person correct a misunderstanding. You might say: I had pictured this as mostly delivery work, but your example shows how much preparation and record checking sit behind it. I will look more closely at those tasks before deciding which roles to target.

Ask whether there is a public resource they recommend if that would help. Avoid automatically requesting another introduction at the end of every conversation. If an introduction would address a clear remaining question, explain why and make it easy to decline. The quality of the exchange does not depend on extending the contact chain indefinitely. Sometimes the right next step is to use what you have already learned.

Send a concise thank-you through the appropriate channel. Mention a specific insight and any action you plan to take. If you promised to share something, follow through. Do not attach a resume unexpectedly unless the person asked for it or the context clearly supports it. A thank-you is a continuation of the actual conversation, not an opportunity to introduce a hidden application request.

Review your notes while the details are fresh. Make three lists: what I learned, what remains uncertain, and what I will test next. Keep the person’s statements separate from your conclusions. If they described long planning cycles in one organization, do not rewrite that as every program role has long planning cycles. The limits of the evidence matter when you use it to make decisions.

Choose a small action that can produce new information. Pavel decides to help organize the registration and attendance process for a fictional weekend workshop. He wants to see whether he enjoys the administrative detail as much as the public-facing work. Another candidate might review several job descriptions, complete a relevant practice task, or speak to a second person in a contrasting setting. The action should address the uncertainty that remains.

You can later update the contact if you have a meaningful result and the relationship supports it. A short note explaining that their insight helped you test a task is more useful than routine messages with no new substance. Do not expect ongoing coaching unless that has been agreed. The original conversation can be complete and valuable even if it never develops into a continuing relationship.

Before meeting, confirm your purpose, core questions, logistics, and agreed time. Keep the introduction brief so most of the conversation can explore the work. Optional questions can guide the discussion.

Afterward, ask what you learned that could change your behavior. If notes contain only encouragement, seek more concrete examples next time. If advice is specific, check whether its context matches yours before acting. Combine others’ experience with direct exploration.

• My request clearly asks for information, with no hidden hiring demand.
• The person’s experience matches a question I actually need to answer.
• My questions explore tasks, decisions, learning, and variation.
• I respect time, confidentiality, and the option to decline.
• I have a concrete next action and know what remains uncertain.