At Indian product companies, a strong GitHub portfolio with 2-3 real, deployed side projects can compensate for a low CGPA, a tier-2 college, or a gap year. Conversely, a candidate from a tier-1 college with a strong CGPA but no real projects beyond the standard curriculum often struggles to differentiate in product company interviews. This guide covers exactly what makes a side project compelling to Indian hiring managers and how to build, document, and present your portfolio.
The most common mistakebuilding yet another to-do list app or CRUD API and expecting it to differentiate. A project impresses a hiring manager when it demonstrates: (1) A real problem worth solving. Not a tutorial problem, not a contrived example: something that would actually be useful. (2) Non-trivial technical decisions. The README should explain why you chose Postgres over MongoDB, why you used a queue for background tasks, why you implemented caching. These decisions show engineering judgment, not just coding ability. (3) Deployment and production readiness. A project that is live (even on a free tier: Vercel, Railway, Render) demonstrates that you understand more than just local development. (4) A specific technical challenge you solved. 'I implemented OAuth 2.0 from scratch to understand the flow' or 'I used Redis pub/sub for real-time updates because WebSockets alone don't scale horizontally': these are the kinds of statements that get attention. (5) User activity or measurable impact. Even 10 real users using your app is more impressive than a polished demo with zero users. The bar is not high: most competing candidates have no projects at all. Two solid projects beat ten mediocre ones.
Projects that have demonstrated consistent interview impact for Indian candidates: (1) A tool that solves an Indian-specific problem. A UPI payment splitter for group expenses, a IRCTC train availability aggregator with notifications, a JEE past-paper analyser with AI. Using your domain knowledge of India-specific problems is a differentiator. (2) An AI-powered tool (since 2024).
Any project using the OpenAI API, Anthropic Claude API, or an open-source LLM: a resume analyser, a code review bot, an interview preparation tool. Shows you understand the current tech landscape. (3) A real-time collaboration feature. Implementing WebSockets or SSE (Server-Sent Events) for live updates (a collaborative document, a live leaderboard, a real-time dashboard) demonstrates understanding of async systems.
(4) A data engineering pipeline. An ETL pipeline that scrapes, transforms, and stores structured data from a public API, with a dashboard. Shows data engineering and full-stack skills simultaneously. (5) An open-source contribution.
A merged pull request to a notable open-source project (React, Django, FastAPI, a popular npm package) is equivalent to a strong side project and demonstrates real collaboration skills. Avoid: projects that are identical to tutorial projects (the 'Netflix clone' that every bootcamp assigns), projects with no README or documentation, projects that only run locally, and projects using only languages/frameworks not relevant to your target role.
- A great project with a poor README gets ignored.
- Every portfolio project needs. a README with: (1) What it does (1-2 sentences, non-technical). (2) Why you built it (the problem it solves). (3) Architecture overview (with a diagram if possible). (4) Key technical decisions and trade-offs. (5) How to run it locally or link to the live demo. (6) What you learned or would do differently.
- GitHub profile optimisation. pin your 3-4 best repositories. Add a profile README (a README.md in a repo matching your username) introducing yourself and linking to projects and LinkedIn.
- Keep commit history clean. squash WIP commits before making a repo public. How to talk about projects in interviews: prepare a 2-minute verbal walkthrough for each project: 'I built [project name] to solve [problem]. The stack is [tech]. The interesting part was [specific challenge]: I solved it by [approach]. If I were to do it again I would [improvement].' This structure takes the interviewer through the project efficiently and naturally leads to follow-up questions you have already prepared for.