Did you actually interview with them? I have Computer Science education, 10+ years of industry experience, am very familiar with most of the Cormen book and have been programming since I was a kid. I was interviewing with Google twice (after their recruiters reached out to me) and haven't made the bar.
Don't think that the fact of recruiter getting in touch mean anything -- they are playing their own numbers game.
> Don't think that the fact of recruiter getting in touch mean anything -- they are playing their own numbers game.
Exactly. In some conversations I've had with fellow dev's they seem to equate a message from a recruiter with a job offer. I never understood this. Sure, I get messages from recruiters on LinkedIn but it's prob. the same generic letter blasted to hundreds or even thousands of candidates. The quality of your online profiles (SEO?) as a programmer is directly related to the volume of messages you get from recruiters.
I don't make the mistake of thinking a recruiter calling me on several occasions, attempting to get me to interview is a job offer. What I find surprising is that the recruiter still wants me to interview even after I explained who and what I am. Maybe that's just an overzealous recruiter trying to fill numbers. Maybe Google has relaxed standards outside of what people usually think. One of the first things I said to the recruiter was something along the lines of "Are you sure you have the right guy?"[0] followed up with "I'm not quite sure that I am qualified". Between talking to the recruiter and people who work there or passed the interview, it sure doesn't seem like they are only looking for geniuses.
I'm just trying to offer a point of data regarding what Google by proxy of their recruiters, looks for. The recruiter himself has been working for Google for quite a while, so either he really knows how to game the system, is currently desperate, or Google doesn't have as extreme standards as one would think.
> What I find surprising is that the recruiter still wants me to interview even after I explained who and what I am.
Did you tell him that you're a psychopath? My point is that if a recruiter reaches out to you, it probably means your online identity matches their criteria for potential candidate. Now this criteria can be as simple as oh neat he uses haskell to I'm impressed by his contributions to project X, Y, Z. So unless you tell him something that is completely contradictory to his superficial impression of you there's no reason he should tell you NOT to interview with the company.
Also, I feel like whatever reason the recruiter decided to contact you (Github / nice linkedin profile) has very little to do with the companies hiring bar. It's a terrible proxy for measuring how a company hires. It's at best an indication of the technologies you'll potentially be working with. For example, if you only have java listed chances are you prob. would have never gotten that phone call. You should try it as an experiment.
Want to know where the bar actually is? Go for an interview. Of course, what they mean by interview is usually 1-2 rounds of phone interviews. So in essence you're still pretty far from being seriously considered as a candidate.
I don't think it really matters to the recruiter if you are qualified, or if they are judged on how many people they source end up getting offers. They are just there to get you in the door.
I suppose that would depend on how the recruiters operate. I'd imagine that at Google's size, they probably have recruiters just feeding people into the pipeline. I tend to assume people aren't just doing a shitty job, in this case throwing people at a wall and seeing what sticks, despite how much it clashes with my "imposter syndrome" mentality.
Don't think that the fact of recruiter getting in touch mean anything -- they are playing their own numbers game.