Projects to Get an Internship: What to Build (No Experience)

It's late June, you have weeks of summer with nothing scheduled, and everyone keeps telling you to "build a project." Nobody tells you which one, or how to write it up so it actually earns interviews. This guide fixes both: a field-matched project you can ship in a weekend to two weeks, the rule for choosing it, and the exact words to turn it into a resume bullet and a portfolio entry. Building this proof is one step inside the overall plan for getting an internship with no experience; here we go deep on the part that step skips.

What makes a project worth putting on a resume

A project earns its spot on your resume when it passes one test: it mimics the actual work of the role you want, and it produces one measurable outcome. That's the whole filter. Everything below is just applying it.

Compare two versions of the same summer. "I'm learning Python and did some tutorials" is a hobby. "I analyzed three years of my city's open bike-share data and found that 40% of trips happen in a two-hour evening window" is a role-shaped project, because that is what a data analyst does on a Tuesday: take a messy public dataset, ask a question, ship a finding. Same hours, completely different signal.

The test works in every field. A marketing hobby is "I post on Instagram." A role-shaped marketing project is "I ran a club's account for six weeks and grew it from 80 to 240 followers with a content calendar I built." The difference is never how impressive it sounds. It's whether the work looks like the job and ends in something you can point at.

Pick your project by target field

Match the project to the role you're applying for, not to whatever's easiest to start. A recruiter reading your resume is asking a narrow question: can this person do the thing we need? Your project answers it directly when it copies the shape of their work. Below is one archetype set per track. All the tools named are free or have a usable free tier.

Software and data

Build a small app that solves an annoyance you actually have: a script that renames your screenshots, a tiny web tool that tracks something you care about. Put the code on GitHub and deploy it free on a host like GitHub Pages, Netlify, or Vercel. This mimics shipping working software. Outcome: it's deployed and live, or a handful of real people use it, like 12 classmates.

