{"title":"Cold Outreach","description":null,"content":"Cold outreach means messaging someone who does not know you yet. It can feel uncomfortable, so many job seekers avoid it. Others send messages that are too long, too vague, or too demanding, then assume outreach does not work.\n\nThe principle is simple: contact the right person, give a real reason for the message, and ask for something small. Most people will not reply, and that is normal. But a few thoughtful replies can lead to useful conversations, better information about a team, and sometimes a referral later.\n\nThis lesson focuses on reaching engineers at companies where you do not already have a connection. Cold-emailing recruiters and hiring managers is a different situation with a different goal, so treat that separately.\n\n---\n\n# Ask for Something Small First\n\nThe biggest mistake in cold outreach is asking too much from someone who has no context for you. \"Can you refer me?\" or \"Can you get me a job?\" is a big request from a stranger. Most people will skip it.\n\nA better first message asks for something small: a few minutes to talk about their team, an answer to two or three specific questions, or their honest view of what the work is like. That kind of request respects their time and starts a conversation instead of asking for a favor right away.\n\nKeep the message short. Say who you are, why you are contacting this specific person, what you are asking for, and thank them. Do not attach your resume in the first cold message unless they ask for it. Do not tell your whole career story. The goal is to earn a reply, not to make your entire case at once.\n\n---\n\n# Which Channel to Use\n\nYou have a few ways to reach someone you do not know. They are not all useful in the same way.\n\n\n| Channel | Reaches | Best for | Notes |\n|---------|---------|----------|-------|\n| LinkedIn connection request + note | People you want to connect with | Most engineer-to-engineer outreach | Short note; keep it specific |\n| LinkedIn message after connecting | New first-degree connections | Continuing the conversation | Better after they accept |\n| LinkedIn InMail | People you cannot connect with directly | Hard-to-reach contacts | Requires Premium; use selectively |\n| Cold email | Public professional email addresses | Recruiters and hiring managers | Better for recruiter or hiring-manager outreach |\n\n\nFor reaching engineers, a LinkedIn connection request with a short note is usually the best starting point. It is normal on the platform, and the note gives them a reason to accept. Save InMail for cases where you cannot connect directly or where the person is especially relevant to your search.\n\nThis is the quick way to pick a channel:\n\n\n```mermaid\nflowchart TD\n Q[Who are you
reaching?]:::start\n Q -->|Engineer on the team| E{Can you connect
directly?}:::decision\n E -->|Yes| CR[Connection request
+ short note]:::primary\n E -->|No| IM[InMail
use selectively]:::secondary\n Q -->|Recruiter or
hiring manager| CE[Cold email]:::secondary\n\n classDef start fill:#00ceff,stroke:#000,color:#000\n classDef decision fill:#ffd43b,stroke:#000,color:#000\n classDef primary fill:#69db7c,stroke:#000,color:#000\n classDef secondary fill:#38d9a9,stroke:#000,color:#000\n```\n\n\nThe connection request path is the usual starting point for engineer-to-engineer outreach, which is what the rest of this lesson covers.\n\n---\n\n# Writing the Cold Message\n\n### Find the right person, not the most senior one\n\nAn engineer on the team you might join is usually a better person to contact than the VP of Engineering. A senior leader may not have time and may be far from the day-to-day work. A peer or someone one level ahead can often give you a more useful view of the team.\n\n### Find one specific, true reason you're messaging them\n\nUse something real: you read their team's engineering blog post, you use a product they work on, or you are interested in the exact team listed on their profile. Generic praise like \"I admire your work\" sounds mass-sent. One specific detail shows you chose them on purpose.\n\n### Keep it to a few lines\n\nInclude who you are, the specific reason you are reaching out, the small request, and a thank-you. Do not include a resume dump or a long background story.\n\n### Ask for time or insight, not a job\n\n\"Would you have 15 minutes to share what it is like working on the platform team?\" is reasonable. \"Can you refer me?\" from a stranger is usually too much. If the conversation goes well, the referral conversation can come later.\n\n### Send the connection request with the note attached\n\nIf the platform lets you include a note, use it. The note explains why you are reaching out and makes the request easier to understand.\n\n### Follow up once after five days, then stop\n\nSend one short follow-up if there is no reply. After that, move on. Silence is part of cold outreach. Do not treat one unanswered message as a judgment about you.\n\n---\n\n# Templates\n\nThe message should fit in a few lines. Here are versions for the two situations you will see most often.\n\n**Cold connection note (engineer at a target company):**\n\n\n```javascript\nHi Wei, I'm a backend engineer focused on payments infrastructure, and I'm\nexploring roles at Figma. I saw that you work on the platform team. Would you be\nopen to a quick 15-minute chat about what the team is like? I understand if\nyou're busy. Thanks either way.\n```\n\n\n**Cold InMail or message (with a specific hook):**\n\n\n```javascript\nHi Wei, I read your team's post about moving a service to a multi-region setup.\nThe section on failover testing stuck with me. I'm a backend engineer going\nthrough a job search and targeting infrastructure teams like yours. Could I ask\nyou 2-3 questions about what the work is actually like day to day? Even a short\nreply would help a lot. Thanks for your time.\n```\n\n\n**Why these work:** Both messages are short, specific, and easy to answer. Each gives a real reason for contacting this person. Neither asks for a referral or a job in the first message, which matters when the person does not know you yet.\n\n**The follow-up:**\n\n\n```javascript\nHi Wei, just following up in case this slipped by. No worries if you don't have\ntime. Thanks again.\n```\n\n\n---\n\n# What to Ask For, and What Not To\n\nThe request is where most cold outreach goes wrong.\n\nGood first requests are small: fifteen minutes to talk about their team, answers to two or three specific questions, or their honest view of what the work is like. These are reasonable because they do not require the person to put their reputation behind you.\n\nBad first requests demand too much too soon: a referral, an introduction to their manager, a job, or a detailed resume review. Save bigger requests for later, after there has been a real conversation.\n\nKeep visa, sponsorship, and salary questions out of the first message to an engineer. Those topics matter, but an engineer you do not know may not have accurate answers and may not be the right person to ask. Bring them up with a recruiter later in the process.\n\nThis is the arc cold outreach usually follows when it works.\n\n\n```mermaid\nflowchart LR\n A[Research
person and team]:::start --> B[Short message
small ask]:::step\n B --> C[One follow-up
after 5 days]:::step\n C --> D[Short call
or reply]:::closing\n D --> E[Referral later
if there is a fit]:::done\n\n classDef start fill:#00ceff,stroke:#000,color:#000\n classDef step fill:#ffa94d,stroke:#000,color:#000\n classDef closing fill:#38d9a9,stroke:#000,color:#000\n classDef done fill:#69db7c,stroke:#000,color:#000\n```\n\n\nThe referral sits at the end of the arc, not the start. The first message only aims to earn a reply, and the larger ask comes later, after a real conversation has happened.\n\n---\n\n# Setting Realistic Expectations\n\nCold outreach has a modest reply rate. A thoughtful message to the right person can work, but most messages still go unanswered. The reply rate depends on timing, how busy the person is, how specific your message is, and whether your background is relevant.\n\nThat means you need enough attempts for the channel to work. Send a small batch of well-researched messages, track who replies, and improve the next batch. Do not read silence as rejection. Most non-replies mean the person was busy, missed the message, or did not feel they could help.\n\n---\n\n# Common Cold Outreach Mistakes\n\nCold outreach already has a low reply rate, and these mistakes lower it further.\n\n- **Asking for a referral or a job in the first message.** It is too much to ask from someone who does not know you. Ask for time or insight first.\n- **Writing a long message.** A short note is more likely to be read. Cut anything that is not needed for the first reply.\n- **Using a generic reason.** \"I admire your work\" sounds mass-sent. Use one specific, true detail about the person, team, or company.\n- **Targeting only senior people.** Senior leaders are busy and often farther from the role. Aim for peers and near-peers when possible.\n- **Leading with visa or salary questions.** Those questions are important, but they usually belong with recruiters, not in the first cold message to an engineer.\n- **Following up too much.** One follow-up is enough. After that, move to the next person.","pageType":"job-search"}

Get Premium