How to Put Personal Projects on a Resume

Photo by Snapmaker 3D Printer on Unsplash

You built something. Maybe it's a budgeting app you made for yourself, a small business you ran out of your dorm room, or a data project you did for a class that actually got used by your school's admin office. Now you're staring at a resume template with an "Experience" section and nothing to put in it. The instinct is to either leave it blank or bury the project in a "hobbies" line at the bottom. Both are mistakes. The fix is simpler than it feels: give the project a title, a date range, and a result, exactly like you would for a job — because as far as a resume is concerned, that's what it is.

Why a project can carry a resume with no job history

Recruiters and applicant tracking systems don't actually care whether a paycheck was involved — the same is true of volunteer work, for the same reason. They care about three things: what you did, what tools you used, and what happened as a result. A personal project can answer all three just as well as a job can — sometimes better, since you probably remember exactly what you built and why, instead of a vague list of "duties" from a role you barely remember.

The problem isn't that your project is weak evidence. It's that most people describe it like a hobby instead of like work. "Made a website for fun" tells a recruiter nothing. "Built and launched a scheduling site for a 40-person volunteer group, cutting sign-up time from 15 minutes to under 3" tells them exactly what you're capable of. Same project. Different framing. The framing is the whole job here.

Give the project a job title, not just a name

Every job entry on a resume has a title, an employer, and a date range. Give your project the same three things, even though the "employer" is you.

• Title: describe your role, not your feelings about the project. "Founder," "Lead Developer," "Independent Researcher," and "Project Lead" all work. Skip "Personal Project" or "Side Project" as the title — that's a category, not a role, and it undersells what you actually did.
• Employer line: write "Independent Project" or "Self-Directed" where the company name would go. Don't disguise it as a company — own that it was self-initiated. Hiring managers respect that more than they penalize it.
• Dates: include a real range, even if it was three weekends. "Feb 2026 – Apr 2026" reads as a defined body of work. No dates at all reads as unfinished or abandoned.

Here's the format side by side:

``` Weak: Strong: Personal Project Founder & Developer — Independent Project (no dates) Jan 2026 – Mar 2026 - Made an app - Designed and built a budgeting app in React and Firebase, used weekly by 60+ classmates to track shared apartment costs ```

The four-part formula for the bullet points

Once the entry has a proper header, the bullets need to do the actual convincing. Use this order every time: what you built, the tools or method you used, who it was for or how big it got, and what changed as a result.

[Action verb] + [what you built] + [tool/method] + [scale or context] + [measurable outcome].

A worked example: say you ran a small side business reselling refurbished electronics while you were a student, with no formal "employer" to list. Written as a hobby, it disappears: "Sold electronics online sometimes." Written with the formula:

"Sourced, repaired, and resold 85+ refurbished laptops and phones via a self-built online storefront, generating $14,200 in revenue over 18 months while managing inventory, pricing, and customer support solo."

That single line does more work than three vague duties would. It names a real number, a real tool implication (an online storefront you built and ran), and a scope ("solo") that signals ownership. If your actual number is smaller — say 12 laptops and $1,800 — use that. A precise small number reads as more credible than a vague big one, and recruiters can tell the difference.

If you genuinely can't attach a number yet — the project is new, or it never had users to count — don't invent one. Describe the scope instead: "Built a full CRUD web app with user authentication and a PostgreSQL backend, deployed to a live URL for public testing." That's still concrete. It's the vague version — "made an app for practice" — that reads as filler, not the absence of a metric.

Where the projects section goes when you have no work history

For a full breakdown by career stage — student, career changer, developer, senior professional — see our guide to where the projects section goes. The short version: if you have zero paid work experience, put Projects above Education and well above any thin "Experience" section — it's your strongest evidence, so it goes where a recruiter's eyes land first after your name and summary. If you have a little work experience (a retail job, a short internship) but your projects are more relevant to the role you want, projects still go first; recency and paid status don't automatically outrank relevance.

Once you have 2-3 years of real, relevant work experience, projects usually move down below Experience, or drop to just your single strongest one. Nobody past their first couple of job searches needs five side projects competing with actual paid roles for attention — but right now, they're not competing with anything. They're the strongest thing on the page.

Limit yourself to 3-4 project entries even if you have more available. A resume packed with eight small things reads as padding; three or four well-described ones read as focus. Pick the projects most relevant to the job you're applying for, not just the ones you're proudest of — a data-cleaning script is more useful evidence for a data-analyst posting than a personal blog, even if the blog got more traffic.

What to do with a project that never really "launched"

Not every project has a launch, a user count, or a dollar figure attached, and that's fine — plenty of legitimate learning projects are also legitimate resume material. The fix is to be honest about what happened and specific about what you learned or built, instead of dressing it up as more finished than it was.

"Built a machine learning model to predict housing prices using scikit-learn and a public Kaggle dataset, achieving 87% prediction accuracy on a held-out test set through iterative feature engineering."

That project has no users and never "launched" anywhere, and it's still a strong entry because the outcome (87% accuracy, a real technique named) is specific and true. What doesn't work is claiming impact you can't back up — "revolutionized how I approach data" is the kind of line that makes a recruiter's eyes glaze over, because it's an opinion dressed as an achievement. Stick to what's verifiably true and let the specificity do the persuading.

One caution: if a stat like an industry benchmark or "X% of recruiters value project work" would strengthen this section, don't invent the number to sound more convincing. Flag it plainly instead: `[NEEDS SOURCE: recruiter-survey stat on project-based hiring]` and swap in a real citation before publishing, or drop the line entirely.

The bottom line

The project happened. The work was real, even if nobody signed your paycheck for it. The only thing standing between "hobby" and "experience" on your resume is formatting — a title, a date range, and a bullet that names what you built, how, and what happened next. Do that consistently across three or four entries, and a resume with no traditional job history stops looking empty and starts looking like proof.

If you're not sure how the formatting should actually look once it's laid out, Simple CV has resume templates built to hold a Projects section properly — worth a look once you've got your bullets written.