4 ms·
When I was making interview questions, I always tested then on my teammates first. Not on all of them, that'd take too much time, but on some of them. If there
by theamk 5y ago
When I was making interview questions, I always tested then on my teammates first. Not on all of them, that'd take too much time, but on some of them. If there are no time for that, take your estimate and multiply by 5x.
(We do not did not do take-home tests though, those were in-person coding tests).
- lomcs 5y agoDoes it make you feel smarter when you give people tests?
- theamk 5y agonot really? The tests are fairly basic - there are just not very many tasks that are (1) can be done in <10 minutes (2) are not "aha!" questions and (3) interesting. If you can solve the programming task like this, it is basic proficiency, not something to be smart about. An analogy: being able to do programming tests is like being able to calculate percentage ratios in the high school. Yes, there are plenty of students who cannot do that - but they are not interested in math. And for the students who are interested in math, the "percentage" problems are so simple it is not even worth mentioning. Also, a bit of general advice: when you work in software, you don't usually want to be "the smartest person in the group" - this can easily lead to lack of professional development. You want to work with people who are smarter the you are, because you can learn from them.