After a career fair at my school I talked to the Google recruiter, who suggested I apply online within the next few days to be eligible for an on-campus interview in a few weeks. A recruiter contacted me 10 days later for a technical phone screen--seems I didn't make the on-campus interview. I arranged a for a phone interview, to take place in 5 days' time. The phone interview stretched on for >45 minutes. Connection wasn't very good. I was asked about experience, general knowledge, and two coding problems, one easier, one harder. On the easier problem I had to re-imagine the algorithm twice to get a time complexity the interviewer was satisfied with. On the second problem I got stuck for a few minutes on an off-by-one error. Recruiter called me later offering an onsite interview. I asked to be interviewed for the Seattle/Kirkland office so she transferred me to a different recruiter who handles that location. I scheduled the onsite as soon as I could (in about 2 weeks' time) because I had a deadline for another offer. Both recruiters were understanding and gave me prompt responses. The onsite was four technical interviews, each an hour long, with an hour-long lunch break in between. All five interviewers asked if I had questions, so by the end of the day I was grasping at straws for any new questions to ask. Each technical interview had two whiteboard coding questions of about equal difficulty. (On interviewer asked three coding questions, but the first was just a warm-up.) On two interviews I answered all questions before time ran out. On one interview, the interviewer made me realize the function I had just coded up wouldn't solve the problem, right as time ran out. I held him back for a few seconds as I drew out the correct solution on the board for him. On the last interview, the time ran out before I could code up the answer to the problem. It was all data structures and algorithms with no architecture questions, but that's probably because I was a new grad. One interviewer was friendly and enthusiastic. Two of them were pretty withdrawn, so I had no idea whether they liked what I was doing or not. The last one was blunt and quick to tell me when I was doing something wrong, but he also never brushed off my questions or weird algorithm ideas. Two weeks after the onsite interview, I got an offer for after graduation. I feel like coding interviews are just as much psychological as they are technical. You have to keep a cool head during a stressful situation and accept criticism with good grace. You also have to be able to communicate your ideas really quickly and effectively. I drew out diagrams on the whiteboard as I was brainstorming--having visual aids really helps.