Overall, the interview process was quick, and the recruiter and interviewers were pleasant to talk to. Though the engineers were excited by the direct impact they were making on the company, none of them expressed any enthusiasm for the actual work they were doing.

I did have trouble with one of the technical interviewers. The question he posed, as described below, did not logically lead to the answer he was looking for, in my opinion. He was looking for the usage of a very specific data structure, but the "correct" answer he gave is not good design given the question as stated. The question would have been better as a systems or API design question.

He was also too eager in giving hints that were ambiguously misleading and didn't give the candidate a chance to think. My advice to the interviewer is to rephrase the question in a better way, give the candidate some time to process and/or try different solutions, and give more helpful, direct hints only if the candidate is truly stuck, instead of smothering the candidate with unhelpful and vague leading questions that steer the candidate away from the "correct" answer.

You want to log the number of hits to a site. Implement two functions:

• log_hit(): This function gets called when a hit is registered.
• get_hits_in_last_five_minutes(): This function returns the total number of hits in the last five minutes.