|
|
|
|
|
|
by gibsjose
3350 days ago
|
|
|
I was rejected from Google when I first graduated from college. Now I work at NASA and I'm very thankful I didn't get that job. Saying that the hiring process is flawed isn't the same thing as saying everyone is special and deserves a job there. From my anecdotal experience, I felt that they focus too much on algorithms and give the same interview to every candidate regardless of their experience or desired job. I made it very clear I wanted to work in embedded systems and write code for microcontrollers and they asked me questions about graph theory. Algorithms are not everything, especially for a company with such diversified technology opportunities. If I'm working on search, then sure. But embedded software? Can't they take the time to focus the interview even the slightest bit? Not a big deal though. I know they have an endless supply of candidates and thankfully we as software engineers have a pretty good selection of places to work. |
|
|
I'm not a Googler, but from what I hear, moving between teams within Google takes less effort than most places, so that might explain why Google tends to interview for a generic "Google developer" rather than a "Embedded developer" position. Who knows, you might progress from initially working on the Google home firmware, then move on to optimizing the search client code and then possibly the search backend for Home itself.
I'm sure there are a lot of specialists at Google, but I suspect those are fewer than generalists with a solid handle on data structures and algorithms.