Internship Resume With No Experience: A One-Page Guide

You open a blank document, type your name, and stall. Every template assumes a work history you don't have. This guide fixes that: by the end you'll have an exact one-page layout for an internship resume with no experience, line budgets for each section, and before and after rewrites of the exact bullets students tend to write.

What recruiters actually look for on a first resume

Nobody screening intern resumes expects employment history. They know you're a student. What they scan for is evidence of three things: you learn fast, you finish what you start, and you've made some real contact with the field (a project, a club role, a course you went beyond in).

That scan is quick, usually under a minute, so your job isn't to look experienced. It's to make those three signals impossible to miss, starting at the top of the page.

The one-page structure that works with no work history

The order matters more than the formatting. With no jobs to list, projects go first, because they're your strongest proof of follow-through. This is the same logic as Step 2 of our step-by-step guide to getting an internship with no experience: lead with what you've built, not what you lack. The University of Washington's Career & Internship Center recommends the same move, swapping "Work Experience" for a "Projects" section filled with class projects, with your specific role spelled out in each entry.

Here's the skeleton. Copy it, then fill it in:

YOUR NAME                                       <- header: 2 lines
City | email | phone | github.com/you or portfolio link

PROJECTS                                        <- 6 to 8 lines
Project name | tools used | date
- What you built and who it was for
- One honest outcome or detail you own
Second project name | tools used | date
- What you built and who it was for
- One honest outcome or detail you own

EDUCATION                                       <- about 4 lines
Degree, university, expected graduation year
Relevant coursework: 3 to 5 courses that match the listing
GPA, only if it helps you (see the FAQ below)

ACTIVITIES                                      <- 4 to 6 lines
Role, club / job / volunteering, dates
- One bullet on what you specifically did
- One bullet on a result you could explain in an interview

SKILLS                                          <- 2 lines
Tools and languages you could use in an interview tomorrow

One rule per section:

• Header: name, city, email, phone, one link. Nothing else.
• Projects: two or three entries, two bullets each. Class projects count. Personal projects count. Half-finished tutorials don't.
• Education: degree, university, expected graduation year, and only the coursework that's relevant to this listing.
• Activities: club roles, volunteering, and any part-time work, even unrelated work. Showing up reliably for a retail shift is a signal employers genuinely read.
• Skills: short and defensible. If you'd panic when asked about it, cut it.

A 2-line summary at the top is optional, and you should skip it unless you can say something specific (covered in the FAQ).

What goes in the top third

The top third of the page decides whether the rest gets read. On this layout, that's your header plus your first project, so your single best project has to sit first, and its first bullet has to carry a concrete result. If a screener stopped reading after line eight, would they know the most impressive true thing about you? Reorder until the answer is yes.

Sections to cut

These take up space and add nothing on a student resume:

• A photo. Not expected in most markets, and it wastes prime space.
• "References available on request." Everyone assumes this.
• A generic objective. "Seeking a challenging internship to grow my skills" describes every applicant on earth.
• A soft-skills list. "Team player, hard-working, detail-oriented" is unverifiable. Show those traits inside project bullets instead.

Before and after: bullet points students actually write

These are composite examples of what first drafts usually look like, and what the same facts look like rewritten.

Class project

• Before: "Worked on a group project for my databases course."
• After: "Built a course-review web app with two classmates using Flask and SQLite; owned the search feature and its 12 unit tests."
• The move: name the thing, the tools, and the part that was yours.

Club role

• Before: "Member of the coding club."
• After: "Organized the coding club's first beginner workshop series; ran four sessions and wrote the starter exercises."
• The move: membership is passive. Lead with what you initiated and did.

Part-time retail job

• Before: "Responsible for customer service."
• After: "Handled checkout, returns, and complaints on weekend shifts at a grocery store; trained two new hires on the register system."
• The move: "responsible for" hides the action. Say what you handled and any responsibility you were trusted with.

Volunteering

• Before: "Volunteered at a local animal shelter."
• After: "Photographed and wrote adoption listings for 20+ shelter dogs; rewrote the intake checklist volunteers now use."
• The move: replace the role label with the artifact you left behind.

Personal project

• Before: "Interested in data analysis, learning Python."
• After: "Analyzed three seasons of my football league's match data in Python; published the write-up and charts on a personal blog."
• The move: interest is a claim, a finished analysis is evidence.

The pattern behind every rewrite is the same formula Columbia's Career Education center teaches: start with a strong action verb, be specific about what you did and how, and end with the result, quantified where possible. One honest constraint: only quantify what you can defend in an interview. "Four sessions" you can prove beats "boosted engagement by 40%" you made up.

And a hard truth no formatting fixes: if you have nothing to put in the Projects section, the resume isn't the problem. Spend a week building one small finished thing first; Step 1 of the guide linked above shows what counts for each field.

Tailoring the resume to each listing in 10 minutes

Tailoring is what turns this skeleton into interviews, and it's faster than it sounds:

1. Mirror two or three exact phrases from the listing, but only where they're true. If the ad says "data visualization" and your project genuinely made charts, use those words.
2. Reorder your projects so the most relevant one is first. The top third should change between applications even when the facts don't.
3. Match the skills line to the tools named in the ad. If they name spreadsheets, Python, or Figma and you can use them, those go first on the line.

A practical way to start: pick three listings from a student-focused board (you can browse internships on our feed) and tailor one copy of your resume against each. Ten focused minutes per listing.

Common mistakes that get first resumes filtered out

• Two pages. With no work history there is nothing that justifies page two. Cut to one.
• Unverifiable soft-skill claims. Delete the adjectives, keep the evidence.
• Listing every course you've taken. Pick the three to five that match the listing, drop the rest.
• Dense paragraph blocks. Screeners scan bullets, not prose. Two bullets per entry, one line each.
• Typos in the header. A broken email address or misspelled name ends the application instantly. Triple-check those two lines.
• Lying about tools. Interviewers test the skills line first. One exposed exaggeration poisons everything true on the page.

On formatting software: you don't need tricks. Standard section names (Projects, Education, Skills) and a simple single-column layout keep your resume readable for both application systems and tired human eyes.

Frequently asked questions

What do you put on a resume for an internship if you have no experience?

Projects first (class, personal, or club work), then education with relevant coursework, then activities including volunteering and any part-time job, then a short skills line. Work history is just one form of evidence, and it's the one form intern screeners least expect you to have.

Should I include a summary or objective on a student resume?

Only if it says something specific: your degree, your strongest proof, and the kind of role you want, in two lines. "Second-year CS student who built a course-review app used by 200 classmates, looking for a backend internship" earns its space. A generic objective doesn't, so when in doubt, give the lines to your first project instead.

Should I put my GPA on an internship resume?

It's a judgment call, not a rule. Roughly: above 3.5, include it; around 3.0 to 3.5, include it if the employer asks for it or your projects section is thin; below that, leave it off and let your projects speak. Never invent or round up, since transcripts get checked.

Can I put class projects on my resume?

Yes, and with no work history they should usually be your top section. Treat a class project like a job entry: name it, list the tools, and claim the specific part you built.

Tonight, build the skeleton and fill in every section, even roughly. This week, rewrite your three weakest bullets using verb, what, outcome. Then pick three listings, tailor a copy against each, and send your first applications. The blank page is the hardest part, and you're past it.