Nowadays I'm starting to think technical interviews are only for junior devs and for most other people you really can't get enough benefit for them to bother with spending time on them.
You can't get an accurate idea of a person's skills with a technical test, and you'll end up having to rely on a trial period anyway. Just have a more of an informal chat -type thing to talk about passions, free form explanations of experience, trying to ensure a culture fit. Make sure they seem to fill your rough requirements on what you want from the hire based on their CV before that.
However, for all of the people having to go to interviews of any kind, I also wrote up something a few months ago, hope it helps: steemit.com/life/@lietu/how-to-do-...
Kim Arnett [she/her] leads the mobile team at Deque Systems, bringing expertise in iOS development and a strong focus on accessibility, user experience, and team dynamics.
This article is designed for people going into technical interviews, not for those who are creating them. And low blow linking to your own article after discounting this one.
Discounting this one? Where exactly did I do that? Also I'm really not sure what you're saying about going vs creating, sure seems to me like both have tips about going to technical interviews.
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.
Nowadays I'm starting to think technical interviews are only for junior devs and for most other people you really can't get enough benefit for them to bother with spending time on them.
You can't get an accurate idea of a person's skills with a technical test, and you'll end up having to rely on a trial period anyway. Just have a more of an informal chat -type thing to talk about passions, free form explanations of experience, trying to ensure a culture fit. Make sure they seem to fill your rough requirements on what you want from the hire based on their CV before that.
However, for all of the people having to go to interviews of any kind, I also wrote up something a few months ago, hope it helps: steemit.com/life/@lietu/how-to-do-...
This article is designed for people going into technical interviews, not for those who are creating them. And low blow linking to your own article after discounting this one.
Discounting this one? Where exactly did I do that? Also I'm really not sure what you're saying about going vs creating, sure seems to me like both have tips about going to technical interviews.