Topic: Resume & LinkedIn

How to write projects on a resume when you have no work experience

Updated · 5 min read · Resume & LinkedIn

When you have no work experience, your projects are your experience, so describe them the way a job would be described: what the project does and for whom, the technologies used, what you personally built, and a concrete result or learning. Use two or three bullets per project that start with strong verbs, include specific details an interviewer can ask about, and link to the code. A well-described small project beats a vague description of a big one.

The formula

For each project, write:

Project name | Technologies | Link
One line: what it does and who it's for.

  • Built / implemented [specific feature] using [specific technology], so that [benefit]
  • Solved / improved [specific problem], by [what you did]
  • Result or learning: [something concrete and true]

Keep each bullet to one or two lines. Two or three bullets per project is enough.

Before and after examples

Before (vague)
E-commerce website

  • Made an e-commerce website using HTML, CSS, JavaScript and PHP
  • Worked on frontend and backend

After (specific)
CampusKart: second-hand book marketplace for students | PHP, MySQL, JavaScript | github link

  • Built listing, search and seller-contact features so students could sell used textbooks within the college
  • Designed the MySQL schema for users, listings and messages; added indexes after search became slow with test data
  • Deployed on a free hosting tier; tested with friends from two hostels and fixed 10+ reported bugs

The second version gives the recruiter a clear picture and gives the interviewer five good questions to ask, all of which you can answer.

Before (vague)
Machine learning project

  • Used Python and ML to predict results

After (specific)
Placement prediction model | Python, pandas, scikit-learn | github link

  • Cleaned and combined three years of anonymised placement data (CGPA, branch, internships) provided by our department
  • Compared logistic regression and decision tree models; chose logistic regression for clearer explanations to faculty
  • Wrote a short report on which factors mattered most; presented it at our department's project day

Before (vague)
Testing project

  • Did testing of a website

After (specific)
Automated test suite for a demo shopping site | Java, Selenium, TestNG | github link

  • Wrote 35 automated UI tests covering login, cart and checkout, using the page object pattern
  • Added data-driven tests from a CSV file for 12 login scenarios, including invalid and boundary inputs
  • Integrated the suite with GitHub Actions so tests ran on every push

Use numbers only when they're true

Numbers make bullets concrete, but never invent them. Good, honest numbers for fresher projects include:

  • How many features, tests, pages or API endpoints you built
  • How many people used or tested it ("tested by 20 classmates")
  • A before-and-after you actually measured ("page load went from about 4 seconds to under 1 second on my laptop after adding pagination")

If you don't have a number, describe the specific thing you did instead. "Added input validation and error messages for all forms" is better than a made-up percentage.

Strong verbs to start bullets

Built, designed, implemented, automated, integrated, deployed, optimised, tested, debugged, migrated, analysed, documented, presented.

Avoid weak openers like "worked on", "involved in", "helped with" or "responsible for". They hide what you actually did.

Group projects: be clear about your part

Most college projects are group work. That's fine, but say what you did:

"Built the REST API and database layer (team of four); others handled the Android app and UI design."

Interviewers will ask, and a clear answer shows honesty and self-awareness. Claiming the whole project and then being unable to explain the parts you didn't build is a common way to lose an interview.

Which projects to include

Choose two or three that:

  1. Match your target role (backend projects for backend roles, automation projects for QA roles)
  2. You understand completely and can explain line by line
  3. Show something beyond a tutorial: a feature you designed, a bug you fixed, a deployment, real users

A final-year project, a hackathon project and one personal project is a strong combination. Put the most relevant one first. The fresher resume format guide shows where projects sit on the page.

Recruiters and interviewers sometimes open your GitHub. Make sure:

  • The repository has a README: what it does, screenshots if visual, how to run it, what you'd improve
  • The code is your own and reasonably organised
  • There are no passwords, API keys or personal data committed
  • The repository is pinned on your GitHub profile

Prepare to talk about every project

Every project on your resume is an interview topic. For each one, prepare short answers to:

  • Why did you build it, and who was it for?
  • What was the hardest problem, and how did you solve it?
  • Why did you choose this technology?
  • What would you do differently now?
  • What exactly did you build, if it was a team project?

These answers also make great material for answering "tell me about yourself".

Frequently asked questions

Can I include tutorial or course projects?

Yes, if you extended them meaningfully and can explain them. Add what you changed or built beyond the tutorial; recruiters recognise common tutorial projects.

How many projects should a fresher list?

Two or three well-described projects are better than six one-line ones.

Should I include projects in a different field from the job?

Only if they show transferable skills, such as programming, data handling or problem-solving. Put the most relevant projects first.

Is it okay to include an incomplete project?

You can, if it has working parts worth showing and you're honest about its status. Say what works and what you're building next.