3 ms·
Been an interviewer and interviewee recently, so being on both sides of the track has given me some perspective. This is the current process that I think is fa
by scanny 4y ago
Been an interviewer and interviewee recently, so being on both sides of the track has given me some perspective.
This is the current process that I think is fair and holistic:
1. meeting with the candidate, our manager, and some devs talking about their past exp., our company, our team, and their wants
2. Take home coding task based on our day to day work: This is linear with direct instructions for inputs and outputs; there is an optional part at the end for testing more tricky concepts. They are instructed to write clean and clear, no stress if they don’t finish, take their time with a week to do it (it’s a few hours work).
3. Interview with them walking through their code on their machine and describing their thought process, field questions from them if any are left.
Then we decide by a team discussion afterwards.
Gives them their space to think, reduced pressure for candidates who are socially pressured.
Thoughts?
I personally detest leet code as a recruiting tool.
- occupant 4y ago> there is an optional part at the end for testing more tricky concepts. If the candidates are anything like me then any optional or bonus features will be considered mandatory. I have no way of knowing what percentage of other candidates do the optional work and so I have no way of accurately assessing the risk of not doing the optional work myself. I will ignore your suggested timebox if the optional work will take longer and then I'll be a little pissed off at you for how long your take home assignment took me.
- scanny 4y agofair points, is there a way we could make this fairer to people in terms of their time? Scrapping it or just making it expected and defining it?