Some things I ask for when interviewing (I'm also a Python Dev that uses Django at work): - Given an arbitrary task what framework would you use and why? I lik

Some things I ask for when interviewing (I'm also a Python Dev that uses Django at work): - Given an arbitrary task what framework would you use and why? I like hearing peoples answers to this as you get to see what they think is important as dev. Do they like a framework because it's modular? Because it is unopinionated? Because it's easy to modify? - Given a set of requirements how would you implement an API to satisfy them? I like to see what questions they ask. Are they thinking about performance? Database impact? How will they handle errors? Are they introducing coupling between resources? I'm more interested in how well you can justify your reasoning than it being the "correct" choice. You should be able to defend your choices/opinion without being belligerent. - Then there are "target of opportunity" questions. Questions that sort of just pop up during the conversation. - Lastly I ask what questions they have for me. These are important as it shows what's important to you. Some good ones I have been asked: - How much ownership do you have as a dev over a project? - How much impact do devs have on technology decisions? - Why do you like working here? I tend to ask more high level questions and don't really do a ton of whiteboarding unless the candidate feels more comfortable writing things down. During a loop we have more than one tech interview so others whiteboard questions.