CGPA Is a Filter, Not a Verdict: How to Handle Low Grades in Indian Interviews
Here is something most students with a CGPA below 7.0 do not know: most interviewers do not bring up your grades because they find them disqualifying. They bring them up because they want to hear how you respond.
"Why is your CGPA low?" is not a gotcha. It is a self-awareness check. It is asking: does this person understand their own track record? Do they take responsibility for it? What did they do with their time and energy when they were not studying? A candidate who answers badly converts a manageable data point into a red flag. A candidate who answers well converts a potential liability into a story about judgment, trade-offs, and initiative.
This post covers how to answer it well — with full worked examples — and what to do when CGPA keeps you out of shortlists before you ever get to answer anything.
What CGPA actually does in the hiring process
CGPA plays two completely different roles in Indian hiring. Most students understand only one of them.
Role 1: A hard filter before round one. Companies like TCS, Infosys, Wipro, Accenture, and Cognizant set a minimum CGPA cutoff — usually 6.0, 6.5, or 7.0 — and reject everyone below it automatically. This filter is applied before any human reads your application. It is binary and indifferent to context. You are either above the line or you are not.
Role 2: A discussion point inside the interview. Once you are in the room, CGPA is one data point among many. A hiring manager comparing a candidate with a 7.2 who led a deployed open-source project and placed in a national hackathon against a candidate with an 8.5 who has nothing outside coursework will often rank them in that order. The interview is where CGPA gets contextualised, and that is where your answer matters.
The distinction is important because the fix for each role is different. If CGPA is filtering you out before interviews, no polished answer will help — you need a strategy to get into the room. If you are getting interviews despite a lower CGPA, your job is to ensure grades do not dominate the conversation.
What different companies actually weight:
- Service companies (TCS, Infosys, Wipro, HCL, Tech Mahindra): The cutoff is the primary gate. Once past it, CGPA matters far less than communication skills, attitude, and basic technical knowledge.
- Product companies and funded startups (Razorpay, CRED, Zepto, Meesho): Cutoffs exist but are often negotiable for strong technical screens. A solid DSA performance or a notable personal project can offset a 6.8.
- Consulting (Deloitte, EY, KPMG, McKinsey India): Academic record carries more weight here, though sustained external achievement — competition placements, positions of responsibility, structured self-directed work — can move the needle.
What the interviewer is actually asking
When an interviewer says "I see your CGPA is 6.5 — tell me about that," they are typically asking three things at once.
First: Are you self-aware? Do you understand your own track record, or does the question catch you off guard?
Second: Do you take responsibility? Did you own it, or did you blame the grading system, the professors, or the university?
Third: Is there a coherent story? Was there something specific going on — a genuine trade-off, a difficult circumstance, a period of poor priorities you've since corrected? Or was it just drift?
The answers interviewers fear are the ones that reveal a candidate who has no explanation, who blames external factors without any ownership, or whose only defence is "I don't test well." The answers that work are honest, specific, and reframe without minimising.
Fully worked examples
Scenario 1: CGPA dropped because of a genuine trade-off
Many students take on significant outside work — a serious internship, leading a tech society, building a real product — and their grades take a hit. This is a defensible trade-off if you name it clearly.
Q: Your CGPA is 6.7. Can you walk me through that?
"My CGPA was 7.4 after second year and dropped in the two semesters that followed. I want to be honest about why. During my third year I joined an early-stage logistics startup as a part-time backend developer alongside my coursework — 25 to 30 hours a week. I chose to prioritise that work over exam prep for two semesters. That call cost me GPA points, but it gave me 14 months of production experience, a deployed Node.js API that handled live orders, and a reference that helped me get shortlisted here. If I had those two years over, I would make the same choice. What I would change is staying current with two core modules I let slip entirely — that was avoidable."
Why this works: it is specific about what changed and when, it owns the trade-off clearly, it names what was gained in exchange, and the final line shows the candidate has thought about what they would actually do differently rather than just wishing the number were higher.
Scenario 2: CGPA dropped because of personal circumstances
This is more delicate. Interviewers will not penalise someone who went through something real, but they are also not looking for an over-share. The key is honesty without self-pity, and a clear signal that you have moved forward.
Q: I notice your CGPA dipped in second year to 5.9 before recovering to 7.1. What happened there?
"My father was hospitalised for several months during my second year, and I was largely managing the household during that period. It affected my attendance and my ability to prepare for mid-semester exams. I did fail one paper that year — I cleared it in the next attempt. By third year the situation had stabilised, and I focused specifically on core subjects, which brought the GPA back up. I wanted to mention it directly rather than leave it as an unexplained number, because I think the recovery arc matters as much as the dip itself."
The final sentence is the move. The candidate is explicitly telling the interviewer how to read the data. A dip followed by a recovery, explained with honesty and no self-pity, is a credible story. It also turns the follow-up question — "how did you recover?" — into a conversation the candidate wants to have.
Scenario 3: You have a semester backlog
A backlog is a cleared or pending failed paper. It comes up on background verification forms, and how you handle it matters.
Q: Do you have any active backlogs?
"I have one pending paper from semester five — Digital Signal Processing — which I'm appearing for in November. I underestimated how different the exam format was from the assignments, and I didn't manage my prep for it well. There is no backlog from any other semester. I wanted to mention it proactively rather than have it surface on a form later."
The disclosure is what earns the trust. An interviewer who discovers an undisclosed backlog during background verification will flag it as an integrity issue, not a grades issue. Proactive disclosure takes that risk off the table.
Before/after: the same situation, two answers
Before — the answer that creates problems:
"CGPA doesn't really reflect my abilities. Our college has a tough grading system and the professors mark very strictly. I'm actually a fast learner and I've done a lot of good projects. I don't think grades should matter that much for a software job."
This answer packs four problems into five sentences. It externalises blame. It dismisses the metric without addressing it. It makes a claim about fast learning with zero evidence. And the final sentence sounds like a complaint about being evaluated at all. An interviewer hearing this will write "lacks ownership" in their notes.
After — the answer that works:
"Honestly, my CGPA reflects a period where I wasn't managing my time well. I was taking on too many things — club work, competitive programming, a personal project — without a system for keeping coursework in parallel. It shows in three specific semesters. What I'd say in my defence is that I've been consistent on the things I've cared most about: my Codeforces rating and the project I'll walk you through today are both things I can back up in detail. But I own that a 7.0 and a 6.4 are genuinely different, and I've been more disciplined about commitments since my fourth year."
Why the second answer lands:
- It owns the outcome without making excuses.
- It names a real cause — overcommitment, not system failure.
- It points to countervailing evidence without dismissing the question.
- The final line shows that the candidate understands the number is real, not a bias or an error.
The candidate in the second answer is not more impressive on paper. They are better at being honest about themselves, which is exactly what the question is probing for.
Common mistakes — and how to fix each
Mistake 1: Blaming the grading system
"Our university has a strict marking scheme" is the most common response and the one interviewers discount most reliably. It may even be true — but it does not explain why some students from the same university have 8.5 CGPAs. Institutional context can be a background note, not a main explanation. The personal part is yours to own.
Mistake 2: Overselling what you did instead
Some candidates swing so far the other direction that the answer becomes its own red flag: "I spent my time on things that actually matter in the real world." The implication that coursework is irrelevant is off-putting. You do not need to put down studying to justify what else you were doing. Name what you built or accomplished and let the interviewer draw their own conclusion.
Mistake 3: Apologising excessively
"I know my CGPA is really bad and I understand if it's a problem" is as damaging as dismissing it. Interviewers are not looking for remorse. They are looking for self-awareness and evidence of a forward motion. Acknowledge it, explain it, and move on. Do not return to it unprompted.
Mistake 4: Being vague when the follow-up comes
If you say "I was focused on my project," be ready to discuss the project in depth. If you say "my CGPA recovered in fourth year," be ready to name specific subjects and scores. The explanation is not the end of the conversation — it is the beginning of one. A vague explanation followed by a vague defence confirms rather than resolves the concern.
What to do this week
If your CGPA is filtering you out before interviews: The application channel matters more than the answer script. Companies that recruit through referrals, run hackathon tracks, or place more weight on technical screens often have more flexibility than their posted cutoffs suggest. Target applications where a hiring manager or engineer can see your GitHub, project, or coding profile before the HR filter is applied. Look specifically for companies with coding contests or national challenges that lead directly to an interview or offer — several mid-size product companies in India run these, and they bypass the GPA screen entirely.
If you are getting interviews but expect the question: Write your answer in two or three sentences. Time yourself saying it aloud. It should take 60 to 90 seconds and not feel like either an excuse or a confession. The test is whether someone with no stake in your outcome finds it convincing and complete. If you are not sure, ask someone who will give you an honest read, not a reassuring one.
If you have a pending backlog right now: Do not wait for the question. In the HR round, before they ask, say: "I want to mention one thing — I have a pending paper from [semester], which I'm appearing for in [month]. I wanted to bring it up directly." That sentence, said plainly, almost always closes the topic. The candidate who hides it and gets caught loses far more ground than the candidate who named it first.
CGPA matters most at the filter stage — it determines whether you get into the room. Once you are there, a clear and honest answer to the question typically closes it in under two minutes. What keeps the conversation going is not the number; it is the quality of your response to it.
If you want to hear how your answer actually sounds before it counts, CareerClutch's HR practice rounds include CGPA and academic background questions specifically, so you can refine it before you are in the room.