What exactly was your role in your final-year project?
Name the part you personally owned, the decisions you made, a problem you solved and the result, using "I" for your work and "we" for the team's. Be ready to go two levels deeper on anything you mention.
Explain it simply
Most final-year projects are done in groups of three or four, so the interviewer wants to separate your contribution from the team's. If you say "we" for everything, it sounds like you watched while others worked.
Give a one-line summary of the project, then clearly say which module you built, which tools you used, and one difficulty you personally solved. Be honest: if a teammate built the machine learning model, say so. Overclaiming is easy to catch with two follow-up questions.
Example
Situation: Sneha's team of four built a canteen pre-order app for their college.
Task: Explain her personal role clearly in a managerial round.
Action: She says: "The app lets students order food before the break so they skip the queue. My part was the backend: I designed the MySQL tables for orders and menu, wrote the REST APIs in Node.js, and handled the case where two people order the last item at once by locking the stock row. My teammates built the Android front end and the admin panel."
Result: The interviewer asks about the stock-locking problem, Sneha explains it confidently, and it becomes the strongest part of her interview.
What to say in the interview
"It was a four-person project. I owned the backend: the database design and APIs. The hardest problem I solved was..."
Common mistakes
- Saying "we did everything together" with no clear ownership.
- Claiming parts you cannot explain under questioning.
- Spending all your time on what the project does rather than what you did.