From college project to portfolio piece: a Final Year B.Tech guide

Every year, a few thousand engineering students reach out to us in the last six weeks before their final-year project deadline. Most of them are stuck. A few of them — the ones we'd hire today — picked the right project, scoped it well, and treated it as more than a viva-pass. This guide is for the second group, or for whoever wants to join them.

1. The two-axis test for picking a topic

When you're choosing a topic, score every candidate on two axes:

• Defensibility at viva: can you explain every part to a panel of professors who'll try to trip you up?
• Resume value: does this look impressive on a CV to a recruiter who's never met you?

Most students optimise only for the first axis and pick safe, boring topics ("Library Management System"). A few optimise only for the second and pick "AI-powered Crypto Trading Agent" with no real understanding — they fail viva. The sweet spot is in the upper-right quadrant: something defensibly buildable in 3 months that also catches a recruiter's eye.

2. Topics that score well on both

From hundreds of projects we've helped ship — these are the ones whose students consistently land interviews:

• RAG-based Q&A app over a specific real-world corpus (your college's exam papers, a public dataset of medical research, etc.)
• Computer vision project with a real-world dataset and meaningful baseline comparison
• Mobile/web app that solves a specific local problem (campus food ordering, hostel maintenance tickets) with real-user testing
• Full-stack analytics dashboard ingesting a real public API (weather, COVID, sports stats) with derived insights
• AI agent that automates a tedious task end-to-end (e.g. classifying support emails, summarising YouTube videos with chapter markers)

3. Scope it like a sprint, not a semester

The single biggest failure mode is scoping for the full 6 months of project work. You won't have that — you have classes, placements, and life. Scope for 6 weeks of focused work, leaving room for documentation and iteration. The best projects we've seen were started seriously around the start of the second-to-last semester.

4. Build it like a portfolio piece from day one

• Put it on your personal GitHub from commit one (not your college repo)
• Write the README as if a recruiter will read it — problem, approach, screenshots, demo link
• Deploy it. A live demo URL is worth more than 20 pages of report
• Record a 90-second Loom of the project working. Embed in your resume
• Write a short blog post on Hashnode/Medium about what you learned. Link it on LinkedIn

5. The viva panel actually cares about three things

1. 1

   "Do you understand what you built?"

   Be ready to walk through any function in the codebase

2. 2

   "Why this approach over alternatives?"

   Have a one-line answer for every major architectural choice

3. 3

   "What are the limitations?"

   Stating limitations honestly impresses panels more than overclaiming

6. The honest answer to "can someone build it for me?"

Some students reach out to us asking exactly this. Our answer is the same every time: we'll build it with you, not for you. You get the code, the documentation and a 1:1 walkthrough so you can defend every line of it. That's the only way the work creates real value for you — at viva and three months later in an interview.

If you're weighing topics or stuck mid-build, drop us a line. We respond on WhatsApp in usually under an hour.

Frequently asked questions