I graduated with a 3.1 GPA. Not terrible, not impressive. My roommate graduated with a 3.9. He studied constantly, optimized every assignment for the grade, and stressed about every point on every exam.

I spent most of my free time building a crappy social media app that maybe 40 people used. I stayed up until 2 AM debugging deployment issues, learned Docker because my app kept crashing, and figured out payment integration because I had the wild idea to charge $1/month for premium features (I made $7 total).

We both applied to the same 15 companies after graduation. I got 8 interviews. He got 3. I'm not saying GPA is meaningless, but that experience taught me something important about what actually gets you through the door in tech.

What Hiring Managers Actually Look For

I've now been on the hiring side for four years. I've reviewed hundreds of resumes. You know how many times I've checked a candidate's GPA? Exactly twice — both times because the candidate put it in bold font at the top of their resume, and both times it was 4.0 (which is impressive, but it didn't change my hiring decision).

What I do look for: evidence that you can build things. Not homework assignments or class projects that 200 other students also completed — something you chose to build because you were curious or wanted to solve a problem. That signals motivation, self-direction, and the ability to work through ambiguity, which is literally what the job is.

What Makes a Side Project Stand Out

Not all side projects are equal. A calculator app or a to-do list won't impress anyone — those are tutorial projects that demonstrate you can follow instructions, not solve problems. Here's what actually gets attention:

It solves a real problem (even a small one)

The best side project I ever saw in an interview was a Chrome extension that automatically saved the user's place in long web articles. Simple concept, real use case, clean execution. The candidate talked about getting 2,000 users from a single Reddit post. That's a better story than any 4.0 GPA.

It has users (even a few)

Deploying something and getting real users to interact with it teaches you things that school never will: dealing with edge cases real humans create, handling server costs, writing documentation, fixing bugs under pressure. If your project has even 10 active users, mention it. That's infinitely more impressive than a project that only runs on localhost.

You can explain the technical decisions

"I used PostgreSQL instead of MongoDB because my data was relational and I needed ACID transactions for the payment flow." That sentence tells me more about your engineering judgment than a transcript full of A grades. The ability to explain why you made certain choices — and what tradeoffs you considered — is exactly what we evaluate in interviews.

It's on GitHub with readable code

A clean README, organized code, meaningful commit messages. These are signals that you care about craft. I've seen candidates get rejected because their "impressive" project had zero documentation and variable names like x, temp, and thing2. Show that you write code for humans, not just compilers.

Project Ideas That Actually Get You Hired

If you're stuck on what to build, here are patterns I've seen work well:

• A tool that automates part of your own workflow. Built a script that formats your commit messages? Turned it into a VS Code extension? That shows initiative and practical thinking.
• A clone of a real product with a twist. Don't build "another Twitter clone." Build "Twitter but for book reviews" or "Slack but for neighborhood communities." The twist shows creativity while the clone shows you can build real software.
• A data project with a story. Scrape public data, analyze it, and build a visualization. "I analyzed 50,000 job postings to find the most in-demand skills" is both a great project and a great interview talking point.
• An open-source contribution. Contributing to an established open-source project demonstrates that you can read other people's code, follow contribution guidelines, and collaborate. Even fixing documentation or small bugs counts.

When GPA Does Matter

I should be fair — GPA isn't completely irrelevant. A few situations where it still carries weight:

• Quantitative roles (quant trading, certain ML research positions) where academic rigor is directly relevant
• Fresh graduates with no work experience and no projects — GPA becomes the only signal
• Graduate school applications still care about undergraduate GPA
• Some government and defense contractors have GPA minimums baked into their requirements

But for the vast majority of software engineering roles? Your GitHub profile speaks louder than your transcript.

The best strategy is building projects that give you stories to tell in interviews. When someone asks "Tell me about a technical challenge you faced," pulling from a side project where you had full ownership is way more compelling than talking about a homework assignment. And if you want to sharpen those interview stories, practicing with an AI interview copilot can help you refine how you present your work. Check out our thoughts on whether a CS degree is still worth it in 2026 for more on this topic.