How to Reach Out to Engineers at Companies You Want to Work At

TL;DR

Reach out to individual contributors (ICs), not hiring managers or recruiters, for the best response rates.
Short, specific messages asking for a 15-minute call get responses. Long, vague messages don't.
Ask for a conversation, not a job or a referral. The relationship has to exist before the referral makes sense.
Follow up once after one week. If there's still no response, move on.
What you do with the conversation matters as much as getting it.

Cold outreach is one of the most underused tactics in a software engineering job search. Most people try it a few times, get ignored, and conclude that it doesn't work. They're usually right that it didn't work. They're wrong that it can't.

The problem isn't the tactic. It's the execution.

We've seen students who come through our program transform their job search by shifting from mass applications to targeted outreach. The ones who do it well land conversations that turn into referrals, and referrals convert to interviews at a rate that no amount of cold applying can match. The ones who do it badly send five messages that get no response and give up.

This article is about execution. If you already understand why networking matters and want the full strategic picture, the networking guide for engineers who find this uncomfortable covers that context. This article focuses on the specific mechanics of reaching out, what to say, what not to say, and what to do when someone actually responds.

Before you start any outreach, your LinkedIn profile and GitHub need to be in good shape. Every person you message is going to check your profile. How to use LinkedIn for your software job search covers what "in good shape" means in detail. Don't start sending messages until that's done.

Who to Reach Out To

The most common mistake in cold outreach is targeting the wrong people.

Reach out to individual contributors (ICs), not hiring managers or recruiters.

Hiring managers receive dozens of messages from job seekers per week. Many have filters or policies against responding to cold outreach about open roles. They're also operating under a different incentive: they're responsible for decisions, which makes them more cautious about who they engage with.

Recruiters are even more inundated. Internal recruiters get LinkedIn messages from job seekers constantly, and responding to all of them is not their job. You can connect with a recruiter, but that connection rarely produces the kind of relationship that leads to a referral.

Individual contributors, especially engineers who are two to five years into their career, are a different story. They're not responsible for hiring decisions, so the pressure is lower on both sides. Many remember what the job search felt like. And they have insight into what the team is actually like day-to-day that a recruiter or hiring manager won't share.

Senior engineers and staff engineers can be good targets too, but they tend to be busier and more selective about who they respond to. They're worth reaching out to when you have a specific, substantive reason. If you've been using their open-source library and have a real question about its design, that's a legitimate opening.

Avoid VP-level and above. The hierarchy gap is too large, and these people are far too busy for informational conversations with unknown job seekers.

Where to Find Engineers to Contact

LinkedIn is the most straightforward place to find engineers at specific companies. Search the company name, filter by "People," and then filter further by title (Software Engineer, Backend Engineer, etc.) and career stage. The alumni filter is particularly useful: if you went to the same school as someone at the company, the response rate is significantly higher.

Second-degree connections are worth prioritizing. When you have a mutual connection, you can reference that person in your message ("Alex Chen mentioned you work on the backend team at [company]"). That one sentence changes the dynamic from stranger outreach to something closer to a warm introduction.

GitHub

GitHub is underrated for finding engineers. If you're interested in a company, search for their GitHub organization and look at who's contributed to their public repositories. Engineers who contribute actively to open-source projects often have contact information in their profiles, post on Twitter/X, or have personal websites.

Reaching out to someone because you've actually used or contributed to their project is one of the strongest openings possible. "I've been using your [library] for a project I'm building and had a question about how you approached [specific design decision]" is a genuine entry point for a conversation. From there, it's natural to ask about the company.

Twitter/X and Personal Websites

Many engineers share their work and thinking on Twitter/X. Engineers who post about technical topics publicly are generally more receptive to outreach than those who don't have a public presence. Their tweets or posts can also give you something specific to reference in your message.

Conference speaker lists are another source. If an engineer gave a talk at a conference you watched online, referencing that talk is a specific and genuine way to open a conversation.

What a Good Message Looks Like vs. a Bad One

This is where most people go wrong. The message itself is the thing that determines whether you get a response.

Bad Outreach: What to Avoid

Here are three real patterns that don't work.

Too long:

"Hi [name], I hope this message finds you well. I'm a recent computer science graduate from [university] and I'm currently looking for opportunities in software engineering, specifically in backend development. I came across your profile while searching for professionals working at [company], and I was really impressed by your background and experience. I'm very passionate about software development and have been working on several projects in my spare time. I would love the opportunity to learn from someone with your level of experience and possibly get some advice on how to break into the industry. If you have any time in your schedule, I would love to set up a call or even just exchange a few messages. Thank you so much for your time and I hope to hear from you soon."

This message is long, generic, says "I hope this message finds you well" (a phrase that signals template immediately), leads with flattery that reads as scripted, and asks for vague help without specifying what kind. The recipient has no reason to respond.

Too needy:

"Hi, I've been applying for months and haven't heard back from anywhere. I really need to get into this industry and I'm running out of options. Would you be willing to look at my resume or put in a referral for me? I would be so grateful."

The emotional framing isn't wrong, but it puts pressure on the recipient and asks for a significant favor from someone who doesn't know you. This message usually makes people uncomfortable and they avoid it.

Asking for a job directly:

"Hi, I see you work at [company]. I'm currently applying for the software engineering role there and wanted to ask if you could help me get an interview. I think I would be a great fit."

Asking a stranger to put their professional credibility on the line for you before they know anything about you is a big ask. Most people won't do it. Some will find it off-putting.

