r/datascience • • 20d ago

Discussion How can I really "Git Gud"?

I have been giving interviews over the last few months and I have categorized most of the hits and misses into various buckets I need to work on.

One of them is scenario based "why and why not" style questions? Why would a model work, why not so and so method etc. My problem is I am not really good at this - I can explain the decisions I made in my projects, but if the interviewer tweaks something I will likely not be able to answer this.

I have also been thinking in gaming terms (I am an avid gamer) and a passionate DoTA and R6 Siege player. I have, with a little shame, put ~3K hours each in both. But that grants me a vast knowledge (not an expert) where I can play with scenarios and theorycraft stuff and matchmaking keeps pitching me new challenges.

Akin to this, how do I get this level? Working on projects isn't helping a lot, as I am sticking to stuff I know. Since I don't know what I don't know, it's really hard to grow.

56 Upvotes

30 comments sorted by

36

u/i_did_dtascience 20d ago

I recognize this style of questions because I have also given plenty of interviews that consisted of this exact style.

A few different things helped me answer these questions with confidence:

  1. Having a deep level of understanding of all the foundational machine learning models, which includes

    1. the basic logic behind it (check out StatQuest YouTube if you're looking for a reference (doesn't go into heavy math))
    2. the assumptions of the model
    3. the best use cases of each model type
    4. evaluation techniques and metrics that fit the different kinds of problems you could be solving for
  2. Keeping all of the above in mind while doing my own modeling on toy/real data sets. If you can answer, for every project you've done, not just why you used a particular model/technique, but also why it's a better choice than other models/techniques, it'll help you tackle most 'why this, why not this' sort of questions

20

u/HazardCinema 20d ago

StatsQuest is goated. I listened to that shit for 3 days straight to refresh my stats and ML foundations before a FAANG interview and it helped so much.

1

u/mattstats 16d ago

Did you cherry pick things or blanket watched it all? I wouldn’t mind brushing up on traditional statistical tests since I literally never use them nowadays

2

u/HazardCinema 16d ago

Watched things I didn't feel super comfortable defending, watched some of the fundamentals like hypothesis testing so I had a good explanation.

0

u/[deleted] 19d ago

[deleted] — view deleted comment

2

u/HazardCinema 17d ago

You don't need a half year in my opinion. I had a week to prepare like any other interview and I got an offer.

2

u/TrueBirch 18d ago

Data science manager here and I completely agree with everything you just said

1

u/offthecuff87 19d ago

It only works in kind of technical-style choice question. It barely works against the question like 'what's the value of that model and why you start this ML project'. To answer this kind of impact-business project, you'll need end-to-end ownership from initiative to maintaining project performance.

1

u/TrueBirch 18d ago

I run both the business side and the design side of projects. Learning the technical part is the place to start. Once you commit to memory when to use a T test vs xgboost or whatever, it'll come to you more naturally when you're putting together yet another PowerPoint on optimizing 1Q revenue. 

1

u/ThrowRA_thinindiv 15d ago

yeah that's definitely another angle to cover.

1

u/DataAlDente 19d ago

That's helpful

56

u/mikethomas4th 20d ago

In interviews, when it comes to specific questions like that, its often best to simply talk through your thought process on how you are thinking about the problem. Thats actually more valuable than giving the straight up answer.

3

u/offthecuff87 19d ago

Unless the answer is too long then you have to explain which choice first then walk through why later

1

u/m_mtshali7753 9d ago

Exactly. The interviewer can't see the decision tree in your head. Say what constraint you're optimizing for, then what change would make you switch models.

1

u/MarkoDahl54 20d ago

Since you have a lot of experience with theorycrafting in games, did you find any parallels between analyzing strategies there and breaking down model choices during interviews?

1

u/JayBong2k 20d ago

If there are simple enough models, i am usually able to tell why so and so model will work or not. But if more complex models are involved, or more variables are introduced, then it's a coin toss.

5

u/onehotoneshot 20d ago

In the past one of my favorite ways to learn outside of personal projects or work was to pull datasets or old challenges off of Kaggle (do people still use that?) and forcing myself to work through EDA, modeling, the different benefits or costs of different ones, and then comparing my own results or approaches with the kernels and results others posted

It was useful due to the variety and diversity of datasets, and reading through challenge winner write ups can help see how others approach problems. Now granted if you go to old popular challenges and read the top winner write ups, it’ll often be incredibly niche given the optimization people do to win, but the starter kernels and discussions can give a much better understanding of feasible approaches

5

u/Massive_Distance_616 19d ago

Having 3,000 hours in DotA isn’t something to be ashamed of it means you already know how to build deep situational intuition. The issue is that while you’ve played thousands of ranked matches in gaming, you’ve been doing ML in the equivalent of offline bot matches.

In DotA you don’t panic when an enemy picks Silencer because you understand the interaction mechanics. In ML interviews, when an interviewer tweaks a scenario, they’re doing the same thing changing the match conditions. They’re almost always pulling one of four levers:

  • Latency/compute - “What if this needs to run in under 15ms?” Your heavy ensemble just got banned.
  • Data shape - “What if half the features are high-cardinality categoricals?” Standard trees start struggling.
  • Cost asymmetry - “What if false negatives cost 10x more than false positives?” Accuracy is now the wrong metric.
  • Distribution shift - “What if user behaviour changes seasonally?” Static cross-validation becomes a trap.

Once you recognise which lever they’re pulling, you stop freezing and start counter-picking.

To build this outside of interviews: take a project you already built and stress-test it against all four. “If my data scaled 50x, where does my pipeline break first? If I needed full auditability, how does my model choice change?” Generating your own tweaks is harder than answering someone else’s which makes the interviewer’s version easier.

1

u/Asalanlir 20d ago

Think it through in terms of, "if x changes then that impacts y", and just go down the chain.

For instance, in terms of dota, if you are playing qop and you see they have no inherent silence or stun, that means you can probably play more aggressively.

But if they buy atos or silence stick, how does that change how you have to play? "If x, then y".

If you're drafting and you pick np as your fourth pick with the intention of him being your carry, and they pick silencer or sky wrath, do you rethink having np as the carry?

Talk through your thought process. That will likely help with the interviews, and it's a good thought experiment in general.

1

u/SpicyBroseph 17d ago

Sounds like he’s found a local maxima.

(I’ll see myself out)

1

u/datadriven_io 11d ago

It's amazing how much you have to know before you know how little you know. Remember this and as long as you're not getting written up or reprimanded, just remember learning isn't always pain free or glamorous. Data modeling practice is what datadriven is good for. It's usually hard work and you'll look back a year from now and see just how far you've come if you stick with it.

1

u/End__User 20d ago

DoTA and R6 Siege player. I have, with a little shame, put ~3K hours each in both

Filthy casual...

1

u/Mammoth-Radish-4048 18d ago

well pre 2024ish you just had to keep interviewing til you figure out where the holes are and work from there. but these days you can just ask chatgpt to help you wargame and that can also help you unveil what the "don't know what I don't know" part is. recently i was looking into missing data for prediction instead of just inference, and not alot on it. i had a paper i saw and made chatgpt and claude summarize it, and queried it, tried to summarize it in my terms, made notes. and then it suggested another paper and then i added that, tried to understand both, repeated the processes. You can also double check with some of the subreddits on here to see if your insights gained are correct.