News for hackers. Stuff that matters.
Re:What I've learned from 100s of interviews with candidates... by siliconc0w on Wednesday May 24, 2017 @03:00PM (#14412538)
Sure- you don't need a CS degree but you need to know everything taught in a CS degree regardless of it's applicability to real life software engineering.

You should also buy a bunch of books and section off at least a month to study. Especially if you don't have that CS degree. Hope you don't have other obligations like a family or a demanding job.

You should also spend a lot of time doing coding competitions even if you find them boring because you got into engineering to build cool stuff- not solve abstract academic CS puzzles.

You should also practice coding in environments you would never use in real life - like a whiteboard. Every single software engineer on the planet codes in an IDE - but no, you will use a whiteboard. You haven't written by hand since like 2012 so your writing looks like a child's scrawl - better work on that too.

Good luck!

Re:What I've learned from 100s of interviews with candidates... by gaylemcd on Wednesday May 24, 2017 @03:12PM (#14412647)
1. No, you don't need to know everything. You should know what a binary search tree. You probably don't need to know the specifics of how to balance one. (If a company is requiring this knowledge, then they're doing whiteboard interviews poorly [or they have a very specific skillset needed]. That's not a problem with whiteboard interviews. That's a problem with that company or interviewer. It takes maybe a week for a smart developer without a CS degree to learn what they need to know for interviews.

2. Yes, I understand that interview prep might interfere with other obligations. You don't have to study. But it'll help you. I'm not sure what you expect here. Do you want companies to hire based on how smoothly you're able to bullshit about what you can claim to have done in the past?

3. Sure, you could do coding competitions if you want. That'll replace existing interview studying; you wrote your comment as though that's in addition to your previous studying.

4. Yes, true, you don't code on a whiteboard. But this, in and of itself, doesn't matter. What matters is whether whiteboards are more predictive and whether they create a better candidate experience. So, forget whether it's "real world" or not. Whiteboards have their pros and cons. The major benefit of a whiteboard is that it allows a candidate to not get caught up in details, like the exact syntax for some function (who cares?) or writing in all the details of some trivial thing just so it can compile. It allows us to focus on the big picture. It encourages more thought process and communication. On a computer, many candidates just shut down -- they try to get things out as fast as possible, and they stop thinking about what they're actually doing.

5. You do not need to work on your handwriting. I've done A LOT of interviews and this has almost never been an issue.

Re:What I've learned from 100s of interviews with candidates... by dnackoul on Wednesday May 24, 2017 @03:38PM (#14412828)
>1. No, you don't need to know everything... It takes maybe a week for a smart developer without a CS degree to learn what they need to know for interviews.

I just went through a job search and I didn't find this true. I think the bar on algorithms has raised significantly with all of the prep material (your book included) out there. I also found a few companies sent over "things to study" lists that were quite comprehensive and included topics that you might not even see in undergrad.

>I'm not sure what you expect here. Do you want companies to hire based on how smoothly you're able to bullshit about what you can claim to have done in the past?

I think this is a false dichotomy. I had two friends that just interviewed at Stripe and loved their process: https://stripe.com/jobs/engineering-onsite.pdf

Re:What I've learned from 100s of interviews with candidates... by cloakandswagger on Wednesday May 24, 2017 @04:06PM (#14413021)
I would estimate a reasonable amount of prep time prior to interviewing is around 100 hours. This is about how long it will take to brush up on and practice data structures, algorithms, DP, design questions, etc.

This is about 2 months of practicing an average of 2 hours a day, meaning you're still working a day job. I figure this could be reduced to 1 month of prep if you quit your job and have all day to yourself.

Re:What I've learned from 100s of interviews with candidates... by gaylemcd on Wednesday May 24, 2017 @07:05PM (#14414134)
Lots of people get offers with little to no prep.
Re:What I've learned from 100s of interviews with candidates... by dnackoul on Wednesday May 24, 2017 @07:32PM (#14414274)
Usually these are people who are coming from companies with similar interview styles and are passively prepped by being an interviewer (for algos/coding) and designing web-scale systems (for system design).
Re:What I've learned from 100s of interviews with candidates... by jarsin on Wednesday May 24, 2017 @05:14PM (#14413519)
See when I read that strip interview doc I don't worry at all. Thats what I do everyday as a software developer. I would love to demonstrate my ability in interviews like this.

These Cracking the Code interview type interviews are not even close to what we do all day everyday.

Re:What I've learned from 100s of interviews with candidates... by siliconc0w on Wednesday May 24, 2017 @05:20PM (#14413551)
Wow - this kinda blew up.

1. Obviously you have a lot of experience with this but I just can't see how a week is anywhere near accurate judging from my personal experience, people I've talked to, and the numerous online stories of people's personal experience.

2. To be honest, I kinda expect the world's smartest organization to find some better way to evaluate talent. Google says they want diversity but requiring a month of studying isn't going to allow for that. Their process throws false negatives on a lot of people that could otherwise be great engineers (which they largely admit to).

3. They're different skillsets. One is about knowledge, the other is about memorizing question patterns and practicing implementation speed.

4. Does Google have data here? My experience is a lot of candidates shut down at a whiteboard because it's not what they're used to. They're afraid to experiment or erase or use longer clearer variable names because of the overhead of writing by hand and dealing with space limitations. It's a lot more messy to modify and extend code you've already written.

5. No, it's really bad. It's like this weird mix of cursive and small caps. I'm not sure what is going on.

Re:What I've learned from 100s of interviews with candidates... by gaylemcd on Wednesday May 24, 2017 @06:40PM (#14414011)
1. I'm not saying a week for preparation overall. I'm saying a week to learn the core algorithms and data structures. Frankly, that's probably much less than a week to learn.

2. Yes, it does throw false negatives. Lots of people get hired with zero prep though. I generally say about a month of prep is where you hit pretty low returns from more time. But that doesn't mean that you need a month, or that a month will be enough for you.

3. I'm not sure I see your point here. If coding interview prep is a different skillset from coding competitions, then you wouldn't do coding competitions in order to do interview preps.

4. Some candidates do shut down because it's not what they're used to. A well-trained interviewer can mitigate this to some extent (not always). Some people will also shut down at a computer. Interviews will always be an artificial environment and people can freeze for different reasons. At a whiteboard, it's often a bit easier to unfreeze candidates and create a happier atmosphere.

5. That's fine. As long as I can read it, it's fine. And if I can't read it and you can explain to me what you're writing, that will also work.

Re:What I've learned from 100s of interviews with candidates... by NTDF9 on Wednesday May 24, 2017 @03:23PM (#14412728)
>> You should know what a binary search tree. You probably don't need to know the specifics of how to balance one.

Fine. I know this. Will this give me a job? No

>> Yes, I understand that interview prep might interfere with other obligations. You don't have to study. But it'll help you. I'm not sure what you expect here. Do you want companies to hire based on how smoothly you're able to bullshit about what you can claim to have done in the past?

No. I want to be hired for the skills I'm bringing in and not for my ability to solve toy problems on a whiteboard.

If the interviewer cannot filter out bullshitters, the interviewer is incapable of the "job of interviewing". Maybe hire better interviewers. Why is the burden on the candidate?

>> The major benefit of a whiteboard is that it allows a candidate to not get caught up in details, like the exact syntax for some function (who cares?) or writing in all the details of some trivial thing just so it can compile. It allows us to focus on the big picture. It encourages more thought process and communication. On a computer, many candidates just shut down -- they try to get things out as fast as possible, and they stop thinking about what they're actually doing.

I agree with this, only so long as the interviewers don't fret about some stupid edge case. Why is there an expectation of perfect code in 15 mins on a whiteboard? Who does that in production?

The interviewer knows about these edge cases because they've seen the problem before. But I can guarantee that the same interviewer would not be able to 'perfectly' solve some problems that I pose them without having seen them before.

Which brings me back to the question. What is the point of the coding interview (or perfection in coding interview) if the only people who can solve them are the ones who have seen the problem before?

Re:What I've learned from 100s of interviews with candidates... by ryandrake on Wednesday May 24, 2017 @03:31PM (#14412784)
I think we just have to accept that the skills needed to pass an interview are a largely different set than the skills needed to excel at the job. One set of skills is not more important than the other, because you need both of them to get and keep the job. We need to practice both.
Re:What I've learned from 100s of interviews with candidates... by gaylemcd on Wednesday May 24, 2017 @03:37PM (#14412824)
>> >> You should know what a binary search tree. You probably don't need to know the specifics of how to balance one. >> Fine. I know this. Will this give me a job? No

No, it's not about knowledge. The knowledge is needed. But the real focus of the interview is to tackle a new question.

>> I want to be hired for the skills I'm bringing in and not for my ability to solve toy problems on a whiteboard.

The ability to see a hard problem, develop your own solution, and translate that into code is a pretty important skill. "Skills" aren't all about knowledge.

>> If the interviewer cannot filter out bullshitters, the interviewer is incapable of the "job of interviewing". Maybe hire better interviewers. Why is the burden on the candidate?

It's a lot more complex than that. It's not just about filtering out bullshitters. It's also about identifying people who might be great but are unable to talk about it. There's also lots of people who are great but haven't been in situations where they've been able to tackle interesting challenges (either because of their inexperience, industry, etc). Or maybe they've done interesting things but in a related field that's hard to understand.

But, yes, absolutely train interviewers. (Interviewing isn't really a role that you hire for.) But even a very well trained interviewer might not be very effective in a behavioral interview.

>> I agree with this, only so long as the interviewers don't fret about some stupid edge case. Why is there an expectation of perfect code in 15 mins on a whiteboard? Who does that in production?

There generally isn't. What an interviewer should be looking at is not some sort of percent correct element. It's about signal. So if a candidate is totally unable to understand an obvious, that might worry me. The signal the candidate is sending is a poor understanding of details. (Or, maybe not. It depends on the situation.) What I train interviewers on is that correctness in and of itself is not relevant. Why a candidate was correct or incorrect might be.

>> The interviewer knows about these edge cases because they've seen the problem before. But I can guarantee that the same interviewer would not be able to 'perfectly' solve some problems that I pose them without having seen them before.

The interviewer is comparing the candidate to other candidates on the same question. So if a candidate is getting rejected because they failed to be perfect, this means that other candidates are actually getting to perfect solutions. Or you just have a crappy interviewer who rejects everyone.

>> Which brings me back to the question. What is the point of the coding interview (or perfection in coding interview) if the only people who can solve them are the ones who have seen the problem before?

If that's the case? Nothing. But that's not the case.

Re:What I've learned from 100s of interviews with candidates... by dang on Wednesday May 24, 2017 @03:50PM (#14412909)
Thank you for being so patient with some of the more ornery commenters in this thread. It's a topic that cuts close to the bone for many HN users, that frequently brings up feelings of rejection (e.g. elitism of 'top' companies) and frustration (e.g. irrationality of interview processes).
Re:What I've learned from 100s of interviews with candidates... by NTDF9 on Wednesday May 24, 2017 @04:16PM (#14413107)
>> No, it's not about knowledge. The knowledge is needed. But the real focus of the interview is to tackle a new question.

>>There generally isn't. What an interviewer should be looking at is not some sort of percent correct element. It's about signal. So if a candidate is totally unable to understand an obvious, that might worry me. The signal the candidate is sending is a poor understanding of details. (Or, maybe not. It depends on the situation.) What I train interviewers on is that correctness in and of itself is not relevant. Why a candidate was correct or incorrect might be.

This would be great if interviewers actually knew that this is what they are testing for.

At this point, interviewers simply do not care about candidates and make a binary Yes/No decision based on "Did the candidate solve the problem perfectly in 15 mins".

I'm not opposed to coding interviews. But I am opposed to the way it is implemented right now.

The current way would be great if I get to reverse interview the interviewer and prove that I know (knowledge plus problem solving ability) better than the interviewer.

If the interviewer accepts this duel, it's fair game. Otherwise, the current process simply selects the people who can pattern match.

Re:What I've learned from 100s of interviews with candidates... by gaylemcd on Wednesday May 24, 2017 @06:28PM (#14413954)
Yeah, there are interviewers who run crappy interviews. This is not a flaw with the process though. If you replace it with any other process, you're going to find interviewers who are bad at evaluating those too.

For example, on behavioral questions, I've seen many interviewers who think "In our company, we handle disagreements by doing X. So I'm going to see if, when the candidate hit a disagreement, they handled it by doing this."

But that's not right. Different companies have different cultures. What's good in one company is bad in another. This is essentially the behavioral question equivalent of the scenario you're raising for technical interviews -- people looking for particular answers, and not considering the context.

Both situations definitely happen, and are very common. But that doesn't make the process flawed. It generally means that the company hasn't adequately trained interviewers.

Re:What I've learned from 100s of interviews with candidates... by NTDF9 on Wednesday May 24, 2017 @06:54PM (#14414075)
The process is flawed in that it ignores the ability of interviewers to rate a candidate.

The solution to this is not getting rid of coding interviews because (coding sure is important). But the overweight emphasis on coding as a binary decision-making is ridiculous.

There are actual engineers doing actual real coding work. They don't necessarily spend entire days solving puzzles. So, they won't do as well in whiteboard puzzle test as a person who slacked off at their last job/college and just practiced whiteboard coding problems.

But the current interview process would rather select the slacker practicing problems than the effective person who didn't practice problems.

Why?

Because the process is overweight on whiteboard coding accuracy and the interviewers who are incapable of identifying a person's ability outside of that overweighted process.

This is a flawed process. And improvements in the process is impeded by flawed interviewers.

Re:What I've learned from 100s of interviews with candidates... by gaylemcd on Wednesday May 24, 2017 @07:04PM (#14414129)
So what do you suggest?
Re:What I've learned from 100s of interviews with candidates... by NTDF9 on Wednesday May 24, 2017 @08:40PM (#14414564)
I'm glad you asked. I have been following your blogs and posts about interviews and this is the first time I've seen you ask this. This is positive.

I do not have a bulletproof solution but I have implemented processes in my current company that filters in better (measured by performance at work) people than the average prolific whiteboard coder.

1. First, we need to establish the goal of the interview. What is our goal? The goal is find passionate candidates who will get the job done or are bring something that makes our team better. Golden State Warriors will not succeed with a team full of Stephen Curry clones. Note that the goal is not to reduce false positives but to hire the best we can get.

2. With that established, we need to interview candidates and see if they are worth it.

a. If they are a generic software engineer/just out of college/did not get a chance to do something interesting yet, what else besides coding (verified by 2 rounds of non-perfect whiteboarding) did the candidate do? We need to identify if they have the potential to do more than just toy coding

b. If they have been doing something interesting at previous jobs/school they obviously did not have time to practice coding. What were they doing? Is it relevant? Is it it interesting?

With point b, I know you get paranoid about bullshitters. I agree. Candidate b can be a bullshit artist. But, if the interviewer is capable enough, the bullshittery will not go anywhere.

In the light of above, I designed the following:

1. 2 coding rounds. It's ok to miss edge cases as long as you can fix them when prompted with decisive hints. The coding problems are also relevant problems from our own codebases and not just some random "skyline problem" ----Note that the emphasis is "OK on missing edge cases". We just want to know if you can solve the problem and translate it to code

2. System design round: Yes even for college grads. For college grads ask something trivial like how would you design a simple diff or a simple OS/compiler. For experienced folks, ask something relevant to their background. This works really well because it shows which college grad really likes exploring the world of "practical" computer science. This also helps remove bullshitters to a large extent. Linkedin has a great round on this and I really enjoyed that round because it got me engaged with the team and they got to explore sides of me that even I didn't know existed

3. "What is special about you round"...We want to know what makes you special (to compensate for lack of toy coding). Here is where a lot of really good engineers would shine. Some will give examples of a compiler they wrote, or how they applied machine learning to an unconventional area. There are no right answers and it quickly becomes a technical discussion. This round shows how insightful the candidate is. Also, this has to be a full round.....not just a 5 min chit chat thing. The reason for it to be a full round is that bullshitters run out of stuff to talk about whereas the person who was engaged in such projects will go far.

Granted some engineers aren't good communicators but whiteboarding is a bad proxy for hiding bad communication skills since a lot of engineering IS good communication. This same candidate will get hired, write design docs, give presentations, explain concepts, mentor interns, interview other candidates. This person better be a good communicator.

Is this process perfect? No. But neither is the current overweighted whiteboarding

So what does this process do? It tried to "select" the better candidate as opposed to trying to "reject" everyone in the name of reducing false positives.

Not perfect but gets me the candidates who are not just whiteboarders.

I am in the bay area and I'll be happy to walk through this process in great detail if necessary.

Re:What I've learned from 100s of interviews with candidates... by gaylemcd on Thursday May 25, 2017 @08:28PM (#14421190)
Oh, no, I've asked people their suggestions all the time. I typically do in these discussions. In fact, I have elsewhere in this comment section.

I'm sort of confused by your suggestions. You've decided a pretty typical interview process. What do you think is different here?

The biggest difference I can see is that you're saying that the coding is "a relevant problem from our codebase and now just some random skyline problem." And you're specifically calling out that it's okay to miss codebases.

Let's discuss these more. 1. It shouldn't really matter whether it's from your codebase, right? If you have two problems, ProblemA from the codebase (which is worse at identifying relevant skills) and ProblemB (which is a toy problem but better at identifying relevant skills), you should go with ProblemB, right? So really the question is to find a problem that is a good predictor of whatever you care about. If I really want to hire people who are smart, is giving them a challenging problem a good predictor? I think so.

2. The edge case thing. You seem very fixated on this. Why? What interviewers should be thinking about is the signal that the candidate sends. Certainly, in many cases, missing an edge case is just a "I haven't written in certain details yet." In some cases, missing an edge case (particularly after a conversation) might actually signal a much bigger issue. For example, imagine someone didn't write in a check to see if an array is sorted. No big deal, probably. But if there's a repeated issue with this and they can't write this code correctly, then we have an issue. Saying that edge cases don't matter is too broad. They might, and they might not. I encourage interviewers to focus on the signal and not on some binary rule.

Re:What I've learned from 100s of interviews with candidates... by piptastic on Wednesday May 24, 2017 @03:32PM (#14412791)
I'm pretty sure the entire parent comment was sarcastic
Re:What I've learned from 100s of interviews with candidates... by gaylemcd on Wednesday May 24, 2017 @03:42PM (#14412867)
I'm pretty sure I interpreted the comment correctly...
Re:What I've learned from 100s of interviews with candidates... by tutufan on Thursday May 25, 2017 @02:20AM (#14415622)
> Do you want companies to hire based on how smoothly you're able to bullshit about what you can claim to have done in the past?

I want to work for a company that doesn't start with the assumption that I'm a liar, yes.

Going further, it'd be nice to have a company that basically knew what they were looking for, and knew how to evaluate that in a casual conversation.

Re:What I've learned from 100s of interviews with candidates... by codesnik on Wednesday May 24, 2017 @07:17PM (#14414198)
bad handwriting is not an issue for interviewer, but it could seriously ruin thought process for interviewee. It ruins it for me, for sure. You know, good code "looks" good, and that feeling is a major part of programmer intuition for me.