Group Discussion Topics for Freshers: What Evaluators Actually Score

Most freshers prepare hard for the interview and then walk into the group discussion cold. That is backwards. In Indian campus placements the GD round is usually the first real cut — a hall of 200 shortlisted students becomes 60 by lunch. Searching for group discussion topics is a fair place to begin, but the topic list is the smallest part of it. What you are actually being scored on is how you behave in a room of eight people who all want the same offer.

This is not a debate. Nobody wins a GD. The panel is watching whether you can think in a group without dominating it and without disappearing inside it. Once you understand that, preparation stops being about memorising opinions and starts being about learning a handful of moves.

What a GD round is actually filtering for

Mass recruiters run GDs for a boring, practical reason: they cannot interview everyone. When TCS, Infosys, Wipro, Cognizant or Accenture visit a campus and 400 students clear the aptitude test, the company still only has a handful of panels for the day. The GD is a cheap, fast filter. Ten minutes, eight candidates, two evaluators, three names taken forward.

That constraint tells you something useful. The evaluator is not looking for the smartest person in the room. They are looking for reasons to remove people. Shouting is a reason. Silence is a reason. Repeating what someone already said is a reason. Your job is to give them nothing to strike you off for, and one or two clear moments to remember you by.

For entry-level IT roles in the ₹3.5–₹4.5 LPA band, the company is hiring for a seat in a team of twelve people on a client project. They need to know you can sit in a stand-up call, disagree without heat, and summarise a decision. The GD is a ten-minute simulation of exactly that.

What evaluators are actually writing on the sheet

Most evaluation sheets are simpler than students imagine. Usually four or five columns, marked out of five each. The wording varies by company, but the substance repeats.

Clarity. Can you make one point in two sentences without hedging? A student who says "I feel that, like, in today's world, there are many aspects to this" has used fifteen words to say nothing. That is marked down even if the student speaks often.

Whether you build on others. This is the column freshers ignore, and it is the one that separates candidates. If your contribution could have been made without listening to anyone else, you were reading from a script. Naming a previous speaker and extending or qualifying their point proves you were present.

Structure. Someone in the group usually offers a frame — let us look at this from the employee side and the employer side, or short term versus long term. That person is remembered. Bringing structure is the highest-value, lowest-risk move available to you.

Summarising. If you can state where the group agreed and where it split, in thirty seconds, you look like the person who was actually tracking the conversation. Very few candidates attempt this.

Content. Yes, knowing something helps. But it is one column out of five, and it is the one most students spend all their preparation on.

The three kinds of group discussion topics

Almost every GD topic you will face falls into one of three buckets, and each rewards a different opening. Current affairs topics reward one concrete fact early. Abstract topics reward a definition — whoever defines the term controls the next five minutes. Case-based topics reward asking what the constraint is before proposing solutions.

The table below is a working list. These are durable themes, not this week's headlines, so they stay usable across a full placement season.

Kind	Topic	How to get in
Current affairs	Will automation shrink entry-level jobs in Indian IT services?	Separate "fewer jobs" from "different jobs" in your first line.
Current affairs	Work from home helps employees more than employers	Split by role type — sales, support, engineering.
Current affairs	Should coding be compulsory in every undergraduate degree?	Ask what problem making it compulsory solves.
Current affairs	Are Indian startups creating jobs or creating valuations?	Distinguish funding news from headcount.
Current affairs	Is English fluency a fair hiring filter in India?	Bring in Tier 2 and Tier 3 college context.
Current affairs	Gig work: flexibility or insecurity?	Name a concrete worker — a delivery rider, a freelance designer.
Current affairs	Should India's space spending wait until basic needs are met?	Refuse the false choice, then give a criterion.
Current affairs	Electric vehicles in Indian cities: readiness or hype?	Move to charging infrastructure quickly.
Current affairs	Has social media made news less reliable?	Separate speed from accuracy.
Current affairs	Should private sector jobs have reservation?	Stay on mechanism, not sentiment.
Current affairs	Is online education a real substitute for a classroom?	Split by subject — theory versus lab work.
Abstract	Zero	Define it as absence, or as a starting point. Pick one.
Abstract	Black or white	Argue the grey, but say so explicitly.
Abstract	The wall	Protection or restriction — choose and commit.
Abstract	Speed versus direction	Anchor it in one real example, then generalise.
Abstract	Silence	Works well as a comment on decision-making in teams.
Abstract	Water finds its own level	Read it as merit, or as complacency.
Abstract	Round pegs in square holes	Take it straight to hiring and role fit.
Abstract	An empty vessel makes the most noise	Careful — do not make it about people in the room.
Case-based	A four-person team must ship in two weeks with one member on leave	Ask what can be cut from scope before adding people.
Case-based	A company must close one of three loss-making branches	Ask for the closing criterion first.
Case-based	A startup has ₹50 lakh of runway and three spending options	State the goal — survival or growth — before choosing.
Case-based	Allocate a ₹10 lakh CSR budget across three villages	Equal split versus highest impact. Name the trade-off.
Case-based	Cut costs by a sixth without laying anyone off	List cost heads out loud, then attack the largest.
Case-based	A city bus service is losing money: raise fares or cut routes?	Ask who the service exists for.
Case-based	Choose between a high scorer and a candidate with a strong internship	Ask what the role needs in month one.
Case-based	An FMCG launch failed in Tier 2 markets. What next?	Separate product problem from distribution problem.

