| Coding questions are often not the toughest interview questions. Tough questions could be some "soft" non-coding questions like: design questions (how to design a class hierarchy for a blog), behaviour questions (if your boss is wrong, what to do?), experience questions (why did you use tool X in your previous project Y? I think tool Z is better.) Those questions are tough because your performance on those questions are very subjective. It depends highly on if the interviewer likes you or not. Coding questions can be tough, but they are much more objective. Google's engineering interview mostly asks coding questions. Questions can be difficult, but at least, if you write great code, you will pass the interview. In this sense, Google is not a very tough company for job interview. In general, the degree of interview toughness depends on the job supply/demand ratio. When many people apply for positions at company X, the company has to apply a high-rejection rate, based on whatever (sometime very random) criteria. |