The developer does came across as a prick. The thing is, does the company allow anybody to access the code? Probably not, because that code is very likely propr

The developer does came across as a prick. The thing is, does the company allow anybody to access the code? Probably not, because that code is very likely proprietary company information that only certain people are allow to view and modify. So from that standpoint, validating the skill set using opensource tools would be the way to go. Having an outsider view and modify internal company code demonstrates poor judgement on the part of the interview, as that code is not her/his to just expose to anybody. I would be wary of even considering that role if interviewer is willing to expose their code without considering the legal and ethical consequences of that action.