Comment by dijit | Hacker News Reader

Comment by dijit | Hacker News Reader

Parent Full thread

My experience was not so stellar.

Interviewer tagged me and I thought I'd go along with it for the fun. I'm a systems engineer not a developer so YMMV.

First stage interviewer put me through a basic aptitude test ("what is netstat?", "what's the expected output of dig?") which was fine and I answered them all with a fair degree of correctness but the questions quickly went on to different programming languages, and while I've done some small things and I definitely know my way around a bourne shell I didn't get spectacular marks honestly, mostly because he was asking programming questions and I haven't had as much exposure to code as I'd like.

the next week I receive what I thought was a follow up call, but it was another round of preliminary questions.. around 2 questions in, and I realise these are the same exact questions I answered the week before. I'm a bastion of honesty, and while I knew the answers to all his questions now (because curiousity made me look up the ones I had failed.) I felt I should tell him that he asked me these questions before. I did.. he fell silent.. "are you sure"

"Yeah, your next question is about netstat"

".. oh.. well I don't have your results"

"Do you have any other questions to ask, you can reask me questions but my success rate will be higher this time"

"no, we'll contact you in 6 months"

Well, he didn't, but that process shook me a bit.. I certainly wouldn't call it stellar, and I'm likely blacklisted from interviewing at google now as I don't think I've had recruiter spam from them in a long time.

As someone who did a lot of interviewing at Google I can say your interviewer didn't do his job and that definitely should not be the usual experience.

That said how are questions about "netstat" and the "expected output of dig" programming questions?

Also for anyone planning to join Google as a sysadmin you should note that even Google's sysadmins do a fair amount of code since Google loves automation. Python will probably figure fairly prominently in your job.

those questions were not the programming ones, I don't remember the programming ones, but they would be considered pretty tame by most programmer standards, I simply lacked the knowledge at the time..

That's interesting. I wonder if that recruiter needs to work on his filing system a bit -- e.g., work on stuff in the inbox, then place it in the outbox :)

I wonder what the most politic way to deal with this situation would be. It sounds like you were polite but honest, which is a good thing in my book. I might have done the same, but perhaps it would have been better to just play along, score higher, and get pushed to the next step? Just speculating!

I had the exact same experience happen to me in a phone interview. I told the interviewer he had already asked me those questions. He told me to just go ahead and answer them again. Needless to say, I aced the phone screen since we went over all of the answers together the first time round.

But how could this have been a more stellar experience for you? Should they have given you a consolidation price?

Job interviews are a business transaction (after all you are there because you want their money). Not hiring you is fair game and once they have decided/committed to pass on the opportunity it wouldn't be rational to waste money by continuing a pointless discussion.

>But how could this have been a more stellar experience for you? Should they have given you a consolidation price?

If we ignore that they asked him programming questions not relevant to his position, there's the whole "they didn't even know they interviewed me, so they called me again to ask me the same exact things" FAIL, plus the lie about "we'll call you in 6 months".

> But how could this have been a more stellar experience for you?

Are you joking? Did you even read their post. The guy literally called and asked the same set of questions twice, then didn't follow through with what they said they would do.

I cannot believe you're even asking "how could this have been a more stellar experience for you?" the gall.

I mean, not parent commenter, but I'd expect, y'know, the recruiter to actually remember giving the exact same preliminary interview to the same candidate a week earlier.

Was it the same interviewer? Maybe there are 10 interviewers going off the same script.

Interviewer 1 called OP and asked questions. Then it was lunch time and he forgot to put result in the CMS.

So the same guy popped up a week later to Interviewer 2. He was reading off the same script, so of course his questions are the same. Not his fault, or Google's per say - Interviewer 1 happened to forget a step. (Which is sad, but we all make mistakes!)

> I felt I should tell him that he asked me these questions before.

The way it was phrased implied that it was the same person (would have otherwise been "I had been asked these questions before")

it was the same guy, we'd spoken before on Linkedin.

Hah then shame on him ;)

He "tagged" you?

Reply on news.ycombinator.com