Projects on a resume are specific, goal-driven efforts you completed that demonstrate your skills, whether they happened at work, in school, on your own time, or as freelance gigs. They differ from your regular job duties because each one had a defined objective, a start and end point, and a tangible result. Adding a projects section (or weaving projects into your experience section) gives you a way to show what you can do, especially when your formal job titles don’t tell the full story.
What Counts as a Project
A project is broader than a single task. Writing one email or reviewing one design mockup is a task. Launching an email campaign that ran for three months and boosted open rates by 25% is a project. The distinction matters because hiring managers want to see that you can take ownership of something with multiple steps, coordinate the pieces, and deliver a result.
Four categories of work typically qualify:
- Work projects: Initiatives or assignments from a full-time or part-time role, like a product launch, a process improvement, or a cross-functional collaboration.
- Academic projects: Research papers, capstone assignments, group presentations, or lab studies completed during school. These are especially useful for students and recent graduates who don’t yet have deep professional experience.
- Personal projects: Side efforts driven by your own curiosity or ambition. Building a blog, creating a mobile app, launching a podcast, or designing a website all count. These signal initiative and genuine interest in your field.
- Freelance projects: Client work you completed independently, whether it was a single contract or an ongoing engagement. Freelance projects demonstrate that someone trusted you enough to pay for your skills.
When a Projects Section Makes Sense
Not every resume needs a standalone projects section. If you have years of directly relevant experience, your work history already tells the story. But a dedicated section becomes valuable in a few situations. Career changers can use projects to prove they have skills in a new field even though their job titles suggest otherwise. Students and recent graduates can fill gaps left by a short work history. And anyone in a technical or creative field (software development, data analysis, UX design, marketing) can use projects to show hands-on ability that a job title alone won’t convey.
If you include one, make sure every project ties back to a skill or quality relevant to the job you’re applying for. A coding bootcamp capstone belongs on a resume for a developer role. It probably doesn’t belong on a resume for a sales position unless it demonstrates analytical thinking you want to highlight.
How to Format a Project Entry
Each project entry follows a simple structure: a name, your role or a brief description, a date, and bullet points explaining what you did and what happened as a result. Here’s the general pattern:
Project Name | Your Role or Brief Description
Date or Date Range
Bullet points detailing your actions, tools, and outcomes
For example, a design student might write:
Foodlife Menu App | App Designer
April 2020
- Designed and coded a mobile app for local restaurant options using iBuildApp
- Tested UX with 103 beta users and iterated based on feedback
A marketing professional might write:
Brand Awareness Campaign | Social Media Lead
January 2023 – March 2023
- Cultivated 300 new Instagram followers in one month
- Generated 700 retweets on a single post through targeted content strategy
You can place these entries in a section labeled “Projects,” or you can use a more descriptive heading like “Research Experience” or “Technical Projects” if that better fits the work.
Writing Results-Focused Bullet Points
The most common mistake people make with project entries is describing what they worked on without explaining what came of it. Hiring managers skim resumes quickly, and a vague bullet like “managed social media accounts” tells them almost nothing. Compare that to “increased social media engagement by 45% in six months through targeted campaigns.” The second version proves impact.
Start each bullet with a strong past-tense action verb: launched, designed, reduced, built, streamlined, led. Then describe what you did and the result it produced. A useful formula is: what you did + the tools or methods you used + the measurable outcome.
Numbers make your entries dramatically more convincing. Think about how many people you worked with, how much money you saved or generated, what percentage improvement you achieved, or how many users, responses, or data points were involved. One DePaul University career center example describes a student who “designed a health awareness survey and collected 200 responses from the community,” which is far more memorable than “conducted survey research.”
If you don’t have exact numbers, estimate based on the trends or improvements you contributed to. Approximate figures still paint a clearer picture than no figures at all.
Linking to Proof of Your Work
When your project produced something visible, linking to it strengthens your credibility. Developers can include GitHub repository URLs. Designers and writers can link to an online portfolio. Analysts can point to a public dashboard. Even a simple Notion page collecting your case studies gives a recruiter something concrete to review instead of relying solely on your written claims.
Keep the link clean and professional. A custom domain or a well-organized GitHub profile looks more polished than a cluttered Google Drive folder. If the project involved confidential client work, describe the outcomes on your resume without linking to proprietary materials.
Where to Place Projects on the Page
Placement depends on how central the projects are to your candidacy. If your projects are the strongest evidence you have for the role (common for career changers, bootcamp graduates, and students), put the section above your work experience so it’s one of the first things a recruiter reads. If your work history is already strong and projects are supplementary, place the section below your experience.
You also don’t have to use a separate section at all. Work projects can live as bullet points under the relevant job in your experience section. This approach works well when the project happened as part of a role and you want to keep your resume streamlined. Reserve a standalone “Projects” section for work that doesn’t fit neatly under an employer’s name, like personal builds, academic research, or freelance assignments completed between jobs.