← Back to Directory

Credit Karma

Large Enterprises

Screna has 3 Credit Karma interview write-ups. The most reported round is the system design round (2).

3 interview notes · updated Jun 2026

Credit Karma·Machine Learning Engineer·Onsite - System Design / Architecture

Jun 2026
ML system design round at Credit Karma focused almost entirely on recommendation and ranking systems for their financial product marketplace. Heavy emphasis on multi-objective modeling, label sparsity, and architecture tradeoffs. Pretty deep interview, not a lot of fluff.
  • How would you design an ML system for Credit Karma's marketplace to maximize revenue?
  • Should you use a single model across the entire funnel or separate models for each stage like click, application, and approval?
  • How do you handle conversion labels that don't arrive until days or weeks after the original impression?
  • Conversion rates in this setting can be extremely low, around 0.1 to 0.5 percent. How do you deal with that kind of label sparsity?
  • If you use negative sampling during training, how do you correct for that bias at inference time?
  • You're training on multiple objectives like CTR, conversion, and approval rate. How do you combine these into a single ranking score at the end?
  • What is the actual objective function you'd use for the final ranking step?
  • When does it make sense to use a two-stage retrieval plus reranking setup versus just scoring all candidates directly?
  • Walk through the pros and cons of two-stage versus single-stage ranking architectures.
  • Under what conditions would you choose a two-stage architecture over a single-stage one?

“This was the anchor question that everything else branched off of.”

View Post

Credit Karma·Machine Learning Engineer·Technical Phone Screen

May 2026
Went through a technical phone screen for an ML Engineer role at Credit Karma. The questions were pretty deep on training dynamics and optimization, less about standard ML theory and more about what you'd actually hit in production.
  • What are the likely causes of a multi-task model's loss going NaN or becoming unstable after an initial period of decrease?
  • How would you go about debugging training instability that only shows up after several hundred steps?
  • What loss functions and optimization strategies would you use for a sparse conversion prediction problem?

“This one is deceptively specific.”

View Post

Credit Karma·Machine Learning Engineer·Onsite - System Design / Architecture

Apr 2026
This was a system design round at Credit Karma focused entirely on large-scale ML model serving. Seven questions, all variations on the same core problem: how do you actually serve thousands of models to hundreds of millions of users without everything falling over. Dense session.
  • How would you design a serving architecture that supports hundreds of millions of users across thousands of different models?
  • At inference time, how do you route an incoming request to the correct model out of thousands of available ones?
  • What strategies would you use to efficiently manage and serve thousands of models simultaneously?
  • When should a model be kept in memory versus loaded from disk on demand? What drives that decision?
  • How would you design a scalable model-loading strategy that can handle a large and growing number of models?
  • How do you handle models that are rarely used versus models that get constant traffic? What's your approach to that split?
  • Walk me through the tradeoffs between memory utilization and serving latency in a multi-model system.

“This was the opening question and it set the tone.”

View Post