It depends on the person and my expectations for the role. The best people have everything, including jobs! So I make it a rule not to expect perfection, helps

It depends on the person and my expectations for the role. The best people have everything, including jobs! So I make it a rule not to expect perfection, helps prevent disappointment. When I'm evaluating candidates from a resume, if they have a link to a Github or personal website I'll visit it about a fifth of the time. I'll open up a couple repos and make note of what they look like. Are they school projects? That's fine but not necessarily indicative of anything since most academic code is write-once, run-once for an assignment. Does it look like a personal project? Great! This is what I'm most interested in. Is it easy to understand what the project is before reading the source code? README files and a clear directory structure/file names can go a long way here. If I look at the source code, how is the readability? Do they have good variable names (i.e. not a, b, c,..,z) and use the idioms of their programming language? Bonus points for good comments. Triple word score if I can understand the code without comments. I'll go through a couple repos this way and use whichever one is best to inform my initial bias. I think it's always a good idea to assume best intent when interviewing someone. I've had some people I wasn't that excited about in an interview become my favorite coworkers over time. PS - Here's a project of mine I'd consider a "good" example. Mostly the number of unfinished {- TODO -} comments in src/Lib.hs would hurt me here, were I evaluating myself. https://github.com/cbzehner/word-frequency https://github.com/cbzehner/word-frequency