Hacker News Reader

I’d say if it takes you three hours you’ve already failed.

I’ve fixed a bug in memcached (improperly cleared buffer, null GETs resulting in zero prepend on next GET under high stress) during a five alarm fire and deployed it across a cluster in less than 30 minutes - and I would consider myself a mediocre devops hire.

View on HN

How would I know that the task actually takes 30 minutes before scheduling as much time they say the process would take? I presume that when they say "come in for an hour of talk and a three-hour practical task" (which the point where I'll refuse) I won't even know the task and can't already assume that I can actually be done much faster.

Right, sorry, I wandered off into the woods while writing that. They should allocate 30 minutes. Even if you don’t finish, by 30 minutes there should be a clear indication of your approach.

Reply on news.ycombinator.com