|
|
|
|
|
by JohnBooty
1678 days ago
|
|
Even when I don't know the answer I manage to
salvage the situation anyway (They asked me what
"regularization" was in a data science interview,
I had no idea, they told me, and then I told
them all the ways I had done regularization.)
Yeah I've found that interviewers are interested in your thought process, not rattling off canned quiz answers.I do something similar whenever I'm unfamiliar with a term like that in an interview. First, I never bullshit. I'm VERY upfront about not knowing a thing - but like you I say, "can you define that term for me -- perhaps I know it by another name" and more often than not, yeah, I can talk about how I've been doing it or something similar to it. And if not I get to have a discussion about the term and learn something, at least. (Tangentially, being upfront about not knowing a thing gives you more authority when you state that you do know a thing...) This field changes so quickly, I don't think any interviewer ever expects you to know more than a % of the topics broached, but they do expect you to be able to converse reasonably about all of them IMO. |
|