How to Write an Internship Resume (No Experience)

This guide walks through every section of an internship resume, with specific examples for students who have no work experience, some work experience, or only non-traditional experience (campus jobs, volunteering, personal projects). If you've never written any resume before, our complete resume writing guide covers the foundations.

Nobody expects five years of industry experience for a role designed for people with zero. The bar for internship hiring is lower than you think — but different than you expect.

Recruiters aren't looking for management experience or domain expertise. They want three things: coursework that proves you've studied the right material, projects that prove you can build something that works, and any sign you do things without being told to. That's it. The rest is formatting.

Your dining hall job counts. Your hackathon project counts. That research assistant position you buried in "Activities" because it was only 10 hours a week? It probably counts more than anything else on the resume. A deployed side project is worth more than a 3.8 GPA to a technical recruiter — and if your career center told you otherwise, they're wrong.

Use a reverse-chronological resume format. One page. No exceptions.

As a student or recent grad, you don't have enough experience to justify two pages, and internship recruiters reviewing 500+ applications will not read past page one. Every word needs to earn its place.

Section order for internship resumes:

1. Contact information (name, email, phone, LinkedIn, portfolio if applicable)
2. Education (this goes FIRST for students — flip it to second once you have 2+ years of work experience)
3. Experience (internships, part-time jobs, campus positions)
4. Projects (class projects, personal projects, hackathons)
5. Skills (technical and relevant soft skills)
6. Activities / Leadership (optional, if space allows)

Education goes at the top — not the bottom. Most career center templates put it last because that's where it goes for experienced professionals. But you're not an experienced professional. Your degree, GPA, and relevant coursework are your strongest credentials right now. Once you have 2+ years of real work experience, education moves down. Until then, it's your headline.

Education

This is your most important section. Make it count.

Include:

• University name, degree, expected graduation date
• GPA if 3.0+ (some companies set minimum GPA cutoffs in their application systems)
• Relevant coursework (3-6 courses that relate to the target internship)
• Academic honors, dean's list, scholarships
• Study abroad (if relevant to the role or company)

Example:

[Your University] | B.S. Computer Science, Minor in Business | Expected May 2027

• GPA: 3.6/4.0 | Dean's List: Fall 2025, Spring 2026
• Relevant Coursework: Data Structures & Algorithms, Database Systems, Software Engineering, Machine Learning Fundamentals
• Honors: [Academic scholarship], Dean's List 3 semesters

Don't include:

