TL;DR: Toss a “Projects” section right after “Skills.” List 4–6 projects—work or personal—and pair each with a one-line punchline about the impact. Call them “External Projects” if they weren’t tied to a job.
So why do projects even matter on a resume?
Recruiters don’t just want to hear you can do the work—they want to see it. A smart “Projects” section turns vague skills into real wins, especially when your work history is thin or your tech stack needs proof. Four to six projects is the sweet spot; any more and you risk overwhelming the reader.
How do I actually place projects on my resume?
- Pick the right spot.
- If a project grew out of a job, tuck it under that role’s bullet list.
- If it’s a side hustle or passion project, give it its own section called “Projects” or “External Projects” right after “Skills.”
- Write one killer line per project.
The template’s simple:
“[Project Name] — [What it does] | [Impact metric]”Example in action:
“Sales Forecast AI — Built Python model to predict quarterly revenue | Cut reporting time by 40 %” - Keep it lean.
- Lead with the title; one sentence only.
- Skip the buzzwords unless the job posting begs for them.
- Dump phrases like “Responsible for…” and show results instead.
- Link it up (if you can).
- Drop in a GitHub repo, a live demo, or a PDF on your site.
- Label links clearly: “GitHub | Demo | PDF.”
What if I don’t have enough projects to fill the section?
- Add 1–2 high-impact personal projects.
- Try something like “Built a Chrome extension to block distracting sites | 500+ active users.”
- Skip the “for fun” stuff; focus on problems you solved.
- Too many projects?
- Bundle related work under one umbrella—call it “Data Pipeline Suite” instead of listing three separate ETL scripts.
- Cut anything older than five years unless it’s a career-defining win.
- Wrong section placement?
- For internships or early-career roles, slide projects under “Experience” and tag the company name.
- For senior roles, move them to a “Portfolio” section and add a “View work” link.
How can I keep my project list from going stale?
| Tip | Action | Why It Matters |
|---|---|---|
| Quarterly review | Update your resume every three months with fresh projects. | Keeps your file current and avoids last-minute panic before applying. |
| Skill-first filter | Ask: “Does this project prove a core skill the job needs?” If not, lose it. | Saves recruiters’ time and makes your resume laser-focused. |
| Impact metric | Turn “built X” into “saved Y hours” or “boosted Z by Q %.” | Numbers speak louder than adjectives; recruiters scan for ROI. |
| Portfolio backup | Set up a single-page site (GitHub Pages, Notion, or Carrd) with full project docs. | Keeps your resume clean and gives recruiters a deeper look when they’re interested. |
Sources: LinkedIn Help (2026), Glassdoor Resume Guidelines (2026), Indeed Resume Advice (2026).
