Final-year Project Viva

In an Indian engineering college, every lab course ends in a practical examination where the student performs one experiment or writes one program and then faces a viva voce from an internal examiner and, in the end-semester university exam, an external examiner appointed by the university. The viva typically lasts five to fifteen minutes per student, and the examiner opens the lab record or the just-completed experiment and asks the student to explain the setup, the readings, the theory behind them and what would change if a condition changed. The final-year project viva is longer: a panel of the guide, an internal examiner and an external examiner, often from industry, hears a presentation and demo and then questions each team member on the problem, design choices, their own module and the results. Marks for the viva are set by the university scheme and usually form a part of the practical or project marks, with the exact split varying by university. The ExamPilot mock compresses this into a twelve-minute viva with one examiner who opens your record, probes one subject in depth, tests what-if reasoning on a scenario from the lab or project, and closes without revealing marks.

1. 1

   Problem statement

   State your project problem in two sentences, and tell me what is new compared with the best existing solution in your literature survey.

   What a strong answer covers

   A crisp statement of who has the problem and what your system does, followed by one specific difference from a named existing approach, such as lower cost, better accuracy or a new use case. Avoid reading the abstract or claiming nothing similar exists.

2. 2

   Individual contribution

   Your team has four members. Which module did you personally build, and walk me through how it works internally?

   What a strong answer covers

   Names the module, explains inputs, processing and outputs, and the key design decision in it, with enough detail that only its author could give. Avoid describing the whole system while avoiding your own part.

3. 3

   Design choices

   You used a Raspberry Pi and a CNN model. What alternative hardware or model did you consider, and why did you reject it?

   What a strong answer covers

   Names a realistic alternative such as an Arduino, a Jetson board or a simpler model, and compares cost, power, accuracy and availability. Avoid answers suggesting the choice was simply what a senior or tutorial used.

4. 4

   Validation

   Your report claims ninety-two percent accuracy. On what data, how was it split, and did you test it on anything outside that dataset?

   What a strong answer covers

   Explains the dataset source and size, the train, validation and test split, the metric used, and any real-world testing, with honesty if results dropped outside the dataset. Avoid claims that cannot be reproduced in the demo.

5. 5

   Limitations

   What is the biggest limitation of your project that a real user would discover in the first week?

   What a strong answer covers

   A concrete limitation such as poor lighting performance, battery life, network dependency or maintenance needs, and a realistic way to address it. Avoid saying there are no limitations.

6. 6

   Scalability

   If a hospital or a municipal body wanted to use your system at a hundred sites, what would break first?

   What a strong answer covers

   Considers what changes at scale: server load and data storage, hardware cost per site, installation and calibration, network reliability and who maintains it, with one practical mitigation for the first bottleneck. Avoid assuming the lab prototype works unchanged at a hundred sites.

7. 7

   Debugging

   Tell me about the hardest bug or hardware failure you faced, and exactly how you found the cause.

   What a strong answer covers

   A specific problem, the debugging steps such as logging, isolating modules or measuring signals, the root cause and the fix. Avoid vague answers like we faced many issues but solved them.

8. 8

   Safety and cost

   For a mechanical or civil project, what safety factor did you use, and how did you estimate the cost of a full-scale version?

   What a strong answer covers

   States the factor of safety and why it suits the loads and material, and gives a rough cost estimate with main components. Avoid unrealistic cost figures or ignoring safety standards.

9. 9

   Future work

   If you had six more months and a small budget, what single improvement would you make, and how would you measure that it worked?

   What a strong answer covers

   One focused improvement tied to the project's main limitation, a realistic plan within the budget, and a clear test or metric that would show it worked, such as accuracy in poor lighting or battery life. Avoid listing many vague future features.

• English
• Hinglish (Hindi + English)Hinglish