What you'll learn
Quick Answer
Skip it for campus placements and bulk portals, where nobody reads it. Write one for direct applications, small companies, referrals and role changes. Keep it under 200 words and make it about the specific company, not about you in general.
When it is read and when it is not
Being honest about this saves a lot of wasted effort.
Usually ignored: campus placement drives, where thousands of resumes are screened against fixed criteria; large job portals, where applications are filtered automatically first; and any process where the cover letter is an optional text box.
Often read: emailing a company directly; small companies and startups where a founder or engineer reads applications personally; applications through a referral, where your contact may forward it; and any case where you are explaining something unusual, such as a gap or a change of field.
The rough rule: the smaller the company and the more direct the channel, the more it matters. For a two-person startup, the email you send is the cover letter and it may matter more than the resume.
Why most of them fail
The standard fresher cover letter reads: "I am writing to apply for the position of Software Developer. I am a hardworking and passionate individual with good knowledge of Java, Python and DBMS. I am a quick learner and a team player. I would be grateful for an opportunity..."
Three things are wrong with it. It repeats the resume without adding information. Every sentence would apply equally to any other applicant. And it is about what you want rather than what you can do for them.
A letter that could be sent unchanged to fifty companies communicates exactly that, and a reader recognises it instantly. If yours does not name something specific about the company, it is not worth sending.
A structure that works, in four short paragraphs
1. Why this company, specifically. One or two sentences proving you looked. "I've been using your API for a college project and found the documentation unusually clear — it's part of why I'm applying here rather than sending this everywhere."
2. The most relevant thing you have done. One project, described by problem and outcome rather than by technology list. Pick the one closest to their work.
3. What you are looking for. One sentence, honest. "I'm looking for a backend role where I'll be reviewed by people more experienced than me."
4. A short close. No begging, no "eagerly awaiting". "Happy to walk through the code if useful. Resume attached."
Under 200 words. A long cover letter from someone with no experience signals padding, and it will not be read to the end anyway.
The research that makes it specific
Paragraph one is the whole letter. It needs one concrete, checkable detail — and finding one usually takes under ten minutes.
- Read the careers page and the product page, and use their own words for what they build.
- Look at their engineering blog if they have one, and reference a specific post.
- Try the product. "I signed up and noticed X" is immediately credible.
- Check their public repositories if any exist.
Avoid flattery that is not specific. "Your company is a leader in innovation" is the written equivalent of saying nothing. "I noticed you moved your docs to an interactive format last month" proves you looked.
If you genuinely cannot find anything specific to say, that is useful information — either the role is not a good fit, or you have not looked hard enough.
The email version, which matters more
For most fresher applications the real cover letter is the body of the email. Treat it accordingly.
Use a subject line that says what it is: "Application — Backend Intern — Asha Kumar" rather than "Job Application" or "Resume". Keep the body to three or four sentences with the same structure as above. Attach the resume as a PDF named with your own name.
Check the recipient's name is spelled correctly and that you have not left another company's name in from a previous send. That mistake is more common than you would think and it ends the application immediately.
Then follow up once, about a week later, briefly and politely. One follow-up is professional; three is not. See resume mistakes that get freshers rejected for the document itself.