Live data from Hacker News

Why do big companies ask unrealistic software engineering interview questions?

tomaszs2.medium.com

41–50 of 92 posts

Re: Why do big companies ask unrealistic software engineering interview questions?

#41
post #13
post #6

Don't publish anymore on Medium, people!

Yeah, you're a software dev, spend an hour learning Hugo ;) (Take this with a grain of salt, I don't want to tell people what to do, I just stop reading your blogpost when it fades out and asks me to sign in...)

I default to scribe.rip for Medium stuff

https://scribe.rip/why-do-big-companies-ask-unrealistic-soft...

Edit: just saw that it won't load the entire article, sad.

Re: Why do big companies ask unrealistic software engineering interview questions?

#42
Same reason the NFL combine has athletes do the bench press and the 40 yard dash. They aren’t going to do a bench press in an NFL game. Neither are they going to a straight 40 yard dash.

However, those activities tend to reveal information about their abilities that are useful in an actual game.

Similarly, while you may not be doing those coding problems in day to day development, those coding problems can (ideally) reveal information about your knowledge and abilities in hat does apply to daily coding.

Re: Why do big companies ask unrealistic software engineering interview questions?

#43

More or less the same reason why psychologists use the Rorschach test [0] Sometimes they are not worried about the specific answer, they're trying to find out your (software engineer) unconscious mind reveals during the process. [0] https://en.m.wikipedia.org/wiki/Rorschach_test

> trying to find out your (software engineer) unconscious mind reveals during the process.

For many decades, Floyd's Cycle Detection algorithm was unknown in academic circles as the most efficient method of cycle detection.

It is not uncommon to encounter this problem in an interview. There's nothing revealing about the unconscious mind and process, other than that the candidate remembered the solution to this problem.

If it was so readily obvious to derive and arrive at a solution, you would have expected the army of PhDs and academics to have done so.

Re: Why do big companies ask unrealistic software engineering interview questions?

#44
These tests and questions are often in place so people feel they can manage the risk/uncertainty of hiring. Some studies show that previous performance is the key indicator of future performance. Interviewing and testing in the hiring process are negligible at best.

Re: Why do big companies ask unrealistic software engineering interview questions?

#45

If you'd like an article giving an explanation for this that doesn't require upgrading to a paid Medium subscription, try this one I wrote a few years ago: https://blog.plan99.net/in-defence-of-the-technical-intervie... It is, natch, hosted on Medium, so you will see a banner, but unlike this paywalled article it's dismissable. Just click the X to make it go away and then you can read the whole thing for free. The su…

A fizzbuzz question would sufficiently address points 1 thru 5.

The issue at hand is that the "unrealistic" algorithm questions aren't fizzbuzz.

Re: Why do big companies ask unrealistic software engineering interview questions?

#46
post #22
post #6

Don't publish anymore on Medium, people!

https://archive.md/Xk2F4 I find it hard to trust the opinion of any “techie” who writes on Medium personally. It reeks of “I want to be an influencer!” type personalities.

Wow, what an incredibly low quality article (TL;DR the questions are hard because the interviewer wants to lord it over the candidate) for something behind a paywall. And he ends with a call to upvote and follow, classy.

Re: Why do big companies ask unrealistic software engineering interview questions?

#48

If you'd like an article giving an explanation for this that doesn't require upgrading to a paid Medium subscription, try this one I wrote a few years ago: https://blog.plan99.net/in-defence-of-the-technical-intervie... It is, natch, hosted on Medium, so you will see a banner, but unlike this paywalled article it's dismissable. Just click the X to make it go away and then you can read the whole thing for free. The su…

Claims 2 and 4 don't apply to the way these algorithmic questions are usually administered at large companies, which is pure whiteboard coding where you can't run any of the code you're expected to write.

Re: Why do big companies ask unrealistic software engineering interview questions?

#49
post #6

Don't publish anymore on Medium, people!

I agree and is not because they are making money out of you (that's fine if you agree) it's mostly because they aren't censorship proof or ideologically neutral.

Medium started expressly for the money. How to let authors monetize.

To criticize it for doing what it was created to do, seems odd.

Sure, there are a lot of software packages out there so any dev can create a new Medium. Who cares? The point was to pull a lot of people to one site to monetize it. They would browse around and find other authors, which is not possible if every dev out there creates their own site.

Just like Twitch isn't it?

Are you saying it is being censored? To what end? What ideology cares about programming. "Those Democrats and their Objects are using the wrong patterns again". "Republicans and their Emacs, holding on to the past".

Re: Why do big companies ask unrealistic software engineering interview questions?

#50

That's the thing I was struggling with, I can solve many of problems for the avg company – but I don't know how to solve a leetcode problem. I bet there aren't as many companies solving the complex problems on a scale. But if we look from the perspective of the company – maybe it's just an filter to get someone very dedicated and nerdy about programming. Less churn, less questions.

I've asked non-leet code questions that aren't directly related to the work the candidate would be doing. It's usually a smallish self-contained problem, solvable in less than a dozen lines, in about 5 to 20 minutes. What I like about it, is that it's novel enough, that I get to see the candidate think through the problem. I get a glimpse into their problem solving capability.

It's not a perfect proxy for how well they'd solve real user facing problems, but so far it has given me a decent indicator of their motivation/passion and apetite for problem solving. There's a dozen other, mostly non-coding questions in the interview, but this one has been the best predicator for me.

(The problem is closer to a more elaborate fizzbuzz with some math parts, than it is to a memorizable b-tree or other leet-code algorithm question)

Post reply on HN