For most engineering and technical roles, a recruiter or hiring manager checking your GitHub profile isn't an edge case anymore — it's close to standard practice. That means your GitHub is functioning as a second CV, whether you've treated it that way or not.
Not your total commit count, and not a green contribution graph for its own sake. What actually gets read: whether your pinned repositories have clear READMEs, whether recent activity looks genuine rather than abandoned, and whether at least one project shows you finishing something end-to-end rather than a folder of half-started experiments.
GitHub lets you pin six repositories to the top of your profile — use all six deliberately. A tutorial-following clone and three forks of other people's projects tell a very different story than two original projects with real README files and a couple of contributions to something you actually use.
A one-line description and no setup instructions wastes the project underneath it. A short README — what it does, why you built it, one interesting decision you made — turns five minutes of browsing into an actual impression, instead of a shrug.
A profile with no activity in the last year reads as inactive even if you've been coding constantly at a job with a private repo. A couple of small, real public commits a month is enough to keep the signal alive.
A GitHub username buried at the bottom of a CV in 8-point font gets skipped. Surfacing your actual repositories — not just a link, but the repos themselves, their descriptions, languages, and star counts — directly on your CV page is exactly why myCv pulls your GitHub content in live rather than treating it as one more outbound link nobody clicks.
Your GitHub doesn't need to be perfect. It needs to look like the profile of someone who's actively building things — because for a technical role, that's often the fastest way to prove it.
Ready to build yours?
Join for free