Academic numbers are a filter early in your career and irrelevant later. The only real questions are whether yours help you today, and what to do if they don't.
Include it when any of these are true
- You're a fresher or within two years of graduating
- It clears the common cut-offs (roughly 7.0 CGPA / 65%)
- You're applying to campus placements, PSUs, banks or government roles, where it's mandatory anyway
- You're applying abroad, where a converted GPA is expected
Leave it off when
Leaving a number off a resume is not dishonesty. Application forms that require it will ask, and you answer truthfully there.
- You have two or more years of work experience — nobody asks
- It's below the usual cut-off and the employer hasn't demanded it
- The space would be better spent on a project or an internship
Presenting a low CGPA honestly
Three approaches work, in this order of preference:
- Show the trend — 'CGPA 6.4 overall; 7.8 in final two years' is true and explains itself
- Show the relevant subset — 'CGPA 8.1 in core CS coursework' if your electives dragged it down
- Crowd it out — put strong projects, internships and contest results above it so the number isn't the first thing read
Don't do these
- Rounding 6.8 to 7 — it gets verified during onboarding
- Converting CGPA to percentage with a favourable multiplier and not saying which one
- Writing 'CGPA: 8.9/10' for one degree and '78%' for another; pick a consistent presentation
- Adding 10th and 12th marks when you're five years into a career
What outweighs it
For technical roles, a strong project with real users, an internship at a known company, or a visible contest rating all outweigh a mid CGPA in practice. Those take a few weekends to build; your CGPA is fixed. Spend the effort where it moves.
Put this into practice
Build, score and tailor your resume with JotCV — free plan, no card needed.
Build a resume that leads with work