A GitHub profile recruiters actually read

How to arrange a GitHub profile so a reviewer finds the right three projects in thirty seconds: pins, a profile README with numbers, project READMEs that lead with the problem, and what to archive.

Pranjul Rathour
Pranjul Rathour

Recruiters and mentors spend about thirty seconds on a GitHub profile before deciding whether to spend five minutes. Most student profiles waste those seconds on a wall of tutorial repositories. Mine has 24 public repositories; three of them do the work, and the profile is arranged so those three are what you see.

Pin three, not six

One retrieval project, one fine-tuning or vision project, one with real users. Pinned repositories are the whole first impression; six dilute it. Each pinned repository needs a description line that states the problem, not the stack.

The profile README

  • One line of positioning and where you are based.
  • Three projects with a one-line outcome each and a link — the same three that are pinned.
  • Wins and sessions with institutes and years.
  • How to reach you. An email, not a contact form.

Project READMEs that survive ninety seconds

  1. First line: the problem and who has it.
  2. A screenshot or a short recording of it running.
  3. The numbers: users, evaluation results, performance.
  4. How it works, in one diagram or five bullets.
  5. How to run it, and a link to where it is running.
  6. What you would do next, honestly.

Archive the rest

Tutorial clones, abandoned experiments and forks you never touched can be archived or made private. A profile with five good repositories reads as focused; one with forty half-finished ones reads as noise, however hard you worked on each.

Commit history is read too

Regular, descriptive commits over months signal someone who ships. A single "final version" commit signals a copy. Push as you build — it is also the habit that saves you when a laptop dies the night before a demo.

Fix the profile in an evening, then keep it current with each project from the roadmap. It is the first thing I open when a student asks me for feedback, and the first thing a recruiter opens when they consider an interview.

GitHubPortfolioCareerStudents
Pranjul Rathour
Pranjul Rathour
GenAI Engineer · Kanpur, Uttar Pradesh, India

GenAI engineer and AI product builder with 2+ years shipping production-grade AI systems: RAG pipelines, fine-tuned LLMs, hybrid retrieval and multi-modal apps across vision, speech and OCR, architected end to end from ingestion to deployment. Leads engineering for SCULT INDIA's 14-member team, founded the 500+ member TechVerse Enclave community and has mentored 200+ students. Three hackathon first prizes: Changethon 2025 (IIT Roorkee), Product Genesis at Vividhotsava 2025 (CSJMU Kanpur) and BYTEBATTLE (MeetKats).

Open to GenAI roles, hackathon judging, mentorship sessions and guest talks at colleges. Email pranjulrathour41@gmail.com.

Keep reading

More on Career guides

All Career guides posts →
Campus talks · hackathon judging · mentoring

Want this as a live session at your college?

Open to GenAI roles, hackathon judging, mentorship sessions and guest talks at colleges.

Pranjul Rathour, GenAI engineer in Kanpur