Internship Cover Letter: What to Write With No Track Record
An internship application is not judged on track record, because nobody expects you to have one. It is judged on whether you have engaged with the field seriously enough to be worth teaching. Show one concrete thing you did because you wanted to, name your dates plainly, and skip the paragraph about being a fast learner.
What an internship is actually hiring for
A team taking on an intern is spending supervision time and getting uncertain output back. They know this going in. What they are trying to work out from your application is narrow: will this person be interesting to teach, and will they still be interested in eight weeks.
That changes what counts as evidence. For a full-time role, the strongest thing you can show is that you have already done the work. For an internship, the strongest thing you can show is that you have gone further into the subject than the syllabus required — the elective nobody made you take, the thing you built with no grade attached, the club you kept running when it stopped being fun.
None of that has to be impressive on an absolute scale. A hiring manager reading intern applications is not comparing you to their senior engineer. They are comparing you to the other applicant who wrote three paragraphs about being passionate and detail-oriented.
The evidence you have at this stage
Almost every applicant at this stage has four categories available, and most only write about the first.
- Coursework. Usable, but only when written as work rather than as a transcript entry. More on this below.
- Things you built or wrote unprompted. The strongest category by some distance, because nobody assigned it. A tool that solved your own annoyance counts. So does a blog with four posts in it.
- Paid work of any kind. Retail, hospitality, tutoring, a campus job. This is real work with real accountability, and applicants discount it constantly because it is not in the field.
- Organising things. Running a society's budget, coordinating a volunteer rota, putting on an event. Stakeholder management under a deadline, with none of the authority.
If your strongest material sits in the last two categories, our guide on writing a cover letter with no experience works through the translation in more detail.
Writing about coursework without sounding like a transcript
The default version lists modules and grades. A reader learns nothing from it that your resume does not already say.
I have completed coursework in Data Structures, Algorithms, Database Systems and Software Engineering, achieving strong results throughout. These modules have given me a solid theoretical foundation and strong analytical skills.
The useful version picks one piece of work and treats it as a small piece of engineering with a decision in it.
In our databases module we were given a schema for a fictional library and asked to optimise a slow query. I found the actual problem was not the query but the schema — the loans table was storing the member's details rather than referencing them, so every join was doing redundant work. I rewrote it in third normal form and the assignment query went from unusable to instant. It was not what the brief asked for, and I made the case for it in the write-up.
Same module, same term. The second works because it contains a judgement call. The reader now knows something about how you think, which is the only thing coursework can honestly tell them.
One piece of work, in depth
Resist listing four projects at one sentence each. At internship stage the reader is not assessing breadth, and four shallow descriptions read as a resume that has been retyped into paragraphs. Pick the single thing you would most enjoy being asked about in an interview, and give it five sentences.
Applying to a company whose product you actually use
This is the one advantage students have over experienced applicants, and it is chronically wasted. Experienced candidates write about a company's market position. You can write about what happened when you used the thing.
The distinction that matters is between generic praise and a specific observation. "I have long admired your commitment to user-centred design" is generic praise; it could be pasted into any application and the reader knows it. An observation is something only a user could have written.
I have used your scheduling app for two years to run shifts for our student radio station, and the thing I have never seen elsewhere is that a swap request notifies both people rather than just the person accepting it. It sounds small. It removed the entire category of argument we used to have about who agreed to what.
That paragraph does something no amount of enthusiasm can: it proves you paid attention. It also gives your interviewer an obvious opening question, which is a favour to both of you.
If you have not used the product, do not fake it. Find something else specific — a technical post from their engineering team, a decision they made that you disagreed with and can articulate why. Pretending to be a user of something you downloaded yesterday is transparent and unravels immediately.
Enthusiasm is not evidence. An observation only a user could make is evidence, and it takes one sentence.
Timing, availability and the logistics paragraph
Internships are scheduled around terms, and a coordinator planning a cohort needs your dates before they need your motivation. Put them in the first paragraph and stop.
What to include: the programme and year you are in, your graduation date, and the window you are available. One clause each.
I am in the second year of a three-year BSc in Computer Science at Ashford, graduating in June 2028, and I am available for the full twelve weeks from June 8.
Three situations worth handling explicitly:
You cannot do the full window. Say so, with the dates. A coordinator can usually work around a two-week overlap with exams if they know in advance. Discovering it after an offer is a different conversation.
Applications open far in advance. Many programmes recruit six to twelve months ahead. Applying early is normal, not eager, and you do not need to apologise for the distance.
You need visa sponsorship or have work-authorisation limits. State it plainly in one line. It is checkable, it will come up, and a company that cannot sponsor would rather know now — as would you, before investing in four rounds.
First year and penultimate year are different applications
The expectations genuinely differ, and writing the wrong one is a common misstep.
| First year / early | Penultimate year | |
|---|---|---|
| What they expect | Curiosity and basic competence. Very little else. | Enough foundation to contribute to real work with supervision. |
| Best evidence | Something self-directed. It need not be in the field. | A substantial project, or a prior internship. |
| What the company wants | Often outreach and pipeline-building, sometimes explicitly. | Frequently a graduate-hire audition. Conversion is the point. |
| Tone | Genuine interest, no pretence of expertise. | Closer to a junior application. Lead with the work. |
The common error runs in both directions. First-years overclaim, writing as though they have industry experience, which reads as thin the moment anyone asks a follow-up. Penultimate-year applicants underclaim, still writing the eager-to-learn letter when they have two years of substantial work to point at. If you are in your final year or already graduated, you are writing a new grad cover letter instead — a different document with different expectations.
Do not describe an internship as a job
A previous internship is worth writing about in detail, but describe it as what it was. Inflating a ten-week placement into a staff role, or claiming ownership of a project you supported, does not survive a reference call — and internship coordinators talk to each other more than applicants expect.
A full worked letter
Fictional candidate and employer: a second-year computer science student applying for a summer software engineering internship at a company making scheduling software.
Dear Hiring Team,
I am in the second year of a three-year BSc in Computer Science at Ashford, graduating June 2028, and I am available for the full twelve weeks from June 8. I am applying for the summer software engineering internship because I have spent two years as a fairly demanding user of Rota.
I run the shift schedule for our student radio station — around forty volunteers, most of whom change their availability weekly. We moved to Rota in my first term. The thing I have never seen elsewhere is that a swap request notifies both people rather than only the one accepting it. It sounds small; it removed the entire category of argument we used to have about who had agreed to what.
The most useful thing I have built came out of the same problem. Before we switched, I wrote a small tool that took our messy availability spreadsheet and flagged the shifts nobody had claimed. It was about two hundred lines of Python and it was ugly. What I learned from it was not the code — it was that the station manager would not use anything that needed a terminal, so I spent a weekend making it output a single HTML page she could open from a bookmark. That was the difference between a tool I used and a tool the station used.
My coursework this year has been mostly databases and systems. In the databases module we were given a slow query to optimise; I found the real problem was the schema rather than the query, rewrote it in third normal form, and argued the case in the write-up even though it was not what the brief asked for.
I would be glad to talk about any of the above.
Sincerely,
Priya Raman
The first paragraph is pure logistics and one sentence of reason. The second is the user observation, which no other applicant can write. The third is self-directed work with an actual lesson in it, and the lesson is about users rather than syntax. The fourth is coursework with a decision in it. Nothing anywhere claims professional experience, and nothing needs to.
Note what is missing: no list of programming languages, no paragraph about passion, no promise to bring value to the team. For the underlying structure, see how to write a cover letter.