A cover letter has to do four things in 250-300 words: hook the reader with a specific reason you want to work here, prove you can do the job with one detailed project, connect your trajectory to the role's trajectory in a single line, and close with a specific next step. The shape is the same across industries; the source material in the proof paragraph changes.
The eight examples below are calibrated to 250-280 words — the consensus length recommendation from ResumeGenius, Indeed, Kickresume, and Resume.io. Each example is paired with a link to the corresponding role-specific resume guide so you can match cover letter to resume. (For an honest breakdown of why this is "consensus" rather than "peer-reviewed," see the dedicated length post.)
Names, companies, and metrics are illustrative. Do not copy them verbatim — recruiters at competitive companies recognize stock-template content immediately. Use the structures as references; the specifics have to come from your real experience and your real research on the company.
1. Software engineering intern → Stripe
Pair with: Software engineering intern resume guide
Dear Stripe Engineering team,
I'm applying for the Backend Software Engineering Internship at Stripe because of the engineering blog post on how the team handled the Black Friday capacity surge — the cursor-pagination rework on the charges API was exactly the systems-thinking I want to learn.
Last summer at Acme, I built the company's first feature flag service. The team had been editing a YAML file in the repo and waiting for the next deploy — sometimes 3 days for a flag flip. I shipped a Postgres-backed service in TypeScript with a small admin UI, and four product teams adopted it in the first month. Rollout time dropped from 2-3 days to under an hour. The interesting failure mode I didn't anticipate was webhook delivery races during deploys — that's the part of the work I'd want to dig deeper on at Stripe.
I've been shifting from full-stack feature work toward systems and infrastructure over the past two years, and Stripe's mix of payments-domain depth and capacity engineering is the next step I want.
I'd welcome the chance to walk through the feature flag service at a 20-minute call next week. Thanks for reading.
— Aanya Sharma
Why this works: The hook references a specific blog post, the proof paragraph names the technical decision (Postgres + admin UI in TypeScript), and the unexpected-finding line (webhook races during deploys) gives the interviewer a concrete topic to ask about.
2. Data analyst intern → Notion
Pair with: Data analyst intern resume guide
Dear Notion Data team,
I'm applying for the Data Analyst Internship at Notion because of the public retro you posted on the activation-funnel rebuild — the SQL framing of "what defines an activated team" is the kind of analyst-judgment problem I want to spend a summer on.
In a class project last semester, I worked with a 12M-row event log from a public dataset to identify the top three onboarding drop-off points for a fictional B2B product. I wrote SQL against a Postgres replica, built a dbt model that refreshed nightly, and presented findings to a panel of 4 industry mentors. Two of the mentors said the third drop-off point — at the team-invite step — wasn't one their teams had identified despite having larger datasets. The framing I used (event-funnel + cohort retention overlay) is something I'd bring into the Notion role.
I'm targeting a career in product analytics specifically — work that connects measurement to product decisions, not dashboards in isolation.
Could we set up a 20-minute call next week? I'd like to walk through the dbt project. Thanks for reading.
— Marcus Chen
Why this works: Names the specific retro the company published, shows technical depth (dbt + Postgres + event funnel), and the panel-mentor reaction is third-party validation without being a humblebrag.
3. Marketing intern → HubSpot
Pair with: Marketing intern resume guide
Dear HubSpot Marketing team,
I'm applying for the Content Marketing Internship at HubSpot because of the recent series on B2B SEO experiments — specifically the post on canonical answers vs comparison content, which I've been trying to apply in a side project.
For the last three months I've run a small SEO experiment for my college's career office: 8 blog posts on internship-prep topics, all structured with TL;DR blocks, FAQ schema, and citation-ready paragraphs. The blog went from 0 to 1,400 monthly organic visitors in 12 weeks. The interesting finding: posts with comparison tables outperformed listicles by 2.3x in time-on-page despite shorter average length. I'd want to keep running these kinds of experiments in the HubSpot Internship.
I'm specifically interested in B2B SaaS content marketing because the audience cares about substance over style — that's the writing I want to do.
I'd welcome the chance to walk through the SEO experiment data at a 20-minute call next week. Thanks for reading.
— Priya Iyer
Why this works: Demonstrates the exact kind of work HubSpot publishes (SEO experiments, content structure analysis), and the unexpected finding (comparison tables outperforming listicles) is the kind of thing a marketing team would screenshot and share in Slack.
4. Nursing student → Stanford Hospital med-surg unit
Pair with: Nursing student resume guide
Dear Stanford Hospital Nursing Education team,
I'm applying for the Nurse Externship in the Med-Surg unit at Stanford because of the recent nursing journal article from your team on early mobilization protocols for post-op patients — the unit-level data on length-of-stay reduction is the kind of evidence-based practice I want to learn from.
During my second clinical rotation last semester, I completed 180 hours on a 32-bed med-surg floor at a regional teaching hospital. I carried a 4-patient assignment under preceptor supervision, including post-op recovery, IV antibiotic administration, blood glucose management, and discharge teaching on anticoagulants. My preceptor's feedback specifically called out my hand-off communication using the SBAR framework and my early identification of a patient with delayed onset post-op delirium that prompted an earlier intervention. I'd want to bring the same systematic clinical reasoning to the externship.
I'm targeting acute care nursing in a teaching hospital because the volume and complexity early in my career has no equivalent in another setting.
Could we set up a 20-minute call next week? Thanks for reading.
— Jamie Nguyen
Why this works: Cites a specific publication from the unit (signals research before applying), names clinical procedures specifically (IV antibiotics, SBAR hand-off, post-op delirium recognition), and connects evidence-based practice to the nursing-education team's actual work.
5. Business analyst → Deloitte
Pair with: Business analyst resume guide
Dear Deloitte Strategy & Operations team,
I'm applying for the Business Analyst position in your S&O practice because of the recent Insights piece on supply-chain re-shoring decisions for mid-market manufacturers — the framework you used to structure the cost-vs-resilience trade-off is exactly the analytical scaffolding I want to build under.
Last semester I led a 4-person team on a strategy case competition sponsored by a regional retailer. The brief: should the company invest in a third distribution center or expand the existing two. We built a 3-year demand forecast, a CapEx vs OpEx comparison, and a sensitivity analysis on three demand scenarios. Our recommendation (expand existing, defer the third DC by 18 months) won the competition. The judge — a current S&O partner at a Big Four — used our framing in the post-competition feedback session as the example of structured ambiguity-handling. I'd want to bring the same approach to client work at Deloitte.
I'm targeting consulting specifically because the case-volume and feedback-density early in your career has no equivalent in industry.
Could we set up a 20-minute call next week? Thanks for reading.
— Anika Patel
Why this works: Specific methodology (3-year forecast, CapEx vs OpEx, sensitivity analysis), measurable outcome (won competition), and the "structured ambiguity-handling" line lands because that's literally what consulting partners care about.
6. Customer service representative (no prior experience) → Notion Support
Pair with: Customer service no experience resume guide
Dear Notion Support team,
I'm applying for the Customer Support Specialist role at Notion because of the public engineering postmortem on the auth outage from earlier this year — the way the support team partnered with engineering to triage incoming user reports in real time is exactly the cross-functional support work I want to learn.
I haven't held a formal customer-facing role yet, so the proof I'd point to is two semesters as a peer tutor in my college's CS lab. I worked with 60+ students over the year, most of whom came in mid-debugging on assignments where they were already frustrated. I learned to ask three diagnostic questions before suggesting a fix, to summarize back what I heard before responding, and to flag a recurring pattern (an outdated example in the lecture notes was confusing 8+ students per week) to the teaching staff so they could update it. Those instincts — diagnose before fixing, summarize before responding, flag patterns up the chain — are the same ones a good support team operates on.
I'm targeting customer support specifically because the work is direct, the feedback loops are short, and good support teams shape the product.
Could we set up a 20-minute call next week? Thanks for reading.
— Diego Ramirez
Why this works: No-experience cover letters are hardest because the proof paragraph has to come from non-traditional source material. This one uses peer tutoring as a stand-in for support work and explicitly maps the analogies (diagnose before fixing, summarize before responding, flag patterns).
7. Research assistant → University biology lab
Pair with: Research assistant resume guide
Dear Dr. Patel and the Computational Biology Lab,
I'm applying for the Research Assistant position because of the recent paper on transformer-based protein structure prediction — the failure-mode analysis on disordered regions was exactly the kind of careful boundary-mapping I want to learn.
In Professor Lin's molecular biology course last semester, I led a small replication of the published method on a held-out test set of 240 proteins. I implemented the model in PyTorch, ran the evaluation pipeline, and produced a written analysis identifying three structural motifs where the model's predictions consistently underperformed. Professor Lin's feedback was that the disordered-region failure cases I flagged were the same ones the original authors mentioned in their follow-up workshop talk — so the boundary I mapped was real. I'd want to bring this kind of careful negative-result work to the Patel lab.
I'm planning to apply to PhD programs in computational biology in two years; this position would be the experience I cite in those applications.
Could we schedule a 20-minute meeting next week? Thanks for reading.
— Rohan Mehta
Why this works: Research positions value careful negative-result work over flashy positive findings. This letter explicitly demonstrates the right epistemic stance ("the boundary I mapped was real") and signals the long-term trajectory the PI cares about (PhD applications).
8. Teaching assistant → University CS department
Pair with: Teaching assistant resume guide
Dear Professor Kim,
I'm applying for the Teaching Assistant position for CS 161 because of the way you structured the assignment ladder this past semester — the progression from the first parsing assignment through the final type-checker felt designed to surface the conceptual gap students hit at week 6, which is exactly where I struggled when I took the course in 2024.
I've TA'd one course already (CS 60, Algorithms) for two semesters under Professor Lee. I held weekly office hours, graded ~40 student submissions per week, and ran review sessions before each midterm. The feedback I got from Professor Lee that I'd want to keep building on: my graded comments were specific enough that students knew what to fix, but I sometimes over-explained on simple errors. I'd want to be more efficient on the high-volume cases for CS 161 so I can spend more time on the conceptually hard ones.
I'm planning to apply to PhD programs in programming languages in two years; TAing 161 would directly strengthen my application.
Could we meet briefly next week? I'd like to discuss the assignment ladder design. Thanks for reading.
— Sara Kim
Why this works: Demonstrates pedagogical depth (notices the assignment ladder is designed around the week-6 conceptual gap), shows self-aware feedback uptake (over-explains on simple errors, working to improve), and signals the professor-relevant trajectory.
The patterns across all eight examples
If you read all eight back-to-back, three patterns repeat:
1. The hook always names a specific thing the company/lab/department has published, shipped, or done. Generic openers ("I am writing to express my interest in...") don't appear in any of the examples. The first 40 words are doing real work — proving research before the recruiter's attention budget runs out.
2. The proof paragraph always includes one technical/methodological detail and one unexpected finding. Whether it's the webhook race condition, the team-invite drop-off point that mentors hadn't identified, or the disordered-region failure cases — every example has a "here's the part that surprised me" moment. That's what gives interviewers something to ask about.
3. The fit paragraph is one sentence. Trajectory sentences ("I've been moving from X toward Y, and this role is the next step") work because they imply continuity without bloating into autobiography.
How to adapt these to your situation
Three steps:
- Pick the example closest to your role and read it side-by-side with the JD you're applying to.
- Replace every illustrative detail — company name, project specifics, metrics, names — with your real material. Do not retain a single specific from the example; recruiters notice.
- Verify length in a word counter. If you're between 240 and 290, ship it. If you're over 320, cut the fit paragraph to one sentence.
If you've drafted the bullets but the four-paragraph version isn't coming together, Laxu Resume's tailoring tool generates a 250-word cover letter alongside the resume rewrite on every run. The first tailoring is free with full output unlocked, including the cover letter, anti-fabrication-guarded so it won't invent claims you can't defend.