Projects Recruiters Actually Open: A Portfolio Plan by Role for Indian Freshers

Why most fresher portfolios get skipped

A recruiter has about a minute for your GitHub. If they see a calculator, a to do app and a weather app copied from a tutorial, they close the tab. Not because those projects are bad, but because they say nothing about you. The fix is simple: build fewer projects, closer to the job, and explain them well.

The rule for every project

• It solves a problem someone actually has
• It is deployed or runnable in one command
• The README answers: what, why, how, and what you would change
• You can explain every file in an interview

Full stack developer

1. A booking system for a real local business (a salon, a tuition centre, a turf). Login, slots, admin view, payment test mode. This shows authentication, databases and real flows.
2. A college notice board or placement tracker with role based access for students and coordinators.
3. A performance fix. Take one of your projects, measure page load, improve it, and write down the before and after numbers.

Data analyst

1. A dashboard on public Indian data (rainfall, crop prices, state budgets) with three clear insights written in plain English.
2. A SQL case study. Ten business questions answered from one dataset, with the queries.
3. A cleaning notebook that turns a messy CSV into a usable table, with every step explained.

AI and machine learning

1. A small model on a real problem, with a baseline, an honest error analysis and what failed.
2. A retrieval based chatbot over a document set you care about, such as your university's rule book, with notes on where it gives wrong answers.
3. An evaluation script that tests your own chatbot on 30 questions and reports accuracy.

Cloud and DevOps

1. Deploy one app three ways: a VM, a container, and a managed service. Compare cost and effort.
2. A CI pipeline that runs tests and deploys on every push.
3. A monitoring setup with alerts, and a short note on what you would watch in production.

Software testing

1. A test plan and bug report set for a public website, written the way a QA team would.
2. An automated test suite for one of your own projects.

How long this takes

Plan for two to three months of steady work for two good projects, alongside college. That is normal. The students who get hired are usually not the ones who started earliest, but the ones who finished something real.

Getting feedback

Ask a senior, a mentor or a working engineer to review one project. If you want structured feedback, the internship month in Ucanly's PTIP programme is built around live project work with mentor reviews. But a good portfolio does not require paying anyone. It requires finishing.