An internship cover letter has one job: convince someone you can do work you have never been paid to do. That is a different problem from a normal cover letter, and the generic samples floating around university career sites mostly ignore it. They tell you to "express enthusiasm" when what the recruiter actually needs is evidence.

This page takes a different approach. Instead of one all-purpose sample, it breaks down what a strong internship letter looks like in five fields: software engineering, finance, marketing, a research lab, and a nonprofit. The skeleton of the letter stays the same across all five. What changes is a handful of specific sentences, and once you see exactly which ones, you can write a tailored letter for any internship posting in under an hour.

Below is a full software engineering internship letter you can study line by line. After it, we walk through every paragraph, then show precisely which sentences you swap for finance, marketing, research, and nonprofit applications.

Recruiters screening intern applications are not looking for experience. They know you do not have it. They are looking for three things, and your letter should be built around proving each one.

Most student letters fail on the first point. They spend three paragraphs on enthusiasm and personality, then hope the transcript carries the rest. Flip that ratio. Enthusiasm gets one sentence; evidence gets the longest paragraph in the letter.

The second point matters more than students expect. Intern hiring is high-volume, and the fastest way a recruiter cuts the pile is by dropping every letter that could have been sent anywhere. A letter that names the company's product, a recent launch, or the specific team is instantly in the smaller pile.

The first paragraph of an internship letter is administrative, and that is fine. Intern programs run on cohorts, terms, and requisition numbers, and the coordinator reading your letter may be sorting applicants across several programs at once. Make their job easy in your first two sentences.

A complete opening covers four facts: the exact program name as the posting writes it ("Software Engineering Intern, Summer 2026", not "a software internship"), the term you are applying for, the requisition or job ID if the posting shows one, and where you found it. That last one is not filler. "I found this role through the campus recruiting session Ms. Alvarez ran at Purdue in October" tells the recruiter you were in the room, and it gives them a colleague's name to anchor you to.

Then add one sentence of who you are: your year, your major, your school. That is the whole opening. Four to five sentences, no life story, no "ever since I was a child." Compare the two versions:

• Weak: "I am writing to express my strong interest in an internship opportunity at your esteemed company."
• Strong: "I am applying for the Software Engineering Intern position (req 4471) for Summer 2026, which I found through the University of Michigan engineering career fair. I am a junior studying computer science with a focus on distributed systems."

The weak version could open a letter to any company on earth. The strong version proves you read the posting, which already puts you ahead of most of the pile.

This is the paragraph that gets you the interview, so give it the most space and the most specificity. The rule: one project, told properly, beats five projects listed. Pick the single strongest thing you have built, analyzed, or produced, and give it four sentences: what it was, what you specifically did, what tool or method you used, and what the outcome was.

What counts as evidence, roughly in order of strength:

Numbers rescue thin material. "Built a study-group matching app" is forgettable. "Built a study-group matching app that 120 students in my dorm used during finals week" is a fact a recruiter repeats to the hiring manager. Users, rows of data, competition rank, budget managed, attendance at an event you ran: any honest number works.

One warning: mirror the posting's language, not your syllabus's. If the posting says "data analysis in Python," write "data analysis in Python," not "STAT 3200: Statistical Computing." The recruiter searches for the posting's words, and so does the applicant tracking system (ATS) behind the portal. If you want to see which of the posting's terms your materials are missing, pulling keywords from the job description takes ten minutes and works for the letter as well as the resume.

Look back at the example above and notice what each paragraph is doing, because the structure is the reusable part.

Paragraph one handles the administrative facts: program name, term, requisition number, source, and one sentence of identity. Nothing else. It ends before the recruiter's attention does.

Paragraph two is the evidence paragraph, and for a software role it is built on a project, not a course list. It names the stack, states what the candidate personally built, and lands on an outcome someone can verify: real users, a hackathon placement, a public repository. For engineering internships specifically, a GitHub link is close to mandatory, and it belongs in your header as well as your resume. Where to put your GitHub link covers the details, but the short version is: make it one click away, and make sure the pinned repos are the ones you would want opened.

Paragraph three is short and does the reliability work: a campus job or club role, framed for what it proves rather than what it was. Tutoring proves you can explain technical ideas to a confused audience, which is most of code review. A club officer role proves you can be trusted with something that breaks if you flake.

Paragraph four closes with a specific ask. "I would welcome the chance to talk about how my capstone work maps to the team's stack" beats "I hope to hear from you at your earliest convenience" every time, because it gives the reader a concrete reason to say yes.

If you are also building the resume side of this application, the entry-level software engineer resume example pairs with this letter, and there are more software engineer cover letter examples for full-time roles when you get there.

Here is the useful secret of internship letters: moving from software engineering to finance does not mean rewriting the letter. The skeleton, the opening structure, the reliability paragraph, and the close all survive intact. Three sentences change, and they are all in predictable places.

The identity sentence. The engineering version names a major and a technical focus. The finance version names the major plus the credential-track signal finance recruiters scan for: relevant coursework (financial accounting, corporate finance, valuation) and, if it is strong, your GPA. Finance is one of the few fields where GPA still gets screened early, so if yours helps, state it. If you are unsure, when GPA helps and when it hurts applies to the letter the same way it applies to the resume.

