Start with programs built for students at your stage
Some programs are designed for early-college students or say plainly that prior experience is not required. Those are the places where having no internship yet is expected rather than a gap to explain. Look for exact phrases in the official eligibility line: a named class year such as first-year or rising sophomore, ‘no prior research experience required’, ‘pre-internship’, ‘discovery’ or ‘exploration’ program, or ‘externship’. Then read the year rule literally. A program for first-years and sophomores does not accept juniors, and a program that names only sophomores does not accept first-years. Early-college programs also tend to recruit early, often in the fall or winter before the summer, so check the published dates before assuming you have time. The freshman and sophomore hubs on this site list only programs whose accepted years are confirmed on an official source, and each program guide links to that source.
Count the experience you already have
At this level, reviewers are usually looking for evidence that you can learn, follow through and work with other people, not for a previous job title. That evidence often already exists. A course project shows you can scope and finish work. A lab section shows you can follow a protocol and record results. A campus or retail job shows reliability, customer handling and working to a schedule. A student organization role counts when you can name something you were responsible for, such as a budget, an event, a newsletter or a recruiting drive. Family or caregiving responsibilities show time management. List everything first, then keep the items that match a skill the posting actually names. Never inflate a role or claim a result you cannot explain in an interview.
Build one finished piece of proof
If the list is thin for the field you want, make one small, finished, verifiable thing before the deadline. Finished matters more than impressive. For software, build a small tool that solves a real problem you have, with a short README explaining what it does and what you would improve. For finance or business, write a one-page analysis of a public company's latest annual report or a question a local business actually faces. For research, summarize a recent paper from a lab you are interested in and write down one question it leaves open. For marketing or media, audit an organization's public channels and propose three specific changes. For engineering, document a build, a repair or a CAD model with photos and measurements. Put it somewhere a reviewer can see it — a link, a short PDF or a portfolio page — and be ready to explain every decision in it.
Use the campus routes most applicants skip
Your own university is usually the least competitive place to get a first line on a resume. Departmental undergraduate research offices list faculty who take students. Professors often accept a student who has read their recent work and asks a specific question — the email templates guide covers how to write that message. Campus jobs in labs, IT help desks, libraries, data offices and admissions build directly transferable skills and are often hired from the student body only. Student organizations with real deliverables count as experience when you can describe what you produced. Career center employer events and info sessions tell you which programs recruit at your school and when. None of these are internships by name, but each produces the evidence that makes the next application stronger.
Write the application around evidence, not adjectives
Put education first, with your expected graduation month and year, because many programs filter on graduation timing. Add a projects section above or alongside work history if your projects are the stronger evidence. Write each bullet as what you did, the tool or method you used, and what changed or what you produced. Replace adjectives such as passionate, hardworking or detail-oriented with the evidence that would make a reader conclude them. In a cover letter or short-answer question, give one specific reason for choosing this program — something only true of it — and one piece of evidence that you can do the work. The internship resume guide walks through the resume itself line by line.
Apply in a deliberate batch and keep records
Build a shortlist of programs where you meet every stated requirement: class year, graduation window, major, location and work authorization. Applying where a hard rule excludes you costs time you could spend on programs that accept you. Put each published cutoff in a calendar, and apply early where review is rolling. Note which documents each application needs — transcript, letters, writing sample, portfolio link — because those take the longest to gather. Tailor the first few lines of each application rather than rewriting everything. Keep a simple record of what you submitted and when, so a follow-up or an interview invitation does not catch you guessing. Rejections and silence are common for every applicant, including experienced ones, and they are not a verdict on your potential.
If this cycle does not work, make the next one easier
A summer without an internship can still produce exactly what next year's application needs. A paid job, a research assistant role, a course with a substantial project, a volunteer role with real responsibility or a self-directed project all create evidence you can describe. Choose the one that gives you a concrete result to talk about. Note which programs you were not yet eligible for and when they open next, so you can apply on time once your class year qualifies. Be careful with any service that charges you a fee to be placed in an internship: read exactly what it promises in writing, and compare that with what you could build yourself through the routes above.
A practical starting point
An evidence inventory to fill in before writing your resume
Target program: [name] Accepted class years on the official page: [exact wording] — do I qualify? [yes/no] Published cutoff: [date, time and time zone, or 'not published'] Skills the posting names (copy them exactly): 1. [skill] 2. [skill] 3. [skill] For each skill, one piece of evidence: Skill → where I used it (class, job, club, project) → what I did → what I produced or what changed → where someone can check it Gaps — skills with no evidence yet: [skill] → the smallest honest thing I can finish before the cutoff: [project, course task, campus role] Documents to gather: [transcript, letters, writing sample, portfolio link] — request by: [date]
This is editorial guidance, not an employer-required format. Use true details, respect authorship rules, and follow the actual application prompt.
Check the program-specific instructions
Use these independent guides to find the official requirements and application route. General advice does not override a publisher's instructions.
Check eligibility and the selected role's document instructions before submitting. FirstInternships does not accept applications or store your resume.
Find a program