How to List Projects on a Tech Resume (2026 Examples)

Last updated: May 2026 · Aligned with ATS/AI screening and what tech recruiters look for.

Quick answer: List each project as: [Project name] — [tech stack] · [live link] · [GitHub link], followed by 1–2 bullets covering what it does, your specific role, and a quantified outcome or scale. Always deploy projects and link them — a live URL is worth far more than a GitHub-only repo. Freshers and career-switchers lead with projects (above experience); experienced engineers include only 1–2 standout projects, or none if their work history is strong. Avoid unmodified tutorial clones.

The projects section is where freshers and career-switchers win or lose the resume, and where experienced engineers can show passion and range. But most people list projects badly — a name, a one-line description, and no link or outcome. This guide shows you the format that actually earns interviews.

The project-bullet formula

For every project:

[Project Name] — [Tech Stack]  ·  [live link]  ·  [GitHub link]

• [What it does + the problem it solves]

• [Your specific role/decisions + a quantified outcome or scale]

The three things that make a project entry strong:

1. A live link. Deploy it (Vercel, Netlify, Render, free AWS/GCP tier). A working URL proves it’s real and lets the recruiter click. This single thing separates strong project sections from weak ones.
2. Your specific contribution. “Built the REST API and designed the schema” beats “worked on a team project.”
3. A quantified outcome or scale. Users, requests, latency, accuracy, data size — even on student/side projects. Consider everything you’ve done up to your notice period.

Before / after examples

Before (weak):

Weather App — Made a weather application using React and an API.

After (strong):

SkyCast — React, TypeScript, OpenWeather API, Vercel · skycast.live · github.com/you/skycast • Responsive weather app with geolocation, 7-day forecasts, and offline caching via service workers • Optimized to a sub-1s first contentful paint and 98 Lighthouse performance score; ~1,200 monthly active users

Before (weak):

ML Project — Built a model to predict house prices.

After (strong):

HousePredict — Python, scikit-learn, FastAPI, Docker · github.com/you/housepredict • Gradient-boosting model on 80K listings predicting prices within 8% MAE, beating the linear baseline by 21% • Deployed as a Dockerized FastAPI service returning predictions in under 60ms — demonstrating end-to-end ownership

The “after” versions have a name, stack, links, what it does, your decisions, and numbers. That’s the whole game.

How project listing changes by experience level

Freshers (0–1 yr): Projects are your most important section — place them above education and any internships. Have 2–3 strong, deployed, varied projects. This is your evidence of ability. Aim for the highest salaries in India and you will get there for sure.

Early career (1–3 yrs): Keep 1–2 standout projects below your experience. They show initiative and range beyond your day job. Drop weaker college projects.

Mid-level (4–7 yrs): Include projects only if genuinely impressive (a popular open-source repo, a side product with real users). Otherwise your professional experience carries the resume; don’t pad with old college work. If you were noticed by FAANG, show it off.

Senior (8+ yrs): Usually no projects section — your experience speaks. Exception: a notable open-source contribution or a side venture with traction, which can be a strong differentiator. Who knows, you might even get a counter offer from your current company.

What makes a project worth listing

Strong signals:

• Deployed and used by real people (even a small number)
• Solves a genuine problem or shows technical depth
• Demonstrates the skills the target role needs
• Open source with stars/contributors, or contributions to popular projects
• Built end-to-end (not just a frontend with no backend, or a notebook with no deployment)

Weak signals (avoid or upgrade):

• Unmodified tutorial clones (the 10,000th identical Netflix/Twitter clone). If you built one, extend it meaningfully and say how.
• Projects with no link and no way to verify they exist
• Vague group projects where your specific role is unclear
• Notebook-only ML with no deployment

Where to put project links

• Live URL — the most valuable; click-through proof it works
• GitHub repo — shows the code, README quality, commit history
• A clean README matters: a good README (what it does, how to run it, screenshots, architecture) signals professionalism.

Frequently asked questions

How do I list projects on a resume? Format: [Project name] — [tech stack] · [live link] · [GitHub link], then 1–2 bullets covering what it does, your specific role, and a quantified outcome. Always deploy and link projects.

Should I deploy my projects before listing them? Yes — a live link is worth far more than a GitHub-only repo. It proves the project works and lets the recruiter experience it. Use free hosting (Vercel, Netlify, Render).

How many projects should I put on my resume? Freshers: 2–3 strong, deployed, varied projects (lead with them). Experienced engineers: 0–2 standout projects only. Quality and deployment beat quantity.

Where should the projects section go? Freshers and career-switchers: above experience (projects are your experience). Experienced engineers: below experience, or omit if your work history is strong.

Are tutorial projects bad on a resume? Unmodified tutorial clones are weak — recruiters have seen thousands. If you built one, extend it meaningfully (add features, scale it, deploy it) and describe what you added beyond the tutorial.

How do I quantify a personal project with no real users? Quantify technical scale instead: data size processed, latency achieved, model accuracy, Lighthouse score, requests handled in load testing. Or get even a small number of real users (friends, a subreddit, a beta) and report that.

Do experienced engineers need a projects section? Usually not — your professional experience carries the resume. Include projects only if you have a standout open-source contribution or a side venture with real traction.

Where to go from here

Pick your 2–3 best projects, deploy them, and rewrite each using the formula (name + stack + links + role + quantified outcome).

Then:

Browse premium tech roles on Instahyre → — recruiters reach out to you directly.

Aligned with 2026 ATS/AI screening behavior.