Cold Email for a Software Engineer Job: Skip HR, Send the Repo

Your resume says Java, Python, DSA and React. So does nearly every other resume in the pile. A cold email for a software engineer job wins when it carries the one thing a resume cannot: a link an engineer can click, read and judge in a minute. And it wins when it goes to the person who reads code, the engineering manager or team lead, not an HR inbox.

Below: who to write to, what to link, how to make that link survive a 60 second look, three templates for SDE freshers, and the one follow-up to send.

Who should you cold email for a software engineer job?

The engineering manager or tech lead of the team you want to join. They own the problem the job exists to solve. They can read your code. And when they like what they see, a one-line forward to their recruiter ("can we talk to this one?") moves you further than another application would. HR and talent teams matter later, for process, but they are rarely the people who can judge a pull request. At an early startup in Bengaluru or Pune, the right person is often the CTO or a founder who still writes code.

Why send a cold email instead of only applying?

Because the application route is crowded and filtered by people who cannot read your code. A typical opening draws about 242 applications (The Interview Guys, April 2026, citing Business Insider data), and the same piece cites the typical success rate of an online application at roughly 0.1% to 2%. Recruiters spend about 6 to 7 seconds on a first resume scan (Ladders eye-tracking study, 2018). That is not enough time to tell someone who has built things from someone who listed the same keywords. An engineering manager clicking your repo can tell in a minute. Studojo's position is simple: email the person who hires, with proof, from your own address. Our report on how to get a job as a fresher in India makes the full case.

What should you link: a repo, a live project or a pull request?

Link the strongest single thing you have, and only one. In our view, they rank like this:

Proof	Why it works	Watch out for
A shipped project with real users, even a few dozen classmates	Shows you finished something and dealt with real bugs	Say what broke and how you fixed it
A merged pull request in a real open-source project	Shows you can read someone else's code and pass review	Link the PR itself, not the project homepage
A deployed side project with a clean README	They can click and use it in seconds	Free hosting can sleep; check it loads before you send
A prototype that touches their product	Shows you looked at their problems, not just their logo	Call it a prototype; never claim you rebuilt their product
A competitive programming profile	Signals problem solving	Weak alone; pair it with something you built

Our Proof-of-Work Report goes deeper on which projects and portfolios hold up.

How do you make a repo readable in 60 seconds?

Assume the manager opens the README, glances at the folder structure and maybe opens one file. Make those three things count:

• The first line of the README says what it does and who it is for, in one sentence.
• A live link and a short GIF or screenshot sit right at the top.
• Setup takes three commands or fewer, and they work.
• A short "decisions" section explains why you chose Postgres over MongoDB, why you added a queue, and what you would change with more time.
• There are tests, even a few, and CI if you set it up.
• Commit messages describe changes, not "final final v2".
• It is pinned on your GitHub profile, and old tutorial clones are archived.

A to-do app or a streaming-site clone from a tutorial is not proof on its own. A clone with one real twist is: offline sync, a UPI payment flow with webhooks handled properly, a load test you ran and wrote up. The twist is what an engineering manager remembers.

How do you find the engineering manager at a company?

Start with the team, not the title. These are the places engineering leads tend to show up in public:

• LinkedIn: search "[Company] engineering manager" or "[Company] tech lead", then read their posts to confirm which team they run.
• The company's engineering blog: authors of recent posts often lead or sit on the team that built the thing.
• GitHub: maintainers of the company's public repositories.
• Meetup and conference talks: speakers usually name their team.
• Hiring posts: many managers post "my team is hiring" themselves.

Then you need the email address, and guessing a pattern is how emails bounce. Studojo does this for you: it finds the person and verifies their email before anything is sent.

Software engineer cold email template for freshers

Three templates, one for each kind of proof. They work as a cold email for a software developer job, a backend role or a frontend role alike. Replace every bracket with something true, and keep the total under about 120 words.

Template 1: the prototype that touches their product

Subject: Built a small [feature] prototype for [Company]'s [product area]

Hi [Name],

I use [Company]'s [product] and kept running into [specific problem]. I built a small prototype that [what it does], in [stack]: [repo link].

The README covers the design choices in under two minutes.

I am a [year] graduate from [College] looking for a [Role] role. If your team is hiring, would you be open to a 15 minute call? If it is not you, who should I speak to?

Thanks,

[Your name]

[GitHub link]

