Live data from Hacker News

I will not do a tech interview

medium.com

241–250 of 554 posts

Re: I will not do a tech interview

#241
post #150

One good thing about reading/browsing HN is that you can get an impression of the ideas that are starting to emerge. One thing that seems to be emerging now is that people are rethinking the grueling technical interview process. There was a huge emphasis on avoiding false positives in the interview process - largely because a single bad hire can do great damage to a software development team. But people seem to be le…

"I was asked to code a singleton" This interview is over!

Re: I will not do a tech interview

#242

Earlier quoted context omitted.

Woah hold on - you're firing people for getting things wrong in meetings? Most people would be unemployed. Seriously though - if you're creating a high stress meeting like that in a company where people are at risk of getting fired then your culture is going to be terrible with people backstabbing each other so they look good at the next meeting. A company is a team - it's everyone's job to make sure the team is work…

> Woah hold on - you're firing people for getting things wrong in meetings? Wrong outcomes for meetings have business consequences, which can include people losing their jobs. That's not necessarily "people getting fired for getting things wrong in meetings" -- indeed it generally shouldn't be that except in rather extreme cases of "getting things wrong" -- but it still means that people's jobs are on the line in the…

Ah okay, good, that's a more reasonable discussion then.

So you're basically saying that a meeting could fail to create value because an employee made mistakes in the meeting as he could not handle the stress. The correct way to solve this for everyone involved is to reduce the amount of stress everyone is under in a meeting and to create an environment conducive to problem solving. This isn't really that hard, a well motivated employee whose rewards and goals align with the company will try his best to create value as it helps him the most as well. If an employee is very bad at meetings, he could also be asked to express his ideas beforehand to someone he feels comfortable with and then that person could help him express his idea in the meeting.

The solution of hiring only people who can shout the loudest and brute force their ideas through in combative meetings is not a solution that will create value over the long term. If someone is breaking down in your meeting the problem is the meeting, not the person. Fix the meeting. Even people capable of taking stress is meetings will still perform better if that stress is removed.

EDIT: You also shouldn't be making snap judgements in a meeting that will affect the future of the company in the market. If there is a lot of tension in the meeting and the outcome is unclear, postpone the issue a short while until people can work out the issues better. If someone notices that there was a mistake in a previous meeting, work through the mistake in the next meeting and change direction ASAP. And obviously, don't fire anyone for this...

Re: I will not do a tech interview

#243
post #85

Granted, there are a lot of bad tech interviews out there (asking about algorithms that nobody ever uses) ... but I do not understand this. Imagine someone's being hired for a front-end position, and we don't have months to get them up to speed. I'm going to ask them to explain how a closure works. How they deal with AJAX. What they think about "!important". Things to be careful about with floats. How CSS precedence/…

The problem is that interviews are high stress affairs. Stress produces adrenaline. One of adrenaline's known effects is to prepare us for "fight or flight", meaning that higher order logic is shut off, digestion is shut off, our senses sharpen, reactions improve. This is great when you've got to climb a tree to get away from a tiger. This is horrible if you are trying to demonstrate your ability to function mentally…

I deal with that kind of anxiety feedback loop in interviews, especially when I feel like I have no other edge besides my interview performance and resume, i.e., no personal connection. At my current job, they gave me the questions on paper and left me alone to answer them. I did well with that. (I also had a personal connection.) Later, I did a phone interview with Google based on having come up on one of their LinkedIn scans, and it went terrible.

How a person does on a pressure interview certainly tells you something, but it would seem to put a high priority on a particular skill at the expense of others. It probably effectively screens out anxious types. I'm not sure you can generalize what you learn too broadly, though.

Re: I will not do a tech interview

#244
As an interviewer, my impression is that interview performance often does not predict success in the workplace. The most extreme example is for a case where the person aced (I mean absolutely aced) the algorithm questions I threw at him but was unable to get things done at work. In technology, we don't have a good way to filter by personality and conscientiousness - these unfortunately turn out to be pretty key in getting things done well.

Re: I will not do a tech interview

#245
Seems like a reaction to yesterday's Google post.

Does anyone know how interviews at Apple and Facebook are like? There are often praises of Microsoft's interview procedures and bash on Google's on HN. Wondering what these two other companies are like.

Re: I will not do a tech interview

#246
post #67

On-site interviews are a necessary for the most part, but phone screens have always been the bane of my existence. About 50% of the time I can barely understand what the other person is saying, mostly because the person conducting the interviewer is not a native English speaker. I almost never have an issue in person with non-native English speakers because you're able to pick up so much more context from subtle phys…

Tangential, but you hit on a really fascinating field in psychology with your post.

We have these differences--linguistic, cultural, even physical characteristics--that are huge. The differences that highlight a lack of shared background/experiences/origin/etc. can be found not only to be at play between, say, native and non-native speakers of a language but even separate groups within the same culture. You see that in how we handle subjective feelings of personal space, for instance --we Americans, for instance, tend to prefer greater personal space over say Scandinavian or certain East Asian cultures. But the fascinating thing is how those expectations can shift based on region, and on an even more micro level, affluence etc.

Even when the differences are minor, such as say race and skin color, the effects can be profound. If you look into what's called the cross-race effect, you'll find a tendency to have difficulty processing faces of members of other groups. If you've ever heard anyone say "all Asians look alike" or the similar "all Westerners look alike", this effect is what's behind that sentiment. And it's universal: this processing difficulty isn't limited to any particular ethnic group. Cross-racial identification statistics for eyewitnesses prove all too well just how troubling this can be even amongst ethnic groups that are otherwise readily familiar (i.e. whites identifying blacks and vice versa). But what a lot of the current literature shows is that the rate of difficulty can decrease with familiarity that shapes how we code faces and integrate them into

