Counterpoint: This is a recipe for only finding unemployed people, and in my opinion, the best people already have jobs. I have been offered to interview with YC startups that wanted me to fly out, spend a week writing code with them, and _then_ they'd offer me a job. I'm already employed, by an employer that legally owns all my code. I can't take a week off, write your code, and then _possibly_ get an offer. I don't…
Ideally the time you spend writing code is both compensated and under a Work For Hire of the company trying you out. Your current employer owns the IP of whatever you do during work ours and using their equipment not what you do on your own time.
I will not do a tech interview
421–430 of 554 posts
Re: I will not do a tech interview
#422Earlier quoted context omitted.
I used to work at Google. I saw a lot of good candidates get rejected. I myself was rejected multiple times before I got an offer. I was talking to my manager who was on the Hiring Committee about this dilemma, and at the end of the day the fact is that good companies don't give a shit about their false negative rate - only their net positives. By having an efficient technical interview process, yes, you let good can…
I interviewed w/ Google a couple of years back, didn't get hired. Interviewing is a two way street, and I won't BS if I don't know something. That said, had one interviewer who had 0 personality, 0 people skills, and didn't introduce himself. He asked one of the typical open ended questions, which was fine, we went through it a bit. At the end, he claimed there was actually a closed answer to the problem, wouldn't ac…
Re: I will not do a tech interview
#423Re: I will not do a tech interview
#424Earlier quoted context omitted.
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…
Sorry, but a negative reinforcement cycle of tensing up in a medium stress situation is exactly the kind of characteristic that I'm trying to screen out in an interview. Stressful situations happen a lot more than never in the real world (and sometimes they even involve talking to people, like customers) -- I don't want to have coworkers who can't handle that.
This completely contradicts the argument that a candidate who has difficulty handling interview stress will not have the ability to handle any stress. I can't speak for everyone who gets nervous during interviews, but in my case it's due to the combination of the uncomfortable environment, lack of access to tools I've grown to rely on, and an awareness of how fickle people's opinions are.
Re: I will not do a tech interview
#425Earlier quoted context omitted.
For me, the interview has always been way more stressful than anything I've had to do on the job. I think lots of people feel the same way (partially based on what I've seen performing interviews myself).
I'm sorry to hear about how stressed you get during interviews, but unfortunately the stress you demonstrate during technical interviews is a useful heuristic when determining whether or not a candidate would be a good fit for a company. Is a good signal all of the time? No. Is it a good signal most of the time? Probably.
Re: I will not do a tech interview
#426Granted, 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 used to work at Google. I saw a lot of good candidates get rejected. I myself was rejected multiple times before I got an offer. I was talking to my manager who was on the Hiring Committee about this dilemma, and at the end of the day the fact is that good companies don't give a shit about their false negative rate - only their net positives. By having an efficient technical interview process, yes, you let good can…
I doubt Google's false positives are better than anybody else's.
Re: I will not do a tech interview
#427Earlier quoted context omitted.
Adult tigers rarely climb trees even when chasing prey and need a significant running start to do so at all. Though they are cats their mass is importantly very different than domestic cats. You fail the interview for not getting the a-ha question right.
Remember: the tiger doesn't need to climb a tree well. It only needs to be better at it than I am. I am confident that a hungry tiger in hot pursuit will be better at it than I am, no matter how terrified I am (which will be quite a lot). And no, we're not going to settle it by experiment.
Re: I will not do a tech interview
#428Re: I will not do a tech interview
#429After going through an initial resume screening and phone call, you show up on-site in the morning.
You then give a presentation about some recent work you've done. For those fresh out of school, it's generally about their grad work.
Then you have a series of 1/2 to 1 hour interviews through the day, mostly with people who were at your talk that morning.
The individual interviews tend not to be the Google-style "please implement a data structure for XYZ on the board" sort of thing. Rather, we'll ask about things from your talk or your resume that interest us. We might describe some work we've done here, to hear what you think about the problem, how you might have solved it.
A lot of what we're looking for is how well you're able to communicate your responses. We also want to get a feel for personality, how well you work with others and how well your personality will interact with the people here. I believe this place is actually pretty diverse, and I like to think we don't fall into the "culture fit = 20-something white male" trap; however, some of the restrictions and circumstances of the work we do may make some people unhappy and we'd like to avoid that.
We also pick two people to take the candidate to lunch. This is supposed to be a chance to talk more about life in the area and what it's like to work here, although honestly a lot of that comes up during the regular interviews.
After all the interviews are done and the candidate leaves, the interviewers get together, share their impressions, and say whether or not they recommend hiring. The hiring manager then makes the final call.
It's not really suitable to everywhere, I'm sure, but I'm pretty happy with it.
Re: I will not do a tech interview
#430Where I work, an interview is a full day thing. I'm pretty happy with how it works: After going through an initial resume screening and phone call, you show up on-site in the morning. You then give a presentation about some recent work you've done. For those fresh out of school, it's generally about their grad work. Then you have a series of 1/2 to 1 hour interviews through the day, mostly with people who were at you…