How to List Projects on a Resume: Format and Examples

Last updated: 21 September 2026 · By the Asuraa Team

Should you put projects on a resume?

Yes, if they show skills the job needs. Resume Genius says projects belong on a resume especially when you do not have much industry experience.

For a fresher, projects are often the strongest evidence you have. This guide covers where to put them, what to write, how many to list and how to choose. If you are still building the rest of your resume, start with our guide to a resume for freshers in India.

How do you list projects on a resume?

Give each project its own short entry with the same fields every time. Indeed's guide (published 4 May 2026) lists the project name, dates or duration, team size, your specific role and the outcome or impact as the details to include.

Use this order for each entry:

1. Project name and a one-line descriptor, such as "sales dashboard for a college club".
2. Tools and technologies you used, in the same words the job posting uses where they are true.
3. Dates or duration, for example "Jan 2026 to Mar 2026" or "6 weeks".
4. Your role and team size, especially if it was a group project.
5. One to three bullets that follow Indeed's pattern of a strong verb, the task, and the impact.
6. A link to the code, demo or write-up, if you have one.

Internshala's fresher resume guide, which shows no publication date, gives similar advice: focus on the tools used, the project's goals and your specific role.

Where should the projects section go on a resume?

Put it where a recruiter will see it early. For most freshers that means directly after education or skills, and before any thin experience section.

Resume Genius suggests placing each kind of project where it fits best. Indeed also notes that projects can sit under job descriptions, in a dedicated section or under education.

The exact heading matters less than consistency and clarity.

How many projects should you list?

Three to five is a sensible range. Resume Genius recommends limiting a resume to the three to five most applicable projects, since listing too many unrelated ones can clutter the page.

Indeed makes a similar point: include only as many as a hiring manager can review properly, especially if you link to a portfolio. On a one-page fresher resume, two to four well-written entries usually fit more comfortably than six thin ones, though that is our editorial suggestion.

Which projects should you include?

Include a project if it passes three tests. It should be relevant to the role, you should be able to explain it in an interview, and it should show a skill you have not already proved elsewhere.

Use this quick decision framework, which is editorial advice and not a sourced rule:

1. Read the job posting and highlight the five skills or tools it mentions most.
2. List every project you have done, including coursework and hackathons.
3. Score each one by how many highlighted skills it shows.
4. Keep the top three or four, and drop any you could not discuss for five minutes.
5. Reorder for each application, placing the closest match first.

Our guide to ATS resume keywords explains how to find the wording a posting uses.

What does a good project entry look like?

A good entry is specific about what you built, with what, and what came of it. The example below is an illustration for a fresher applying for a data analyst role. The project and figures are invented to show the format, so do not copy them.

Hostel Mess Feedback Analysis | Python, pandas, Matplotlib | Jan 2026 to Feb 2026

- Cleaned and combined 1,200 survey responses from three hostels into one dataset.

- Built four charts showing complaint categories by meal and by week.

- Presented findings to the mess committee, which used them to review the weekly menu.

github.com/yourname/mess-feedback (illustrative link)

Notice that every bullet starts with a verb and says what was done. The last bullet shows an outcome without claiming more than it should.

How do you write project bullets when you have no numbers?

Describe the scope, the action and the result you can accurately state. Resume Genius recommends quantifiable results, but a project does not always produce them.

When you have no metrics, use one of these instead:

• Scale: the size of the data, the number of users or the number of features.
• Outcome: what the project let someone do, such as "lets students compare bus routes".
• Recognition: a hackathon placement, a faculty review or a committee that used the output.
• Proof: a link to code or a demo that a recruiter can open.

Never invent figures. Interviewers often ask follow-up questions about the numbers on a resume, so use only ones you can explain.

What do most guides on projects on a resume get wrong?

Most guides explain the layout and stop there. These are the gaps that tend to hurt freshers.

• They treat all projects equally. A relevant project in the first position does more than a long list in date order.
• They assume you have metrics. Many student projects have none, so guides that insist on percentages push people towards made-up numbers.
• They ignore the link. A repository or demo that a recruiter can open is evidence, while a project with no way to check it is only a claim.
• They skip readability for software. Keep the section in plain text with standard headings, as covered in our guide to making an ATS-friendly resume.

FAQ

Should a fresher put projects on a resume?

Yes. When you have little or no work experience, projects show that you can apply skills, and Resume Genius says they belong on a resume in that situation. Choose the ones that match the job and describe what you built, the tools you used and the result.

How many projects should I list on a resume?

Aim for three to five that match the job. Resume Genius recommends limiting the list to the three to five most applicable projects, because too many unrelated ones clutter the page. On a one-page fresher resume, two to four strong entries often work well.

What should I include for each project on a resume?

Include the project name, the tools you used, dates or duration, your role, and one to three bullets on what you did and the outcome. Add a link to the code or demo if you have one. Indeed also suggests noting team size for group work.

Where do I put projects on a resume?

For a fresher, a dedicated Projects section after education or skills usually works. Academic projects can also sit under education, and work or freelance projects can go inside the relevant experience entry. Place the section where a recruiter will see it early.

Can I list college projects on a resume?

Yes. College and final-year projects count, especially if you have no job history, and Resume Genius suggests listing them under education or in a projects section. Describe your own contribution, the tools and any result, and be ready to explain them in an interview.

How do I describe a project with no measurable results?

Describe the scope, your action and what the project made possible. For example, mention the size of the dataset, the features you built or who used the output. Add a link to code or a demo, and do not invent percentages you cannot explain.

Final thoughts

Projects turn a claim like "I know Python" into something a recruiter can check. Choose the few that fit the role, write each one the same way, and make sure you can talk about every line.

To see how your projects and keywords read against a real job description, try the AI resume reviewer on asuraa.in. If you are still looking for experience to show, read how to get a job without experience.