How to open when you know nothing about the topic

This happens. The topic is announced, you have never thought about it, and someone next to you is already talking. You have roughly ninety seconds before the group settles into a shape you cannot enter.

Do not open with an opinion you do not hold. Open with a frame instead. Frames work without knowledge:

• "Before we take sides, can we agree on what we mean by this term? I read it as two different things."
• "There seem to be two stakeholders here. Can we look at each separately?"
• "I would separate the short-term effect from the long-term one, because I think they point in opposite directions."

All three are safe, all three are scoreable under structure, and none of them require a single fact. Then listen hard for ninety seconds. Someone will supply a fact you can build on, and now you have content that is genuinely yours because you shaped it.

The other reliable move is a concrete example. Abstract discussions drift; a specific case pulls them back. "Take a delivery rider in Pune" is worth more than three sentences of theory.

Exact phrases that buy you a way in

Entering a moving discussion is a skill, not a personality trait. These lines work because they signal cooperation, which makes the group let you in rather than talk over you.

• "Can I build on what he just said —" The single most useful line in a GD. It buys you the floor and scores you on the listening column at the same time.
• "We seem to be arguing two different points." Deploy this when the discussion has become a fight. It makes you the person who noticed.
• "I want to disagree with that, but only on one part of it." Disagreement without hostility. Panels notice the difference.
• "Can we come back to what she said about costs? I do not think we finished it." Recovers a dropped thread and credits someone else. Very hard to mark down.
• "So far we have covered A and B. Has anyone thought about C?" Summary plus new direction, in one sentence.
• "Let me put a number on that." Then do. Even a rough one.

Say the person's name if you caught it. Naming people is disproportionately effective — it proves attention and it makes the other candidate less likely to cut you off.

The mistakes that get freshers cut

Shouting. Volume reads as panic, not confidence. If two people are talking, stop, wait two seconds, then start with "Sorry — go ahead." You lose four seconds and gain a mark.

Speaking first with nothing to say. Students are told that speaking first is an advantage. It is, only if you have a point. Opening with a vague restatement of the topic is the worst possible first impression, because it is the one moment everyone is listening.

Staying silent. Zero contributions is an automatic zero, however good your listening was. Three clear entries beat eleven noisy ones.

Repeating. If your point has been made, add a qualifier, a counter, or an example. Never say it again in different words. Evaluators hear this constantly and it is the fastest way to look unprepared.

Getting personal. Attacking a candidate rather than an argument ends your candidature in most panels, especially in bank PO and SSB-style group tasks where cooperation is explicitly scored.

Fabricating data. Do not invent a percentage. If someone asks for your source and you have none, you are finished. Say "I have read this but I am not certain of the figure" instead — honesty scores better than false precision.

If you are naturally quiet

Plenty of good engineers are quiet, and campus GDs are unkind to them. The fix is mechanical, not emotional.

Set a target before you walk in: three entries, thirty seconds each. Not more. Quiet candidates fail because they wait for the perfect moment, which never arrives. Instead, plan your entries by clock. One in the first two minutes, one in the middle, one in the last two. Write it on your hand if it helps.

Use posture to claim a turn. Lean forward slightly, raise a hand to chest height, and start with two loud words before dropping to normal volume. The first two words are the whole battle.

Second, pick a role. Being the summariser, or the person who brings in the counter-view, or the one who keeps time, gives you a reason to speak that does not depend on having the best opinion. This also helps enormously in the HR interview afterwards, because you will have a real story about working in a group.

Third, practise out loud. Reading about GDs does nothing. Sit with four friends, take a topic from the table above, run eight minutes, and have one person keep score on the five columns. Ten sessions is enough to change how you sound.

The last two minutes, where it is decided

Most candidates fade in the final stretch. The discussion becomes louder, three people are repeating themselves, and the evaluator has already stopped taking notes on them. This is the cheapest opportunity in the whole round.

Do this. At roughly the eight-minute mark of a ten-minute GD, come in with a consolidation:

"Can I try to pull this together? We broadly agreed on two things — that the cost side matters and that it varies by role. We did not resolve whether the responsibility sits with the employer or the individual. If I had to take a position, I would say the employer, because they control the incentives."

Three things happened there. You summarised. You named the unresolved point honestly instead of pretending consensus. You took a position. That is a full three columns of the sheet in forty seconds.

If the panel asks for a formal conclusion, do not use it to make a new argument. Restate the group's shape, then your stand. And when the moderator says stop, stop mid-sentence. Talking over the end is remembered badly.

Fitting GD prep into your placement season

A GD round is one gate. It sits between the aptitude test and the technical or HR round, and the same shortlist carries through, so the work is cumulative. If your campus process starts in July, the sensible order is aptitude first, then GD practice in group sessions, then interview answers.

Do not over-invest. Six practice sessions and a mental list of ten topics per bucket is enough for most drives. Spend the rest of your time on your campus placement preparation broadly and on getting your resume past the screening filter, and read up on the specific pattern where you can — the TCS interview pattern and the Infosys process differ in how much weight the group round carries.

One last thing. Every year, students who spoke twice and summarised well clear the round while the loudest person in the room does not. That is not luck. The sheet was never rewarding volume.