Viva Voce & Oral ExamsEngineering VivaLive

CS / IT Lab Viva

Students of Computer Science, IT, AI-ML, Data Science and allied branches, as well as BCA and MCA students, sitting the internal or end-semester practical examination of a programming or systems lab, where a program is written and executed and then a viva voce follows.

B.Tech / BE / B.Sc / BCA / MCA students, any semester 4 rounds · ≈ 10 min 9 subjects 2 languages 2-member panel or 1:1
2 AI interviewers · hand over between rounds

From our research

What this interview looks like

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.

How it is weighted

Viva marks are a component of the practical examination marks under each university's scheme, alongside the lab record and the program executed in the exam; the exact split varies by university and the viva often decides who gets full practical marks.

Who this is for

Students of Computer Science, IT, AI-ML, Data Science and allied branches, as well as BCA and MCA students, sitting the internal or end-semester practical examination of a programming or systems lab, where a program is written and executed and then a viva voce follows.

The panel focuses on

  • Explaining the program you just wrote line by line, including the one line you copied without understanding
  • Why behind the output: complexity, memory, what happens on an edge case or a wrong input
  • Concepts behind the lab: normalisation, scheduling, sockets, OOP pillars, train-test split, asked as examples not definitions
  • What-if changes: remove a semaphore, drop an index, change the input size, swap the algorithm
  • Reading an error, a traceback or a wrong output and saying what you would check first
  • Honesty about what you did not understand in the lab record

Step 1

Pick your subject

The expert on the panel probes these areas at the level of this post. Optional here; you can choose during setup.

Step 2

Choose how you want to be interviewed

What to expect

4 rounds · 10 minutes

A ten-minute oral examination of the kind held at the end of a laboratory course or project: school board practicals, engineering lab and project vivas, pharmacy and nursing practicals, dissertation and thesis defences. One external examiner, sometimes seated with the internal teacher, asks the candidate what they did, why it works, what they observed and what could go wrong, then looks at the record file or project and asks one question that tests whether the work is the candidate's own. The examiner escalates when answers are correct, gives one hint when the candidate is stuck, and never teaches during the viva.

  1. Round 1

    Introduction

    · 1:00

    Settle the candidate and establish exactly which experiment, practical, project or thesis the viva will be about, so that the subject questions can be anchored to work the candidate actually did.

    Prof. Raghunath Kulkarni
    1–2 questionsup to 1 follow-up each
  2. Round 2

    Viva on concepts and experiments

    · 7:00

    Test whether the candidate understands the principle behind the experiment or project they did, can describe the procedure and observations accurately, knows the precautions and sources of error, and can reason about a change in conditions. Separate genuine understanding from a memorised record file.

    Prof. Raghunath Kulkarni
    4–6 questionsup to 2 follow-ups each
  3. Round 3

    Record file or project

    · 1:00

    Check that the record file, activity or project is the candidate's own work and that they understand it: why they chose it, what the data or result was, what went wrong and what they would improve.

    Prof. Raghunath Kulkarni
    1–1 questionsup to 1 follow-up each
  4. Round 4

    Closing

    · 1:00

    End the viva courteously and formally, as an external examiner does, without feedback, marks or any hint about the result.

    Prof. Raghunath Kulkarni
    1–1 questions

Sample questions

Engineering Viva CS/IT labs interview questions

