What you'll learn: how to write a short, specific outreach message, ask for feedback or a referral without pressure, track what you send, and run a weekly loop of build, practice and outreach you can keep up.
At a glance
Figure 1. The weekly loop
How to read this: the loop is small on purpose; a routine you can repeat for twelve weeks beats a burst you cannot.
- Outreach works best when short, specific and easy to answer.
- Ask for feedback or a conversation, not a job.
- A tracker turns a feeling ("nothing is happening") into a count; nothing here predicts outcomes.
Scenario
Composite scenario, not a real company. An engineer sends the same long message to thirty strangers: a full career history, a request for any opening and a CV link. The replies ask questions the message already answered. A second engineer sends five short messages, each naming one thing in the recipient's public work and asking one small question. Both cases are illustrative.
What you will be able to do
- Write an outreach message of under 100 words that asks for one small thing.
- Write a referral request that is easy to decline.
- Keep a weekly tracker and run a four-part routine, adjusting after a review.
Prerequisites
You need your case study from Portfolio, case studies and LinkedIn and your lines from Positioning your enterprise experience.
Core ideas
What makes a message easy to answer
| Weak | Strong |
|---|---|
| Long history of you | One sentence on who you are and why you write |
| "Do you have any openings?" | One small question answerable in a minute |
| A generic compliment | A specific reference to their public work |
| Silence after a reply | A thank-you and what you did |
The default here is feedback first: it is a smaller request than a job, and useful whatever they answer. When you would not: if a person has told you they are hiring, say what you are applying for and attach what they asked for.
Three editable templates
FEEDBACK REQUEST (under 100 words)
Hello <name>, I read <specific public thing> and it helped me with <one point>.
I am building a Python service that turns vague product requests into cited
recommendations (a learning project, fictional data). Case study: <link>.
Would you be willing to tell me, in a line or two, what you would test that I
have not? No problem at all if you are busy.
REFERRAL REQUEST (to someone you already know)
Hello <name>, I am applying for <role type> roles. Would you be comfortable
telling me whether my case study reads as evidence for that? If you know of a
suitable team and think it is a fit, I would value an introduction; if not,
that is completely fine.
THANK-YOU AND FOLLOW-UP
Thank you for the feedback on <thing>. I changed <what> and the result was
<count, method>. If it is useful, here is the update: <link>.In the interview: "Tell me how you built your network" asks about initiative. Describe one honest interaction and what you did with the answer, not a count of connections.