Introductions, a refactoring pairing exercise in C# and some questions. The pairing exercise was unfit for purpose as it was too basic (think junior developer level) to form an opinion about the ability or otherwise of a lead developer. In addition, the requirements were written poorly so it was difficult to follow given the time constraints, and there were clear mistakes in them (which the interviewer acknowledged). If the exercises are going to be used to judge a candidate, they need to be written well and as objectively as possible, and in a way that would allow a candidate to show their skills. These did neither. The interviewer also didn't know about a key C# rule that static class can only have static members, and not instance variables, for example, which had a direct impact on one of the exercises. It's not a big deal, as one can't know all the intricacies of a given language, but if you're going to judge candidates so rigidly on a programming exercise, you'd best get all your facts right! On the bright side, the interviewer was friendly and explained the role and expectations well.