Anyhow, as far as communication is concerned, it's not just verbal. On the contrary, most of our cues are distinctly non-verbal: body language, gestures, expressions, prosody, paralanguage, and a lot more. People toss around Albert Mehrabian's "93%" number a lot without considering its context (namely, his work was limited to the communication of feelings and attitudes), but the broader point is that these cues serve as a means of helping to imply meaning to the words they accompany.

Now, where the really fun stuff begins is when you start to consider the universality of some of these nonverbal cues. Particularly with the face with microexpressions: involuntary expressions lasting only a tiny fraction of a second that correspond to six basic emotions. Contrary to the idea that expressions and meaning were culturally determinate, the research is fairly overwhelming that despite differences in culture, language, and even physical face characteristics, microexpressions and the emotions represented are consistent. Rules governing those emotions are be culturally specific, but how they're expressed and the emotions themselves aren't. Back in '71, Ekman went to the Papua New Guinea to show this with the Fore people even though they had almost no direct contact with the outside world up until the fifties, and at the time Ekman went, had no access to Western media or entertainment that might have given the Fore the experience with outsiders and their facial expressions.

Related to your post, however, are the findings that show we're able to recognize these expressions by people outside our own ethnic groups. In a sense, not only are the emotions and expressions universal but so too are our ability to recognize them. Biologically determined, hardwired. So talking in person, rather than on the phone, can make all the difference in the world.

If you're curious, I'd recommend taking a look at a reprint of Ekman's Unmasking the Face and Darwin and Facial Expression: A Century of Research in Review if you're curious about some of the historical origins of the work. The latter, in particular, is truly fascinating.

Re: I will not do a tech interview

#247
post #95
post #54

Earlier quoted context omitted.

I've become a real believer in the "portfolio". I make the assumption that any person with a github (bitbucket/etc) site with a track record is someone worth looking at; if their portfolio demonstrates quality work and the resume looks all right, I'll recommend them. Yes, false negatives, people with horrible IP agreements get screwed, etc. False positives are much worse than false negatives in the common business wi…

It seems to me like software engineering is one of the only fields with people arrogant enough to assume that every good and passionate programmer should also be doing programming as a hobby. I loved software engineering so much that I decided to turn it into a career, so that I could do it every day. But now you want me to do it every day and every night? No. My work during the day is fulfilling. My hobbies provide…

If I have two candidates and the only signals are (resume, portfolio), then I will select the highest signal. I am sorry, but I can't in conscience decide to take someone without proven work over someone with proven work without other information.

If your resume is significant, then I will probably add to the signals with a phone call followup. I'm not looking to create false negatives.

I also want to point out that taking some time to develop a small and interesting project (say, a pure left-leaning red-black tree with deletion - not much code, but tricky to get right) does not take that much time and massively demonstrates your capability over having nothing at all. It also demonstrates your social awareness of the state of the field when you have a github account with projects in recent technology.

Re: I will not do a tech interview

#248
post #189

Not quite the same, but I once had a no name company (getglue) tell me that I need to do a 3-hour programming assignment before I can interview with them. I have too much self-respect for myself to put myself through that process. I declined the "opportunity" to interview with them. The interview process is broken and many of the interviewing techniques either do not correctly judge a candidate, or place too much bur…

Good decision. I regret very much that I didn't make the same decision you did. I did a 5-7 hour programming homework assignment, didn't hear back for weeks, and then it was just from a recruiter (sorry, we've decided not to continue the process). I won't do it again, ever. It's not the wasted time that I regret so much. I do agree with you that there is a self-respect element to this.

[deleted]

Re: I will not do a tech interview

#249
post #83

Granted, there are a lot of bad tech interviews out there (asking about algorithms that nobody ever uses) ... but I do not understand this. Imagine someone's being hired for a front-end position, and we don't have months to get them up to speed. I'm going to ask them to explain how a closure works. How they deal with AJAX. What they think about "!important". Things to be careful about with floats. How CSS precedence/…

I'll try to turn the table on you. Pick some particular technology that you don't hold in your head. three.js, Angular, Bootstrap, canvas, WebRT - whatever. I'm sure among those we'll find some details you don't have in your head right now and you will look up some APIs/details. Now I'll structure my interview around those topics which I happen to hold in my head since we use them all the time. I am not a front-end w…

I agree a few years ago I had to pick up Pl/1G to look after one of BT's Billing Systems took me all of a week.

Re: I will not do a tech interview

#250

Earlier quoted context omitted.

Truthfully, I'm not certain I'd trust someone who can go through an interview without freezing up or having any similar problems. Confidence is a valuable thing, but only in moderation.

I find it very bizarre that anybody would say something like this. Are you afraid of people who are more confident than you? Would that deter you even if they demonstrate superior technical skills?

I find it very bizarre that you don't see a need to keep out people who are overconfident. Are you afraid of people less confident than you? Would that deter you even if they demonstrate "superior technical skills" (whatever that means)?

Confidence gives you the strength to get up and go to the interview. It tells you you're competent enough to get the job even if you freeze a couple of times.

Overconfidence tells you you can't make mistakes. It tells you you have "superior technical skills", and that freezing up is only something that happens to lesser mortals.

Post reply on HN