For me, it's less about the hiring process, and more about actually getting an interview. When I finished my CS degree, I considered applying for Google, but I

For me, it's less about the hiring process, and more about actually getting an interview. When I finished my CS degree, I considered applying for Google, but I ended up working in a startup instead, which is probably for the best, because I ended up getting thrown into the deep end and learning a ton. A few years later, I had worked at a few agencies, and had a few decent projects/promotions under my belt, so I decided that I'd apply to Google, just to see what my chances were. I submitted my CV, and got a flat-out rejection. Not to worry, I thought. There's always another time. A year ago, I submitted my CV again, and after about two weeks I received another rejection. It might be because I work on the .NET stack, but Google won't touch me, it seems. I wouldn't consider myself a bad developer by any means. I've contributed to open-source, I've got a decent rep on Stack Overflow, none of my employers would have anything bad to say about me. I've had offers for interviews from Amazon and once from Microsoft; I refused the former, and accepted the latter, although the recruiter never got back to me. Personally, I consider the process to be quite fun, and while I've probably forgotten most of the content from my Algorithms classes, above anything else I think it'd be a nice thing to try, even if I don't get the job. At the very least, it'll be a good opportunity to test myself to see if I can (re)learn the stuff I'd need to be a Google developer.