• High school (unless you're a first-semester freshman and it has notable achievements)
• Every course you've taken — only the ones relevant to the role
• GPA below 3.0 (just leave it off; nobody assumes the worst)

Experience

Same campus barista job, two resumes. One gets interviews, one doesn't.

Weak:

Barista at University Coffee Shop, Sep 2025 – Present

• Made coffee drinks
• Worked the register
• Cleaned the store

Strong:

Barista | University Coffee Shop | Sep 2025 – Present

• Handle 100+ customer orders per shift during peak hours
• Trained 3 new hires on POS system, drink prep, and customer interaction standards
• Reconcile daily cash drawer ($2K+ in transactions)

Same job. The second version shows volume, reliability, and the ability to train others. That's what internship managers actually scan for — not whether you worked somewhere impressive, but whether you can describe what you did with action verbs and measurable outcomes.

Previous internships, part-time jobs, campus employment, freelance work, volunteer roles — all of it belongs here. The bar isn't "relevant industry experience." It's "can I describe this in a way that shows I'm capable?"

If you have any kind of research position, treat it like your most important job — because to an internship recruiter, it is. Here's how a student might write up a research assistant role (adjust for your actual work):

Undergraduate Research Assistant | [Professor's Lab] | Jan 2026 – Present

• Annotating a large-scale dataset for sentiment analysis, developing annotation guidelines that improved team agreement scores
• Built a Python pipeline using spaCy and pandas to automate text cleaning, saving several hours of manual work per week
• Co-authoring poster for a national conference student research workshop

Most applicants don't have research experience. If you do, don't bury it under "Activities" — it goes in Experience, with full bullet treatment.

Projects

For technical internships, projects often matter more than work experience. A deployed app with real users will impress a recruiter more than six months as a campus tour guide.

Include class projects with real-world applications, personal projects, hackathon entries (especially if you placed), and open source contributions. Format each one like a mini job — name the tech stack explicitly (ATS parsers need those keywords), link to the repo if public, and quantify what you can.

Two examples of how this might look (substitute your own projects):

[Your App Name] | React, Node.js, PostgreSQL | github.com/you/project

• Full-stack web app solving [specific problem] for [specific users]
• Integrated third-party APIs for [specific functionality]
• Deployed on AWS with CI/CD pipeline

[Course Project Name] | Python, scikit-learn, Tableau | Course: [Course Name]

• Built a predictive model using real-world dataset, outperformed the course baseline
• Presented findings to industry panel as part of capstone evaluation

Put whatever is most relevant to the target internship first. And if your best project is a personal one you built for fun — that's often more impressive than a class assignment, because nobody told you to do it.

Skills

A sprawling list of every tool you've touched in 4 years of college looks unfocused. Be surgical.

Format:

Languages: Python, JavaScript, SQL, Java Frameworks/Tools: React, Node.js, pandas, scikit-learn, Git, Docker Other: Tableau, Figma, Google Analytics, Agile/Scrum methodology

Rules:

• Only list skills you could demonstrate in an interview
• Match the job description's language (if they say "Python," don't list "Python 3.11" — unless the posting is that specific)
• Group by category for scanability
• Put your strongest and most relevant skills first
• Skip generic items like "Microsoft Office" or "teamwork" unless the job specifically asks for them

Activities and Leadership

This section is optional but powerful for students with limited work experience. Leadership roles show initiative, responsibility, and soft skills that work experience alone might not demonstrate.

Worth including:

• Officer roles in student organizations (President, Treasurer, VP Events)
• Varsity or club sports captainship
• Greek life leadership (chapter president, philanthropy chair)
• Community service leadership (not just participation)
• Competition placements (case competitions, hackathons, debate)

Example (adapt to your actual role):

Vice President of Finance | [Student Organization] | Aug 2025 – Present

• Manage annual budget across 15+ events, negotiated corporate sponsorships
• Organized weekly workshops with 30+ attendees, recruiting industry speakers from local companies

Not worth including:

• Club membership without a role or notable contribution
• One-time volunteer events
• Social activities (intramural ultimate frisbee won't help unless you're applying to a sports company)

Example 1: Computer Science Student — No Prior Internships

This student has coursework, a research position, and personal projects but no industry experience.

Sections to emphasize: Education (strong GPA, relevant courses), Projects (2-3 substantial ones), Research Experience, Technical Skills.

How it reads to a recruiter: "This person can code, has built real things, and is currently doing research. They'll contribute from week 1."

Example 2: Business Student — Retail Job + Campus Leadership

This student has a part-time retail job, two leadership roles, and class projects but nothing directly related to finance or consulting.

Sections to emphasize: Education, Experience (reframe retail around transferable skills — see the barista example above), Leadership/Activities, Projects (case competition results, Excel/modeling projects).

How it reads to a recruiter: "This person has customer-facing experience, leadership initiative, and relevant analytical skills. They can handle the professional environment."

Example 3: Student With a Previous Internship

If you already have one internship, you're ahead of most applicants. Lead with it.

Sections to emphasize: Experience (previous internship gets the most bullets), Education, Projects (if they strengthen the application), Skills.

How it reads to a recruiter: "Someone already validated this person with an internship offer. The experience section shows they delivered. Low risk."

Most resume guides tell you to go Education, then Experience, then Projects, then Skills. For most internship applicants, this order is wrong.

Here's why: a recruiter sees your strong GPA and coursework, then immediately hits your barista job. Momentum drops. By the time they reach your deployed web app or research project, they've already formed an impression — and it's not the one you want.

If your projects are stronger than your work experience (and for most students applying to technical internships, they are), flip the order:

1. Contact info
2. Education
3. Projects — move this above Experience
4. Experience
5. Skills
6. Activities

A deployed app with real users beats 6 months as a campus tour guide. Put it where the recruiter sees it first.

The exception: if you have a previous internship or directly relevant work (TA for the department, freelance work in the field), keep Experience above Projects. Whatever makes the recruiter think "this person can do the job" goes highest.

Following your career center's template

Unpopular opinion: most university career centers give mediocre internship resume advice. Their templates are designed to be "safe" — which means generic, which means forgettable. They'll tell you to put Experience before Projects (wrong for most students), include an objective statement (waste of space), and list every extracurricular you've ever joined (padding). Use their formatting guidelines for margins and fonts, then ignore everything else.

Using an objective statement instead of a summary

"Seeking a software engineering internship to leverage my skills" wastes space and says nothing unique. Skip the summary entirely (common for internship resumes — the space is better used for projects) or write one that positions you:

Computer science junior with hands-on NLP research experience and 3 deployed web applications. Seeking a software engineering internship to contribute to production systems at scale.

The second version tells the recruiter what you bring, not just what you want.

Including every job you've ever had

Your lifeguard job from high school doesn't belong on a resume when you're a college junior applying to a data science internship. Be selective. Every entry should either demonstrate relevant skills or show meaningful responsibility.

Neglecting to tailor for the specific internship

This is the biggest missed opportunity. An internship posting at a marketing agency and one at a tech company's marketing team want different signals — even if both are "marketing internships." Read the job description carefully and tailor your resume to emphasize what each one specifically asks for.

Padding with fluff

Recruiters review hundreds of internship resumes. "Excellent communication skills" and "detail-oriented self-starter" are empty calories. Show communication through a presentation you gave. Show attention to detail through a project you delivered with zero bugs. Evidence beats adjectives.

Using a template that's more design than content

Creative templates with progress bars, pie charts for skill levels, and multi-column layouts look nice on Dribbble but break ATS parsing. Stick with a clean, single-column layout with clear section headers. The content sells you, not the template design.

Big internship programs — Goldman, Google, Deloitte — run every application through ATS software before a human touches it. When 5,000 students apply for 200 spots, there's no other way. Your resume needs to survive this filter.

The most important thing: use the job description's exact keywords. If the posting says "Python," write "Python" — not "Python 3" or "Python programming language." And put those skills in context. "Python" in a skills list is worth less to the parser than "Built a data pipeline in Python" in a project description.

Use boring section headers. "Education," "Experience," "Projects," "Skills." Not "My Journey" or "Cool Stuff I've Built." ATS parsers look for conventional labels. Submit as PDF unless they specifically request .docx.

One thing to never try: hidden text keyword stuffing. Pasting white text full of keywords onto your resume might have worked in 2018. Modern ATS platforms detect it automatically and auto-reject. Don't risk it.

Your resume gets you into the interview pipeline. What gets you hired is preparation and the ability to talk about your work. Three things that trip up students who have strong resumes but still don't get offers:

• A LinkedIn profile that matches your resume. Recruiters will check. Inconsistencies (different dates, missing roles) raise flags.
• A portfolio or GitHub with your project work. Linking to live projects or code repositories lets the recruiter verify what's on your resume.
• A cover letter that adds context, not repetition. Don't restate your resume in paragraph form. Use the cover letter to explain why this company and why this role — see our cover letter guide for the approach.
• Following up once. Send a brief email 1-2 weeks after applying if you haven't heard back. More than one follow-up crosses into annoying territory.

FAQ

What should I put on my resume if I have no work experience?

Focus on education (coursework, GPA, honors), projects (class and personal), skills, and activities/leadership. A strong project section with 2-3 well-documented projects is often more impressive to internship recruiters than a generic part-time job. See our no experience resume guide for more detail.

Should I include my GPA on my internship resume?

Include it if it's 3.0 or above. Many large internship programs use 3.0 as a screening threshold. If your major GPA is significantly higher than your cumulative GPA, you can list both. If your GPA is below 3.0, simply leave it off — don't lie about it.

How long should an internship resume be?

One page. No exceptions. You don't have enough relevant experience to justify two pages, and internship recruiters expect concise resumes from students. Every line should demonstrate a skill or achievement relevant to the target role.

Should I include high school achievements?

Only if you're a first-semester freshman with no college activities yet, or if the achievement is exceptional (national competition winner, published research, Eagle Scout). By sophomore year, replace high school items with college experience.

Is it okay to list group projects on my resume?

Yes — but be specific about your contribution. Instead of "Worked on a group project to build an e-commerce site," write "Led front-end development for a 4-person team building a React e-commerce prototype, implementing cart functionality and Stripe payment integration." The recruiter needs to know what you did.

---

Your experience is more valuable than you think — it just needs the right framing. GetNewResume tailors your resume to match each internship posting's specific requirements and keywords, using your real experience. No fabrication, no generic templates — just your background, optimized for the role you want.