OS and CN Rapid-Fire Viva round·Engineering·Medium·20 min

TCS Digital Interview — OS and CN Rapid-Fire Viva

20 min · 1 credit · scorecard at the end
Z
ZeroPitch Research Desk
Updated 2026-06-09 · Newly added · be among the first to take it
Field
Engineering
Company
Tata Consultancy Services
Role
Digital Software Engineer Trainee
Duration
20 min
Difficulty
Medium
Completions
New
Updated
2026-06-09

What this round is about

  • Topic focus. Rapid-fire operating systems and computer networks fundamentals: process versus thread, deadlock, paging and virtual memory, the OSI and TCP IP layers, TCP versus UDP, the three-way handshake, and what happens when you type a URL.
  • Conversation dynamic. The interviewer fires short questions, expects a crisp thirty to sixty second answer with one concrete example, and drills one or two topics deeper such as walking through a page fault step by step.
  • What gets tested. Whether you genuinely understand the mechanism behind a concept or only memorised its definition, and whether you can stay precise and well paced under quick questioning.
  • Round format. A single twenty minute technical viva calibrated to the TCS Digital fresher track, with a competency tracker and a shared whiteboard for the handshake and layer diagrams.

What strong answers look like

  • Definition plus example. You give a one line precise definition then immediately ground it, for example a browser is a process and its open tabs are threads sharing its memory.
  • Named conditions in order. For deadlock you name mutual exclusion, hold and wait, no preemption and circular wait, and add that breaking any one prevents deadlock.
  • Mechanism on demand. When asked to go deeper you walk the steps, for a page fault the access traps to the OS, the OS finds the page on disk, loads it into a free frame, updates the page table, and restarts the instruction.
  • Sequenced networking. For what happens when you type a URL you order it cleanly: DNS resolves the name, TCP connects via the handshake, TLS secures it if HTTPS, then the HTTP request and render.

What weak answers look like (and how to avoid them)

  • Definition with no example. Reciting a textbook line and freezing on the follow-up. Have one concrete example ready for every core concept before you start.
  • Concept confusion under speed. Mixing up paging and segmentation, or naming streaming as a TCP use case. Slow down for one breath and anchor on the distinguishing property.
  • Bluffing a wrong answer. Inventing a confident wrong definition rather than admitting a gap. Say you are not sure and reason aloud instead, it scores higher.
  • Rambling past a minute. Burning two minutes on one question so breadth suffers. Lead with the answer, give one example, then stop and let the interviewer drill.

Pre-interview checklist (2 minutes before you start)

  • Recall your process versus thread example. Have one everyday picture ready, such as a browser and its tabs, for the opening question.
  • Identify the four deadlock conditions. Be able to name mutual exclusion, hold and wait, no preemption and circular wait without hesitation.
  • Have the page fault steps ready. Rehearse the trap, locate, load, update page table, restart sequence for the likely deeper drill.
  • Pull up the whiteboard. Be ready to sketch the three-way handshake arrows and the OSI layer stack as you talk.
  • Re-read the URL sequence. Fix the order DNS, TCP handshake, TLS, HTTP, render in your head so you can sequence it under pressure.
  • Think of one TCP and one UDP use case. Pair web or file transfer with TCP and video calls or DNS lookups with UDP.

How the AI behaves

  • Probes every definition. Asks for one concrete example or the underlying mechanism after each answer, never accepts the headline definition alone.
  • No mid-interview praise. Will not say great answer or tell you how you are doing, it acknowledges what you said and pushes on.
  • Pushes you to the board. For the handshake, the layer stack and the deadlock graph it directs you to sketch within the first couple of turns and references what you drew.
  • Interrupts on rambling. If you run long it gently asks you to compress, because pacing is part of what it is measuring.

Common traps in this type of round

  • Memorised list, no mechanism. Naming the four deadlock conditions but unable to give a real example of two threads taking locks in the wrong order.
  • Fragmentation mix-up. Saying paging causes external fragmentation when paging causes internal and segmentation causes external.
  • Wrong transport choice. Claiming TCP for real-time streaming, or being unable to justify why a video call tolerates UDP loss.
  • Layer count slip. Saying the OSI model has four layers or the TCP IP model has seven, or naming the layers out of order.
  • Naming parts, not the sequence. For the type-a-URL question, listing DNS, TCP and HTTP without ordering them or connecting them end to end.
  • Silent freeze. Going quiet on an unknown instead of reasoning aloud from first principles, which forfeits the partial credit the interviewer wants to give.

Interview framework

You will be scored on these 6 dimensions. The full rubric with definitions is below.

Concept Precision
How exactly you define each OS and CN concept, naming the distinguishing property rather than circling it with vague words.
22%
Example Grounding
Whether you back each definition with one concrete everyday example instead of stopping at the textbook line.
22%
Mechanism Walkthrough
On a deeper drill like a page fault, whether you can walk the actual steps in order, not just restate what it is.
18%
Networking Layer Reasoning
Whether you keep the OSI and TCP IP layers, the handshake order, and TCP versus UDP use cases straight under speed.
18%
Honesty Under Uncertainty
Whether you admit a gap and reason aloud rather than bluffing a confident wrong answer when you are unsure.
10%
Answer Pacing
Whether you lead with the answer and keep each response near a minute so the round can cover breadth.
10%

