Write a networking message that is easy to answer

Decide what you need to understand

“I want to work in technology” is too broad for a useful first conversation. “I am comparing implementation and customer-success roles, and I cannot tell how much each owns after launch” gives the other person a subject.

Choose a question connected to a real decision. Perhaps you need to understand a role's weekly work, which experience matters, or whether a job title means the same thing across employers. Research the obvious facts before asking someone to explain them.

Berkeley's career service^[1] distinguishes an informational interview from a job interview: its purpose is to explore work and a field, rather than ask for an opening. That distinction should be visible in your message and true in the conversation that follows.

If what you actually want is a referral to a specific vacancy, say so when appropriate. Do not book an “informational chat” and spring an application request on someone who agreed to something else.

Make the connection relevant, not flattering

A useful reason for contacting somebody might be a move they made between two functions, a public explanation they wrote, or experience with a type of work you are considering. You do not need to tell them they are inspirational.

Here is a fictional message from an operations coordinator exploring implementation roles:

“Hi Alex, I saw that you moved from operations into software implementation. I currently coordinate service rollouts and am exploring a similar move. When you started, was the larger adjustment learning the product or managing the customer's project? A short reply would be helpful, or I would appreciate a brief conversation if that is easier. No problem if you do not have capacity.”

The message does not claim a relationship that does not exist. It gives enough background to interpret the question, while leaving the recipient free to decline or reply asynchronously.

A shorter version can work for someone you know: “I am looking at implementation roles and remembered your move last year. Could I ask what part of the job turned out to be different from the adverts?”

Never imply a shared contact recommended you unless they actually did. If someone gave you a name privately, check whether you may mention that introduction.

Give the conversation a useful shape

If the person agrees to talk, send the main topic and agree a duration. Fifteen or twenty minutes can be a reasonable small request; it is not a rule everyone must accommodate.

Prepare a short introduction and a few questions that move beyond the public job description. For the fictional career change above, you might ask: “When a customer project stalls, what is usually missing?” and “Which part of my rollout experience would need a stronger example for this kind of role?”

Ask for a concrete recent situation if their answer is broad, without requesting confidential details. “Could you describe the type of decision involved?” is safer than asking to see an internal client document.

Listen for differences between employers. One person's experience is useful evidence, not a complete description of an occupation. Their company size, customers and responsibilities may be very different from those in the vacancy you are considering.

At the agreed end, finish. “This has answered my main question. Thank you for the time” is enough. If they choose to continue, that is their choice, not an assumption you should make.

Follow up with substance, not another task

A useful thank-you names what changed in your understanding: “Your distinction between coordinating delivery and owning the customer decision helped. I am going to revisit the roles I saved with that in mind.”

Later, if it is appropriate, share a brief outcome: “I used your suggestion to ask about implementation handovers. It helped me rule out a role that was mostly support.” Do not turn every follow-up into a request for another introduction.

Reciprocity does not require you to offer something artificial. A relevant resource, a thoughtful update or help within your actual expertise is enough when it naturally fits. You do not owe public praise or unpaid work in exchange for a conversation.

If nobody replies

A missed reply can mean many things. It does not tell you that your question was foolish or that nobody in the field will help.

If the first message was relevant, one brief follow-up after a reasonable interval can be enough. Then stop. Do not move across their personal channels, repeatedly tag them or treat visible online activity as an obligation to answer you.

Look for other routes: an existing colleague, an alumni group, a professional community with an explicit questions channel, or an open event. People who have invited questions are often a more suitable audience than a famous person with a crowded inbox.

Networking should not become a second full-time job. Start with one question that matters to your next decision, not a quota of new contacts.

Your next move

Write a message containing three things: why this person, what you need to learn and how small the response can be. Remove anything that sounds impressive but does not help them answer.

You are not asking somebody to manage your career. You are inviting them to help you understand one part of it.

If the conversation leads to an interview, use a preparation plan that does not depend on memorising a script. If applications are going unanswered, find the weak point before rewriting everything.

About this guide

UC Berkeley Career Engagement: Informational interviews. Supports the distinction between career exploration and a job request, preparation and respecting the agreed duration. The messages and implementation-role scenario are original fictional examples, not proven response-rate techniques.