Internship resume and cover letter — what actually gets interviews

Internship recruiters know you have limited tenure. They scan for curiosity, reliability, and evidence you can do a slice of the job. A generic "hard-working student" summary loses to a two-line pitch naming the stack, domain, and type of team you want.

Pair a tight one-page resume with a cover letter that names the team, one project that maps to their work, and why this employer — not a template paragraph you send everywhere.

Lead with education and graduation date. Follow with two projects or prior internships — each two to three bullets max. Skills row mirrors the posting (Python and SQL for data; Figma and user research for product).

Include availability (summer dates, days per week for part-time) in the header or summary when the posting asks — it saves a screening round.

Paragraph one: role + why this company (one specific product, mission, or team). Paragraph two: one project or experience with metrics. Paragraph three: what you want to learn and when you can start.

Keep it under one page. Mirror language from the job description where you have real proof — do not paste keywords you cannot discuss in an interview.

Save roles to your pipeline, run match score, tailor the top five, autofill on ATS via the extension, and track applied / interview / offer. Internship cycles move fast — a repeatable weekly rhythm beats 50 untailored uploads.

When 0 intern listings are live in the job feed, filter by match score so you spend rewrite time where fit is already plausible.