Live data from Hacker News

Deep Learning Interviews book: Hundreds of fully solved job interview questions

github.com

101–110 of 157 posts

Re: Deep Learning Interviews book: Hundreds of fully solved job interview questions

#101
post #32

Why are all the em dashes missing from the PDF?

This may be a rendering issue. Some interaction of the Computer Modern font, the TeX layout algorithm, and Chrome's rendering engine sometimes ends up making em-dashes and minus signs invisible.

I'm not using Chrome's rendering engine, is he?

Re: Deep Learning Interviews book: Hundreds of fully solved job interview questions

#102
post #53

Earlier quoted context omitted.

In part because ML fails silently by design. Even if the code runs flawlessly with no errors, the outputs could be completely bunk, useless, or even harmful, and you won't have any idea if that is true just from watching The Number go down during training. It's not enough to know how to build it but also how it works . It's the difference between designing the JWST and assembling it.

I'm sure this happens, but do you think the problem is actually one of mathematical savvy? My guess would be that more machine learning projects go off the rails for want of understanding the data or the {business, research} problem.

My experience is bulk of the problem is insufficient monitoring. ML systems need heavy monitoring and should be sending lots of metrics to stuff like prometheus/grafana. There should also be validation/consistency checks for all data pipeline/feature transformations. And you should strongly avoid duplicating logic for stuff like feature preprocessing. I've seen people implement "same" feature preprocessing pipeline twice (one python, one java) and it is so common to find edge case bugs for a long time especially when these bugs only slightly impact model behavior.

Another issue is proliferation of data pipelines. The more distinct pipelines you have, the more painful they become to monitor. It is much better to minimize pipelines and do views on a small number. I think proliferations of models is a similar issue. It is often easier to build 4 models instead of 1 multi-task model, but monitoring/operational tasks grow more and more painful as you manage more models.

Re: Deep Learning Interviews book: Hundreds of fully solved job interview questions

#103

I have been working as an ML Engineer for a few years now and I am baffled by the bar to entry for these positions in the industry. Not only I need to perform at the Software Engineer level expected for the position (with your standard leetcode style interviews), but I need to pass extra ML specific (theory and practice) rounds. Meanwhile the vast majority of my work consist of getting systems production ready and hu…

> ... I'll seriously consider a regular non-ML position.

What about asking for more money at the end? Multi-stage complex interview process eliminates more candidates. Some, like you say, will opt for a developer gig instead, probably because ML wasn't something they were interested in to begin with. That narrows down the list of candidates even more. Either "play the game" and ask for more money or don't play the game at all. Let employers pay extra for polished candidates.

Re: Deep Learning Interviews book: Hundreds of fully solved job interview questions

#104
post #87

Earlier quoted context omitted.

Having recently completed an MLE interview loop successfully at a top company, I'm wondering where you are getting asked complicated linear algebra questions in interview?

Hopefully you aren't equating "eigenvectors" to "complicated linear algebra question". But I agree, a lot of MLE roles don't get asked such things. I think the OP's guide is closer to interviews I've seen for phd programs.

> Hopefully you aren't equating "eigenvectors" to "complicated linear algebra question".

They explicitly say something harder than eigenvectors in the GP.

I was imagining something involving the spectral theorem or something like that, ie. beyond the most basic linear algebra.

OPs guide seems to cover plenty of things I'd expect someone to learn in undergrad, I think I touched on almost all of this - except for stuff involving jax and recent CNN architectures, both of which can easily be supplemented online.

Re: Deep Learning Interviews book: Hundreds of fully solved job interview questions

#105

Question aside: using arXiv for distributing such interview questions, seems to me inappropriate. Is there any SEO trick behind it?

Yes I was also surprised how this is hosted on arxiv. Can someone explain why this is ok ? It is definitely not a scholarly article.

Re: Deep Learning Interviews book: Hundreds of fully solved job interview questions

#106

I have been working as an ML Engineer for a few years now and I am baffled by the bar to entry for these positions in the industry. Not only I need to perform at the Software Engineer level expected for the position (with your standard leetcode style interviews), but I need to pass extra ML specific (theory and practice) rounds. Meanwhile the vast majority of my work consist of getting systems production ready and hu…

there's a bunch of gatekeeping to get into ML. Part of it is that ML people don't want non-ML people to know just how much of what they do is drudgery and how little of it is exciting math, or have competition from people with similar skills. And those roles come with a lot of prestige.

I went through all that and am a SWE again instead of an ML engineer. The one thing I learned from all that? "The very best models are distilled from postdoc tears".

Re: Deep Learning Interviews book: Hundreds of fully solved job interview questions

#107
post #90

Earlier quoted context omitted.

