Hacker News new | ask | show | jobs
by IgorPartola 4105 days ago
My approach has been to treat it less like a "they are judging my technical abilities" and more like a conversation. I have only been in one interview where the people interviewing me really put on the pressure. Otherwis, it is usually my own interpretation that is putting on the pressure on myself. Once I started treating it like a friendly chat, it got a lot easier.

When you are asked technical questions, do your best to answer, but don't sweat it if you cannot answer fully. Know that with enough time you can most likely figure it out, then figure out as much as you can on the spot.

Lastly, know your stuff. Being a strong interviewee doesn't mean you can get any job. It just means that you can show off your own are of expertise well. Figure out what that is, and if need be improve on it. Side projects help a lot: to learn, to boost your own confidence and as a resume builder.

2 comments

Thanks you, that a great advice. I think you are right about applying pressure on youself, that might be the case. I'm getting very anxious trying to get things right from the first shot.

Another thing I noticed is that the less you care about the outcome of the interview, the more likely you are to succeed.

That said, it seems that the key to master those interviews seems to be the mind control, rather than raw experience and intelligence.

On your last point: I don't have any problems showing off expertise and I have a bunch of cool side-projects. The problem is that I'm weak at the low-pass filter of a basic technical screening.

Note that this might not work in the google-style whiteboard coding questions. In these, you're usually judged on the output you manage to produce within the duration of the interview, and being chatty or even thoroughly explaining your thinking process will eat into those precious minutes.
That's debatable.

I actually had the same impression from my Google interview, but at the same time they claim that they actually judge you based on you cognitive skills, rather than the output.