See his posts How We Interview Programmers [0] and Hacker-vs-Programmer [1] for more insight. It is ironic, then, that the author is claiming that algorithms, and knowledge of them, are unimportant for a programmer. "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." He believes he is a good programmer, and that learning algorith…
It is ironic, then, that the author is claiming that algorithms, and knowledge of them, are unimportant for a programmer He didn't say that.
Why I Don’t Talk to Google Recruiters
81–90 of 674 posts
Re: Why I Don’t Talk to Google Recruiters
#82> 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. Interview process: complete success.
I'd be interested in hearing from people who work at Google, and get to figure out a cool algorithm for solving an interesting puzzle-problem more an about once a year. I bet there aren't very many. In my experience, the stuff you do in this kind of interview has very little relation with the stuff you do in the actual job. (I wish it did! I love those algorithmic puzzles.)
This is what confuses me. I tend to take the problems I get during an interview as representative of the work I would be doing, and then get turned off by the job immediately.
At least at the PhD level, you'd expect that the job would be using more of my unique expertise, I'm not a BST expert (though I can write one when I need to, it definitely isn't "warm" in my brain).
Re: Why I Don’t Talk to Google Recruiters
#83Earlier quoted context omitted.
And in theory it should totally be worth it as a candidate unless they are coasting on reputation. Otherwise the supply of candidates would dry up. In practice it wasn't for me, but I refused to tell them how much I made just to see what would happen. If you interview at Google and they ask how much you make you should probably tell them or you might get a weak non-negotiable offer. Unless what you make is already fa…
refusing to tell your prospective employer how much you want to get paid is a 'negotiation tactic'?
Re: Why I Don’t Talk to Google Recruiters
#84I've had countless interviews where I could immediately tell upon entering the room that the interviewer does not want to be there at all. It's a lose lose situation. For me, because I get demoralized instantly, and he's already got a chip on his shoulder for having had to do this in the first place. Everything I say going forward from that point on is an uphill battle.
I think only managers/very few people who are truly trained should interview people as that is kind of the essence of a manager's job--making sure they have happy, solid team. I don't even mind the technical questions. I just want to be in a room with someone who is actually potentially excited having me there. Not grilling me in a depressed fashion
Re: Why I Don’t Talk to Google Recruiters
#85> 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. Interview process: complete success.
Re: Why I Don’t Talk to Google Recruiters
#86So many posts telling the world that they don't want to be the algorithm guy--the world doesn't care. Forgetting the Maxim: "Not everyone gets to be an astronaut when they grow up."
https://cdn.shopify.com/s/files/1/0535/6917/products/potenti...
Re: Why I Don’t Talk to Google Recruiters
#87> 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. They are just looking for smart people. If you ever looked it up it's 5 lines of code. That's the whole point they're not forcing you to learn something: A) so esoteric you will never encounter in your programming career B) so complicated that you'd have to spend days practicing…
Which lead them to refuse to give a job to the guy that actually developed a software used by those with higher IQ to come up with tree inversion algorithms?
Re: Why I Don’t Talk to Google Recruiters
#88Once I got messaged by a recruiter who was very enthusiastic about meeting "expert Rails devs" and wanted to hop on a call to see if I had any interest in their company. I've never touched Ruby in my life though.
I also just started my first machine learning job recently. Before I was even a month into it I started getting messages from recruiters from companies like Microsoft who were looking for "top ML talent" like me.
Unless there's an actual genuine interest from the recruiter, I don't think you gain any advantage by responding to them.
Re: Why I Don’t Talk to Google Recruiters
#89Re: Why I Don’t Talk to Google Recruiters
#90Unlike most of HN (it seems), I like hearing from recruiters, because despite the very low signal-to-noise ratio, there's always that remote chance that one of them could be able to set me up with a "dream job". It's zero cost to me to politely reply to a recruiter and ask for more info, and I try to at least respond to everyone. What I've found is that they must have a lot of candidates they're juggling because fall…
See, I see that time as very expensive.