News for hackers. Stuff that matters.
Re:Everything I googled in a week as a professional software... by blackflame7000 on Friday September 06, 2019 @02:48PM (#20898600)
Isn't that what a whiteboard interview is? Proving you can do things without google or else you aren't a proper engineer? (For the record I disdain whiteboard interviews as the accepted metric for testing one's ability)
Re:Everything I googled in a week as a professional software... by munchbunny on Friday September 06, 2019 @04:07PM (#20899413)
IMO it's not. I've never given or taken a whiteboard interview where the I (or the candidate) was not allowed to either google things or to make assumptions about how certain things worked.

For example, if your solution involved generating all permutations of a sequence, and you didn't remember how to do that efficiently, I would let you make up a black box function that just does it. We might come back to this later in the interview, but I'm generally uninterested in whether you memorized an algorithm for it or remembered how to call the standard library function that does it.

That said, if you make up the black box function, I might dig into why you designed the function signature the way you did, and I'd do that to see whether you can talk about code design from a "other people will read and use and debug your code" perspective.

Re:Everything I googled in a week as a professional software... by Infinitesimus on Friday September 06, 2019 @04:33PM (#20899621)
> if your solution involved generating all permutations of a sequence, and you didn't remember how to do that efficiently, I would let you make up a black box function that just does it

But sometimes, the interview question is generating all the permutations :(

Re:Everything I googled in a week as a professional software... by munchbunny on Friday September 06, 2019 @05:07PM (#20899916)
True... but that does mean they're not expecting that you can remember the algorithm. :)
Re:Everything I googled in a week as a professional software... by latencyloser on Friday September 06, 2019 @03:36PM (#20899098)
Not necessarily. The purpose is to show how you reason your way through a problem where you can't simply google "how do I solve x problem." It's intended to see how you communicate, how you handle mistakes, how thorough you are in double-checking yourself, your work style (do you jump right in or ask lots of questions first), etc.

In any case, there's a lot of strategies to show that you understand a concept without relying on exact memorization. For example, a common answer I give if I can't remember something might be something like: "The language has a sort function that can accept a list, I don't remember the exact API or the underlying implementation but let's assume it's n log(n) as that's a common runtime complexity for sorting--I'm going to define that as 'sort(listArg)'." I don't remember the exact function, so I'll just define and explain how it might work myself. If you're expected to be able to compile the code you're writing, simply ask the interviewer and explain the API you're looking for, I've had great success with that as well and prefer when an interviewee asks me over staring at the screen or board.

If it's a problem where you're expected to produce some algorithm, if you can't come up with any solution, explain to your interviewer what you're stuck on. They may provide a hint that will get you rolling. I had this happen during an interview at Microsoft (spoiler, I got the job) where I forgot how to determine the length of the hypotenuse of a triangle haha. The interviewer wrote the formula on the board and we moved on. Interviewer later told me I seemed nervous and he chalked it up to a brain fart--good call, I was really nervous! The point of that problem wasn't to see if I knew the Pythagorean theorem--it was just a small piece of the puzzle I was stumped on. Similarly start from a simple, naive solution, and interatively optimize rather than trying to recall a perfectly optimal solution. If time is running low, explain your intended optimization or ones you think might be meaningful, making note of any uncertainties in that explanation.

I've worked at Microsoft, Amazon, some other notables and interviewed at many others. I am speaking from that experience. Others may have better ideas. Of course, not all places approach this in a reasonable fashion and some are just missing the point entirely with their interview and they do expect you to somehow memorize everything.

Re:Everything I googled in a week as a professional software... by blackflame7000 on Friday September 06, 2019 @03:50PM (#20899255)
I totally understand your philosophy and you make some great suggestions, but overall there's one big flaw with whiteboard interviews: Artificial Pressure and its impact on people's ability to think clearly on the spot. I am a very methodical thinker which is why I tend to prefer work in large scale ore high-performance systems where you consider the implications of thread contention and so forth. I've designed and built multiple large scale production systems and i've also simultaneously forgotten whether it should be += or =+ during a whiteboard interview because of a phenomenon I can't quite describe. Obviously I was laughed at for someone who's actually had 10 years experience with c++ to forget something so basic but it happens when you are on the spot.

The biggest problem with whiteboards is that they reward exactly what they say they try to weed out, rote memorization. It's no secret you could spend weeks practicing on leetcode for an interview but those skills simply don't translate to real-world programming. Algorithm design is maybe 2% of software engineering. The vast majority is knowing what pieces of technology are out there in order to avoid reinventing the wheel all the time. Whiteboards don't test that skill. It tests a marathon runner on their 100 meter dash time.

Re:Everything I googled in a week as a professional software... by abalone on Friday September 06, 2019 @03:59PM (#20899343)
> Obviously I was laughed at for someone who's actually had 10 years experience with c++ to forget something so basic but it happens when you are on the spot.

This 100% happened to me (apart from being laughed at) only it was even more of a meltdown. Also 10 years experience and a problem I could do in my sleep. It was my first interview after a long time and it triggered performance anxiety and nervousness.

The solution is you need to practice live interviews, not just leetcode solo.

Re:Everything I googled in a week as a professional software... by levythe on Friday September 06, 2019 @06:58PM (#20900625)
If the system is so poorly evaluating people that they have to train an irrelevant set of skills to succeed in it, what does that say about the system?
Re:Everything I googled in a week as a professional software... by blackflame7000 on Friday September 06, 2019 @08:06PM (#20900931)
I am a big fan of the take-home problem. For example, Symantec once asked applicants to design a simple virus detector with wildcards (similar to grep) and then they gave interview spots to people with the best performance. During the actual interview, however, there wasn't much whiteboard coding only designing or "how would you do X" sort of questions.
Re:Everything I googled in a week as a professional software... by levythe on Friday September 06, 2019 @08:48PM (#20901087)
There's a small list of companies I'd do a, "Take home test," for. In my experience, most companies that ask for it are looking for free labor.
Re:Everything I googled in a week as a professional software... by crummy on Friday September 06, 2019 @09:07PM (#20901141)
I've never done a take home test that produced anything that could have been vaguely useful for the interviewing company. Usually the problems are pretty artificial.
Re:Everything I googled in a week as a professional software... by mjfisher on Saturday September 07, 2019 @04:29AM (#20902549)
They absolutely should be artificial problems. If they're not carefully designed to test what the hiring company cares about, it's a bad test
Re:Everything I googled in a week as a professional software... by blackflame7000 on Saturday September 07, 2019 @12:06PM (#20904633)
Well if they are good enough for you to put their code into your program then shouldn't they be good enough to be offered a job? Seems like it works exactly as intended in terms of trying to find someone who can do the job
Re:Everything I googled in a week as a professional software... by levythe on Wednesday September 11, 2019 @07:32PM (#20945910)
I've had multiple take home tests result in changes to the products that company offers. I've never received a job offer from those companies. Maybe your experience differs, but I've had a sour taste left by such practice.
Re:Everything I googled in a week as a professional software... by abalone on Friday September 06, 2019 @10:26PM (#20901401)
I wouldn't say coding algorithms is "irrelevant". It's sort of like saying the SAT is irrelevant. It's a general aptitude test. It's not about the "relevancy" of trigonometry to your day to day work.

You could argue it's stupid and colleges should only look at personal essays and GPAs and extracurriculars. But then there's problems with that too (lack of standardization for one).

You could argue that high schools shouldn't teach trig or calc because they're largely irrelevant to most tasks in most fields and "what does that say about the system". But actually they do come into play once and awhile and lay a conceptual foundation, so they're still sort of useful to learn. And thus they form a good common foundation to test aptitude inside an hour or so, or at least no one's thought of a better one.

Re:Everything I googled in a week as a professional software... by blackflame7000 on Friday September 06, 2019 @08:02PM (#20900915)
I knew when the interviewer pulled out his phone to snap a picture of only that part of the whiteboard that I didn’t get the job lol
Re:Everything I googled in a week as a professional software... by xvector on Friday September 06, 2019 @04:04PM (#20899390)
Whiteboard interviews exist because without them companies wouldn't have a metric to artificially restrict hiring. Passing a whiteboard interview makes both the company and interviewee feel special and maintains the bubble of software engineering salaries.
Re:Everything I googled in a week as a professional software... by lliamander on Friday September 06, 2019 @06:01PM (#20900295)
Companies don't care about artificially restricting hiring: they want developers to be as cheap as possible.

The truth is, software engineering really quite hard, but that whiteboard interviews just happen to be a rather poor way of evaluating candidates.

A work sample test, structured interview, or IQ test (alone or in combination) would be a much better filtering process.

Re:Everything I googled in a week as a professional software... by abalone on Friday September 06, 2019 @10:30PM (#20901414)
> A work sample test, structured interview, or IQ test (alone or in combination) would be a much better filtering process.

I'm not sure what any of these mean in concrete terms. Is an IQ test like those "why are manhole covers round" Microsoft questions of yore? Yuck. Is a work sample a homework test? That takes more time for both parties. It's not a good substitute for a 1 hour first round screen. And what's a "structured" interview??

Re:Everything I googled in a week as a professional software... by james_s_tayler on Saturday September 07, 2019 @02:44AM (#20902186)
You should probably look up what an IQ test involves instead of just guessingly blindly, getting it wrong and then writing off the suggestion based on a wrong assumption.
Re:Everything I googled in a week as a professional software... by xvector on Saturday September 07, 2019 @02:24PM (#20905583)
Is stratifying income based off of IQ any more than we already have something that would benefit society?
Re:Everything I googled in a week as a professional software... by lliamander on Saturday September 07, 2019 @05:47PM (#20906758)
in sofar as IQ helps predict actual job performance, I'd say yes.

Now I'm not saying the situation isn't complicated. In the mid-20th century, IQ testing was a great driver of social mobility. However, as was pointed out in _The Bell Curve_, it's becoming the opposite. From what I understand, the heritability of IQ and assortative mating (i.e. people marrying other people of similar IQ/educational attainment) are the main drivers of this.

I don't think the formation of an entrenched class system is necessarily a good thing, but I think in the local context of our industry there's still a lot of good that could be done by improving our hiring process. I mean, would you rather hire people who only sound smart, or who are smart?

Re:Everything I googled in a week as a professional software... by lliamander on Saturday September 07, 2019 @02:31PM (#20905625)
You have questions, and I have answers!

https://www.wired.com/2015/04/hire-like-google/

If you have more questions after reading that, then ask away.

Re:Everything I googled in a week as a professional software... by sharadov on Friday September 06, 2019 @03:17PM (#20898902)
Every engineer on HN (several threads that I've browsed) seems to have a serious disdain for coder-pad interviews/whiteboard sessions. And I think HN has a good representation of software engineers. So, who are these companies hiring?
Re:Everything I googled in a week as a professional software... by munchbunny on Friday September 06, 2019 @05:31PM (#20900087)
A couple personal observations here.

I think there's a serious disdain for interviewing in general. The whole process sucks from end to end. Often it's because the interviewers just aren't good at it. But when it comes down to whiteboard interviewing, I think it's about your value system.

More specifically, I think every interviewer has an opinion on the practical <--> theoretical spectrum, and the problem is when the candidate disagrees with the interviewer's opinion on where on the spectrum the interview should be.

The upside of a practical interview is that you are testing whether they can do the work. The downside of a practical interview is that it indexes heavily on experience and lightly on the ability to cross disciplines. Theoretical interviews are the reverse.

So the important question is: what does your team care about? Google will care much more about the ability for their engineers to move around than your startup will. In general large companies will care much more about portability. They have deeper pockets and are therefore more willing to train you on the job, so generally speaking if they think you can ramp up (even for senior hires), they're happy. As much as startups will say they see things this way, it's not really true. Startups in general care that their senior hires come with substantial domain expertise.

Re:Everything I googled in a week as a professional software... by NoodleIncident on Friday September 06, 2019 @05:05PM (#20899891)
I'm not sure HN is representative of anything, especially if you only look at what's upvoted. If I had to guess, I'd say that this sentiment is posted by people with 10 years of experience who feel like they should be talking about something else during interviews, but that it's being upvoted by college students or recent grads (no matter what you're asked to learn, a large fraction of the group will be frustrated by it)
Re:Everything I googled in a week as a professional software... by sanderjd on Friday September 06, 2019 @03:53PM (#20899287)
They are hiring a bunch of people who have a serious disdain for the way they are interviewed. A better question might be, "who are these companies putting in charge of their interview process?". I think the answer there is largely, "people who have a serious disdain for this kind of interview, but still need to interview people and don't have any better ideas for how to do it".
Re:Everything I googled in a week as a professional software... by abalone on Friday September 06, 2019 @03:23PM (#20898969)
Every student I’ve ever met seems to have a serious disdain for exams, but for some reason universities keep giving them.
Re:Everything I googled in a week as a professional software... by sharadov on Friday September 06, 2019 @05:43PM (#20900195)
I would rather do an exam every year, and get a grade on the skills that they expect. Exams are standardized, granted that they are not perfect, but its closest to a system that works. Am not at the whims and fancies of an individual interviewer.
Re:Everything I googled in a week as a professional software... by abalone on Friday September 06, 2019 @10:35PM (#20901432)
I'm not sure what you mean by standardization. You're totally at the whim of the exam-maker either way. If anything I find algorithm screens tend to draw from a semi-standard set of fundamentals as outlined in books like Cracking the Coding Interview and tested on Leetcode among many other examples.
Re:Everything I googled in a week as a professional software... by kenhwang on Friday September 06, 2019 @03:52PM (#20899276)
I let candidates use their phone to Google or ask me to Google on their behalf. What they're Googling for never matters in the context of the interview and it's mostly to make them feel more comfortable.

It's a whiteboard, I'm looking out for far more important things than whether the method is named `size` or `length`.

Re:Everything I googled in a week as a professional software... by jonfw on Friday September 06, 2019 @03:11PM (#20898820)
A good whiteboard interview doesn't require much outside of basic syntax/data structures, and will offer some form of help along the way (often in the form of a somewhat helpful interviewer).
Re:Everything I googled in a week as a professional software... by lliamander on Friday September 06, 2019 @05:52PM (#20900254)
I think whiteboard interviews are fine, so long as the candidate is told ahead of time what the subject the whiteboard test will be about and has time to study for it (perhaps even given a take-home coding assignment about the same subject) and where the subject is actually relevant to code that has been written at the company.

But I do think that Computer Science Jeopardy on a whiteboard is a bad idea.

Re:Everything I googled in a week as a professional software... by TrackerFF on Friday September 06, 2019 @05:10PM (#20899937)
A good interviewer will not care about syntactic things, but rather try to sniff out your workflow and thoughts / processing when breaking down a process. It should be a proper two-way interaction.

A shitty interviewer will follow a rigid script and "ding" you on trivial errors.