3 ms·
First things first; if you want a job at Google then you should apply and nothing anybody says is going to change that. It's not a huge opportunity cost and the
by xen0 6y ago
First things first; if you want a job at Google then you should apply and nothing anybody says is going to change that. It's not a huge opportunity cost and there is no shame in rejection; you're always allowed to try again later.
I cannot say if its "easier" or "harder" than it ever used to be; Google likes to say it doesn't "lower the bar" at all, so take from that what you will.
But here's a data point:
I started at Google in December in Europe. I graduated with a Bachelor's in 2012 (Maths & Phys) and have been working as a Developer since. Everything I learned regarding programming was learned post-Uni. Most of my "interview prep" was really a few weekends of leetcode/hackerrank questions (I was interviewing for several companies, so the time investment didn't feel too bad). I've done things like Project Euler and Advent of Code over the years too (but not to an insane degree; I've only solved ~120 PE problems over 8 years). You need to practice solving problems, and less an encyclopedic knowledge of everything (of course, the latter helps with the former). I didn't really do anything to prepare for the System Design interview; I don't really know what kind of prep one would do for that.
You may be asked to do at least one interview in one of {Java, C++, Go}, so make sure you're comfortable with one of them (expertise not required); I did two interviews in Python and one in Java.
(Things might be difficult right now because of the Coronavirus pandemic, so hiring may be temporarily frozen for where you want to go.)
Edit: With so much experience, you shouldn't be applying to a Graduate role.