How long should I talk about my project?

Start with about 90 seconds, then answer questions. If they ask for more detail, go deeper on the part they ask about, not on everything.

What if my project was a group project and I did a small part?

Say exactly what your part was and explain it well. A clear, honest small part beats a vague claim to the whole thing.

Should I bring my project report or a demo?

Bring a one-page summary or a few screenshots on your phone in case they ask. Don't start a demo unless they invite it.

What if the interviewer asks about something in the project I don't understand?

Admit it, then show how you'd find out. If a teammate handled that part, say so and describe how it connected to your work.

Can I talk about a mini project or internship project instead?

Yes, if it is stronger or more relevant to the role. Just be ready to explain why your final year project isn't the one you chose.

Tell me about your final year project: how to answer

Why campus interviewers love this question

For a fresher, the final year project is usually the biggest piece of real work on the CV. It is the closest thing to a job: a problem, a deadline, a team, choices you had to defend. Interviewers use it to check three things:

Do you understand what you built, or did you follow a tutorial or a senior's code?
Can you explain technical work clearly to someone who wasn't there?
Can you judge your own work, including what went wrong?

The project discussion can easily run longer than any single theory question in a technical round. Prepare it like an exam topic.

The five-part answer

Part	What to say	Example line
1. Problem	What it solved and for whom, in plain words	"Our college library had no way to tell students which seats were free."
2. Your part	What you personally owned in the team	"There were four of us. I built the sensor code and the backend."
3. How	The main approach and two or three key tools	"We used ultrasonic sensors on an ESP32, sending readings to a small Flask server."
4. Result	What worked, with a number if real	"It ran on 40 seats for two weeks with about 95 percent correct readings in our own checks."
5. Hindsight	One thing you'd change and why	"I'd use pressure mats. Ultrasonic sensors got confused by bags on chairs."

Spoken at a steady pace, that is about 90 seconds. Stop there and let them choose where to go deeper. A five-minute monologue gives them less control and you less chance to show you can handle questions.

Example answers

These use made-up projects. Replace them with your own details.

Computer science: attendance with face recognition

"My project was an attendance system using face recognition, for classes where roll call takes ten minutes. We were a team of three. I owned the recognition model and the accuracy testing. We used a pre-trained face embedding model and compared embeddings against a database of enrolled students. In tests on 60 students it matched correctly about nine times in ten in good light, but much worse in our dim lab. If I did it again, I'd collect training photos in the actual classroom lighting from day one, because that's where most of our errors came from."

Mechanical: solar food dryer

"We designed a low-cost solar dryer for small farmers drying chillies. My part was the airflow design and the temperature testing. We built a prototype from plywood and polycarbonate sheets with a small fan powered by a solar panel. It dried a batch in about two days instead of four in open sun, in our trials. What I'd change: we never tested in the monsoon season, which is exactly when farmers need it most."

Commerce or management: a market study

"I studied why small grocery shops in my town were losing customers to quick-delivery apps. I designed the survey, interviewed 25 shop owners and ran the analysis in Excel. The main finding was that delivery time mattered less than shoppers thought; credit and personal trust kept regulars loyal. Looking back, my sample was all from one area, so I'd widen it before drawing conclusions."

Prepare for the technical follow-ups

The follow-ups are the real test. Interviewers often pick the detail you mentioned quickest and ask why.

Likely follow-up	What they're checking	How to prepare
"Why did you choose X over Y?"	That decisions were reasoned	For each tool, know one alternative and why you didn't use it
"How does X work internally?"	Real understanding	Revise the theory behind your main algorithm, circuit or method
"What was the hardest bug or problem?"	Problem solving	Have one real story ready with the fix
"How did you test it?"	Rigour	Know your test setup, data size and how you measured results
"What exactly did you do versus the team?"	Honesty	Be precise; never claim a teammate's part
"How would you scale it?"	Thinking beyond the project	Think through 10 times the users, data or load
"What would you do differently?"	Self-awareness	Have one technical and one process change

If you don't know an answer, say so and reason out loud: "I didn't look into that. My guess would be..." That is far better than bluffing. Interviewers can usually tell. See how to answer a question you don't know and how to think out loud in a technical interview.

When the project didn't work

Plenty of final year projects half work. That is fine to admit. Interviewers often find failed projects more revealing than polished ones, if you can explain why it failed and what you learned. Say clearly what worked, what didn't, and what you'd change. Don't hide it, and don't spend the whole answer apologising.

"I" versus "we"

Use "we" for the team's decisions and "I" for your own work. A whole answer in "we" makes interviewers wonder what you did. A whole answer in "I" for a four-person project sounds like you are taking credit. The five-part structure handles this: part 2 states your role, so the rest is easy to follow.

How to rehearse it

Write the five parts as five bullet points, not a script.
Say the 90-second version out loud three times, timing it.
List ten follow-up questions a sceptical lecturer would ask. Answer each out loud.
Explain the project to a friend outside your branch. If they get lost, simplify part 1.
Do one run with someone who interrupts you with "why?"

Speaking Coach can play a technical interviewer: tell it about your project and it asks follow-ups on what you actually said, then shows you where you rushed or used fillers. For the wider round, see the campus placement interview guide.