Data Scientist Interview Question

Two of your predictors have a correlation of 0.95. Does that matter, and what do you do about it?

What the interviewer is probing, how to structure your answer, and a spoken example you can adapt.

Quick answer

It depends on your goal. For pure prediction, collinearity barely hurts accuracy; the model just splits weight between the twins. For inference it is serious: coefficients become unstable and their standard errors inflate, so signs can flip between samples and you cannot say which variable drives the outcome. Check variance inflation factors, then drop one, combine them, or use ridge.

Why interviewers ask this

The right answer starts with a question rather than a fix, and interviewers are listening for exactly that. Candidates who immediately say drop one are showing they have a single recipe. Saying that collinearity is an inference problem more than a prediction problem, and knowing that tree ensembles behave differently from linear models here, shows you understand what coefficients actually mean rather than treating them as importance scores.

How to structure your answer

  • Ask first whether the model is for prediction or explanation.
  • Explain what collinearity does to coefficient stability and standard errors.
  • Name a diagnostic such as VIF or a condition number.
  • Give the options (drop, combine, regularize) and when each fits.

Example answer

Spoken example, first person

My first question is what the model is for. If we are scoring leads and nobody reads the coefficients, a 0.95 correlation is mostly harmless. The fit is fine, the predictions are fine, the weight just gets split between the two variables in some arbitrary way. Where it bites is when someone plans to act on the coefficients. Then it is a real problem, because that split is unstable: refit on a slightly different sample and one coefficient swings positive while the other swings negative, and the standard errors are wide enough that neither looks significant even though the pair clearly matters. I check VIF, and anything over about ten I treat as suspect. The fix depends on the pair. If they are the same thing measured twice, like revenue and revenue in local currency, I drop one. If they are genuinely two facets of something, I combine them into a ratio or a single component. If I need both and only care about prediction quality, ridge handles it cleanly by sharing weight in a stable way instead of an arbitrary one.

Walking into this interview soon? GhostPilot listens to your live call, spots the question the moment it is asked, and puts a structured answer on your screen in real time. Try it on your next mock, or grab a $29 Session Pass, no subscription, for the real thing.

See how it works

Follow-up questions to expect

  • How does a random forest handle two nearly identical features?
  • What does a VIF of 15 actually tell you numerically?
  • Would principal components solve this, and what do you give up?

Related data scientist questions

Your interviewer will ask their own version of this. Paste your actual job description into the free Question Predictor and get the 20 questions that role is most likely to ask, with what each one is really probing.

Predict my questions

Rehearse the hard questions before they are asked

Practise with a live copilot, then walk in ready. A $29 Session Pass gets you through the interview with no subscription and no lock-in.

Get GhostPilot