--- title: How to Explain a Low CGPA in an Interview description: How to explain a low CGPA in an interview without excuses — a three-part answer, what recruiters in India actually screen on, and what to say about backlogs. url: https://usegreenroom.app/blog/how-to-explain-low-cgpa-in-interview last_updated: 2026-08-01 --- ← Back to blog India · Campus # How to explain a low CGPA in an interview August 1, 2026 · 11 min read ![How to explain a low CGPA in an interview — guide cover from Greenroom, the AI mock interviewer](/assets/blog/how-to-explain-low-cgpa-in-interview-hero.webp) The HR manager glanced at the sheet and said, mildly, "6.4. Tell me about that." What followed was four minutes of a very good engineer explaining that the college had a strict evaluation policy, that one professor was known for it, that the lab exams were unfair, that his hostel had power cuts, and that anyway CGPA does not measure real skill. All of that was true. None of it was the answer. By the end, the only thing the interviewer had learned was that this candidate blamed things. If you are searching for **how to explain a low CGPA in an interview**, here is the short version before the long one: the interviewer is not trying to make you feel bad about a number from three years ago. They are checking one thing — whether you take responsibility or distribute it. The number is already on the sheet. Your reaction to it is the only new information in the room. I built Greenroom after freezing in an interview I had prepared hard for, and this is one of the questions people most often prepare in their heads and never once say out loud. ## Why interviewers ask about your CGPA at all Three reasons, and only one of them is about academics. - **A hard filter you already cleared.** Many Indian companies screen at 6.0, 6.5, 7.0 or 60% aggregate. If you are sitting in the interview, you passed that gate. Nobody re-litigates a filter they already applied. - **A proxy for consistency.** Grades are four years of small, boring, repeated effort. A low CGPA raises a fair question about follow-through, and the answer is evidence of follow-through somewhere else. - **A stress probe.** This is the real one. It is a socially awkward question asked to see what you do when you are uncomfortable. Defensiveness, rambling and blame all score worse than the number itself. That last point is why the answer is a delivery problem, not a content problem. Our [campus placement interview guide for India](/blog/campus-placement-interview-guide-india) covers the rest of the screening funnel. ## The three-part answer ![Diagram of the three-part answer for explaining a low CGPA in an interview — own it briefly, give one real reason, then pivot to evidence](/assets/blog/how-to-explain-low-cgpa-in-interview-diagram.webp) The whole answer is under sixty seconds. Most candidates spend three minutes on part one and never reach part three. **Part one: own it, in one sentence.** "My CGPA is 6.4, and it is lower than it should be." That is the whole apology. No "but", no context yet, no mention of the college. One sentence, level tone. **Part two: one real reason, stated as finished.** Not five reasons — one, and in the past tense. "I spent my first two years doing almost no academic work; I was building things instead, and I let the marks slide." Or: "My father was ill through my second year and I was travelling home most weekends." Or the hardest and most respected one: "I did not take it seriously early on." **Part three: what changed, with a number.** "From the fifth semester my SGPA was above 8, and I finished with two backlogs cleared." Or, if the marks never recovered: "The marks did not recover, but in that time I shipped a project that now has forty users, and I completed a six-month internship at [company]." Then stop. Hand the round back: "Happy to walk through that project if it would be useful." The whole thing is under sixty seconds. Most candidates spend three minutes on part one. **The core move:** answer in the past tense, then pivot to present-tense evidence. A low CGPA describes who you were in your second semester. Everything you say after it should describe who you are now. ## What not to say - **"The college marks strictly."** Even when true, it sounds like blame and the interviewer has heard it from every candidate at your college. - **"CGPA doesn't matter in the real world."** You are saying this to someone who is currently using it. It reads as contempt for their process. - **A medical or family reason with no boundary.** One sentence is respectful; five minutes makes the interviewer uncomfortable and they will remember the discomfort, not the reason. - **Blaming a single professor.** It sounds petty in a way that is very hard to recover from. - **Volunteering it before you are asked.** If they do not raise it, do not open with it. Some candidates apologise for their CGPA in "tell me about yourself", which introduces a weakness into the one answer they fully control. Our [how to answer tell me about yourself](/blog/how-to-answer-tell-me-about-yourself-software-engineer) guide covers what belongs there instead. ## How to answer about backlogs Backlogs are asked more bluntly than CGPA, and they are more often a hard eligibility criterion — many Indian service companies require zero active backlogs at the time of joining, and some require zero across the whole degree. Answer with the facts in this order: how many, whether they are cleared, and when. "I had two backlogs in the third semester. Both were cleared in the supplementary exam that year, and I have no active backlogs." Precision does the reassuring work here — vagueness reads as hiding something. If a backlog is still active, say so plainly along with the date you are clearing it. Getting caught later during background verification is far worse than an awkward moment now, and Indian employers do check. Our [background verification in India](/blog/background-verification-india) guide covers what actually gets verified. ## Building the evidence that outranks the number The answer only works if part three is real. Between now and your interviews, the highest-yield things you can point to: - **One project you can demo.** Deployed, with a link, that solves something. One finished thing beats four half-repositories. Our [how to talk about GitHub projects in interviews](/blog/talk-about-github-projects-in-interviews) guide covers how to present it. - **An internship, however small.** Even two months of real work resets the conversation from grades to experience. - **A visible ranking.** A competitive programming rating, a Kaggle placement, a hackathon result — any external number that is not your CGPA. - **Open source.** Two merged pull requests to a real project is disproportionately persuasive because it is verifiable. - **Certifications, honestly weighted.** A cloud certification helps at the resume-screen stage. It does not substitute for a project in the interview. Our [resume for freshers with no experience](/blog/resume-for-freshers-no-experience) guide covers how to place these so the recruiter sees them before the CGPA. ## Where each prep option actually helps - **GeeksforGeeks and PrepInsta placement sections** — good for knowing which companies filter at which CGPA, which is genuinely useful for targeting. - **Your seniors and college WhatsApp groups** — the most accurate source for what a specific company asked on your campus last year, and worth more than any generic list. - **ChatGPT** — will write you a polished paragraph about your CGPA. The problem is that the paragraph is written, and you will deliver it in a rush with a shaky voice, because you have never said it aloud to anything that reacts. - **A friend doing a mock** — genuinely helpful, though friends rarely ask the follow-up. The follow-up is where this answer breaks: "So why did it take you until the fifth semester?" - **Greenroom** — the spoken layer. [Ari, the AI interviewer](/) asks the CGPA question in the flat, slightly impatient tone a real HR round uses, then asks the follow-up. Honest tradeoff: Ari cannot tell you which companies filter at 7.0 — your placement cell can. ## A rehearsal drill that works - **Say it out loud ten times, timing yourself.** Target 45-60 seconds. Most people start at three minutes and get to sixty seconds by the sixth attempt. - **Record one attempt and listen back.** You are listening for two things: how many times you say "but", and whether your voice goes up at the end like a question. - **Practise the follow-up.** Have someone ask "why so late?" or "what stopped you earlier?" and answer without adding a new excuse. - **Practise it after a technical question**, not cold. In a real round it arrives when you are already tired, which is when the rambling starts. Our [how to stay calm in interviews](/blog/how-to-stay-calm-in-interviews) guide covers holding your composure through that. **The verdict:** a low CGPA has never cost anyone a job in the room. The four-minute defensive answer about it has. Own it in one sentence, explain it in one more, and spend the rest of the time on the work you have actually done. ## What to do if the CGPA filter blocks you entirely Sometimes the number keeps you out of the room, not the round. That is a targeting problem, not an interview problem: product startups and mid-size companies filter on CGPA far less than large service companies, off-campus applications rarely apply the same cutoff, and referrals bypass the filter almost entirely. Our [off-campus placement strategy for India](/blog/off-campus-placement-strategy-india) guide covers the channels that do not start with a marksheet. ## Frequently asked questions ### How do you explain a low CGPA in an interview? Answer in three parts and keep it under a minute. Own it in one sentence without blaming the college or the evaluation, give one real and finished reason in the past tense, then pivot to what changed with a number — an improved SGPA, cleared backlogs, an internship or a shipped project. Then hand the round back by offering to talk about that work. The interviewer is testing whether you take responsibility, not re-scoring your degree. ### What is considered a low CGPA in India? Most large Indian employers screen somewhere between 6.0 and 7.0 CGPA, or 60% aggregate, so anything below about 7.0 is commonly treated as low by campus recruiters. That said, if you are already in the interview you have cleared whatever filter that company applies, so the number is context rather than an obstacle at that point. ### How do you explain backlogs in an interview? State how many, whether they are cleared, and when — in that order and precisely. For example: two backlogs in the third semester, both cleared in the supplementary exam that year, no active backlogs now. If a backlog is still active, say so plainly with the date you are clearing it, because Indian employers verify academic records during background verification and being caught later is far more damaging than an awkward moment in the interview. ### Should I mention my low CGPA before the interviewer asks? No. If they do not raise it, do not introduce it, and in particular never work it into your answer to tell me about yourself — that puts a weakness into the one answer you fully control. Prepare the answer thoroughly, and use it only if the question actually comes. ### Does CGPA matter after your first job? It matters much less once you have real work experience, and most companies stop asking after two or three years. It matters most at the campus and fresher stage, where it is used as a screening filter because there is little else to filter on, which is exactly why building one demonstrable project or internship changes the conversation faster than anything else. ### Can I get a job with a 6 CGPA in India? Yes, though it narrows which doors open by default. Several large service companies filter at 6.0 or 6.5 and will still consider you, product startups and mid-size companies weight projects and skills far more heavily, and off-campus applications and referrals often bypass academic cutoffs entirely. The practical strategy is to target channels that assess work rather than marksheets, and to have one deployed project you can demonstrate. This question is not hard to answer — it is hard to answer calmly, under a stranger's stare, sixty minutes into a round. [Greenroom](https://usegreenroom.app/) lets you practise it out loud with Ari, including the follow-up, and tells you when you drifted into excuses. Free to start. Curious how it works? See [how AI mock interviews work](/blog/ai-mock-interview).