News for hackers. Stuff that matters.
Re:Technical and non-technical tips for rocking your coding ... by golergka on Tuesday September 26, 2017 @07:34PM (#15343600)
> "do you find this more useful than questions that are more representative of the work you're expecting me to do?"

Yes, because tasks representative of the work we're expecting you to do are too obvious and simple for an interview 95% of the time, and are too hard and take too long for an interview 5% of the time.

Re:Technical and non-technical tips for rocking your coding ... by cableshaft on Wednesday September 27, 2017 @11:12AM (#15348536)
If 95% of the work you need done is too obvious and simple, maybe you don't need to hire as good of programmers as you think you do, and why are you trying to make things in the interview artificially harder than the work that needs to be done?

It's kind of like asking someone interviewing to be a cashier at a fast food restaurant multivariable calculus problems, because 95% of the math they're going to have to do at their job is "too obvious and simple".

Re:Technical and non-technical tips for rocking your coding ... by golergka on Wednesday September 27, 2017 @11:55AM (#15349076)
> If 95% of the work you need done is too obvious and simple, maybe you don't need to hire as good of programmers as you think you do, and why are you trying to make things in the interview artificially harder than the work that needs to be done?

If these high-priority and hard 5% were easily separable from the tedious 95%, this logic would be correct.