Choose projects that help answer the employer's question
A project section can give a reader evidence that does not appear in a conventional job title, especially for students and people early in a technical field. Look for class assignments, personal work, hackathon entries, research, volunteer work, or collaborations that show the kind of problem-solving the target role needs.
Select for relevance rather than trying to document every project. Two well-chosen examples that show a useful capability are stronger than a crowded inventory of unfinished experiments or work unrelated to the role.
Write each entry like a compact case for your contribution
Give each project a clear name, then use concise bullets to explain what you made, investigated, improved, or delivered. Name the tools or methods only where they clarify the work, and describe your own contribution precisely when the project involved a team.
Add a concrete result when you can verify it: a working feature, completed analysis, tested prototype, presentation, publication, or measured change. Do not claim that a class, personal project, or group effort was paid professional work; accurate labels preserve trust.
Put the section where it can do useful work
Place Projects near the top when it is a primary source of relevant evidence, such as during a student job search or a transition into a technical role. As paid experience becomes more directly relevant, move projects lower or keep only the ones that add a distinct capability not shown elsewhere.
Before submitting, open any portfolio, repository, or demo link you include and make sure it supports the description on the resume. Remove links with unfinished work, private material, or an unclear connection to the project; the resume should make the next step simple for the reader.
Sources consulted
This guide is an original synthesis of the following career guidance. Read the source material for its full context.