Cover letter guide
Cover letter for an internship.
Internship cover letters are shorter than full-time application letters, and they're the only cover letter where writing about coursework and side projects is genuinely useful. This guide shows how to make a half-page letter that a hiring manager will actually finish.
1. Keep it short
Internship letters should be 200–300 words. Shorter than full-time applications, because you don't have enough to say yet to fill a full page without padding. Recruiters read hundreds of internship letters; short and direct wins.
2. The three-paragraph structure
Skip the standard four-paragraph structure and use three:
- Opening: what role, why you're applying.
- Evidence: one specific piece of work — a project, coursework, or a self-directed thing.
- Interest: what you want to learn and why this role would help.
3. Opening
I'm applying for the Summer 2025 Software Engineering Internship. I'm a third-year computer science student at National University of Computer Sciences in Karachi.
That's enough. Don't spend two sentences introducing yourself. The letter shouldn't start with "My name is..." — your name is at the top.
4. Evidence
Pick one project you're proud of and describe it well. One well-described project beats three vaguely-described ones.
Last summer I built CollabNote, a real-time collaborative text editor. It uses React on the frontend, a small Node.js WebSocket server, and a simple operational-transform model to keep multiple clients in sync. The hardest part was handling a race condition where messages could arrive out of order — I ended up adding sequence numbers and a re-ordering buffer on the client side. It's been used by about 15 people in my study group, and it's on my GitHub if you want to look.
Notice what that paragraph does: it names the project, describes the technology, describes the hardest technical problem, and provides a link. That's more useful than "I'm interested in software engineering and have experience with React."
5. Interest
Internship letters have one extra job: showing that you have some idea what you'd like to learn. Don't say "I'm eager to learn" — everyone is. Say specifically what you want to learn, and why this role would give you that.
I'm specifically interested in backend and infrastructure work, which is the part I've enjoyed most in my projects. Your team has a public engineering blog with detailed posts on how you structure services, and I'd love to learn that kind of architectural thinking from people who've clearly thought about it carefully.
6. Closing
I've attached my resume and the CollabNote GitHub repository is on it. Thank you for considering my application.
That's it. You don't need a call to action, or a statement of how excited you'd be, or a promise to follow up. You're applying for an internship — the reader knows what you want.
7. What to avoid
- "I'm a fast learner" — every letter says this. It's not evidence.
- "I'm passionate about technology" — replaceable with "I'm passionate about X" for any X.
- "I want to contribute to your company's success" — vague and generic.
- Listing every course you've taken — mention two or three relevant to the role.
- Long paragraphs about your passion — one specific project beats a paragraph of enthusiasm.
- Apologising for lack of experience — you're applying for an internship. The company knows you don't have much experience.
8. Final checklist
- Is the letter 200–300 words?
- Does it name the specific internship role?
- Does it include one specific project described in detail?
- Does it mention something specific about the company or team?
- Have you removed "passionate" and "eager to learn"?
- Have you proofread it?