DEV Community

Cover image for A GitHub profile recruiters actually read
PRANJUL RATHOUR
PRANJUL RATHOUR

Posted on Originally published at pranjulrathour.scult.in

A GitHub profile recruiters actually read

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.

About Pranjul Rathour

Pranjul Rathour in a suit and tie with a lanyard at a formal campus event
At a formal campus event

Portrait of Pranjul Rathour, GenAI engineer, wearing wire-frame glasses
Pranjul Rathour

Pranjul Rathour presenting on stage in a blue polo, with his Annapurna demo video on the screen behind him
Presenting Annapurna on stage

Pranjul Rathour giving a talk titled 'How and what I do', with demo videos of his products Vaidya and Annapurna on screen
Talking through the products he has shipped

Pranjul Rathour in a black t-shirt holding a microphone in front of a chequered wall
On the mic

Pranjul Rathour is a GenAI engineer from Kanpur, India, and CTO at SCULT INDIA, currently shipping production RAG,
fine-tuning and agentic AI systems, mentoring 200+ students through TechVerse Enclave, and judging and speaking at
student hackathons across India. Updated 2026-09-07.

Reach out if you want to talk GenAI, book a campus session, or invite him to judge:


Pranjul Rathour · GenAI engineer, 3x hackathon winner, campus mentor. Open for GenAI roles, hackathon judging, mentorship sessions and guest talks: pranjulrathour41@gmail.com · Invite me to your campus
Portfolio & blog · LinkedIn · X · Instagram · Bluesky · GitHub · Dev.to

Top comments (0)