A personal project belongs on your resume when it provides relevant evidence that your work history does not already show clearly.

Treat it like professional evidence, but label the context honestly.

Where projects go

Common options:

Dedicated Projects section

Best for:

  • students;
  • graduates;
  • career switchers;
  • technical candidates with several relevant projects.

Under Education

Useful for:

  • capstones;
  • coursework projects;
  • thesis work.

Inside Experience

Only when the project genuinely belongs to a role, freelance engagement or organization.

Do not disguise a personal project as employment.

Title and context

Use a clear title.

Examples:

  • Inventory Optimization Project
  • Mechanical Bracket Design & Validation
  • Customer Churn Analysis
  • Safety Incident Analysis Exercise

Optionally add:

  • Personal Project;
  • Academic Project;
  • Freelance Project;
  • Volunteer Project.

What to include

Include:

  • problem;
  • tools;
  • your action;
  • important method;
  • result;
  • artifact/link if useful.

Strong bullets

Weak:

Created a machine learning project using Python.

Stronger:

Built a churn-classification pipeline in Python, compared logistic regression and gradient boosting, and evaluated precision/recall trade-offs against a baseline.

Weak:

Created inventory dashboard.

Stronger:

Built an inventory dashboard for 300 synthetic SKUs, defining stockout-risk and excess-inventory logic and adding drilldowns by product category.

Useful links can include:

  • GitHub;
  • portfolio page;
  • live demo;
  • technical report.

Only add links that work and contain something worth reviewing.

Do not force a recruiter to navigate a messy repository to understand the project.

Tailoring

Choose projects based on the job.

For a data analyst role, surface analytics projects.

For a mechanical design role, surface CAD/design/test projects.

For a safety role, surface risk/audit/investigation evidence.

Do not list every project you have ever built.

Common mistakes

Hiding that it is personal

Be transparent.

Too many bullets

Two or three strong bullets are usually enough.

Technology dumping

Do not list ten tools without explaining why they were used.

Fake business impact

If no customer or business used the project, do not invent revenue or cost savings.

No outcome

Explain what the analysis/design produced.

The purpose of a project section is not to show that you stay busy. It is to prove relevant capability.

Related content