1 / 5
What is the purpose of a GitHub profile README?
-
-
-
-
Profile README: create a repo named exactly your GitHub username, add README.md. Key sections: bio, skills (tech stack icons), pinned repos, stats widget, contact. Key vocab: "profile README", "GitHub profile page", "pinned repositories", "contribution graph".
2 / 5
Which repositories should you pin on your GitHub profile?
-
-
-
-
Pinning strategy: 6 pin slots. Mix: personal projects (initiative), OSS contributions (community), professional demos (work quality). Well-documented README with screenshot > star count. Key vocab: "pinned repository", "profile showcase", "live demo link", "repository credibility".
3 / 5
How should you write your GitHub bio (150-character limit)?
-
-
-
-
GitHub bio formula (150 chars): role + focus + differentiator or CTA. Technical focus > HR buzzwords ("passionate developer"). Key vocab: "GitHub bio", "technical positioning", "differentiating statement", "call to action (CTA)".
4 / 5
What does your contribution graph tell a recruiter viewing your profile?
-
-
-
-
Contribution graph: "green squares" = activity signal. Recruiter reading: consistent activity (positive) vs. sporadic bursts. Private contributions invisible unless enabled. Key vocab: "contribution graph", "activity streak", "private contributions visibility", "GitHub activity signal".
5 / 5
Your README includes shields.io badges — what purpose do they serve?
-
-
-
-
shields.io badges: CI badge (tests pass = code works), coverage badge (you test), version badge (actively maintained), license badge (open for use). Key vocab: "status badge", "CI badge", "coverage badge", "shields.io", "repository credibility signals".