A GD is not a debate you win by being loudest. Here is what evaluators are marking, and how to be visible without being aggressive.
Quick answer
How do you perform well in a campus group discussion?
Enter within the first two minutes, open with a structure rather than an opinion, back each point with a fact or example, bring in quieter participants, and offer a summary near the end. Evaluators mark clarity of thought, structure, listening and group behaviour — not speaking time. Dominating the discussion is a common way to fail it.
Group discussions filter more candidates than most students expect, and they fail for a counter-intuitive reason: people prepare content and forget that the round is largely marking behaviour. Two candidates can make the same point and get opposite scores depending on how they entered, whether they listened, and what they did when interrupted.
This guide covers what is being marked, the topic categories that actually come up, and a practical way to structure your contributions.
| Criterion | What it looks like in the room |
|---|---|
| Clarity of thought | You make one clear point at a time instead of three tangled ones |
| Structure | You frame the topic before arguing inside it |
| Content depth | Facts, examples, second-order effects — not just opinion |
| Listening | You reference and build on what someone else said |
| Group behaviour | You bring people in, you do not talk over anyone |
| Language and composure | Steady pace, no aggression when contradicted |
The most common misconception
Speaking the most does not score the most. Evaluators are usually watching a group of eight to twelve for ten to fifteen minutes; three well-structured contributions land better than nine interruptions.
For technology-and-society topics in particular, having a genuine view helps — see will AI replace entry-level jobs in India for one that comes up constantly.
Aim to speak within the first two minutes. Entering early is easier than entering late, and it establishes you as a participant rather than a spectator.
GD preparation checklist
Speaking first is an advantage only if you have something structured to say. If you are unsure of the topic, let one or two people speak, then enter with a framing point in the first two minutes.
Three to five substantive contributions across a ten to fifteen minute discussion is a strong showing. Quality and structure are marked, not frequency.
Stay out of it and try once to restore order by addressing the group and proposing a structure. Evaluators notice the person who stabilises a chaotic GD more than anyone shouting inside it.
No. GDs are common in consulting, banking, FMCG, and many mass-recruitment drives, and less common in pure software roles, which usually replace them with technical rounds.
The only real GD preparation is doing one and getting told what you actually looked like.
Book a live mock GD/interview session →The questions that come up in almost every fresher interview — what each one is actually testing, and how to build an answer that sounds like you rather than a script.
Skills & LearningCommunication feedback is the vaguest rejection reason there is. Here is what it actually refers to, and how to fix each part of it.
Interview PreparationBeing prepared and being chosen are different things. Here's the strategy layer that separates candidates who clear rounds from candidates who only attempt them.
Placement PreparationA round-by-round walkthrough of what actually happens during a campus placement drive, and how to prepare for each specific stage.