Good Outreach: What Works

Good messages share three properties: they're specific, they're short, and they ask for something small.

Template 1: The shared interest angle

"Hi [name], I've been building a [project type] using [relevant tech stack] and found your [post / talk / repo] on [specific topic] really useful. I'm targeting backend roles at [type of company] and had a question about [specific thing]. Any chance you'd have 15 minutes for a call? Happy to work around your schedule."

This works because it opens with something specific (a real project, a real technical reference) and asks for something specific (15 minutes, a defined topic). The recipient can say yes or no easily.

Template 2: The alumni angle

"Hi [name], I came across your profile through [University] alumni. I'm a [year] grad targeting entry-level backend roles and I noticed you've been on the [team type] at [company]. Would you have 15 minutes to tell me a bit about what the team looks like and what they tend to look for? No worries if you're swamped."

The alumni connection does a lot of work here. The "no worries if you're swamped" is genuine and takes the pressure off.

Template 3: The specific question angle

"Hi [name], I'm working through [problem you're solving] and noticed you've written about [related technical topic]. I'm also job searching and would love to ask a few questions about [company] if you have a few minutes. A quick 15-minute call would be great, but totally understand if the timing doesn't work."

All three templates are under 100 words, reference something specific, and ask for 15 minutes. The ask is small. The person can make a quick yes/no decision.

How Long Should the Message Be

The answer is shorter than you think. Three to five sentences is the target. If you can't make your case in five sentences, you haven't thought clearly enough about what you're asking.

One sentence for who you are and what you're working on. One to two sentences for why you're reaching out to this specific person. One sentence for the ask. An optional closing line.

That's it. Anything longer signals that you haven't considered the reader's time, which is not the impression you want to make.

What to Ask For: The 15-Minute Call

The right ask is a 15-minute call to have a conversation. Not a job. Not a referral. Not a resume review.

There are a few reasons for this. First, a call is low-commitment. Fifteen minutes is easy to say yes to. Second, a conversation gives you information you can't get from any other source: what the team is actually like, what they look for, what the day-to-day work feels like. Third, people who've had a good conversation with you are significantly more likely to refer you than people who've only read your LinkedIn message.

The referral is the output you're working toward. But asking for a referral before the relationship exists is asking someone to take a professional risk for a stranger. That's a big ask. Ask for the conversation first. Let the relationship develop. The referral often happens naturally.

Following Up: Once, Specifically, Then Let It Go

You send the message. Nothing happens.

Wait one week. Then send a single follow-up:

"Hi [name], just wanted to follow up on my message from last week. No worries at all if the timing isn't right, but wanted to check in."

That's the whole message. Short, low-pressure, clear.

If you don't hear back after two messages, stop. Following up a third time crosses into territory that feels like pressure, and it can damage how you're perceived at that company for future interactions. Some people never respond to cold outreach, no matter how good the message is. That's fine. Move to the next person on your list.

If someone says they're not available or aren't taking outreach right now, respect that. Respond with: "Totally understand, thanks for letting me know." That's it. Don't argue or ask for an alternative. The graceful response to a no builds more goodwill than most people expect.

What to Do With the Conversation When You Get It

Getting a response is only half the work. The conversation is where the relationship actually forms.

Come prepared. Bring three or four specific questions. Avoid questions you could answer with a Google search. Ask about things only an insider would know: what the code review culture is like, how the team handles on-call, what they wish they'd known in their first few months, what a typical sprint looks like.

For your questions, make sure your resume and materials are already clean before the call. If the conversation goes well, the engineer might ask to see your resume or offer to pass it along. You want that version to be ready.

Don't lead with your job search. Let the conversation develop naturally before you bring it up. Usually the engineer will ask what you're working on or what kind of roles you're targeting. That's your opening.

When you do talk about your background, be specific. Describe what you've built, what kind of role you're targeting, and what your timeline looks like. Keep it brief. This is not the pitch; it's the context.

At the end of the conversation, ask: "Is there anyone else at [company] or elsewhere you'd recommend I talk to?" This one question can turn a single conversation into a chain of introductions. Most people who had a good conversation with you are happy to make a connection. Many won't think to offer unless you ask.

Follow up within 24 hours with a short thank-you. Reference one specific thing from the conversation: "Thanks for taking the time today. Your point about [specific thing they said] was really useful. I'm going to try [specific thing] with my job search." That specificity shows you were listening and makes you memorable.

A Realistic Timeline

Cold outreach is not a fast tactic. It takes time to send messages, wait for responses, have conversations, and let relationships develop. For most job seekers, it takes four to six weeks from first outreach to first referral, sometimes longer.

That's not a reason to avoid it. It's a reason to start it earlier than feels necessary.

The pipeline looks like this: you send 10–15 messages over two weeks. Three to five respond. You have those conversations over the following two to three weeks. One or two of those conversations produce warm introductions or referrals. Those referrals go into applications. Those applications move faster than cold ones.

The candidates who get the most out of cold outreach treat it as a parallel track alongside job applications, not a replacement for them. You're building relationships that will compound over weeks and months, while continuing to apply to roles where you have the right qualifications.

Cold outreach works when it's done with care. Be specific. Be brief. Ask for a conversation, not a favor. Follow up once. Then have a genuinely good conversation when someone says yes.

The engineers you reach will mostly be reasonable people who remember what it felt like to be job searching. Treat them that way and the responses will come.

If you want to practice your outreach and interview narrative with structured feedback, here's how Globally Scoped works with job seekers on the networking and interview phase.