The classic start-and-end-of-the-interview questions can tell you a lot if you listen carefully to how they respond and ask follow-up questions: - What do you

The classic start-and-end-of-the-interview questions can tell you a lot if you listen carefully to how they respond and ask follow-up questions: - What do you know about the company already? - What is it that excites you about this role? When discussing previous projects, after covering the technical side, I will ask specific questions about how their work impacted the bottom line or what difference it made to the business as a whole; not necessarily looking for something financially quantifiable but for something that indicates they understand how dev fits into the bigger picture. For graduates, I will actually take an interest in their extracurriculars and side projects, these can reveal a lot about whether they have any commercial nous as well as technical chops. I will generally come up with some hypothetical on-the-job situation where there may be some perceived conflict between business needs and the ideal developer scenario, asking them to walk through how they might go about resolving the situation, how they would communicate, what questions they would ask and of whom, all the while looking for answers that suggest a leaning towards teamwork, collaborative problem-solving that encompasses more than just lines of code, and hopefully some kind of rudimentary understanding of what drives a business. Also, I will generally look for the Spolsky dyad of "smart" and "gets things done" [0] [0] https://www.joelonsoftware.com/2006/10/25/the-guerrilla-guide-to-interviewing-version-30/ https://www.joelonsoftware.com/2006/10/25/the-guerrilla-guid...