Live data from Hacker News

I will not do a tech interview

medium.com

281–290 of 554 posts

Re: I will not do a tech interview

#281
post #27

Earlier quoted context omitted.

I guess I do not see how you can lose if you take the contract-to-hire approach I agree with most of what you said, but one way you can lose if you insist on contract-to-hire is that you are filtering out a portion of the highest quality candidates who are only interested in immediate full time hiring.

I don't think many candidates are interested in "immediate" hiring. Most people I know need to take extra time to wait for other offers to come in. It also gives the candidate a way to see what kind of problems he'd be working with, and the quality of the code-base, working conditions, etc. I think it's a win-win.

I recently switch jobs and can say with certainty I had no interest in contracting or contract-to-hire positions.

Quitting a full time job for a new position is a big commitment on my part, and I'd like a big commitment on the other side of the table. Not to mention contracting gigs don't usually have insurance, vacation, or other benefits.

If it means a more rigorous interview that's okay with me.

Re: I will not do a tech interview

#282
post #222

Earlier quoted context omitted.

>Of course not. Interview situations are very, very different than the others. Really? I disagree. There even exist situations (in the case of some positions) where you will be talking to a client of the company you're working for, effectively interviewing with the client, representing the company. And interviewing is a subset of "sales", which is important for working on many teams -- including selling management on…

> There even exist situations (in the case of some positions) where you will be talking to a client of the company you're working for, effectively interviewing with the client, representing the company. What positions would require you to prove the technical capability of your company at this level? I've been working for a consultancy for a few years now. I can't recall a time when a client asked me to describe a clo…

Funny you should ask. I was JUST interviewed by a client of a local consulting company I work for periodically, and he asked all kinds of technical domain questions. Different domain than JavaScript, so different questions. I'm not even sure what's meant by "!important", honestly, though I do know what a closure is.

I'm not an employee of the consulting company, but I COULD be if I asked, and in that case I would have been in that exact situation. I just prefer my contracting status; the upshot is that, not only did I do an interview like that, but I did it for free, on behalf of this company.

Re: I will not do a tech interview

#283

Earlier quoted context omitted.

Good developers cost, what, $120K-150K/year? If a two week trial period is "expensive" to you, you don't have the budget for someone in that pay range.

It's expensive in other ways though. A programmers who is currently employed but thinking about moving on probably won't agree to a two-week trial period because of the substantial risk that they get rejected afterwards and end up unemployed. That makes the trial period expensive to him . In turn, it makes it expensive to the employer as well, because you'll filter out good people.

Can they not do this two-week project after hours? Must it be in your office, on your schedule? Where you code, the hours you code, these do not matter. The code is what matters.

Re: I will not do a tech interview

#284
post #122

Earlier quoted context omitted.

I hire people based on their ability to learn, not what they know. If you're asking interview questions that can be googled in 20-30 seconds, you're wasting your time and theirs.

You have a pretty low opinion of our field if you think everything that you need to know about our field can be googled in 20-30 seconds. I'm not arguing about minutia questions, but if you can't be bothered to understand how and why to optimize a database or the difference between TCP and UDP (really?) and that's what the job requires, then I don't want to hire you.

My argument is don't play puzzles, don't ask stupid questions about "What does this command do with these flags?".

An interview should be the same as a discussion about concepts you'd have with a colleague. Does the person know the concepts? That's all that matters.

Re: I will not do a tech interview

#285
post #95

Earlier quoted context omitted.

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…

> 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.

On the upside, the person with a code portfolio and less other hobbies is also more likely to be winning to commit more of their time to work, stay later, do "hackathons." It's a win-win for the employer! /s

Re: I will not do a tech interview

#286

Earlier quoted context omitted.

It seems to me that software engineering is one of the only fields with people arrogant enough to assume that employers should hire folks without being able to see what they've actually accomplished. A "portfolio" does not have to, and should not , consist of side projects. Don't have any real code that you are allowed to share? Obviously, many employers won't hire engineers without reviewing existing code or having…

What? Not everyone works on front-facing, UI applications. What if I contributed a good amount of code to a large tech company's networking infrastructure. What do you want me to show you? A picture of the servers? A picture of Amazon's homepage or google.com, if those are the companies I'm working for? Not being able to show "code" or "screenshots" is not the fault of the prospective employee (as you "oh so subtly"…

If you're concerned about your ability to convince a prospective employer that you're the real deal, that's for you to figure out, isn't it?

The point here is not what you share, but that you have something to share and can present it in a manner that's compelling to your prospective employer. In some cases, that might be nothing more than a well-written, detailed description of what you developed. In others, a picture is worth a thousand words and can a preferable format for somebody who isn't a great writer.

And finally, while I wouldn't be so naive as to argue that "engineering" equals "working on public-facing applications", engineers should consider the risks of roles that do not enable them to work on systems that are "visible" or "close to the money". Obviously, there are some industries and specializations that provide lucrative opportunities that don't do this, so there are exceptions. Not every young engineer, however, can realistically count on being able to build a decades-long career in these industries/roles.

Re: I will not do a tech interview

#287
post #17

Earlier quoted context omitted.

Google recently revealed that going back over the data they kept about past hires demonstrated that an individual's GPA was completely independent of the quality of their future contributions to the company. Why should Oracle be any different?

google are a notoriously selective employer, so it's hardly surprising that GPA has limited predictive power within the sample of people who were successful applicants.

That could go the other way too - if they don't hire people based on their GPA they might be weeding out bad developers even if they did well in school.

Re: I will not do a tech interview

#288

Earlier quoted context omitted.

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.

>Is it a good signal most of the time? No.

Neither of us have statistics on that, so a yes/no battle here is pointless. I and many others find it to be a useful signal when someone demonstrates intense anxiety under pressure, you and many others do not. Agree to disagree.

Re: I will not do a tech interview

#289
post #255
post #135

Earlier quoted context omitted.

I'm curious, is this a money issue, i.e., you refuse because it feels like working for free? Not OP, but it doesn't "feel" like working for free. It is working for free. Having someone perform work for you without paying them is illegal in the United States (see minimum wage laws). There's a simple solution; pay them $x per hour to do your 3 hours of work. Even if you pay them $100 per hour that's a cheap way of filt…

Hm, I guess I didn't think about it that way since we wouldn't actually ever give out "real" work, we give out the same problem (which is an extremely scaled down version of a real application) to most everybody who passes a phone screen. I think paying them is perfectly reasonable, but I'll also note anecdotally that having done this for many candidates for years, I think very few people have ever declined.

>>...which is an extremely scaled down version of a real application

You're putting the candidate in a very vulnerable and stressful position:

You're potentially asking a candidate to solve a problem with your application (even if scaled down)--

The question/assignment could be a long-standing issue your staff have been unable to address on their own and you want to try to find out whether you can get a free solution from qualified people.

The candidate(s) could get the correct answer, yet you could walk away from the process with a free solution.

>> "I think very few people have ever declined"

That's short-sighted - they're not declining because the want/need a job and are already vulnerable during the process; many would not, understandably, have the presence of mind to decline.

Re: I will not do a tech interview

#290

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/…

Yes the problem is with freezing up. As a person with ADHD, high pressure situations will cause a lockup if my brain due to the inability to focus.
Post reply on HN