Should You Put Your GPA on a Software Engineer Resume?
Published ยท Finch Team
Updated
Every semester, thousands of CS students ask the same question when they start applying for internships and new grad roles: do I include my GPA?
The answer depends almost entirely on what your GPA is. Here's the actual breakdown.
The Basic Rule
3.5 or above: include it. You earned it. It's a positive signal and worth the space.
3.0 to 3.49: include it only if the rest of your resume is thin. At this range, it's neutral: neither a selling point nor a red flag for most companies. If you have strong projects and internship experience, skip it and use the space for something more useful.
Below 3.0: leave it off. You're never required to list your GPA on a resume. A sub-3.0 hurts more than it helps on a first-pass screen, and omitting it isn't lying.
There's no universal rule here. The calculation changes based on what else is on your resume and which types of companies you're targeting.
Why Most Tech Companies Don't Care That Much
GPA matters less in software engineering hiring than most students think, and it matters almost entirely at the resume screening stage.
Once you're in an interview loop, nobody is looking at your transcript. An interviewer doing a technical screen cares whether you can solve the problem, not whether you got a B in sophomore-year physics.
GPA shows up as a meaningful filter in two specific contexts:
1. Big tech structured recruiting programs. Some large companies run automated or recruiter-level filters that screen out applications below a GPA threshold. This isn't universal. Many large tech companies don't use GPA as a formal filter at all. But it exists at enough of them that a sub-3.0 is worth worrying about if you're specifically targeting FAANG-tier.
2. Campus recruiting at target schools. When a recruiter is reviewing 400 resumes from the same university, GPA becomes a quick way to narrow the pile. Outside of campus recruitment pipelines, it matters much less.
If you're applying broadly (to startups, mid-size tech companies, and companies not running formal campus programs), GPA is rarely the deciding factor.
What Actually Matters More
When we built Finch's first version, a resume generator, GPA was one field among many. What consistently drives better outcomes in both ATS keyword matching and recruiter attention:
Projects with specific technologies and measurable outcomes. A 3.2 GPA candidate with a polished GitHub repo with real users gets more callbacks than a 3.8 GPA candidate with no visible work. Every time.
Relevant work experience. Part-time tech work, research assistant roles, and side projects all shift attention away from grades. If you have any, lead with them.
Technical skills aligned to the job. Your skills section matching the keywords in the job description is what drives ATS hits. GPA doesn't touch that.
Bullet points that demonstrate impact. "Reduced API response time by 280ms" beats "Relevant Coursework: Data Structures" in recruiter attention span every time.
If your GPA is low, the move isn't to hide and hope. It's to make the rest of your resume so strong that GPA becomes irrelevant noise before the recruiter gets to your Education section.
Should You Use Your Major GPA?
Some students have a strong major GPA even when their overall GPA is dragged down by non-major requirements: a tough language course, a gen-ed they hated, a rough semester with a lot going on.
This is a legitimate option. List both, formatted clearly:
GPA: 3.1 overall | 3.8 in CS coursework
Only do this if your major GPA is genuinely meaningfully higher. If your overall GPA is 2.8 and your major GPA is 3.0, the distinction isn't compelling enough to call out.
What to Do When an Application Asks for GPA
Many ATS forms (Greenhouse, Workday, and Lever are the most common) include a GPA field. It's usually optional.
If the field is optional and your GPA is below 3.0: leave it blank. This is normal, and a blank GPA field is not a red flag.
If the field is required: put your accurate number. Never falsify academic information on a job application. Companies run background checks, and a falsified GPA discovered after you're hired is grounds for immediate termination.
You don't need to proactively explain your GPA in a cover letter or recruiter call. Let your technical screen do the talking. If someone asks directly, answer honestly and move on. Don't apologize for it.
The Referral Shortcut
If your GPA is below 3.0 and you're worried about it, the most effective countermeasure is a referral.
A referral from someone inside a company moves your resume into a different review queue. The person who referred you is vouching for you. That changes the calculus for whoever is reviewing the application. The GPA filters that apply to the cold application pool often don't apply to referred candidates.
This is one of the strongest arguments for spending time on networking if your GPA isn't where you'd like it to be. A strong referral is worth more than a GPA bump at most companies. For how to find and ask for referrals, read our guide to getting software engineering referrals.
How to Compensate for a Low GPA
If your GPA is low, here's the actual playbook:
Build visible projects. Your GitHub should have at least 3-4 polished projects with READMEs explaining what you built and why. No abandoned tutorial repos pinned at the top. If a recruiter clicks your profile and sees 30 forks with no commits, that's worse than no GitHub link.
Apply through referrals when possible. Even a weak referral (someone you met at a career fair who submitted your name internally) can change how your application is routed.
Target companies that evaluate on interviews, not credentials. Most startups and mid-size tech companies care far more about your technical screen than your GPA. They're the right target if grades are a concern.
Write a strong cover letter when applying cold. Don't address your GPA directly. Just make the case for why you're the right person based on what you've built. Give the reader reasons to get past the transcript.
Apply in volume. GPA is partly a targeting problem. More companies in your pipeline means more companies that filter by interview performance rather than academic record. For finding enough roles to stay at volume, Finch's board lists open internships and new-grad roles, newest first, and each week Finch picks the 3 that fit your major best.
GPA Checklist
Before your next application session, run through this:
- GPA 3.5+? Add it to your Education section.
- GPA 3.0-3.49? Add it if your resume is thin; consider leaving it out if you have strong projects and experience.
- GPA below 3.0? Leave it off the resume entirely.
- Significantly higher major GPA? Consider listing both, clearly formatted.
- GPA field in the application is optional? If below 3.0, leave it blank.
- Have you made the rest of your resume strong enough that GPA isn't the first thing a recruiter notices? Projects, skills, bullet points all polished?
Your GPA is one data point in a package. At most tech companies, it's not even the most important one once you're past the first filter. Build something real, optimize your resume for the roles you want, and get your applications in front of enough relevant hiring managers.