3 ms·

FAANGs are a different beast altogether. Especially at the IC level, it is 99% technical, given a normal-human-being-behavior. Then, technical the way they (ind

FAANGs are a different beast altogether. Especially at the IC level, it is 99% technical, given a normal-human-being-behavior. Then, technical the way they (individual interviewer and company) evaluate it and you don't know about, since I had a few interviews in which I was confident I did a very good job (I am not a junior...) and they got back with a rejection on technical grounds. One striking example was when I solved the coding problems posed to me in 15 minutes out of the 45 available, the interviewer said "that's great, I don't have any more questions, please use this time for you to ask about the company" and then the recruiter told me I was rejected because I did not do the coding part well enough.

jefftk 6y ago
> One striking example was when I solved the coding problems posed to me in 15 minutes out of the 45 available, the interviewer said "that's great, I don't have any more questions, please use this time for you to ask about the company" and then the recruiter told me I was rejected because I did not do the coding part well enough. That's terrible behavior from the interviewer. Did you try raising this with your recruiter?
- borroka 6y ago
  The decision is already made, there is no point, nobody is going to backpedal on anything. I remember saying: "I don't get it", but she was clueless about the interview itself. It was a company in LA with a ghost.
  - jpmoral 6y ago
    If I liked other people I'd met well enough I'd give that feedback (politely and without assigning blame), not to change their mind but just to let them know.
tootie 6y ago
The one moment I know went wrong was when I couldn't remember the name "trie" and the interviewer just wrapped up and left 15 minutes early. And I still had 3 more sessions that day.
cercatrova 6y ago
It's because they thought you memorized the problems and solutions. Next time if you get something you know, feign ignorance and just stumble through it naturally.

jefftk 6y ago

> One striking example was when I solved the coding problems posed to me in 15 minutes out of the 45 available, the interviewer said "that's great, I don't have any more questions, please use this time for you to ask about the company" and then the recruiter told me I was rejected because I did not do the coding part well enough. That's terrible behavior from the interviewer. Did you try raising this with your recruiter?

borroka 6y ago
The decision is already made, there is no point, nobody is going to backpedal on anything. I remember saying: "I don't get it", but she was clueless about the interview itself. It was a company in LA with a ghost.
- jpmoral 6y ago
  If I liked other people I'd met well enough I'd give that feedback (politely and without assigning blame), not to change their mind but just to let them know.

tootie 6y ago

The one moment I know went wrong was when I couldn't remember the name "trie" and the interviewer just wrapped up and left 15 minutes early. And I still had 3 more sessions that day.

cercatrova 6y ago

It's because they thought you memorized the problems and solutions. Next time if you get something you know, feign ignorance and just stumble through it naturally.