The evidence sentence. Instead of a shipped project, finance evidence is an analysis: a stock pitch for an investment club, a case competition, a valuation model built in a corporate finance course, managing a student fund's position. The winning shape is the same as engineering's: what you analyzed, what method you used (DCF, comparables, three-statement model), and what came of it. "I built a three-statement model for our investment club's pitch on a mid-cap industrial, and the club took the position" is a complete piece of evidence in one sentence.

The motivation sentence. Finance recruiters, especially in banking and asset management, test for informed interest harder than any other field. "I am drawn to your firm's culture" gets deleted. A sentence naming the group, the kind of deals or coverage it does, and why that specific work interests you is the price of entry. If you are aiming at banking specifically, the investment banker cover letter examples show what that sentence looks like at full-time level; the intern version is the same sentence with humbler evidence behind it.

Everything else in the letter carries over unchanged. That is worth internalizing, because it means applying to a finance internship and a software internship in the same week is not two writing projects. It is one letter and six edited sentences.

The same three-sentence pattern holds for the remaining fields. Each has one distinctive move the other fields do not use.

Marketing internships are won by shown work, so the distinctive move is a link, placed in the evidence paragraph, to something the recruiter can see in thirty seconds: a campus event's Instagram you ran, a newsletter you write, a class campaign deck, a blog. The evidence sentence pairs the link with a number: "I ran the marketing club's Instagram for two semesters and grew it from a dead account to the channel that filled our 200-seat speaker events." Growth, attendance, and engagement are all numbers a student can honestly own. If you have no public work yet, a course campaign project with a stated result stands in. For tone and structure one level up, the marketing coordinator cover letter examples are the closest full-time reference.

A research internship letter is read by a scientist, not a recruiter, and scientists read for two things: whose lab trained you, and which methods you can run without supervision. So the distinctive move is naming names. "I have worked in Professor Okafor's microbiology lab since sophomore year, where I run PCR and gel electrophoresis independently" answers both questions in one sentence. Add one sentence connecting your interest to the target lab's actual published work, which means reading at least the abstracts before you write. Enthusiasm for "research" in general reads as not having done any.

Nonprofit hiring managers screen hard for mission fit because interns who do not care burn out on unglamorous work fast. The distinctive move is proving the fit with something you already did, unpaid, before this application existed: volunteering at a related organization, organizing a fundraiser, running a mutual aid effort in your dorm. "I care deeply about food insecurity" is a claim. "I coordinated volunteer shifts for our campus food pantry for three semesters" is evidence. If your history connects to the organization's specific cause, that sentence goes first in the evidence paragraph, ahead of coursework.

Read the table column by column and the pattern is obvious: every field wants the same letter with different proof. That is why the fastest way to write five tailored applications is to write one strong letter and maintain a swap list, not to start from a blank page five times.

The third paragraph exists to answer an unspoken question: will this person show up? Students either skip it, assuming a dining hall job is beneath mention, or bloat it into a second resume. Both are mistakes. The right move is one short paragraph that stacks two or three commitments and frames each for what it proves.

The framing is the whole trick. Nobody cares that you shelved library books; they care that you held the same job for two years, which is the strongest reliability signal a 20-year-old can offer. Translate each role:

Three sentences, maximum four, then move to the close. If you have a genuinely strong item here, like managing a club budget in the thousands, promote its number into the sentence. Otherwise keep this paragraph brisk. It is a supporting witness, not the star.

Apply early, and treat the posted deadline as fiction. Many intern programs review on a rolling basis and fill seats before the deadline passes, especially in finance and tech. The letter you send in week one competes with a small pile; the same letter at the deadline competes with the whole applicant pool. Being early is the cheapest advantage in intern recruiting.

One page, and realistically less. Three to four paragraphs, somewhere around 250 to 350 words. A student letter that runs long signals padding, because the reader knows you do not have a decade of material. Short letters with dense evidence read as confident.

PDF, always, unless the portal explicitly demands otherwise. A PDF renders identically on every machine; a Word file can reflow, break, or open with tracked changes you forgot about. Save the letter as a PDF and check it once after export.

Name the file like the recruiter will see it, because they will. "coverletter_final_v3 (2).pdf" sits in their download folder telling a small story about you. Use Firstname-Lastname-Cover-Letter-CompanyName.pdf. Same convention for the resume. It takes ten seconds and it is one of the few parts of the application where perfection is free.

Match the letter to the resume. Same header, same fonts, same contact details. A mismatched pair looks assembled from parts, which, to be fair, it usually was. If you build both in the same editor this problem disappears; Roleframe's resume and cover letter editor is free to use without an account and exports a clean, unwatermarked PDF, which for a student budget is the correct price.

The single most common failure in intern applications is a letter written once and sent everywhere. The fix is a five-minute check per application: put your letter next to the posting and confirm three things. The program name and term match the posting's wording exactly. Your evidence paragraph uses at least two or three of the posting's own key terms. And one sentence in the letter could not have been written about any other company.

If you want that check done systematically, paste the posting into Roleframe and it will draft a job-specific cover letter for you to edit, and show you which of the posting's keywords your materials cover and which are gaps. You edit and approve everything yourself, which matters, because a recruiter can smell an untouched machine letter, and you will be asked about its claims in the interview. The guide to AI cover letter generators explains why most tools get this wrong and what a draft-then-edit workflow looks like instead.