3 ms·

While I agree in principle, the average developer is not going to have released and maintained an open source project. Let alone one that is used. Let alone one

While I agree in principle, the average developer is not going to have released and maintained an open source project. Let alone one that is used. Let alone one that is widely used. People in your position should rightfully do that, you have all the leverage. Other people not so much, especially new graduates. I agree that having tasks that simulate the real environment is the goal but we also work in an industry that it is common place for productivity to only really start after 6 months. Thus, any interview is going to be some simulacrum of the real thing. Personally, I would like to see something like "Make 10 commits to X open source project and we'll talk". Make the world a better place while actually evaluating the candidate for job readiness. Both technically and behaviorally as you see how they behave in the community.

usrbinbash 5y ago
Not every developer has the time and resources to dedicate to FOSS. Some of us spend most of their working time writing software for, well, the company we work for, which won't suddenly open source their IP. Making commits to FOSS a general requirement in interviews would exclude a whole lot of highly skilled and experienced engineers, limit the chances of beginners, and lead to loads and loads of BS open source projects that exist solely to fatten resumes.
- hervature 5y ago
  First, 10 commits to an open source project is not "dedication". It feels like table stakes if we want a meritocratic process. Second, where do people get the time to work on leetcode problems? Replace that with open source contributions and/or open blog posts. I do agree that it would probably lead to a glut but that makes the interviewer's job incredibly easy if a commit is BS or not. It seems you are asking for a miracle: an interview that properly assesses the candidate's job readiness without time involvement. How much time do people spend preparing for interviews and then have to do it again the next time they want to interview? At least with this system, you have a history that is reusable.

usrbinbash 5y ago

Not every developer has the time and resources to dedicate to FOSS. Some of us spend most of their working time writing software for, well, the company we work for, which won't suddenly open source their IP. Making commits to FOSS a general requirement in interviews would exclude a whole lot of highly skilled and experienced engineers, limit the chances of beginners, and lead to loads and loads of BS open source projects that exist solely to fatten resumes.

hervature 5y ago
First, 10 commits to an open source project is not "dedication". It feels like table stakes if we want a meritocratic process. Second, where do people get the time to work on leetcode problems? Replace that with open source contributions and/or open blog posts. I do agree that it would probably lead to a glut but that makes the interviewer's job incredibly easy if a commit is BS or not. It seems you are asking for a miracle: an interview that properly assesses the candidate's job readiness without time involvement. How much time do people spend preparing for interviews and then have to do it again the next time they want to interview? At least with this system, you have a history that is reusable.