When I'm interviewing for software roles, I rarely look, and when I do, I don't look deep. I look to get some ideas of problems that the candidate has solved - same with any job listed, or publications. Then I'm going to start with "tell me about project X", "how did you approach it", "what did you learn", "were you surprised by anything" and similar questions.
With respect to "what to put there" - don't put anything in front of an interviewer that you're not comfortable talking about. Also, you never know when you'll be interviewed by someone who is the expert in the topic.
Came across this post randomly. It is great! I already updated my repo and will keep tinkering. Thank you!
When I'm interviewing for software roles, I rarely look, and when I do, I don't look deep. I look to get some ideas of problems that the candidate has solved - same with any job listed, or publications. Then I'm going to start with "tell me about project X", "how did you approach it", "what did you learn", "were you surprised by anything" and similar questions.
With respect to "what to put there" - don't put anything in front of an interviewer that you're not comfortable talking about. Also, you never know when you'll be interviewed by someone who is the expert in the topic.