Template 2: the merged pull request

Subject: [Role] applicant: my merged PR in [open-source project]

Hi [Name],

Your team works on [system or service], so this may be relevant: I fixed [bug or feature] in [open-source project], which your stack also depends on. The merged PR is here: [link].

Getting it through review taught me [one specific thing, such as their test conventions or a race condition you tracked down].

I have also applied for the [Role] opening on your careers page. Could I get 15 minutes to hear what your team is building?

Best,

[Your name]

Only say a company depends on a project if you have checked. One wrong claim ends the read.

Template 3: the feature you shipped in an internship

Subject: Shipped [feature] to [number] users in my internship

Hi [Name],

I read your post on [topic] and it matched a problem I worked on.

During my internship at [Internship company], I built [feature] in [stack]. It went live to [number] users and cut [metric] by [amount]. A short write-up with code samples: [link].

I am looking for a [Role] role from [month]. Is your team at [Company] hiring? I would value a short call.

Thanks,

[Your name]

The follow-up, sent once

Hi [Name],

Following up in case this got buried. Since I wrote, I added [one improvement, such as tests, a benchmark or a deploy] to [project]: [link].

Happy to speak with whoever on your team is hiring for [Role].

Thanks,

[Your name]

Send it about a week later, in the same thread. A follow-up that shows progress gives them a fresh reason to click. Then stop and move to the next team on your list.

How long should a cold email to an engineering manager be?

Short enough to read on a phone between standups: under about 120 words, one link, one ask. Subject lines that work name the thing you built or the role, so "Merged PR in [project], [Role] applicant" beats "Job application for SDE role". Do not make a resume attachment the main event. Link the proof in the body and put your resume link in your signature.

What gets a cold email for an SDE job ignored?

Mostly, emails that describe you instead of showing your work:

• A stack dump: "Java, C++, Python, React, Node, AWS, Docker, Kubernetes" with nothing built.
• "I am passionate about coding" as the first line.
• A link to your whole GitHub profile, full of forks, instead of one repo.
• Leading with your problem count on a coding platform.
• Asking a stranger for a referral in line one.
• "Respected Sir/Madam", or the same email sent to fifty managers.
• Calling a prototype a rebuild of their product.

Should you still apply on the careers page?

Yes, for the one role that fits. Many companies need you in their applicant system before a recruiter can move you forward, so apply to that role and mention it in your email. What you should not do is apply to every opening on the page: recruiters quoted by NBC News (17 November 2024) named one person applying to dozens of roles at the same company as a pattern they flag as a bot. Mass fresher hiring at large IT services firms usually runs through their own hiring tests and drives, and a cold email is unlikely to skip that process. The engineering manager route pays off most at product companies, startups and specific teams.

Applying outside engineering too? Our guide to the cold email for a fresher job has templates for marketing, analytics and sales.

How does Studojo send this email for you?

We built Studojo to do exactly this. You upload your resume, and setup takes about 2 minutes. Studojo finds the person who can actually hire you, the engineering manager or team lead rather than a generic HR inbox, with people sourced from 20,000+ databases. It verifies their email address, writes a personal email for that one person based on your background and their work, and sends it from your own Gmail. It is a one-time payment, not a subscription.

8,500+ students signed up, 4,000+ matched with hiring managers and 28,000+ personal emails sent from students' own Gmail (Studojo's own records, September 2026). Replies are not guaranteed. What you get is your repo in front of someone who can read it. When your project is ready, email the engineering manager with Studojo.

Frequently asked questions

Should I ask an engineering manager for a referral?

Not in the first email. Ask about their team and the role. If they like your work, they can pass you to their recruiter directly, which often does more than a referral from someone who barely knows you.

Can I cold email a CTO at a startup?

Yes. At a small startup the CTO is often the hiring manager for engineers. The same rules apply: one link, one specific line about their product, one small ask.

What if my projects are basic?

Pick one and make it deep. Add tests, deploy it, write up your design decisions and add one feature that solves a real problem. One project you can defend line by line beats five tutorial clones.

Does this work as a cold email for a tech job outside SDE roles?

Yes. For DevOps, QA, data engineering or mobile roles, the rule is the same: email the lead of that team with one artifact they can check, such as a pipeline, a test suite or a published app.

Should I attach my resume to the email?

Put a resume link in your signature and let the project link do the work in the body. If they ask for a PDF, send it in your reply.