Questions panels commonly ask in the Engineering Viva CS/IT labs interview, with what a strong answer covers. Practise them aloud with the AI panel.

  1. Data structures

    You wrote a program to reverse a singly linked list. Tell me what each pointer holds after the second iteration, and how your code behaves when head is null.

    What a strong answer covers

    Traces previous, current and next pointers step by step, shows the head finally points to the old tail, and explains that an empty or single-node list is returned unchanged without a null dereference. Avoid reading the code aloud without tracing actual values.

  2. DBMS

    Your table has student ID, name, course ID and course name in one table. Is it in third normal form? If not, fix it.

    What a strong answer covers

    Identifies the transitive dependency of course name on course ID, splits it into student, course and enrolment tables with proper keys, and explains the update anomaly the split removes. Avoid reciting the definitions of normal forms without applying them to this table.

  3. Operating systems

    In your producer-consumer program, what goes wrong if I remove the mutex but keep both semaphores?

    What a strong answer covers

    Explains that the semaphores still count empty and full slots, but two producers or consumers can access the buffer index simultaneously, causing a race condition and lost or overwritten items. A strong answer gives a concrete interleaving. Avoid saying the program will simply deadlock.

  4. Computer networks

    Your socket program works on localhost but the client cannot connect from another lab machine. What would you check first?

    What a strong answer covers

    Checks whether the server binds to all interfaces rather than the loopback address, the correct IP and port, the firewall, and whether the server is listening, using tools such as ping or netstat. Avoid rewriting the code before checking network basics.

  5. Object-oriented programming

    Explain the difference between method overloading and overriding using a class from your Java record.

    What a strong answer covers

    Overloading means one class has methods sharing a name but differing in parameter lists, chosen by the compiler; overriding means a child class supplies its own version of an inherited method, chosen at runtime by the actual object. A strong answer points to real classes in the record. Avoid definitions with no example.

  6. Machine learning

    In your machine learning lab, why did you split the data into training and test sets, and what would happen if you tuned the model on the test set?

    What a strong answer covers

    The test set estimates performance on unseen data; tuning on it leaks information and gives an optimistic score, so a validation set or cross-validation should be used. Avoid saying the split is only a formality.

  7. Debugging

    Your Python program crashed with a KeyError during the lab exam. What does that error mean, and how would you prevent it?

    What a strong answer covers

    Explains that a dictionary key was accessed that does not exist, then mentions checking with in, using get with a default or handling the exception, and finding why the key was missing. Avoid suppressing all exceptions with a bare except.

  8. Algorithms

    What is the time complexity of the sorting algorithm you implemented, and what happens to it if the input is already sorted?

    What a strong answer covers

    States the average and worst-case complexity correctly for the chosen algorithm, and explains the effect of sorted input, for example quicksort with a poor pivot degrading to quadratic time while insertion sort becomes linear. Avoid stating complexity without reasoning.

  9. Web technology

    Your web page form submits data, but the server receives nothing. How would you debug it using the browser?

    What a strong answer covers

    Opens developer tools, checks the network request, method, URL and payload, inspects form field names and the server log, and looks for JavaScript errors. Avoid guessing at backend changes without inspecting the request.

Reading is not rehearsing. Answer these out loud to an AI Engineering Viva CS/IT labs panel that follows up like the real one.

Practise these questions

Meet the panel

Your AI interviewers

Distinct personas, voices and questioning styles, briefed on this post.

Prof. Raghunath Kulkarni

Chair

Subject expert

Professor and former Head of Department, government engineering college (Pune); external examiner for university lab and project vivas for 20 years

Unhurried, exacting, fair; wants the reasoning, not the recited definition.

Male voice · 4 languages

Ms. Deepika Venkatesan

Subject expert

Principal Engineer at a Bengaluru product company; industry external examiner for final-year project vivas and lab exams at VTU-affiliated and autonomous colleges

Brisk, practical, curious; judges whether it would actually work.

Female voice · 4 languages

Languages

Answer in the language you think in

The panel asks in your chosen language. Switch mid-answer if you like.

  • English
  • Hinglish (Hindi + English)Hinglish

How scoring works

A report you can act on

  1. Every round is scored on the rubric

    Each interviewer scores only the criteria their round covers. Weights add up to your overall score out of 100.

  2. Only what you actually said counts

    Feedback quotes your own answers. Rounds you skip show as “Not assessed” rather than a zero.

  3. Communication is always measured

    Fluency, clarity, confidence and structure are tracked across the whole interview, in any language.

  4. Pass mark, then a plan

    You see the pass mark for this interview, your gaps, and the courses that close them fastest.

Scored on

  • Conceptual understanding40%

    States the principle, law or formula behind the experiment or project correctly and in their own words; explains why the method works rather than only what the steps are; handles a why or what-if question with reasoning; does not confuse related concepts or recite a definition that does not answer the question.

  • Experimental procedure & observation30%

    Describes the actual procedure, apparatus or tools, readings or data and how they were processed; knows the units, the expected result and the order of magnitude they obtained; names sources of error and the precautions that address them; for a project, knows the data, method and limitations of their own work.

  • Clarity of explanation20%

    Answers the question actually asked in short, ordered sentences; uses correct technical terms and units; can explain the same idea more simply when asked; does not ramble or bury the answer in unrelated recall.

  • Confidence & honesty10%

    Speaks steadily, holds a correct answer when gently challenged, corrects themselves when shown an error, and says I am not sure rather than guessing; recovers after a hint instead of freezing.

Pass mark 50 / 100 · Practical / project viva voce with an external examiner

Keep exploring

Related interviews and courses

All Viva Voce & Oral Exams interviews

Free

Engineering Viva CS/IT labs