> How is a small team of programmers to know that you will be able to collaborate with them effectively within the space of an interview ? Isn't my github prof

> How is a small team of programmers to know that you will be able to collaborate with them effectively within the space of an interview ? Isn't my github profile enough proof to show that I can collaborate with people? Also, as I pointed out in my recent comment: Eran Hammer, (creator of OAuth and Hawk) presents a new way to hire engineers. He suggests the concept of a 'Homework' wherein prospective employees are presented with a problem/bug that they are actually facing in their product. One of my acquaintance from Mozilla also pointed out that he was hired in a similar way. > 2. What exactly do you mean by "competitive problems" or "puzzles"? What is off-limits? For me, competitive problems are the kind problems for which interviewstreet/codechef etc are known for. At times, they involve the kind of problems which a developer is not likely to face during his time at the company. For example, being a web developer, I don't think that there will be a time when I need to write a string matching program from scratch. Wouldn't questions related to scalability/databases/some selected data structures make more sense for such a profile? Don't take me wrong, I am not against questions involving string matching/sorting/kernel concepts, all I am saying is that they should be asked from those who are really going to face such problems while working. [1] https://news.ycombinator.com/item?id=6828411 https://news.ycombinator.com/item?id=6828411