No app idea? Do a data analysis instead. Grab a public dataset (Kaggle, a city open-data portal, a sports league's stats), ask one question, and write a short conclusion with two or three charts. This mimics analyst work exactly. Outcome: the finding itself, stated as a number you can defend.

Marketing and social media

Run a real content account or a mock campaign for a local business, a campus club, or a cause you care about. Plan posts in a free Google Sheets calendar, design them in Canva's free tier, and run it for a set window like four to six weeks. This mimics the daily work of a social or content intern: plan, publish, measure, adjust. Outcome: follower growth, reach, or engagement over that window, with honest small numbers.

Prefer not to post publicly? Build a mock campaign brief for a real local business: target audience, three sample posts, a one-page plan with a goal. The artifact is the proof.

Design

Redesign one confusing screen from an app or website you use, and write three sentences on why your version is clearer. Mock it in Figma's free tier and show a clean before and after. This mimics product and UX work, where you justify decisions, not just make things pretty. Outcome: a before/after others can judge in seconds.

Or build a brand kit (logo, colors, type, a few templates) for a campus org and let them actually use it. Outcome: a shipped asset real people adopted.

Business, analytics, and finance

Build a competitor or market analysis deck on an industry you find interesting: who the players are, where the gap is, one defensible recommendation backed by numbers you cite. Or build a simple financial model for a public company in a free spreadsheet, pulling figures from its public filings. This mimics the analyst and consulting work of turning messy facts into a call. Outcome: a recommendation backed by numbers, not a vibe.

A mock pitch works too: a one-page memo arguing a specific decision (enter this market, cut this product) with the math attached.

Writing and communications

Start a curated newsletter on a narrow topic you know well and send it on a schedule for a month. Free tools like Substack or a Google Doc you share will do. Or write a teardown of a brand's messaging: what their homepage promises, where it's vague, how you'd rewrite it. This mimics comms and content work: clear thinking, shipped on a deadline. Outcome: subscribers, published pieces, or a visible body of work others can read.

Research

Write a short literature review on a question in your field (five to eight sources, your synthesis at the end), or design a small survey, collect responses, and write up what you found. Free survey tools like Google Forms handle the data collection. This mimics the core of research work: a careful, written finding. Outcome: the finding itself, stated plainly. This track pairs naturally with reaching out to a professor, since a small finished review is exactly what makes that email land.

Scope it so you actually finish

A finished small project beats an ambitious abandoned one every time, because a half-built thing proves nothing and can't go on a resume. The most common failure here isn't picking a weak project. It's picking a project so big it's still 60% done in September.

Four rules keep you out of that trap:

• Pick exactly one outcome before you start. One number, one finding, one shipped asset. Not three.
• Timebox it. A weekend or two weeks, hard stop. The deadline shapes the scope, not the reverse.
• Decide what "done" looks like in one sentence, written down, before you write any code or design anything. "Done is: deployed, with five people having tried it."
• Document as you go. Take screenshots, save your numbers, jot the decisions you made. You will not remember them in three months, and you'll need them for the write-up.

There's a seasonal reason to start now and not in August. Ship something this summer and it's on your resume and profile before fall applications open, when the openings you want actually go live.

How to capture one measurable outcome

The outcome is where students freeze: "I don't have an audience, so I have no numbers." You don't need big numbers. You need true ones. A small, real figure beats a vague claim and beats an inflated one, every time.

Real beats big. "12 classmates used my study-scheduler" is more convincing than "designed for thousands of students," because the first one clearly happened. "200 survey responses," "18% faster after my change," "grew from 80 to 240 followers" all work at any scale, as long as they're real. (Those are illustrative figures, not benchmarks to hit; your honest count is the right count.)

And if there's genuinely no number to capture, you still have three honest outcomes:

• A clear before/after. The redesigned screen next to the original. The cleaned-up spreadsheet next to the mess.
• A shipped artifact someone used. The brand kit a club adopted, the template people downloaded.
• A decision you made. "Analyzed the data and recommended X because Y." The defensible call is the outcome.

The one rule that matters: never invent or inflate a number. An interviewer will ask how you measured it, and a made-up figure unravels in one question. A modest true number you can explain is far stronger than an impressive fake one.

The write-up template: from project to resume bullet and portfolio entry

You built the thing. Now make it work for you in two places: one tight line on your resume, one slightly longer entry on your portfolio or profile.

The resume bullet formula

Use this structure:

Action verb what you built using tool/method, one measurable outcome.

Filled in across different fields:

• "Built a study-scheduler web app using JavaScript and Netlify, used by 12 classmates in its first week."
• "Ran a campus club's Instagram for six weeks using a Canva content calendar, growing it from 80 to 240 followers."
• "Modeled a public company's revenue in Google Sheets from its filings, recommending against the new product line based on its margin."

Each one names the action, the thing, the tool, and the result. For where this bullet goes on the page and how to budget your lines, see how to format the bullet on your resume; this post is about producing the bullet, that one is about placing it.

The portfolio and LinkedIn entry

The same project gets a longer write-up wherever it lives online, in four short beats:

1. Problem: the one-sentence reason this exists.
2. What you built: what it is and the tools you used.
3. Outcome: your one measurable result, stated honestly.
4. Link: to the live thing, the repo, the deck, or the writeup.

This entry can live on a free one-page site, in a shared PDF, or directly on your profile. University career centers note that a portfolio is a tool for any field, not just design, to give employers a clear view of your skills. For exactly where your project lives on your profile, specifically your LinkedIn Featured and Projects sections, the LinkedIn guide walks through the mechanics. One bonus you get for free: this same problem-to-outcome story is your answer when an interviewer says "tell me about something you've built."

Frequently asked questions

Do personal projects actually count for internships?

Yes. Recruiters hiring interns want evidence you can do the work, and a self-directed project is direct evidence: you chose it, scoped it, and finished it. Be honest about what it does, though. A well-documented project strengthens your case and gives you something concrete to talk about; it doesn't guarantee an interview on its own. It's one strong signal among several.

What if I'm not a programmer? What project do I build?

The same selection rule applies to every field. Use the marketing, design, business, writing, or research track above. A finished competitor analysis, a six-week newsletter, or a redesigned screen is proof of skills in exactly the same way a deployed app is. Non-technical does not mean no project.

How many projects do I need?

One well-scoped, well-documented project beats three half-finished ones. Depth wins: a recruiter would rather see one thing you can explain end to end than a list of abandoned starts. Add a second project only if it shows a different skill the role specifically asks for.

Can a class or capstone project count?

Yes, as long as you can describe what you personally did and point to an outcome. Group projects count when you can claim your specific part. Framing coursework you've already done is the resume post's job, so for that move see how to format the bullet on your resume. This guide is about building something new when you don't have coursework that fits.

How do I list a project on my resume?

Use the bullet formula above: action verb, what you built, the tool, the outcome. Section order, where projects sit on a one-page layout, and line budgets are placement questions, covered by the resume guide linked earlier.

Pick your field from the picker above, choose one measurable outcome, and start this weekend. Timebox it to two weeks so it's finished and written up before fall applications open. Then match your project to the kind of role you'll find when you browse internships, and apply with proof instead of a blank page.