A framework for shaping scenario interviews that offer candidates a great experience — and your team vital evidence for quality decisions.
Scenario interviews are one of my favourite tools for collecting this evidence for product roles, because behavioural characteristics are so much of what makes a strong candidate a terrific asset to the team.
Thoughtfully constructed and facilitated, a scenario can give terrific insight into the candidate’s thought process, communication preferences, and professional behaviours.
But poorly structured and haphazardly run scenarios lead to confusion, poor performance on the day, weak decisions by the hiring team, and leave the candidate with a poor perception of your company.
In my experience, most organizations run bad scenario interviews.
In this article I will try to help — by outlining two models that most scenario interviews fall into, explaining why the collaborative model is my preferred approach, and offering five concrete things you can be doing to make your scenario interviews a valuable experience for everyone involved.
I’ve been through numerous scenario interviews in my career. Some great, others have been awful. All have fallen more or less into one of two models. I call them ‘figure it out’ and ‘discover, together’.
In this model, the candidate is given an outline of a problem or opportunity by the interviewers–usually in writing, sometimes verbally–and is told to work through the problem.
The interviewers take a largely passive observer role by default, though they may provide prompts if the candidate appears to get stuck. If the candidate wants the interviewers to engage in the process, they must actively invite them to do so.
My worst experience with a scenario interview followed the ‘figure it out’ model.
I arrived at the office, was eventually greeted at the door, and led to a narrow room that barely fit a long table and the dozen chairs set around it. The table held a few scrap post-its and a couple of unpromising whiteboard markers. The wall was filled with old scrawls.
The two interviewers sat on one side of the table; I squeezed in between the whiteboard wall and the table on the other side.
After an hour or so of questions back and forth, the interviewers announced it was time for the scenario/whiteboarding exercise.
It's been over 6 months since I joined KritiLabs. The learning that I have had been very steep and intense, considering its a career shift for me from a services based pre-sales to a product based pre-sales and product management.
What is API product management and what can you be doing to be a better API product manager — get aligned with SaaS and enterprise software requirements. This guide lays out what is API product management and some of the things you should be doing to be a good product manager.
Digital Assets Management Software helps an organization or business to upload, store, organize, manage, share, and track digital assets in one place. Our AI-based Assets Management System allows companies to unite their asset data on the intelligent blockchain network.
Product features, the atom, and usability
Top Android Interview Questions & Answers from Beginner to Advanced level. Get ready to crack your next android interview with these android interview questions