How to Write the Projects Section of Your Resume

Write each project as what you built, the tools you used and what came out of it. Every good entry for projects in resume for freshers follows that pattern, and it holds for engineering, commerce and statistics students alike.

Key takeaways

  • Write each project as what you built, the tools you used and what came out of it.
  • Two to four strong projects close to the job beat eight thin ones.
  • Give each project a title line with tools and date, then two to four bullets that start with a past-tense action word.
  • A result can be accuracy, time saved, a grade, a prize or a clear finding, not only a big number.
  • Link GitHub, dashboards or reports only when they are tidy, and show links as visible text so they survive printing.

This section carries more weight for you than for someone with five years of work behind them, because you probably have no job to describe yet. A well-written project is the nearest thing you have to proof that you can do the work. It also hands the interviewer something specific to ask about.

Choosing projects in resume for freshers

Choose the projects closest to the job in front of you. For a data analyst role, that means analysis work; for finance, something with numbers, statements or Excel models; for a core mechanical role, design or manufacturing.

Places to look:

  • Final year and mini projects from your course
  • Academic projects from lab work or term papers, if they produced something real
  • Personal projects you built on your own time
  • Hackathon or competition entries
  • Freelance or volunteer work for a local business, a college club or an NGO

Two to four strong projects beat eight thin ones. A weekend project that taught you one function belongs in your skills section instead. Starting with almost nothing on the page? Our guide to a resume with no experience shows how to fill those gaps honestly.

The formula: what you built, tools, result

Give every project a title line and two to four bullets.

Title line: project name, your role if it was a team, the tools in brief, and the month and year. Example: "Sales Dashboard for a Kirana Chain | Excel, Power BI | Mar 2026".

Bullets: open each with a past-tense action word (built, analysed, designed, tested, cleaned, modelled), then say what you did, with which tool, and what happened.

Results needn't be big numbers. Accuracy on test data counts, and so do time saved, a grade, a prize, something a real person used or a clear finding. "Found that weekend sales were driven by two product categories" is a result. "Learnt a lot about Python" isn't.

Compare these two lines about the same piece of work:

Weak: Did a project on student performance using machine learning.

Better: Built a model in Python (pandas, scikit-learn) to predict which first-year students were likely to fail a subject, using three semesters of anonymised internal marks; it flagged 18 of the 22 students who later failed in the test data.

From the second line a recruiter learns the tools, the data, what you built and how well it worked. The numbers in these examples are made up for illustration; use your own, and only ones you can explain.

How to write projects in resume: three sample entries

The students and projects below are fictional. Borrow the shape, not the words.

A data project

A BSc Statistics student in Thrissur, applying for junior data analyst roles:

Air Quality Trends in Pune, 2021 to 2025 | Python, pandas, Matplotlib | Jan 2026

  • Cleaned five years of daily air quality readings from public government data, handling missing days and duplicate station entries.
  • Analysed seasonal patterns and found that the worst months were consistent across all monitoring stations in the city.
  • Published charts and a short written summary as a notebook on GitHub: github.com/ananya-k-example/pune-aqi

Look at what the bullets cover: where the data came from, what was messy about it and what the student found. A data interviewer will poke at exactly those.

A commerce or finance project

A BCom student in Delhi, applying for finance and accounts trainee roles:

Ratio Analysis of Two Listed FMCG Companies | Excel | Oct 2025

  • Pulled five years of annual report figures for two listed FMCG companies into an Excel model with linked sheets for income statement, balance sheet and ratios.
  • Calculated liquidity, profitability and efficiency ratios and compared trends, with a one-page written conclusion on which company managed working capital better.
  • Presented findings to the department as part of the Financial Management course; scored 18 out of 20.

No code, and that's fine. Excel is the tool, ratio analysis the method, and the result is a conclusion plus a grade.

An engineering project

A mechanical engineering student in Vijayawada, applying for design and production trainee roles:

Low-cost Solar Dryer for Chillies | Team of 4, CAD lead | SolidWorks, AutoCAD | Apr 2026

  • Designed the dryer frame and air flow path in SolidWorks and produced manufacturing drawings in AutoCAD.
  • Built a working prototype with the team using locally available sheet metal for under ₹6,000 (example figure).
  • Tested it at a farm near Guntur over two weeks; drying time came down compared with open sun drying, measured by daily moisture checks.

"CAD lead" tells the reader what this student did inside a team of four. Leave it out and the interviewer has to guess.

With a link, the recruiter sees the work instead of taking your word for it. Add one where it genuinely helps.

GitHub: put the repository link on the project's title line or in the last bullet. First, open the repository and ask yourself three questions. Is there a README that explains what the project does and how to run it? Is the code tidy enough that you'd be fine with someone reading it? Have you removed any passwords, API keys or personal data? A repository with a single file called "final.py" and no README is worse than no link.

Dashboards: for something built in Power BI, Tableau or Looker Studio, publish a public view and link to it, as long as the tool allows it and the data isn't private. If not, save two or three screenshots into a short PDF on Google Drive, set sharing to "anyone with the link can view", and link to that.

Reports and models: for finance or research projects, a Google Drive link to the PDF report or the Excel file works. Name the file clearly.

Show links as visible text, such as github.com/yourname/project, never hidden behind a word like "here": resumes get printed, and a hidden link vanishes on paper. Keep them short. When an address is long and messy, put just your GitHub profile in the header and name the repository in the bullet.

Mistakes that weaken a projects section

Writing a project as a topic rather than a piece of work is the commonest. "IoT-based smart irrigation system" gives the reader the title of your report and says nothing about what you did.

Pasting in the abstract from your project report is nearly as bad. Abstracts are written for examiners and stuffed with background, while recruiters want your actions.

Don't list tools you didn't use. If the project ran on Excel, adding Python because it looks better just means you'll be asked about Python.

And put the dates in. A recruiter wants to know whether this was last semester or three years ago.

Where this section sits on the page, and how it fits with the rest, is covered in our complete guide to writing a fresher resume in India.

Tonight, take your strongest project, rewrite it as built, tools, result, and drop it into one of our CV templates to see how it reads on the page.

Frequently asked questions

How many projects should a fresher put on a resume?

Two to four is enough for most freshers. Pick the ones closest to the job you are applying for and give each one proper bullets, rather than listing eight projects in one line each.

Can I include a project I did by following a YouTube tutorial?

Only if you changed it meaningfully, for example by using a different dataset, adding a feature or fixing something the tutorial skipped. Then describe your changes. A straight copy is easy to spot in an interview.

Should the projects section come before education?

For most freshers, education comes first, then projects. If your projects are much stronger than your marks and closely match the role, you can move projects above education.

What if my project was a group project?

Include it, say it was a team of four or five, and write the bullets about the part you did yourself. Interviewers will ask what you personally built, so be ready to explain it.