That would just test syntax, though. Fizzbuzz tests logic. Your bug was a logic bug. To a certain extent you can dispense with mental logic by using a compiler. But the feedback loop is much slower. Thinking your logic through before feeding it to a compiler is like looking at a map when you're driving a car; you can cut off whole branches of exploration. Binary search is a particularly tricky logic problem in part b…

Ye I meant running it and then correcting the error. Concerning binary search I acctually implemented that in an ECU for message sorting. It took like a whole day, including getting the outer boundries one off too big in the first test run. Funnely enough the vehicle ran fine anyway. I would never pull that algorithm off correctly in an interview without training to, I think.

Take a look at the downvoted-to-0 formulation I gave upthread, then see if you can program it that way tomorrow without looking, and then think it through to see if it could possibly be wrong, and once you're satisfied it's correct, try testing it. Probably you'll never need to implement binary search yourself again, but it's a good exercise for thinking through algorithms. You can probably get it working that way in under an hour instead of a whole day.

Re: Deep Learning Interviews book: Hundreds of fully solved job interview questions

#108

Earlier quoted context omitted.

I had an "implement binary search" interview once. I came away feeling like I was being interviewed for the wrong role. I don't understand how anyone could think that's an appropriate interview task for a DS position.

I'm an MLE and I get asked much harder questions than that. Implement a binary search seems ... fine?

Implementing anything even a little tricky under pressure can be tough. unless you’ve practiced with bit or pointer twiddling regularly, you are mostly validating whether they did interview prep or not. That probably selects for more serious candidates, so it probably works. But i was tripped up by a simple binary search problem the other day, even after i’d just solved several harder problems quite quickly. It’s just the nature of algorithmic problem solving — until you’ve done a lot of prep, it’s dicey whether a novel problem will take me five minutes or five hours to solve.

Re: Deep Learning Interviews book: Hundreds of fully solved job interview questions

#109
post #53
post #41

The ML/DS positions highly competitive these days. I don't get why ML positions requires hard preparations for the interviews more than other CS positions while you do similar things. People expect you to know a lot of theory from statistics, probability, algorithms to linear algebra. I am ok with knowing basic of these topics which are the foundations of ML and DL. But I don't get to ask eigenvectors and challenging…

In part because ML fails silently by design. Even if the code runs flawlessly with no errors, the outputs could be completely bunk, useless, or even harmful, and you won't have any idea if that is true just from watching The Number go down during training. It's not enough to know how to build it but also how it works . It's the difference between designing the JWST and assembling it.

ML doesn't just fail silently by design. because ML is based on error minimization, it fails in a way that is maximally hard to tell from random garbage. This is, remarkably, a subtlety that is lost on most people, which is a real surprise- my introduction to this was in structural biology, where you always do hold-outs and check the performance on the hold-out set before overfitting is such a problem.

Re: Deep Learning Interviews book: Hundreds of fully solved job interview questions

#110

Earlier quoted context omitted.

It will be rat race when there are so many interview books and courses and websites. It was a not rat race before 2005, when there were only two reasons that one can solve problems like Pirate Coins or Queen Killing Infidel Husbands: the person is so mathematically mature that such problems are easy for them; the person is so geeky that they read Scientific American or Gardner's columns and remembered everything they…

You're missing the third category: people like myself who absolutely love this kind of riddles and destroy them in a few minutes, without any significance on their actual work abilities. I don't think I'm a bad engineer, but I'm certainly not the rock star you absolutely need for your team, but when it comes to this kind of “cleverness” tests, I'm really really good. I've had the “Queen Killing Infidel Husbands" (wit…

If somebody asked me logic/brainteaser questions like that, I would politely stop them, explain that if they're asking me that question I'm not a good match for the company, and if they would like to ask a better question, I'm open to it, but otherwise, we can end the application process now. I did that recently with a junior eng who asked me a leetcode question literally with the same exact test data as the leetcode page. I ended up explaining to the CEO that at the very least his engineers should be creative enough to come up with different test data, but that realistically, if "recognize the need for, and implement binary search in 45 minutes" is your go-to question, I'm not gonna be a match at your company.

I had to fight my way into google by doing every bit of prep and practice to solve stupid questions and code quicksort but when I joined, nothing I did in the 12 years I was there required any of that. And I wrote high performance programs that ran on millions of cores (I did know some folks who needed that skill, like the search engine developers, or the maps engine, or the core scheduling algorithms in borg). The entire time I was there I tried to get people to understand the questions they're asking are just not good indicators of programming, but it was repeatedtly pointed out, the goal is to minimize false-positive hires.

I do admire your ability to solve problems like that quickly, always wished I could.

Post reply on HN