Thank you so much for sharing this feedback. Being the recruiter for my very small company when it's needed, I'm always struggling between building a saavy process and not making it too cumbersome for candidates to avoid making them lose their time for nothing. A lot of your feedback will be actionable for us and our candidates.
Something I like to do, but don't see a lot in interviews: instead of doing a live coding session (which I think can lead to too much stress, and is not realistic, just like when at school they ask you to write code without Internet access), I ask candidates to write a LOGBOOK.md in which they explain what they are doing, explain their choices and blockers, and even tell us about their mindset and feelings at the moment.
This gives an opportunity to also test their written communication skills - useful when they will communicate with a client, a stakeholder or write documentation - but also, they can explain why something we asked wasn't done, so we can judge how they think instead of their skills. Very useful for more junior profiles.
The real pair-programming session is a great idea though ; the "Bring-your-own coding challenge" too. Will definitely include those in our next recruitment process !
Thanks again and wish you the best at your new job and your personal life ;)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thank you so much for sharing this feedback. Being the recruiter for my very small company when it's needed, I'm always struggling between building a saavy process and not making it too cumbersome for candidates to avoid making them lose their time for nothing. A lot of your feedback will be actionable for us and our candidates.
Something I like to do, but don't see a lot in interviews: instead of doing a live coding session (which I think can lead to too much stress, and is not realistic, just like when at school they ask you to write code without Internet access), I ask candidates to write a LOGBOOK.md in which they explain what they are doing, explain their choices and blockers, and even tell us about their mindset and feelings at the moment.
This gives an opportunity to also test their written communication skills - useful when they will communicate with a client, a stakeholder or write documentation - but also, they can explain why something we asked wasn't done, so we can judge how they think instead of their skills. Very useful for more junior profiles.
The real pair-programming session is a great idea though ; the "Bring-your-own coding challenge" too. Will definitely include those in our next recruitment process !
Thanks again and wish you the best at your new job and your personal life ;)