Home » Career » Why I Don’t Talk to Google Recruiters

About Yegor Bugayenko

Yegor Bugayenko
Yegor Bugayenko is an Oracle certified Java architect, co-founder and CTO of Teamed.io, lead architect of Rultor.com and Jcabi.com, and a big fan of test automation.

Why I Don’t Talk to Google Recruiters

This is a real story, and it’s not only about Google. I’m getting emails from recruiters at Amazon, Facebook, and smaller Silicon Valley startups. They find me somehow, most likely through this blog, my books, or my GitHub account. They always start with “We’re so impressed by your profile” and finish with “Let’s schedule an interview.” I always reply with the same text, and they always disappear, only to come back in a few months under a different name. Let me explain my reasons; maybe you will do the same and we can change this situation in the industry.
 
 
 
 
 

The Deer Hunter (1978) by Michael Cimino

Disclaimer: I do realize that these are multi-billion-dollar companies, the best in the industry, and I’m nothing compared to them. I do realize that their recruiters don’t care about my answers—they simply click “delete” and move on. I also realize that they will never see this post, and this article probably won’t change anything. However, I have to write it.

This is what I’m sending back to them:

Thanks for your email. I’m very interested indeed. I have nothing against an interview. However, there is one condition: I have to be interviewed by the person I will be working for. By my future direct manager.

The recruiter who gets this reply never gets back to me.

Why do I send this?

Well, because I learned my lesson two years ago, when Amazon tried to recruit me. I got an email from the company that said they were so impressed by my profile and couldn’t wait to start working with me. They needed me, nobody else. I was naive, and the message did flatter me.

They paid for my ticket to fly there and a night in a 5-star hotel. I was impressed.

We scheduled an interview in the head office in Seattle. They paid for my ticket to fly there and a night in a 5-star hotel. I was impressed. They definitely were interested. So was I.

What happened at the interview was, most probably, very close to what Max Howell experienced with Google: some programmers who didn’t know a thing about my profile asked me to invent some algorithms on a white board for almost four hours. Did I manage? I don’t think so. Did they make me an offer? No.

What did I learn?

That it was a waste of time. For both sides.

Their bureaucratic machine is designed to process hundreds of candidates a month. In order to fish and attract them, there is an army of monkeys recruiters sending warm emails to people like me. They have to screen candidates somehow, and they are too lazy to make this process effective and creative. They just send them through random programmers who are supposed to ask as complex questions as possible.

I’m not saying that people who pass their tests are not good programmers. I’m also not saying that I’m a good programmer—let’s face it, I didn’t pass the test. I do believe this filtering system is rather good. My point is that it contradicts the original email I got from the recruiter.

If she would have started her email with “We’re looking for an algorithm expert,” we would never have gotten any further and would not have wasted our time. Clearly, I’m not an expert in algorithms. There is no point in giving me binary-tree-traversing questions; I don’t know those answers and will never be interested in learning them. I’m trying to be an expert in something else, like object-oriented design, for example.

There is no point in giving me binary-tree-traversing questions; I don’t know those answers and will never be interested in learning them.

There was a clear mismatch between my profile and the expectations of the interviewers. I don’t blame them, and I don’t blame her. They all were just slaves employees. I blame myself for not setting this all straight at the very beginning.

I should have told her that I didn’t want to be interviewed by some programmers, because I would most certainly fail. There was no need to try. I wanted to be interviewed by the person who really needed me: my future boss. That person will understand my profile and won’t ask pointless questions about algorithms, simply because he or she will know what my duties will be and what kind of problems I will be capable of solving, if they hired me.

Unfortunately, as I keep observing from two years of bouncing such emails back to recruiters, they can’t change anything. They have to provide formal and standard screening for everybody, beginning with those same warm and flattering initial promises.

I’m sorry, recruiters, no more standard interviews for me.

You may also find these related posts interesting: You’re Just the Mayonnaise in a Bad Sandwich; How We Interview Programmers; Investors Are Too Scared; Competition Without Rules Is Destructive; Five Principles of Bug Tracking;

Reference: Why I Don’t Talk to Google Recruiters from our JCG partner Yegor Bugayenko at the About Programming blog.
Do you want to know how to develop your skillset to become a Java Rockstar?
Subscribe to our newsletter to start Rocking right now!
To get you started we give you our best selling eBooks for FREE!
1. JPA Mini Book
2. JVM Troubleshooting Guide
3. JUnit Tutorial for Unit Testing
4. Java Annotations Tutorial
5. Java Interview Questions
6. Spring Interview Questions
7. Android UI Design
and many more ....
Email address:

Leave a Reply

5 Comments on "Why I Don’t Talk to Google Recruiters"

Notify of
avatar
Sort by:   newest | oldest | most voted
Suresh
Guest

Well said Yegor. I’m sick of it too…

Nishan
Guest
Absolutely True. Its a similar scenario for java recruiters. I have a lit more to say on this subject. Java recruiters want algorithm for apps even for basic web page apps. And the crowd follow this logic like sheep. Cheap labor has kept a low level language like java afloat and has killed American inventiveness in this area. There hasn’t been an alternative to java for over 20 years. Apple evolved swift from a low level objective C. But because cheap labor is available in java coders , the sane idiotic interview style as well as language has never evolved.
Nick Christopher
Guest
My favorite solicitations of this sort are where they say that their extensive search brought them to me, and my background really impressed them, and them talk about a job requiring skills in an area I have *no* background in at all….. blah blah blah as a database expert…. what? I too had the trip out to Seattle where they interviewed me for a role I could not possibly fit. I’d specifically told them though the phone screens that I was not an X and when I got to Seattle they spent 8 hours interviewing me to see if I… Read more »
Cathrin
Guest

Thank you for sharing this experience! Although I am far away from working for names as big as those you mentioned, my hope is to be able to change the recruiting process for companies who are willed to understand what you explained. It’s a long way, but articles like this help to understand: it’s the only way.

Vincent Marshall Sr
Member

Been there, done that. I was beginning to wonder was it just me.
Been into tech for 40+ years with excellent references and credentials
and I’ve been bothered by this many times.

Maintain your expertixe, professionalism and your integrity and always
be ready to learn the next innovation to provide solutions to the worlds
problems and you will be successful.
VTSr