A Primer
Because oftentimes, the reverse direction is much harder. That, and candidates seldom communicate feedback to their interviewers.
Alright, so I’ve conducted a fair number of DS&A interviews on interviewing.io, algoexpert.io, and pramp.io, and if there’s anything I’ve personally learnt, it’s that interviewees badly struggle to communicate feedback to their interviewers.
And that’s understandable. Typically, interviewers are more experienced; they summarize feedback and communicate their findings : verbally or written.
But a mock setting is a a two-way street : both parties spend quality time to improve. Plus interviewers ( and for that matter, interviewing ) are imperfect. Good, seasoned interviewers know that they should practice and hone their skills in mock settings to bolster their real-world interviewing skills. By doing so, they better ensure that their future candidates are “set up” for success.
Feedback Case Study #1
- TI1 asked a question at the right rigor, difficulty, and level.
- TI focused on asking real-world relevant problem which stress-tested complex requirements gathering.
- TI had a more conversational, dialouge-esque style in their session.
- TI took extra time during their session to cogently and coherently explain complex concepts.
Feedback Case Study #2
- TI prepared level-appropriate questions : equivalency to Google L4-L5 candidates.
- TI focused on high-level details and asked questions surrounding the code : the complexity analysis, the high-level approach, and the constraints.
- TI prepared two leetcode-medium rigor level questions in event of TC2 answering the first question ahead of time.
- TI provided solid hints to help TC think of alternative approaches and optimal approaches.
- TI did a good job making TC feel comfortable during the session.
- TI provided verbal feedback during the last 5 minutes.
harisrid Tech News 
Leave a comment