1. 3
  1.  

  2. 4

    In my experience as an interviewer, few things were more surprising than “I’m a senior architect. I don’t need to demonstrate my ability in an interview.” Wowzers. First time I wasn’t quite ready for it. After that, it went straight to “nice to meet you. Here’s the door. Good luck.”

    1. 2

      I think that focusing on years of experience is a big mistake, but for different reason. The article states that experience doesn’t matter near as much as talent or aptitude. I think that experience gives you the opportunity to learn and keep progressing but doesn’t imply you took advantage of that opportunity.

      I’m on the fence when it comes to “recruiting for the other team”. I’ve been at large companies where sometimes a candidate really is best for another team. Let’s say they don’t know the difference between a process and a thread, but they’ve been doing angular for 2 years (and before that backbone, dojo/jquery, etc). I wouldn’t hire them for one of my backend teams, and I’d consider their knowledge deficient, but they could provide lost of lift to the team building the company’s apps. Engineering skill isn’t a one dimensional quality.