I've talked to a few different hiring managers and recruiters about for the sake of my own project[1] this so I'll share what I've learned here (this applies mo

I've talked to a few different hiring managers and recruiters about for the sake of my own project[1] this so I'll share what I've learned here (this applies more to GitHub/portfolio than resume): - Projects should have a clear README explaining what it is and why it exists. Some hiring managers will dive into the code properly but others simply won't have the time and are looking to get a good overview. Both groups want to see a clear README that explains what the project is about and ideally provides a link or some screenshots if relevant. Things like installation instructions should be there as a component of good documentation, but don't expect them to actually go to the effort to do install and run things, most won't. - Curating your GitHub profile a little can make their lives easier. Simplest way to do this is by pinning your best repos. Consider removing (or making private) things that might be considered "clutter" like e.g. forks that you haven't done anything with. - Having good, atomic commit messages, and clear, helpful comments on issues, prs, etc. is good, but many simply won't go into this much depth. - Having detailed, well-written blog posts about technical issues can definitely be impressive. As with your code, a hiring manager may often just skim this, but all they need to come away with is the impression that "this person knows their stuff". - As said in another comment, things like typos and grammar mistakes are a big no-no, especially on resumes. [1] - https://profiled.app https://profiled.app (tool for generating a portfolio site from a GitHub account)