Live data from Hacker News

The technical interview is an ego trip

blog.kowsheek.com

101–110 of 206 posts

Re: The technical interview is an ego trip

#101
post #10

This was my take on interviewing with Amazon at one point a long while ago. The initial interview itself was pretty straight forward, but it seemed like every answer I gave was "wrong" because the interviewer was looking for key phrases instead of understanding of the concepts. We talked about hashing, and when he asked if I knew what hashing was I said sure, its a one-way function to create a unique identifier. He a…

Respond with "then you could phrase your question a bit better and ask about the relationship or connection b/w hashing and fingerprinting".

If you're not throwing the keyword you're a 12-year-old fanboy of in the question, you can go eat a carrot for all I care.

Re: The technical interview is an ego trip

#103
post #28
post #10

This was my take on interviewing with Amazon at one point a long while ago. The initial interview itself was pretty straight forward, but it seemed like every answer I gave was "wrong" because the interviewer was looking for key phrases instead of understanding of the concepts. We talked about hashing, and when he asked if I knew what hashing was I said sure, its a one-way function to create a unique identifier. He a…

Sounds like my Google interview. By the end I had absolutely no interest in working there. Such a toxic environment. The guy they had take me to lunch also seemed completely miserable. Dunno if that was representative of Google or big companies in general but it turned me off forever.

Google had a guy take me to lunch as well. I suppose this is part of their process. I was surprised it was a random developer (a quiet, uninterested, also slightly miserable young guy), rather than someone who was otherwise involved in my (potential) recruitment. It seemed like a lost opportunity for them to get to know something about me other than whether I could do simple coding exercises quickly and accurately under pressure without recourse to external resources. (I can, but apparently not quite quickly or accurately enough for them). I was amazed that they were prepared to fly me to another country (NZ to Australia), but at no stage showed the slightest interest in me personally or anything I had ever done. I am 59 years old, I've been working with code since I was 21 and worked out how to program a significant embedded application on an Intel 8085 CPU using nothing but the manufacturer's data sheets and a simple hex keyboard and display breadboard target. I've learned a few useful skills along the way.

Re: The technical interview is an ego trip

#104
post #16

Articles like this always underestimate how many bullshit artists there are out there. The technical interview is not perfect but it is still far more meritocratic than many fields.

I can't believe how many people claim to have years of experience but are completely unfamiliar with terms like "binary", "library", "compiler", and "filesystem".

Re: The technical interview is an ego trip

#105
post #50

Earlier quoted context omitted.

I think it says a lot more about the individual interviewer than anything about the company. I've had great interviews with a company, and then I've had one where the person was looking for me to say 'base64" (which I wasn't actually aware of at the time!) even though I was explaining the same exact concept from the same company. The whole process is capricious.

If the whole process is capricious, it says a lot more about the company than about any individual interviewer.

IMO, "capricious" is a word that could be used to describe any interview process that isn't a structured, formalized process. You don't get a good signal out of ad hoc interviews, you can't calibrate across interviewers, and you can't compare accurately across candidates, so why bother?

Re: The technical interview is an ego trip

#106
post #28
post #10

This was my take on interviewing with Amazon at one point a long while ago. The initial interview itself was pretty straight forward, but it seemed like every answer I gave was "wrong" because the interviewer was looking for key phrases instead of understanding of the concepts. We talked about hashing, and when he asked if I knew what hashing was I said sure, its a one-way function to create a unique identifier. He a…

Sounds like my Google interview. By the end I had absolutely no interest in working there. Such a toxic environment. The guy they had take me to lunch also seemed completely miserable. Dunno if that was representative of Google or big companies in general but it turned me off forever.

At the ~500 person tech company I work for, the first goal of the recruitment and interview process is to decide if the candidate would be a good fit for the role, and the second goal is to convince the candidate that they should accept the job if offered.

I recently interviewed at both Apple and Amazon. None of the interviewers or recruiters at either company tried to sell me on the job and I left both interviews not wanting to work there. My theory is that Apple and Amazon don't spend time trying to sell the company because they already have more than enough willing applicants for each position. Is the same true for other large tech companies?

Re: The technical interview is an ego trip

#107
post #49

Earlier quoted context omitted.

I don't think googling is even a valid answer. If he asked "how would you find out how many ridges are on a quarter" then yes (and I think Google it would be everyone's first answer). But counting, as a verb implies the act of measurement, not just obtaining the final number. Assuming that he used that word, it sounds like a trick question.

I was once asked how many golfballs could fit in a school bus. I blathered on about measurements of the bus, volume of a ball, the average due to gaps between balls, are the seats still there, etc... bottom line we could spend a lot of time getting an ever more precise estimate. The guy seemed satisfied. Later at home I realised that my test engineer friend may have suggested doing an actual experiment - rent a bus a…

If we live in a world where reality is on deck, and not the seemingly arbitrary and capricious one that folks sometimes weave, I think you can determine what answer is "better" with more context.

Renting a bus and filling it with golf balls is significantly more effort intensive than calculating, but it might give interesting, real world insights if the values differ.

For the purpose of running a business, the choice, to my mind, hinges on how much your revenue / customer satisfaction / product depends on the real world intelligence such an endeavour might bring. The situation illustrated is contrived, so it's hard to contrive an answer to that question.

There's hybridized approaches. Here's a 3D/AV interactive developer's contribution to your approach list:

I've used lidars and depth cameras as a hammer quite a bit over the last year, so I'd do thus - Realsense D435 capture the inside of a bus. Use meshlab to align and stitch all your pointsets. Perform reconstruction on it so you get a 3d mesh. Use your tool of choice to perform a physics simulation on golf balls (I'd probably use Unity3d, because customers love simulations they can play with.)

Run your simulation a ton of times with epsilon changes to initial conditions. Maybe even do it with an evolutionary algorithm that tries to maximize the count!

Either way, report back with a distribution. Also capture frames every once in a while so you can give them a timelapse. God customers love timelapses.

Re: The technical interview is an ego trip

#108
If we aren't complaining about interviews where we got the offer and turned it down, there's a serious risk we're experiencing "sour grapes". Every interview I failed was an opportunity to get better. If it feels arbitrary and you don't get the job... you may just be below the bar. No shame in that... buy there's definitely shame in this sadly common framing attack on the concept of the tech screen.

Re: The technical interview is an ego trip

#109
post #35

Earlier quoted context omitted.

I don't take crap like this from interviewers. One time an interviewer asked me "how would you go about counting the ridges of a US quarter?" I rattled off some ideas about counting the ridges in an arc and then multiplying to get total ridges but the interviewer kept prodding and eventually ended the question and said he was looking for me to say "google it" (I didn't realize it was a known, fixed number). I just ro…

It's funny that his expected answer was "Google it". In most cases when people answer with that (it could be the answer for any tech interview question...) you get encouraged to actually do the problem, so it's a time waster. For the interviewer it gives them no signal outside of you having the ability and awareness of the existence of search engines, although there could be some vague behavioral signal that shows yo…

False. We want you to be confident and admit you Google all day every day. Simple as that. You seriously would have done all that before Googling it?

Re: The technical interview is an ego trip

#110

Earlier quoted context omitted.

When he inevitably asked you to code an algorithm as the next question I hope he also accepted using Google for the answer.

I see nothing wrong with this, why would I write algorithm X from memory or taking my best guess at it on the spot, isn't the whole point of learning them recognising when are they applicable and how to find them quickly ?

It's kind of like knowing multiplication tables, or intervals in music. There's some stuff you just gotta know.
Post reply on HN