4 ms·
Being a developer myself, I agree with most of the things. I learnt this in a different way though. When we started RemoteInterview.io, we started as real time
by munirusman 12y ago
Being a developer myself, I agree with most of the things. I learnt this in a different way though. When we started RemoteInterview.io, we started as real time coding interview tool [0]. Even Though, it's really helpful for interviewer to watch candidate code in real-time, we soon realized that a number of candidates don't like to code under stress.
We then developed RemoteInterview.io Tests [1]. It's a screening platform based on coding tests where candidates solves the challenge in offline mode whenever they want. Some candidates still don't like to have time limits but I personally think it is important to have a deadline for every task because in real-world, no project can have infinite time.
[0] https://www.remoteinterview.io/features-interview https://www.remoteinterview.io/features-interview
[1] http://blog.remoteinterview.io/post/109864123971/screen-candidates-using-programming-tests http://blog.remoteinterview.io/post/109864123971/screen-cand...
- kasey_junk 12y agoWhat sort of time limits are you talking about? If its on the order of "we'd like to have this back in the next week or so, unless you have something else going on?" I'll buy it. If it is "you need to complete this problem in 2 hours from the time we on our server observe an arbitrary event", that would be a complete non-starter for me. A) those deadlines quite simply do not exist in the real world and B) it adds a whole level of stress to some candidates, much like the stage fright stress, that is unnecessary.
- asadlionpk 12y agoI think it completely depends on the task given. If it's a quick question or some MCQs, I think giving X hours is fine. If it's something like "design this project/prototype" then a week should work.