No. I'm afraid you are missing the point entirely. Let's use your example as context. I am running a Scala or Ruby development team and regularly meet a lot o

No. I'm afraid you are missing the point entirely. Let's use your example as context. I am running a Scala or Ruby development team and regularly meet a lot of developers in conferences. I meet an amazing Scala developer at a conference but he seems happy in his current job and I don't want to plead with him to join our company. Lets assume this amazing Scala developer subsequently signs up to your site and selects me as someone he would like to be interviewed by. I will never, ever find out that he's interested. Why? Using your current model, I, the hiring manager, would also have to select him as someone I want to be interviewed by. The chances of this happening aren't slim, they are literally zero. Hence my question on why you don't have a SEPARATE sign in for employers so that they can list people they would willingly interview. You have potentially created an amazing tool but it's only 50% complete.