My approach to technical interviews has not changed over the past many years of interviews I have done. Sure you get candidates that slip through the cracks and look good during the interview, but that gets figured out pretty fast once they start.
What I look for in a Developer
When hiring any technical resource I’m always looking for the same characteristics;
- Are you a problem solver?
- Do you have a willingness to learn?
- Do you need constant supervision?
- What is your technical level?
Will you work to solve problems or give up, if you don’t know the answer will you go and try to figure them out, while you’re doing that work do I need to watch over and help you every step of the way and where are you starting from?
I don’t look for a regurgitation of facts or get any examples from the internet (because if I can get them there so can you). I tried coding tests and those were an utter failure — we have intellisense, prettier, IDEs for a reason that are designed to help us code better so we don’t have to memorize semi-colon spacing and brackets.
I am interviewing you, about what you have done, what you have accomplished, and whether with that background you can…
