Low CGPA? No, It Doesn't End Your Career. Here's What Overrides It.
Your CGPA is 6.5. Or 6.2. Or you have a couple of backlogs you are still clearing. Every placement-related WhatsApp forward mentions "minimum 60% throughout academics." Your seniors say "no company will hire you below 7 CGPA." Your placement cell has stopped calling you for drives. You are convinced your engineering degree was a waste of time because one number on your mark sheet is lower than a recruiter's cutoff. Here is the real data on CGPA filtering, which companies actually enforce cutoffs, and — most importantly — what overrides a low CGPA in the hiring decision.
WHICH COMPANIES FILTER BY CGPA — AND AT WHAT THRESHOLD
| COMPANY TYPE | CGPA CUTOFF | ARE BACKLOGS A PROBLEM? | WHAT OVERRIDES CGPA |
|---|---|---|---|
| TCS (Ninja / Digital) | 6.0 (Ninja), 7.0 (Digital). Hard filter. | Yes. Active backlogs disqualify. Cleared backlogs: case-by-case. | Nothing. CGPA is a hard gate. If you are below 6.0, TCS is off the table. |
| Infosys / Wipro | 6.0 (Systems Engineer). 7.0+ for specialist roles. | Active backlogs disqualify at most service companies. | Nothing. Same as TCS — the volume hiring process uses CGPA as a standardized filter. |
| Mid-Tier Product Companies | 6.5 typically. Some have no cutoff. | Sometimes. Backlogs matter less than portfolio at product companies. | Deployed projects. Live URLs. Clean GitHub. These can override a 6.5 CGPA entirely. |
| Startups (Seed to Series B) | Rarely have a cutoff. Most do not check. | Almost never. Startups care about what you can build today, not your semester 3 marks. | Everything overrides CGPA. Portfolio, GitHub, take-home project performance, culture fit. |
| FAANG / MAANG India | 7.5+ typically. Hard filter at resume stage. | Yes. Multiple backlogs, even cleared, can be a negative signal. | Extremely strong portfolio or referral can get you past the filter, but rarely. |
The pattern is clear: CGPA is a hard filter at service companies and FAANG. It is a soft filter or non-existent at startups and mid-tier product companies. If your CGPA is low, your strategy is simple and specific: do not apply to companies that filter by CGPA. Apply to companies that hire based on what you can build. This is not settling — it is optimizing. A deployed project that demonstrates production-level competence will get you interviewed at a startup paying ₹8-12 LPA. The same project will not even be seen at TCS because your CGPA filtered you out before a human looked at your resume.
If they ask directly: "My CGPA reflects my performance in a curriculum that is heavily theoretical and exam-focused. My real strength is in building production software — you can see my deployed project at [URL]. I would rather you evaluate me on what I have built than on my semester exam scores." What not to say: "The professors were biased." "I was going through personal issues." "The college didn’t teach anything useful." These sound like excuses. The interviewer knows the Indian education system is flawed. They want to see whether you took responsibility for your own learning despite it. Your deployed project is the answer to that question. If you have backlogs: "I had X backlogs, all of which are now cleared. I do not have any active backlogs." Be direct. Do not over-explain. Backlogs matter only if they are active. Cleared backlogs, combined with a strong portfolio, are typically ignored by product companies and startups.
01. Do not apply to service companies. They use CGPA as a hard filter. You will waste time and morale on applications that never reach a human. 02. Target startups and mid-tier product companies. They hire based on what you can demonstrate, not what your mark sheet says. Your portfolio is your primary credential. 03. Build the deployed project. This is non-negotiable. A low CGPA without a deployed portfolio is a very hard sell. A low CGPA with a deployed portfolio is a manageable one. 04. Do not hide your CGPA. List it. Hiding it signals shame, and the interviewer will ask anyway. Owning it signals maturity. 05. Let the portfolio do the talking. The first 5 minutes of the interview should be about your project — the architecture, the deployment, the trade-offs. By the time they ask about CGPA, they have already decided they want to hire you based on what you built.