Make your tech interviews more humane
The following paragraphs attempt to draw out the changes that a data-driven technical interview can bring to the recruitment process, and how these changes can serve you with an objective and informed process.
Lending a window to quality conversations
Here are a few data-points that could lend a richer context and help shed the ambiguity from a technical interview's flow, while also enabling you to understand your candidates reasonably.
A window into their experience on previous projects that sheds light on their primary inclinations and interest areas
- It helps you avoid misalignment of talent with the requirements of a job role at the most initial step.
- It ensures a proper alignment - helping you keep your talent driven and engaged with their job over a wider span of time.
Conversations circling a candidate’s past and present contributions across Social forums such as GitHub and Stack Overflow
For instance, a single glance at this GitHub profile would help you --
- Observe your candidate’s work contributions over a period of time – thus opening a window to discussing and understanding their technical inclinations and projects in a crisper manner.
- Observe their activity patterns over a span of time as they make contributions to projects
- Help you pin down their technical proficiencies from their contributions across projects
- Also, platforms such as Stack Overflow help you understand your candidate’s problem-solving capabilities along with the breadth and depth of their technical knowledge basis their answers and accuracy.
Shifting from the dependency on a mere score towards conversations that revolve around technical efficiency
Certain practical aspects such as the ones mentioned below would help map out their skillsets more realistically.
Understanding the types of coding violations that occur in a candidate’s solutions, and what it implies
For instance, observe the code solution after it has run through DoSelect’s engine -
Our assessment engine points out the various forms of coding violations such as -
- Complexity in the code
- Vulnerability to bug risks
- Vulnerability to Security issues
- Improper code implementation leading to Performance errors
Adherence to the best programming practices in their solutions
A candidate’s code lends a wider historical context on their technical capabilities over a period of time. Some of the key particulars that our testing framework helps draw out from their code are –
- Understandability and usability of code
- Adherence to a language’s style
- Instances of duplication or redundancy in the code
Wider Historical Contexts that gauge a candidate’s technical acumen objectively and exhaustively
Some of the best resources that help you gauge such evolutions are social forums such as GitHub and Stack Overflow. GitHub gives you a wider perspective on a candidate’s work and contributions over a period of time, an insight into the frequency activity, their best and worst coding practices, and their grasp on concepts based on their contributions and popularity (for forums such as Stack Overflow).
DoSelect’s Crunch ties in a candidate’s social profiles. By putting together relevant information about a candidate’s technical contributions across GitHub, Stack Overflow and DoSelect.
Insights such as these serve as conversations that help them relate and understand to the work they’re being interviewed for. As is always the case, a data-driven perspective is equipped with clarity, and the power to make informed and sensible decisions – decisions devoid of subjectivity. At DoSelect, we strive towards imbibing our tech sphere with this understanding every day.
Till next time.