1) Working on algorithm problem requires very little in common between interviewer and interviewee. I'm C++/C#, I won't be able to give Ruby dev a real world task and evaluate it properly. Algo/data structure problems are universal and looks similar in any language. In my practice I completely failed to make any conclusions by talking about previous experience. It was not clear to me what person actually did vs what was already on the project, may as well just fixed couple UI bugs on the complex project. This part might be might personal failure as interviewer, but it was it is, and I've seen enough developers with years of experience who barely code. So unfortunately having great resume doesn't prove anything.
2) Everyone knows that big tech companies ask these questions. Knowing that you didn't take to prepare, says one of two things to me: you don't find it interesting topic/usefull or you don't have enough grit to go thru that. When I prepared for the interview I went thru two algo books, it took some time but it was easy for me, I did enjoy the learning part, yes it's not something I use every day. But learning things is a trait of good developer, knowing fundamentals if part of that. Some folks found it useless, but since it's known fact that's being asked on interiewes, motivated developer would spend time and learn it. Over the years at work, we have to learn things that are not interesting and that I'd rather choose not to know at all, same as algorithms to some people. If you can't make yourself learn algorithms to pass interview, likely you wont learn things for the work too.
Your second argument admits that this is basically a hazing ritual. Of course you will have to learn some things you don't intrinsically care about in the course of your work. The difference is, that isn't part of a process that we intentionally designed to be that way. Admitting that your hiring process requires useless knowledge that people just have to learn to get through the process means you admit your process doesn't measure what matters and is just a hazing ritual. You're putting up hoops just to see who will jump through them.
Of course, knowing how to play the system is part of getting a job, but we can still point out that the system is broken. After all, these are systems we set up ourselves.
Solving trivial problems does not give you any useful information about how a person solves nontrivial problems. This is especially true if you are not specifying the language the candidate needs to use.
What if I solved fizzbuzz in Haskell? It certainly would not look like a c# implementation, and you wouldn't be able to judge anything about it other than maybe it might produce a correct answer- is it idiomatic? Is it performant? Will it even compile? Technical interviews (especially when you consider candidates outside of your current language / stack) are about assessing capability and trajectory - willingness to learn and adapt. Rote memorization of objective problems that can be found online tell you nothing about how they will solve problems on the job.
As for point two, memorizing solutions to problems with objective answers isn't a terribly valuable skill; presuming that it should be a requirement without announcing it in the job requirements is certainly analogous to hazing. Unless you want a team with little to no creativity, you are selecting for candidates that do not demonstrate what you actually need- and the success of your team is in spite of your hiring process, not enabled by it.
I am sorry if this came across as either personal or exceptionally harsh, but I am pained by the amount of incredibly intelligent people who are willing to accept that suboptimal things ought to be, simply because they are.
One of the biggest contributing factors for a team's - and company's- culture is its hiring practice, and it deserves far more attention than what our industry gives it.
"Assessing the capabiliyt and trajectory, willing to learn and adapt" - that's the intent of the algo/data sturcture related questions. The questions are not about knowledge of specific algo, but assess way of thinking and write some code. Typically solution include recursion, nested loops, pointers/references, some not-trivial composition, etc. I'm never expecting candidate to know the specfici algorithm righ away.
The fundamental problem with whiteboard / live coding technical interviews is that you're selecting for candidates whose strengths aren't necessarily useful on the job.
They: - have memorized answers to solved problems - work well under immediate pressure - demonstrate knowledge of basic programming techniques
They do not: - demonstrate collaboration - demonstrate researching and gathering requirements (i.e. no access to the internet) - demonstrate planning or reasoning about business requirements
In short, yes, they're solving problems, but they're not solving the same kinds of problems that you'll need them to solve on the job, nor are they solving them in the same way they'll be solving them on the job.
These interviews select based on superficial qualities, and practically ignore the qualities of top candidates (teamwork skills, interpreting technical requirements from business requirements etc.)
I had typed out a lengthy explanation of the process I'm currently using, but I realized I don't want to go too deeply into the weeds. In short, design a small challenge application for candidates to build, with the expectation that it'd take no more than a handful of hours, and let them turn it in on their own time (say, within a week). If they "pass", bring them in for a second, technical interview, which is a conversation based on what they submitted (i.e. how could they do X better, how would they add new feature Y, etc.)
The benefit of that kind of process are numerous: 1- The time commitment of candidates is the same as a long whiteboard interview (or set of them), and they don't need to commit to all of the time at once (takes less time away from their current engagements) 2- The time commitment of employees is reduced to ~2-3 hours (one to evaluate, one to interview) 3- candidates are building a small application, meaning there's not an objective answer to be found on stack overflow to memorize 4- candidates have time to ask questions and demonstrate skills they are passionate about, but might not have been specifically requested- say, testing, user experience, flexible architecture to support future features, that sort of thing 5- The second interview becomes a relaxed conversation, where a broader selection of engineers perform well, as opposed to the more biased high-pressure scenarios that aren't typical of our day-to-day
To do this well, of course, you ought to review the challenge and process each year, and have (preferably junior) employees test it to ensure that it will be respectful of candidate's time commitments and the value of the information the challenge will provide an evaluator. Given that you want to keep it limited to a few hours, you'll need to balance features that you think will be interesting with features that actually yield interesting information about the candidate for a second interview- anything that can be learned by simply asking a question doesn't actually need to be included.
Finally, to return to the original topic of this thread, you potentially eliminate certain cultural biases that are irrelevant; not only is the candidate demonstrating capabilities more reflective of the job itself, but they are doing so before ever meeting in person.
2) There are a billion things to learn as a technology professional. The time you spend practicing specifically to be able to whiteboard algorithms for interviews is time you're not spending doing something else. Something that will be more beneficial to you and to your business on a day to day basis than learning how to interview well. So choosing to do those other things instead doesn't show that you're not engaged.
Not to mention that if I see a candidate is stumped on the modulus part I'll offer them % myself.
The stuff people complain about (big O, data structures, algorithms in theory) are stuff even us with degrees have to study and relearn before job interviews. I think you might be underselling yourself. Those big companies use questions like this (often instead of hard checks for degrees) specifically to allow self-taught coders who are good an opportunity to get in.
To some extent, as other have posted, it is kind of silly, but you might be able to look at it as a leveling of the playing field.
> I never understood how this was a valid metric for determining suitability of a candidate, when candidates have come to expect a FizzBuzz test coming up.
It's not--it's a metric for determining unsuitability.
Well, they're far from the ones with the hardest interviews.
Technical interviews are broken because they favour developers fresh out of college or with academic backgrounds. Not every development task is a coding problem or puzzle, rarely do you ever need to write your own algorithm implementation in real world situations. The times you do, most developers (even the intelligent ones) will Google. My problem solving ability is decent enough I am at a senior level and always complete what is asked of me, but give me a code golf/coding puzzle and unrealistic constraints like only being able to solve it on a whiteboard? I will fail. Ask me to solve problems on sheets of paper as quick as possible? I will fail.
Give me a laptop, an IDE and ask me to build something. Better yet, sit me down with one of the developers in your team, give me a simple Jira task and ask me to help solve it pair-programming style. I would rather hire a developer who can get things done opposed to being able to solve a non-real world programming puzzle I found on Google. Interviews seem to forgo the highly acknowledged fact that developers rely on Google/StackOverflow than companies care to admit.
Problem solving is one percentage of the hiring equation, being a great developer also requires patience, cooperation, understanding and communication. I think above anything else, a developer who is a good communicator is a dream combination. I would take communication skills over coding puzzle solving skills any day of the week.
Even the much beloved FizzBuzz test is a scam. Any developer can memorize a FizzBuzz implementation 10 minutes prior to the interview. I never understood how this was a valid metric for determining suitability of a candidate, when candidates have come to expect a FizzBuzz test coming up. Maybe it worked in 1999, but not in 2016.