What Indian Recruiters Really Check on GitHub Before Calling You

For a B.Tech student in India, your GitHub profile is no longer just a backup for your code—it's your public tech resume. With recruiters from TCS, Infosys, and fast-growing startups like Razorpay and Freshworks actively screening candidates through their code, a blank or messy GitHub can silently kill your application before you even get a call. In a market where thousands apply for the same role, your GitHub activity is a tangible filter that separates the genuinely curious builders from those who just list languages on their resume.

Why Your GitHub Matters More Than Your Resume's "Skills" Section

Your resume says you know Python and React. Your GitHub shows how you know them. Indian recruiters, especially in product-based companies and ambitious startups, use GitHub to verify self-proclaimed expertise. They are looking for proof of consistent learning, problem-solving approach, and code quality—things a one-page resume cannot convey.

A strong GitHub profile answers critical questions for a recruiter: Can this candidate write clean, maintainable code? Do they understand version control? Have they built anything beyond college assignments? For roles in development, a robust GitHub can sometimes outweigh a slightly lower CGPA, as it demonstrates practical initiative. It's your first technical interview, conducted on your own time.

The 4-Point Checklist Indian Recruiters Actually Use

While every recruiter has their own method, most follow a simple, quick-scan checklist when they open your profile. They have hundreds to review, so you have seconds to make an impression.

1. The "Green" Contribution Graph: Consistency Over Spikes

The calendar of green squares on your profile is the first thing anyone sees. It’s a visual log of your coding habit. Recruiters aren't looking for a perfect, unbroken streak, but they do look for consistency. A graph that's green only in the week before campus placements sends a clear signal of last-minute padding. They prefer a profile that shows steady, regular commits over months, indicating a genuine engagement with coding as a practice, not just an exam to pass.

2. Pinned Repositories: Your Portfolio's Highlight Reel

The six slots for pinned repositories are prime real estate. This is where you curate your best work. Recruiters scan these for:

• Project Complexity: A basic calculator or to-do app is a start, but they look for projects that solve a real problem, use multiple technologies, or have some level of complexity.
• README Quality: Is there a clear description, tech stack, setup instructions, and maybe even a live demo link? A good README shows you care about communication and documentation—a crucial soft skill.
• Tech Stack Relevance: Are your pinned projects aligned with the roles you're targeting? If you're applying for backend roles, pin that Node.js API or Python data pipeline, not just front-end clones.

3. Code Quality & Commit Hygiene

This is where the technical eye scrutinizes. They might open one or two key files in your main projects to check:

• Clean Code: Is it readable, well-structured, and commented where necessary?
• Commit Messages: Are your commits labeled with clear, descriptive messages like "fix: resolve API authentication error" instead of vague ones like "updated code"? Good commit hygiene signals professional habits.
• Project Structure: Does the repository have a logical folder structure? This reflects your understanding of organizing a codebase.

4. Beyond Code: Issues, Pull Requests, and Collaboration

For roles requiring teamwork, recruiters look for evidence of collaboration. Have you contributed to open-source projects, even small ones? Have you properly used issues to track bugs or features? A profile showing merged pull requests (PRs) to other repositories indicates you can work within a larger codebase and community—a huge plus for companies like Flipkart or Zerodha that use open-source tech extensively.

What to Build: Project Ideas That Get Noticed

Wondering what to actually put on GitHub? Move beyond tutorial clones. Build projects that tell a story about your skills and interests.

• For Full-Stack/Web Dev Aspirants: Don't just build another blog. Create a full-stack application with authentication, a database, and a clean UI. Examples: A expense-splitting app for roommates, a interview preparation tracker, or a clone of a specific Swiggy or Zomato feature with your own twist.
• For Data Science/Analytics Roles: Showcase Jupyter notebooks or scripts on repositories like Kaggle. Clean, well-documented analysis of a real-world dataset (e.g., Indian census data, stock trends, sports analytics) with clear visualizations is more valuable than multiple incomplete projects.
• For DevOps/Aspiring SREs: Show your understanding of infrastructure as code. Have repositories with Dockerfiles, CI/CD pipeline configurations (like GitHub Actions), or Terraform scripts to deploy a simple web app.
• The "Problem-Solver" Profile: Consistently solve problems on platforms like LeetCode or CodeChef, and maintain a repository where you commit your solutions with explanations. This directly appeals to companies with rigorous coding rounds.

Common Pitfalls That Make Recruiters Swipe Left

Avoid these mistakes that can instantly downgrade your profile:

• The "Hello World" Graveyard: A profile with dozens of repositories, each containing only a basic starter file or assignment PDF. Quality trumps quantity every time.
• No README.md: A blank README is like submitting a project file without your name. It shows a lack of polish.
• Pushing Everything at Once: A contribution graph with massive, irregular green blocks is a red flag for "GitHub gardening." It's obvious when all commits are back-dated or piled in a weekend.
• Sensitive Data Exposure: Never commit configuration files with passwords, API keys, or personal data. Recruiters will see this as a major security oversight. Always use environment variables.
• Forked Repositories as Main Work: Pinning repositories you've only forked (and not contributed to) as your primary work is misleading. Differentiate your original projects.

How to Learn & Build Your GitHub for Free

You don't need paid courses to build an impressive GitHub. India has an abundance of high-quality, free resources.

1. Master Git & GitHub Fundamentals: Start with the interactive tutorials on GitHub's own website. Then, watch tutorials by CodeWithHarry or Apna College on YouTube—they explain Git commands in a simple, practical way.
2. Learn to Code & Build Projects: Use platforms like freeCodeCamp (which gives you project-based certifications) or NPTEL/SWAYAM for structured computer science courses. For DSA, follow Striver (takeUforward) or Gate Smashers on YouTube.
3. Find Project Inspiration & Best Practices: Browse trending repositories on GitHub in your language of choice. See how experienced developers structure their code and documentation.
4. Contribute to Open Source: Start small. Look for repositories with tags like good-first-issue or hacktoberfest. Fixing a typo in documentation or a simple bug is a valid and respected first contribution.

Next Steps

Your GitHub is a living document of your coding journey. Start curating it today, commit regularly, and build projects you're passionate about. To find free courses that can help you build the skills for those projects, browse our curated list of top-rated tech courses. If you're specifically looking to strengthen your DSA for coding interviews, explore these platform guides and free resources. Ready to build a full-stack portfolio? Check out these project-based learning paths.