For most students the final year project is the first real piece of engineering they own from start to finish. It also tends to be the project an interviewer actually asks about, because it is the one where you made the decisions. Do it well and it becomes your best interview story; do it as a formality and it is three months you never want to explain.

How to choose a topic

A good final-year topic is not the most ambitious one — it is the one you can actually finish and defend. Filter ideas with these questions:

1. Is it clearly scoped? "An app that helps X do Y" beats "an AI platform for everything". Small and finished beats big and abandoned.
2. Can you build a working version with the time, tools and skills your team has?
3. Does it connect to your branch? The examiner and the interviewer both want to see branch-relevant work.
4. Can you explain the problem it solves, in one sentence, to a non-expert?
5. Do you have a way to show results? A demo, a measurement, a comparison — something concrete at the end.

Where to find ideas

• Problems around you. The best projects often solve something small and real — a lab process, a local business, a campus problem.
• Recent previous-year projects, for the format and scale expected — then do something different, not the same.
• Industry pain points in your branch — maintenance, quality, energy, records, automation.
• New tools applied to an old problem — a mobile app, a sensor, a simple analysis.

Plan it backwards from the deadline

Stage	What to lock down
Topic & scope	Problem statement, objectives, what "done" looks like.
Design	Block diagram, method, tools, and who is doing what.
Build	A working core, even if the extras slip.
Test & measure	Evidence that it works — results you can show.
Report & viva	Documentation and rehearsal finished before the scramble.

Build the core first. A working minimum project with clean documentation scores better than a half-finished grand idea.

The report

Follow your department's format, but expect to cover:

• Abstract & introduction — the problem and why it matters.
• Literature / existing work — what already exists and what gap you address.
• Methodology & design — diagrams, tools, and the choices you made.
• Implementation / working — how it is built or performed.
• Results & discussion — evidence, measurements, and what they mean.
• Conclusion & future scope — honest limits and what you would do next.
• References — cited properly.

The viva: expect these questions

• "Why did you choose this problem?"
• "Why this method or tool, not another?"
• "What did you personally do?" — be ready to split the work honestly.
• "What are its limitations?" — a realistic answer earns respect.
• "What would you improve next?"

Rehearse a two-minute walkthrough of the whole project. If you can explain it simply and defend the choices, the viva becomes a conversation rather than an interrogation.

Browse Your Branch Subjects