Curating a list of issues on open source projects for job interview
1–7 of 7 posts
Re: Curating a list of issues on open source projects for job interview
#2I'd prefer a take home project instead. I recently implemented poker and chess and really enjoyed it.
Re: Curating a list of issues on open source projects for job interview
#3It would be interesting to see this implemented as an experiment.
On the one hand, I'm not expecting high signal from this because it's not standardized - too many external variables you can't control. It would also be pretty hard to evaluate as "just watching the path of struggle" is very subjective.
On the other hand, potential "public good" benefit can't be ignored, plus it can be added to interviewees' public resume/github account to be shown to the future employers.
Re: Curating a list of issues on open source projects for job interview
#4Yes, I love this idea! It also raises a very important issue for me that goes unnoticed on interviews: the ability to debug/troubleshoot something random.
Re: Curating a list of issues on open source projects for job interview
#5At first sight idea seems to be good however I'm wondering if "officially" turning OS projects into job market sieve in long term could not lead to associating contribution to OS projects with mandatory unpleasant chore. I mean - a lot of coders do like to solve coding puzzles like Advent of Code but I get impression that similar thing in the form of LeetCode is commonly hated to some degree.
Maybe it's because problems are constructed differently but my suspicion is that it may be also connected to the fact that job interviews can be stressful and not pleasant experience and humans like to avoid stressful experiences if possible.
Re: Curating a list of issues on open source projects for job interview
#6If I remember correctly, Stripe does this (or used to?) during some of their software engineering interview rounds.
Re: Curating a list of issues on open source projects for job interview
#7It would be interesting to see this implemented as an experiment. On the one hand, I'm not expecting high signal from this because it's not standardized - too many external variables you can't control. It would also be pretty hard to evaluate as "just watching the path of struggle" is very subjective. On the other hand, potential "public good" benefit can't be ignored, plus it can be added to interviewees' public res…
Being able to regurgitate a memorized dynamic programming solution during an interview is already a pretty subjective signal which does not take into account the candidate's history or experience. I personally think that the real signal leetcode style interview provides is confirming that the candidate has a good work ethic and sticktuitiveness.