Hacker News new | past | comments | ask | show | jobs | submit login

Ugh. This reminds me of when I interviewed with Google some years ago. It's a somewhat long and boring story, but basically, it was a distributed map-reduce problem. I clearly stated my assumptions and asked for clarification/confirmation so we could disambiguate. The interviewer and I were very clear what he was asking and what I would be answering.

So I proceed to answer the question, describing what I was doing and writing code, and at one point he stops me to say, "That won't work because X may not be the case." But X was one of the points of clarification up-front, so I called him out on it politely but firmly. I wasn't sure if it was [a] a language thing (he's a non-native English speaker with a fairly heavy accent), [b] an issue with experience (he was being reverse-shadowed in the interview), [c] him trying to test soft skills in some really bizarre way, or [d] some bullshit that won't fly.

I have no real problem with a,b,c, though the more experienced engineer doing a reverse shadow should step in when things go amiss, so I fault that engineer for jumping in. But regardless, I was thoroughly nonplussed by the way Google runs interviews, and I've essentially sworn them off. It wasn't until Facebook that I found a company that I want to work for even less.




But everyone loves FAANG

Where would you want to work?




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: