After the CV passes and the first conversation goes well, most leads will look at your GitHub or portfolio before they move to a deeper technical discussion or an offer. They are not looking for a polished profile with hundreds of stars. They are answering a narrower set of questions about how you actually work.
They want evidence that you can own something end to end. A repository where the commit history shows you making decisions, handling tradeoffs, and shipping changes without constant back and forth tells them more than a list of technologies on a CV. They notice when the README or the issues show clear thinking about the problem being solved, rather than a pile of code with no context. They look for signs that you document what matters and leave enough behind for someone else to pick up the work later.
What tends to get discounted is activity that looks like maintenance or minor contributions with no clear ownership. A long list of small pull requests across many repositories can read as someone who executes tasks well inside someone else's system. That is useful, but it does not tell the lead whether you can drive work forward when the requirements are incomplete or the direction is still forming.