What we evaluate

Your final scorecard breaks down across these dimensions. The full rubric and tier criteria are revealed inside the interview itself.

  • OS Concept Precision20%
  • Concrete Example Grounding20%
  • Mechanism Walkthrough Under Drill18%
  • Networking Layer and Transport Reasoning18%
  • Honesty Under Uncertainty12%
  • Rapid-Fire Answer Pacing12%

Common questions

What does the TCS Digital OS and CN technical round actually test?
It tests whether you understand operating systems and computer networks fundamentals deeply enough to explain them quickly and back each one with a concrete example. The interviewer fires short questions across process versus thread, the four conditions for deadlock, paging versus segmentation, virtual memory and page faults, semaphore versus mutex, the OSI versus TCP IP layers, TCP versus UDP, the three-way handshake, and what happens when you type a URL. The signal is real understanding versus last-night cramming, so every definition gets a follow-up asking for an example or a mechanism.
How should I structure each answer in a rapid-fire round?
Lead with a one-line precise definition, then immediately give one concrete everyday example, then stop. Aim for thirty to sixty seconds per question. For a process versus thread question, define both in a sentence, then say a browser is a process and its tabs are threads sharing its memory. Resist the urge to recite every property you memorised, because the interviewer is covering many topics and rewards crisp pacing. If asked to go deeper, then expand into the mechanism step by step.
What are the most common mistakes candidates make in this round?
The biggest is reciting a textbook definition but freezing when asked for one concrete example. The second is confusing closely related concepts under speed, mixing up paging and segmentation, or naming a wrong use case for TCP versus UDP. The third is bluffing a confident wrong answer instead of admitting uncertainty. The fourth is rambling for two minutes on one question so the round cannot cover breadth. Each of these is exactly what the interviewer is listening for.
How is this AI interviewer different from a real TCS interviewer?
It behaves like a real senior panelist and stays in character throughout. It fires one question at a time, always asks at least one follow-up before moving on, and never offers mid-interview praise or tells you how you are doing. It pushes you to the whiteboard for visual questions like the three-way handshake and the OSI stack, and references what you actually drew. Unlike a nervous human panel it is perfectly consistent in pacing and never penalises your accent, only the substance of your reasoning.
How is scoring done in this practice round?
Your transcript is scored against fundamentals dimensions such as concept precision, example grounding, the mechanism walkthrough on a deeper drill, networking layer reasoning, honesty under uncertainty, and answer pacing. A live competency tracker ticks off the core concepts as you cover them. Afterwards you receive a scorecard that names the specific concept you could define but could not ground in an example, and the moment your pacing slipped, with concrete quotes from what you said.
What should I do in the first two minutes of the round?
Settle your nerves and listen for the framing, the interviewer will tell you it is rapid-fire and that examples matter. On the opening process versus thread question, give a crisp definition and one example rather than everything you know. Have your whiteboard ready because visual questions are coming. Remember it is fine to say you are not fully sure and then reason aloud, which the interviewer rates higher than a smooth fabrication. Set a mental clock of about a minute per answer.
How do I handle a question I genuinely do not know in a rapid-fire viva?
Say plainly that you are not certain, then reason aloud from what you do know rather than going silent or inventing a confident wrong answer. For example, if you blank on thrashing, you might reason that if memory is overcommitted the system would spend more time moving pages than running work. Honest reasoning from first principles is explicitly rated above bluffing, and it often gets you most of the way to the right answer while showing the interviewer how you think.
What does a strong answer to the three-way handshake question sound like?
A strong answer names the three steps in order and draws them: the client sends a SYN with an initial sequence number, the server replies with a SYN plus ACK, and the client sends a final ACK, after which the connection is established. The strongest answers add why it exists, to synchronise sequence numbers on both sides so lost segments can be detected and retransmitted, and contrast it with UDP which skips this because it is connectionless. Drawing the arrows between client and server while explaining is exactly what the interviewer wants.
Which operating systems topics are most likely to come up?
Process versus thread, the four conditions for deadlock and how it is handled by prevention, avoidance or detection, paging versus segmentation and the fragmentation each causes, virtual memory with a step-by-step page fault, thrashing, and semaphore versus mutex including ownership. The producer-consumer and dining-philosophers problems can appear as synchronization examples. The page fault walkthrough is a very common deeper drill, so be ready to go from the definition into the mechanism.
Which computer networks topics should I prioritise?
The OSI versus TCP IP layer models and what each layer does, TCP versus UDP and when you would use each with a real example, the three-way handshake, what happens end to end when you type a URL and press enter, DNS resolution, HTTP versus HTTPS and the role of TLS, IP versus MAC address, switch versus router, and subnetting basics. The what-happens-when-you-type-a-URL question is a favourite because it lets the interviewer see whether you can sequence DNS, TCP, TLS and HTTP together rather than naming them in isolation.

Sources this interview is built on

Real candidate-report URLs (Glassdoor / AmbitionBox / PrepInsta / GeeksforGeeks / Medium) reviewed when authoring the questions, persona, and rubric. Verify the realism yourself.