University Student (internship) cover letter example
Without a career to summarise, a student's letter has to turn coursework, a summer job and a project into evidence that reads like experience. This one names the internship, describes one project with a number, admits what the applicant has not done yet, and asks for the chance to learn it; it does not apologise for being a student.
Dear University Recruiting team,
I am applying for the Summer 2026 Operations Analyst Internship in your Grand Rapids distribution network. I am a third-year Industrial and Operations Engineering student at the University of Michigan (GPA 3.7, graduating May 2027), and the posting describes the two things I most want to do this summer: work inside a live warehouse and build the models that change how it runs.
Last summer I interned in operations at Lakeshore Fulfillment, a 300,000-square-foot facility shipping 20,000 orders a day. My main project was a slotting model for 4,000 SKUs that put fast-moving items closer to the pack stations; after the re-slot, picker walking distance fell 18% and the site kept the change. I built it in Python and Excel from a year of order data, presented it to the site director, and spent two weeks on the floor with the pickers before I trusted any of the numbers. I also ran the daily labour-planning sheet for two weeks while the planner was on leave.
What I have not done yet is work with a warehouse management system at your scale or with carrier contracts, and I would want to learn both. In coursework I have completed Stochastic Processes, Production Systems and a simulation project modelling a hospital pharmacy's queue in Simio; as a peer tutor in calculus and statistics I have learned to explain a model to someone who did not build it, which I suspect matters on a warehouse floor.
I would be glad to walk through the slotting model in an interview. I am available from May 4 to August 21 and can relocate to Grand Rapids. Thank you for your consideration.
Sincerely,
Jonah Reyes
A fictional applicant, a fictional employer; the numbers are the kind a real letter should carry.
Questions
A course project, a club role or a part-time job, written the same way: what you did, with what, and what the result was. Serving 200 customers a shift without a complaint is a result.
If it is 3.5 or above, or the posting asks for it, yes, in the first paragraph. Otherwise leave it out and let the project speak.
Address the team the posting names ('University Recruiting team', 'Operations Internship team'). It is better than 'To whom it may concern' and more accurate than guessing a name.
More cover letters
All cover letters →Dear Platform Engineering team,
I am applying for the Senior Backend Engineer role on your platform team. Your posting describes a Go monolith that has started to slow down a fast-growing delivery business, and a team that wants to split it without a freeze on features. That is the work I have spent the last four years doing at Parcelwise, and I would like to do it again with you.
At Parcelwise I led the split of our order monolith into twelve Go services behind an API gateway. We kept shipping throughout: deploy frequency went from weekly to more than thirty releases a day, and the migration finished without a single Sev-1 incident. The part I am proudest of is not the architecture but the sequencing. We moved the rate calculator first because it was the hottest path, rewrote it with cached carrier tables and request coalescing, and took p95 latency from 820 ms to 240 ms at 40,000 requests a minute before touching anything else.
Your posting also mentions event-driven integrations with carriers and warehouses. I designed the event schema and the outbox pattern that nine Parcelwise teams now publish through; duplicate shipment events fell to zero after rollout. Before that, at Northbank Payments, I built the direct-debit mandate service that processed £1.2bn in its first year and passed its PCI DSS audit without findings, so I am comfortable where correctness matters more than speed.
I would welcome a conversation about where your monolith hurts most today and how I would approach the first ninety days. Thank you for reading.
Kind regards,
Daniel Okafor
Dear Mr. Hale,
Your posting for a Senior Product Manager, Billing says the quiet part plainly: Harbor's invoicing product grew faster than its collections flow, and involuntary churn is now the largest leak in net revenue retention. I have spent the last five years on exactly that leak, and I am applying because I think I can close a good part of it in the first two quarters.
At Ledgerline I own payments and billing for 30,000 businesses. The self-serve invoicing product I took from launch now runs at $18M ARR. The result most relevant to you is the smart-retry program: by sequencing retries around payroll dates and card-issuer behaviour, and by rewriting the dunning emails so that they read like a reminder rather than a threat, we cut involuntary churn by 28% in nine months. I wrote the business case, ran the experiments with two engineers and a data analyst, and reported the numbers to the board myself.
I also know what it costs to get billing wrong. At Fieldstack I inherited a usage-based pricing migration that had stalled; we shipped it to 4,000 accounts with a 0.3% support contact rate by building a preview invoice customers could see a month in advance. If Harbor is considering pricing changes alongside the collections work, that experience is directly reusable.
I would start at Harbor by listening to twenty recorded support calls about failed payments, because the fix is usually visible in what customers say before it is visible in the data. I would be glad to talk through how I would run that first month. Thank you for your time.
Sincerely,
Priya Raman
Dear Ms. Vasquez,
Brightline is hiring a Head of Demand Generation to take a product-led company into its first real sales-assisted motion, and your posting is honest that the pipeline today comes mostly from inbound sign-ups. I have built the other half of that engine once before, at a company the same size, and I would like to build it for you.
At Northfield Software I lead a team of eight across demand generation, content and brand. When I joined, 71% of new revenue came from inbound; today the pipeline programs my team runs source 62% of new revenue at a $45M ARR company, and cost per qualified lead is down 38% in two years. The levers were unglamorous: a webinar series we rebuilt around customer speakers, an ABM program for 120 named accounts with sales sitting in our planning meetings, and ruthless pruning of paid channels that produced leads sales never called.
I should also tell you about the campaign that did not work. Our first ABM attempt in 2024 produced 400 engaged contacts and two meetings. We had chosen accounts by firmographics alone. We relaunched with intent data and with sales choosing a third of the list, and the second run booked 41 meetings in a quarter. I would rather bring you that lesson learned than learn it on your budget.
If it would be useful, I can bring a one-page outline of how I would stage Brightline's first two quarters, from attribution clean-up to the first outbound plays. Thank you for considering my application.
Best regards,
Rachel Donovan