SS
Key Takeaways
- CGPA cutoffs are absolute filters on campus — no appeal, no discretion, and no amount of skill changes them.
- Off-campus hiring weights CGPA far less, which reverses the disadvantage for candidates with strong demonstrable work.
- A deployed project with real users is the single most effective counterweight to a weak academic record.
- Answer the CGPA question directly and briefly, with what changed rather than what went wrong.
- Your CGPA stops mattering after your first job, so the goal is getting the first one.
A low CGPA is the most demoralising constraint in campus placements because it operates before anyone assesses you. You do not get rejected after an interview; you are filtered out of the eligibility list by a number set months or years ago.
The useful response is not to argue with that. It is to understand precisely which doors it closes, which it does not, and how to build a profile that works through the doors that remain open.
This guide covers all three.
Start with the document every application depends on — run your resume through the free ATS score checker.
What CGPA actually blocks
On-campus eligibility filters. Companies specify a cutoff — commonly 6.0, 6.5, 7.0 or 7.5 — and the placement portal filters automatically. There is no discretion and no appeal, which is worth accepting quickly rather than fighting.
Some companies also screen on tenth and twelfth marks, which catches people out.
Backlogs are frequently a separate filter — many companies require none current, some require none ever. This is often a bigger barrier than CGPA itself — see the campus placement backlog guide.
What it does not block:
- Off-campus applications at companies with no academic cutoff
- Startups, which rarely screen on it
- Off-campus hiring challenges run by large employers
- Anything where you enter through a referral rather than an application filter
The strategy that works
Stop applying to what you cannot access, and get precise about what you can.
Get the criteria list from your TPO early. Know exactly which companies you are eligible for, and prepare specifically for those rather than for a general idea of placements. Students routinely spend weeks preparing for companies they were never eligible to sit for.
Weight off-campus heavily and start early. This is the structural point: off-campus hiring weights demonstrable skill and projects far more than academics, which is exactly the trade you want. Do not treat it as a fallback after campus season fails — run it in parallel from semester 7 — see campus placement vs off-campus.
Target off-campus hiring challenges. Several large employers run regular open assessments for freshers. These function as campus placements without the campus eligibility filter, and they are the single best-matched route for a low-CGPA candidate with real ability.
Use referrals. A referred application bypasses the filter that would otherwise remove you. Seniors from your college who were placed are the natural starting point — see networking messages for referrals.
Building the counterweight
Your CGPA is fixed. Your evidence is not.
One deployed project with real users. This is the highest-leverage thing available to you. Not a repository — something live, with a link, that someone other than you has used. It demonstrates in one line what your transcript denies, and it gives an interviewer something concrete to discuss instead of your marks. See choosing a final year project for placements.
An internship, however small. External validation carries weight precisely because it comes from someone who is not you and not your college — see converting an internship into a PPO.
A real GitHub profile with commit history and README files. Reviewers open it, and for a candidate whose academics are weak it does disproportionate work — see how to optimise your GitHub profile.
Competitive achievements. Hackathon placings, coding contest ratings, and open-source contributions are all objective third-party signals.
Strong aptitude and DSA. These are tested directly rather than inferred from your CGPA, which makes them the fairest ground available to you — see the campus placement aptitude test guide and the DSA roadmap.
Leave CGPA off the resume where it is below typical cutoffs and not explicitly requested. It is not dishonest — you are not obliged to volunteer every number — and it keeps the reader on your projects. Include it where a form or posting requires it.
Answering the question
You will be asked. Prepare for it rather than improvising.
A structure that works: what happened, briefly — what changed — what the evidence is now.
My second and third semesters were poor. I was spending most of my time on a startup project with two friends that eventually failed, and I let my coursework slide. From fourth semester my SGPA has been above 8, and the practical work led me to the backend development I've been doing since — including the scheduling tool I mentioned, which the department library uses.
Why this works: it is honest, it takes responsibility without excessive apology, it shows an upward trend, and it connects the period to something real.
What does not work:
- Blaming teachers, evaluation or the college
- Elaborate medical or personal explanations unless genuinely necessary and briefly stated
- Denying it matters
- Sounding defensive
Mention the upward trend if you have one. A rising SGPA across semesters is a genuine argument and interviewers respond to it.
Common Mistakes
Preparing for companies you are not eligible for. Get the criteria list early and direct your effort at what is actually accessible.
Treating off-campus as a fallback. It weights skill over academics, which is exactly the trade a low-CGPA candidate needs — start it in parallel, not after campus season fails.
Ignoring off-campus hiring challenges. They function as campus placements without the eligibility filter and are the best-matched route available.
Not using referrals. A referral bypasses the filter that would otherwise remove you before anyone reads your application.
Building certificates instead of projects. A deployed project with real users demonstrates what a transcript denies; a certificate does not.
Volunteering a low CGPA on the resume. Where it is below cutoffs and not requested, leaving it off keeps the reader on your evidence.
Improvising the CGPA answer in interviews. It is asked reliably enough to prepare properly.
Blaming the college or evaluation. It reads worse than the marks themselves and confirms the concern the interviewer had.
Frequently Asked Questions
Can I get placed with a low CGPA?
Yes, though the route differs. On-campus eligibility filters are absolute, so the realistic path is off-campus applications, hiring challenges and referrals, backed by demonstrable projects.
What CGPA do most companies require?
Commonly 6.0 to 7.5 depending on the company, sometimes with additional filters on tenth and twelfth marks and on backlog history.
Should I put my CGPA on my resume?
If it is below typical cutoffs and not explicitly requested, leaving it off is reasonable and keeps attention on your projects. Include it wherever a form or posting requires it.
What is the best way to compensate?
One deployed project with real users, plus an internship if possible. Both are third-party evidence that a transcript cannot provide.
Do startups care about CGPA?
Rarely. They hire on demonstrable ability, which is why they are a strong target for candidates with weak academics and real skills.
How do I answer the CGPA question in an interview?
Briefly and honestly — what happened, what changed, and what the evidence is now. Mention an upward trend if you have one, and never blame the college.
Does CGPA matter after the first job?
Essentially no. Once you have professional experience, employers assess that instead — which is why the entire goal is getting the first role.
Your resume has to clear screening either way. Check your ATS score free.
Make This Practical
Get the eligibility criteria from your TPO this week and split your target list in two — companies you can sit for, and everything else. Then stop spending time on the second group and run off-campus applications in parallel from the start rather than after campus season disappoints you.
Then build the one thing that outweighs the number. A deployed project with real users and a live link does more for a low-CGPA candidate than any certificate, because it is evidence a transcript cannot contradict — and it gives interviewers something concrete to talk about instead of your marks.
Finally, prepare the answer. Write out what happened, what changed and what the evidence is now, keep it under thirty seconds, mention an upward trend if you have one, and never blame the college — the way you handle the question matters more than the number behind it.
Find out why your score is low
Scan your resume against the job description and see exactly which checks fail.
Drop your resume here or choose a file
PDF only. Max 2 MB.
We never share your data or use it to train AI models.
Was this guide useful?
Be the first to rate it.
