The folks at Karat offer resources and services to help you nail down your interview techniques and processes (https://karat.com/guide-to-technical-interviews/).
On Technical Interview Questions
Not every question is a good interview question, even if it’s a proxy for a large task that the job entails or asks about a real-world problem. Asking a software engineer to discuss their previous work or how to solve a real-world problem usually results in a lengthy answer. The reason: Software engineering requires understanding the problem being solved, frameworks, protocols, dependencies, and the codebase. You run into the same constraints of an ideal interview — an interview takes an enormous amount of upfront effort for a marginal benefit.
As an interviewer, you should be very cautious about using technical questions on complex topics. Generally speaking, the rule of thumb to use is to keep technical questions very, very, very, simple. Otherwise you risk spending a whole lot of interview time learning very little about the candidate.
If you have good information about a candidate's background with regards to education, past project successes, online work portfolios, access to trusted former colleagues, etc, you can likely skip right past most of the technical questions anyway and keep your interviewers focused on their own important engineering work.
On Interview Interactions
Providing a great interview experience to the candidate is important, and interviewers play a key role. Good interviewers put candidates at ease, deliver questions clearly and unambiguously, and partner with candidates to bring out their best performance. They also practice asking questions about the core competencies that matter to the organization.
Practice is important! Many interviewers are very nervous, not terribly confident in their evaluation or communication abilities, and this only increases anxiety for the candidate and will negatively impact your results. However, interview skills can be learned!
Comments