This is better than a lot of the processes I've seen. But. Developers that do interviews seem to want a step by step algorithm for doing an interview... Or wo

This is better than a lot of the processes I've seen. But. Developers that do interviews seem to want a step by step algorithm for doing an interview... Or worse yet just want to throw them a topcoder style algorithm question so they can "spend" an hour on the interview and come up with an easy yes/no answer. I've been conducting interviews for about 5 years and started out doing the same. I came to realize however, that we were rejecting perfectly fine candidates. Several devs would either knock our take home puzzle out of the park or show us a great portfolio, but then would flub or stumble when the (mostly JR) devs would ask them to implement something akin to a topcoder challenge. Now, much like we expect devs to tailor their resumes to us, I tailor my interview to the person being interviewed. If you're relatively new, you might get asked some data structures / algorithm questions.. If you're senior expect to go into great detail about your past projects and design decisions. There is no process or formula. Interviewing is an art.