7 min read
A side project isn't a personality badge. It's proof. If it doesn't show you can do tomorrow's tasks, it doesn't belong on the one-page file you're sending tonight.
Most candidates dump builds into a Projects section because templates suggest it. Recruiters often read Experience first. When you bury the only React proof below unrelated jobs, you're making them hunt. check your resume for free against the posting before you add another line. You'll see whether keywords land under an employer block or float in a side list parsers underweight.
You're not deciding if side projects are impressive. You're deciding where they earn space: under a job header as a bullet, or in a short Projects block when you've got more than one relevant build and no honest employer line.
The comparison below walks Experience bullets vs a Projects section, then shows formatting that keeps parsers and humans aligned.
Side projects on a resume: Experience bullets vs Projects section
Both placements can work. They do different jobs. Experience ties skills to a timeline recruiters trust. Projects collects extra builds when you do not have a paid header that fits.
| Placement | Use when | Risk if misused |
|---|---|---|
| Experience bullet or freelance line | One flagship build proves a posting must-have | Fake employer names or vague dates get challenged in screen |
| Projects section (2 to 3 entries) | Several relevant builds, thin paid history, or career pivot proof | Long lists look like a hobby dump and push paid roles down the page |
| Omit from resume; link only | Senior scope already fills the page; project is unrelated or unfinished | You lose keyword tie if the posting demands that stack and you skip the file entirely |
Default rule: if you'd stake an interview answer on the build, give it an Experience-style bullet with tools in the first line.
When the side project belongs under Experience
Treat paid and unpaid work the same in the bullet. The header carries honesty. The bullet carries skill proof matchers can link to dates.
Before: Projects section lists Weather App with no stack and no outcome.
After: Independent Contractor, 2024 to Present, with a bullet that opens Built a React dashboard pulling OpenWeather data, deployed on Vercel with CI from GitHub Actions.
Career changers can use one freelance-style line for a capstone that mirrors the target role. Keep dates narrow. Do not stretch a weekend build across three years.
Gap fillers work the same way. If you built during unemployment, one dated line with two bullets beats a vague gap explanation in a cover note. The resume should show motion, not a blank year.
If the side project supported a real client, even a small one, name the engagement or use Contract work for [Client type]. That reads cleaner than inventing a product company.
I've screened side-project-heavy files where the only React proof sat in Projects while Experience still listed unrelated retail bullets. Moving that one build under a dated header got the match signal recruiters actually sort on.
Should you include GitHub on your resume pairs with this choice: link in the header, proof in Experience bullets.
When a Projects section beats a junk drawer
Open Projects when you have multiple relevant builds and no employer line that fits all of them. Students and bootcamp grads often need two entries: capstone plus one production-style clone.
Before: Six tutorial repos listed with equal weight.
After: Two entries with stack, scope, and link. Everything else stays on GitHub only.
Place Projects after Experience unless you're entry-level with no paid roles yet. Then Projects can sit above Education. Never above a strong internship line.
Skip Projects entirely when ten-plus years of paid scope already proves the skill. A staff engineer's weekend API does not need page space when leadership bullets fill the screen.
Resume tips for switching industries covers how pivot proof should sit relative to older job titles.
Format side project bullets like paid work
- Lead with the verb and the tool the posting repeats.
- State scope in one clause: users, data volume, or integration, as illustration not a market claim.
- Add one link if the repo or demo is interview-ready.
- Match date style to the rest of the file (month year or year only).
- Delete entries you cannot explain for five minutes in a screen.
Copy-paste project bullet:
Built a Node.js inventory API with PostgreSQL, cut manual stock checks for a 12-SKU pilot shop (personal contract project)
Do not label everything Personal Project without context. Recruiters assume toy code. Say what problem you solved and which stack matched the req.
Open-source contributions can sit as one bullet under a Projects entry or under a volunteer line if you maintained a module recruiters will recognize. Name the repo once. Do not paste ten commit hashes.
Designers can list a shipped side site with Figma, Webflow, or HTML proof in one bullet. Keep screenshots off the PDF unless the employer asks for a portfolio file. A single URL in the bullet is enough for the resume pass.
Why weak bullet points get ignored applies to side work the same way it applies to day jobs.
Generate a cover letter when the side project is the whole story for a pivot and you need one paragraph to frame scope without adding a second page of repos.
Placement mistakes that waste space
- Skills list without a bullet: posting terms in Skills alone rarely beat the same term in Experience.
- Duplicate project in two sections: pick Experience or Projects, not both.
- Unfinished repos on the file: empty readmes signal risk in technical screens.
- Unrelated builds for keyword stuffing: matchers and humans both notice mismatch.
Match projects to the posting before submit
Paste the job description next to your draft. If the must-have tool appears only under Projects, test moving one bullet under Experience and re-run match.
Run a job match score after you place side projects. You'll see whether keywords tie to employer lines or stay orphaned.
Run the ATS check on your project section if headings fail to import. Fix column layout before you add more builds.
Put proof where recruiters sort first
Should you include side projects on a resume comes down to relevance and placement, not pride in the repo. Your best build earns Experience treatment. Extra relevant work fits a tight Projects section. Everything else stays off the file.
Edit one project tonight. Move it under a dated header or trim the list to two entries. Re-test parse and match before you send the next application.
When the posting is silent on personal work, let paid bullets lead. Add side proof only if a must-have would otherwise be missing from Experience.
Read more
Frequently asked questions
Put one strong build under Experience when it proves a posting skill and you can date it honestly, often as a freelance or independent contractor line. Use a Projects section when you have two or more relevant builds and no clean employer header, or when the work was coursework you still want searchable.
One to three that match the role. More reads like a junk drawer. Move the rest to a portfolio link in the header or LinkedIn. Recruiters skim for proof tied to the job, not a catalog of every weekend experiment.
Most parsers recognize a Projects heading if it sits in the main column with standard headings. Bullets under Experience usually score higher because matchers tie keywords to employer blocks. If you use Projects, mirror the same action-verb bullet style as paid roles.
Yes when it demonstrates the skill the req asks for. Label the line clearly: Independent Project, Freelance, or Contract if you had paying clients even once. Do not invent a company name. A honest one-line header beats a fake startup title.