Cold Emails to Hiring Managers and Founders, Done Respectfully

Writing to a company's general HR address puts your email in the same queue as hundreds of applications. Writing to the engineering manager whose team is hiring, or to the founder of a thirty-person startup, puts it in front of someone who has the problem the role is meant to solve. If your note shows you understand that problem and have built something related, they may forward it to the recruiter with "worth a look", which is often all you need.

It does not always work, and it can easily become intrusive. This article is about doing it well, and rarely.

• When cold outreach to a hiring manager or founder is worth the effort.
• How to identify the right person from public information.
• Which contact routes are acceptable, and which are not.
• A subject line and body that respect a busy reader.
• How to follow up once, and how to measure whether the channel works for you.

Cold outreach supplements applying. It does not replace it: apply through the careers page as well, so your application exists in the system, and mention that you have.

Use only public information:

• The job description. It may name the team ("Payments Platform", "Growth Engineering"), the manager's title or the location.
• The company's team or about page. Small companies often list their engineering leads.
• The engineering blog and talks. Authors and speakers often lead or belong to the team doing that work.
• LinkedIn. Search the company with titles such as "engineering manager", "head of engineering" or "tech lead", and the team or domain name.
• Founders and CTOs at startups, who are usually easy to identify from the company site or news coverage.

Check that the person is still at the company (their LinkedIn profile) and that the team matches the role.

Why the line matters: people did not agree to be contacted at addresses you inferred, guessed messages often bounce or land in spam, and being contacted unexpectedly at a private address feels intrusive, which is the opposite of the impression you want. A published address or a platform built for professional messages is enough.

The subject decides whether the email is opened. Be specific and about their work.

Goal: a reply, a forward to the recruiter, or a look at your project.

A weak first draft:

Respected Sir,I am a final year student from XYZ College with a CGPA of 8.1. I am very passionateabout technology and have done many projects in Java, Python and web development.I came to know your company is a leading company in fintech. I request you tokindly consider me for any suitable role. My resume is attached. Hoping for apositive reply.

Everything in it is about the sender, and nothing gives the reader a reason to act.

A better version:

Subject: Backend role on Payouts: built a related retry serviceHi Neha,Your team's post on making payout retries safe was the clearest explanation ofidempotency I've read; I used the same "store the request key first" approach ina small payment service I built ([demo] [code]). The trickiest part was tworetries arriving at the same moment, which I solved with a unique constraint andcovered with tests.I've applied for Software Engineer I, Payouts (job ID 4821937) on your careers page.If my project looks relevant, I'd be grateful if you could pass my application tothe recruiter, or tell me what you'd want to see from a junior on your team.Thanks for writing the post either way.[Name] · [LinkedIn] · [GitHub]

Why it works:

• Opens with their work, specifically and honestly. You read it, and you can say what you took from it.
• One piece of proof connected to their problem, with a detail an engineer will recognise.
• States the role and that you applied, so they know exactly what you are asking about.
• A small, concrete ask with an alternative ("tell me what you'd want to see").
• No attachment needed; links are lighter and safer. Attach a resume only if a company's process asks for it.

Edit this cold email to a hiring manager. Keep my facts and voice.Rules: under 150 words; first sentence about their published work, using onlywhat I wrote; one project link; state the role and job ID and that I applied;end with a small ask and an easy out. Suggest a specific subject line.Remove flattery, "kindly", "respected sir", and any claim about their companythat is not in my draft.[paste draft]

Then check that every statement about their work is accurate. If the assistant made your praise more effusive, tone it down; specific beats glowing.

Some candidates send a sixty to ninety-second screen recording walking through their project, with a one-line message. It can stand out, but it asks more of the reader, and many people will not click a video from a stranger. If you try it, keep it short, show the working project in the first fifteen seconds, and send it only where you have a strong, specific connection.

Day 0     SendDay 7     One follow-up, with something new if possibleThen      Stop. Keep the person in your tracker; do not write again for this role

Hi Neha, a short follow-up on my note about the Payouts role. Since then I'veadded a load test to the project (p95 under 200 ms at 50 concurrent users locally):[link]. Thanks for considering it, and no need to reply if it's not a fit.

Silence is an answer. A manager who did not reply may still have forwarded your note, so keep applying and preparing.

Record each outreach in your tracker with the channel "cold outreach", the person's role (founder, manager, lead) and the outcome. After ten to fifteen, compare its response rate with referrals and careers-page applications for the same time spent. For many freshers it works well with startups and poorly with large companies; your numbers will tell you.

Arjun targets developer-tools startups. For one company with 40 people and a "Backend Engineer, 0 to 2 years" opening:

1. He applies on the careers page.
2. The job description mentions the "CLI and integrations" team. The company's blog has a post by the team's lead on designing helpful error messages.
3. Her LinkedIn profile shows she leads that team; the company's site lists a careers email but no personal addresses.
4. He connects on LinkedIn with a note about the post, then sends a 120-word message after she accepts, linking his own command-line tool and its error-message design.
5. A week later, no reply; he sends one follow-up with a link to a new feature.
6. Two days later the recruiter emails him an assessment link, saying the team lead had flagged his application.

He cannot know for certain that the message caused it, but the timing suggests it helped. He records it, and moves on to the next company.

• Writing to managers instead of applying, rather than as well as applying.
• Guessing or harvesting private email addresses.
• Generic openings that could be sent to any company.
• Long emails with your whole background.
• Praising work you have not read.
• More than one follow-up.

Subject: Junior backend role: built live order tracking with server-sent eventsHi [Founder name],Your post on tracking delivery partners in real time made the trade-off betweenpolling and push very clear. I built a small order-tracking service that pushesstatus changes with server-sent events, including reconnection when the networkdrops ([demo] [code]). Handling events arriving out of order was the hardest part.I've applied for the Backend Engineer (0 to 2 years) role on your careers page.If it looks relevant, I'd be grateful if you could pass my application on, or tellme what you'd want to see from a junior engineer.Thanks either way.[Name] · [LinkedIn] · [GitHub]

• Next: Application Execution: Volume, Quality, Cover Notes and Speed turns everything in this module into a weekly routine.
• For email templates for applications, see How to Write a Cover Letter and Job Application Email That Gets Replies.
• For finding startups before they post, revisit Find Companies Before They Post: Funding News and Founder Signals.