Back when Google was officially "not evil", and I was just about to graduate in Computer Science, I sent them my CV to be a developer. They called me back, said

Back when Google was officially "not evil", and I was just about to graduate in Computer Science, I sent them my CV to be a developer. They called me back, said that they didn't have any dev jobs fitting my profile, but seeing the subjects I was learning, I might be interviewed for a Data Center Sysadmin role. Would I be interested? Of course! In my circles, working at Google was a sign of excellence back then. Did I want to interview right away, literally during the same phone call, or would I prefer some time to prepare? What did my cocky, eager-to-please-the-Google-gods 19-year-old self do? Bring the questions on! No need to prepare! Needless to say, I hadn't the slightest idea of what to answer for most of the questions. If memory serves, the interviewer tried to save the disaster by dynamically adjusting the difficulty of questions asked, going so low as to asking "do you know what an RJ45 cable is, and what it's used for?". That one question I did get, but by that point it was clear that I wasn't going to be a Googler Sysadmin. My obvious-in-retrospect takeaway: Always prepare for interviews in advance, and don't be afraid to speak for yourself, even if you want to make a good impression.