Hacker News Reader

"an architecture challenge" oooh, these are the worst :)

I can usually research a decent solution for most "architectural challenges" in 15-30 mins, but I find it so difficult to have on my brain rolodex a wide variety of possible answers and probe live which of them will not disappoint a specific interviewer :)

View on HN

Again, this is mainly for screening and understanding what the candidate knows. There's no single right answers: some candidates will talk about assets caching, others will focus on software optimizations, others on infrastructure, or database...

High availability is one of our core problems, so a candidate must be familiar with at least some of the answers. And again, we still guide the candidate on the different points if they're stuck ("what about the db?", "what if the clients are in the US and in Europe?", etc.)

If an interviewer expects a single "right" answer, they're doing it wrong.

Reply on news.ycombinator.com