7 ms·
i second this. know basic data structures and algorithms. they are not going to ask you to implement red-black trees but they'll probably ask questions that r
by pz 17y ago
i second this. know basic data structures and algorithms. they are not going to ask you to implement red-black trees but they'll probably ask questions that require you to use hash tables or priority queues. know how to implement these and their running times.
and definitely practice solving problems on the whiteboard. its completely different. if its within the realm of comfort also get used to thinking out loud in the interview. some people really can't do this but i've found, both as an interviewer and interviewee, its really helpful.
your resume will basically get you a phone screen, beyond that i suspect its irrelevant.
(for the record, i've interviewed with the GOOG and was offered a job)
- Imprecate 17y agoMy friends have all had similar experiences, though most of them were interviewing straight out of undergrad, so it may have been a little different. Have seriously in-depth knowledge of the languages you claim to know, practice solving problems under pressure, and have a strong algorithmic foundation. They seem to have a reputation for being rude, but it's a competitive market and they're looking for the best. Things are pretty similar where I work. We will look at most people if their resume lists the relevant technologies, but the phone screen and in-person interviews are very tough. There are so many liars out there that resumes aren't a very good filter. Even academic pedigree doesn't seem to count much in the software development world, though it counts more if you're doing more research-y/academic things like machine learning.