3 ms·
I had a similar experience with Amazon many years ago but my takeaway was "don't work at Amazon" not "don't do technical interviews". I've had great technical i
by ng12 6y ago
I had a similar experience with Amazon many years ago but my takeaway was "don't work at Amazon" not "don't do technical interviews". I've had great technical interviews (Google, Square) and terrible ones (Amazon, Stripe). Companies you want to work for are cognizant of this and spend time developing their process and training their interviewers to make sure their experience is one of the good ones.
- FireBeyond 6y agoCertainly. I had a really good interview recently that was entirely technical, but none of this. It was a "this service is down, walk me through your process of isolating and debugging". If I said "I'd check these logs or services" then I'd get answers. And I'd get architecture described. Was more a technical problem solving and thought process exercise than "prove you know the same technical trivia I do".
- pjmlp 6y agoI cannot relate to, after two miserable phone interviews with Google I told them on their third request, that if my CV looks so great (by their own words why they were reaching out to me) and yet I had to deal with such interview processes better not bother me ever again.
- erikpukinskis 6y agoIt’s a stochastic process. Some percentage of Google interviews are bad. As a job-seeker you are drawing a few samples from each company and you make a judgement. The bigger the company the more variability in experiences. So you make a decision with imperfect information. But it doesn’t really matter because even if you have perfect information through the interview that’s still an imperfect measure of how the job will be. It’s all stochastic so the only way to get a good outcome is to iterate—guess, evaluate, try again until you find something you like.