Anvil Career
Get Your Report
Back to Blog
PORTFOLIO AUDIT

Your GitHub Profile Is Getting You Rejected. Here's the 30-Minute Audit That Fixes It.

•8 min read

A recruiter opens the GitHub link on your resume. They have approximately 30 other profiles to review before lunch. They will spend 30 seconds on yours — maybe 60 if something catches their eye. In that time, they are running a specific 5-point scan. They are not reading your code. They are not admiring your commit streak. They are answering five yes/no questions about whether you look like a professional developer or a student who uploaded their coursework. If the answers to more than two of these questions are "no," they close the tab and move to the next candidate. Here is the scan, the questions, and exactly what to fix today.

THE 4 QUESTIONS EVERY RECRUITER ASKS WHEN THEY OPEN YOUR README

THE QUESTION WHAT A BAD README SAYS WHAT A GOOD README SAYS
What does this project actually do? "A full-stack MERN application" (could be anything) "A placement management dashboard that lets TPOs upload company schedules, students track application status, and generates aggregate statistics for NAAC reporting."
How do I run this on my machine? No setup instructions. Or: "Clone the repo and run npm start" (fails because no env vars, no DB instructions) "Prerequisites: Node 20+, PostgreSQL 16. Clone repo. Copy .env.example to .env. Run: npm install → npx prisma migrate dev → npm run dev. App runs at localhost:3000."
What does the architecture look like? No architecture description. Or a screenshot of the login page. "Tech stack: Next.js (App Router), PostgreSQL (Prisma ORM), JWT auth. Data flow: Client → Nginx → Next.js API routes → Prisma → PostgreSQL → JSON response." Plus a Mermaid diagram.
Is this project deployed and working? No URL anywhere in the README. Or: "Coming soon." First line of README: "Live at: https://placement-dashboard.example.com" — with HTTPS, working, and the link is above the fold.
IF YOUR README DOES NOT HAVE A LIVE URL ABOVE THE FOLD, THE RECRUITER ASSUMES IT IS NOT DEPLOYED

The most common failure mode on student GitHub profiles is the missing or buried live URL. A project without a live URL is indistinguishable from code that was never tested outside of localhost. The recruiter does not need to spend 30 seconds scanning your code to reach this conclusion — they just need to look at the top of your README and not see a link. Fix this in 5 minutes: buy a ₹99 domain, point it to your VPS, add SSL, and paste the URL as the very first line of your README after the project title. It is the single highest-ROI change you can make to your GitHub profile.

Git Commit History: The Single Dump vs. Professional Incremental History WHAT RECRUITERS SEE: THE SINGLE DUMP abc1234 — initial commit (8,432 lines) Recruiter reads this as: "This person copied the entire codebase and uploaded it at once. They do not use version control the way a professional developer does." WHAT RECRUITERS SEE: PROFESSIONAL INCREMENTAL HISTORY feat: implement JWT authentication middleware (32 files, +480 -12) fix: resolve CORS configuration for API routes (3 files, +18 -5) feat: add rate limiting middleware with express-rate-limit (2 files, +45 -0) test: add unit tests for user registration and login flows (4 files, +210 -3) docs: add API documentation with request/response examples (1 file, +95 -10) Recruiter reads this as: "This developer works incrementally. They test. They document. They fix issues. They write meaningful commit messages. They know how software is actually built."

REPOSITORY NAMES: BEFORE AND AFTER

BAD REPO NAME (WHAT IT SIGNALS) GOOD REPO NAME (WHAT IT SIGNALS)
final-year-project (unprofessional, generic) placement-dashboard (specific, professional)
MERN-app (tutorial clone) inventory-api (production-oriented)
placement-project (lazy naming) attendance-tracker (clear purpose)
todo-v3 (third attempt at a tutorial project) task-scheduler (real utility)
college-website (could be anything) campus-event-portal (specific domain)
react-app (framework as identity) expense-splitter (problem as identity)
THE 30-MINUTE AUDIT: DO THIS RIGHT NOW

01. Open your GitHub profile. Are your 2-3 best projects pinned to the top? If not, go to each repo → Settings → "Pin to profile." A recruiter will not scroll past your pinned repos. If your best work is buried on page 2, it does not exist. 02. Open your best project. Is there a live URL at the top of the README? If not, deploy it now. Buy a domain. Add SSL. Add the URL. This takes 2 hours, not 2 weeks. 03. Does your README answer: what does this do, how do I run it, what is the architecture, is it deployed? If any of these are missing, add them. 04. Open the commit history. Is it one commit or a series of incremental ones? If it is one commit, start a new habit today: commit every time you complete a logical unit of work. The history will build itself. 05. Are your repo names professional? Rename repos that sound like coursework. GitHub allows renaming without breaking links. 06. Check your contribution graph. Is it mostly green in the last 3 months, or mostly grey? Daily commits — even small documentation updates — fill the graph and signal consistency.