← Back to Directory

Tubi

Mid-sized

Screna has 13 Tubi interview write-ups. The most reported round is the technical phone screen (11).

13 interview notes · updated Jul 2026

Tubi·Machine Learning Engineer·Onsite - System Design / Architecture

Jul 2026
ML system design round at Tubitv for an MLE role, focused entirely on building a thumbnail selection system for a streaming catalog. Pretty deep dive, lots of follow-ups that pushed into territory I wasn't fully prepared for.
  • Design an end-to-end ML system that selects which thumbnail to show each user for a given streaming title, with the goal of maximizing engagement. Cover problem framing, data, modeling, offline and online evaluation, serving, and production monitoring.
  • Your training data only has feedback for thumbnails that were actually shown. How do you reason about thumbnails that were never shown to a given user, and how do you evaluate a model that needs to compare all candidates?
  • If a click-maximizing model starts surfacing sensational or slightly misleading thumbnails that get clicks but result in low watch completion, how do you detect that and adjust the objective?
  • A brand-new title enters the catalog with five thumbnails and zero engagement history. Walk through exactly what the system does for that title over the first hours and days.
  • How would you determine whether personalizing thumbnail selection per user is actually worth the added complexity compared to just picking one globally best thumbnail per title? What experiment would you run?

“This was the main question and it ate up most of the session.”

View Post

Tubi·Machine Learning Engineer·Technical Phone Screen

Jun 2026
Interviewed for an ML Engineer role at Tubitv and got a probability/sampling problem that looked deceptively simple at first glance. The core challenge was implementing weighted random sampling efficiently, which ended up being more of an algorithms question than anything ML-specific.
  • Design and implement a class that takes an array of positive integer weights and supports a method that returns a random index with probability proportional to its weight, with O(n) construction time and O(log n) per query.

“My first instinct was to just expand the weights into a big array and sample uniformly, which works but blows up memory if weights are huge.”

View Post

Tubi·Data Scientist·Technical Phone Screen

Jun 2026
SQL-heavy technical screen for a data scientist role at Tubi. One meaty question about computing user retention metrics from raw event logs, with a bunch of edge cases baked in to see if you'd actually think through the definitions.
  • Given a raw event log table, write SQL using CTEs to compute new users, retained users, churned users, and net users for a specific target date, broken down by device platform. Definitions are precise: new means first-ever event on that date, retained means active both the day before and on the target date, churned means active the day before but not on the target date, and net equals new plus retained minus churn.

“The definitions sound clean until you start writing the CTEs and realize you need to be careful about what 'first-ever event' means across all of history, not just the two days in scope.”

View Post

Tubi·Data Scientist·Technical Phone Screen

Jun 2026
Tubi data scientist interview with a single very involved measurement question about Super Bowl ad effectiveness. The whole thing was basically one giant case study broken into seven sub-parts, which felt more like a take-home exam than a conversation.
  • Your app ran a 30-second national Super Bowl ad. Design a full measurement plan to estimate the incremental impact on installs and revenue, covering KPIs and measurement windows, identification strategies without a clean control group, a difference-in-differences setup and its assumptions, confounders, uncertainty estimation, falsification checks, and a power calculation for detecting a 4% lift in daily installs.

“This was one question with seven sub-parts and I genuinely did not expect the power calculation at the end.”

View Post

Tubi·Machine Learning Engineer·Technical Phone Screen

Jun 2026
Interviewed for an MLE role at Tubitv and it was a pretty dense technical screen covering everything from basic ML concepts to a full recommendation system design. A lot of ground to cover in one sitting.
  • What is overfitting and what are the common ways to prevent it?
  • Explain bagging and describe when it actually helps in practice.
  • Walk me through linear regression and logistic regression, including their practical differences.
  • How do transformer models work and what are their key trade-offs?
  • Compare SGD and Adam as optimizers. When would you prefer one over the other?
  • How would you approach hyperparameter tuning for a model that's going into production?
  • Design a recommendation system end to end: problem framing, feature selection, model choice, training, evaluation, and handling cold start and feedback loops.

“Pretty standard starting point.”

View Post

Tubi·Machine Learning Engineer·Technical Phone Screen

Jun 2026
ML breadth interview at Tubitv covering a pretty wide range of fundamentals, from classic regression stuff all the way to transformers and optimizers. They also went applied with a full recommender system walkthrough, which I wasn't totally ready for at that depth.
  • What causes overfitting, how do you detect it, and what are the main ways to address it?
  • Explain bagging versus boosting and how each relates to the bias-variance tradeoff.
  • Walk me through linear regression: the core assumptions, when you'd use closed-form versus gradient descent, and how Ridge, Lasso, and Elastic Net differ.
  • How does logistic regression work, including the link function, the loss, handling multi-class problems, and model calibration?
  • Explain how transformers work: self-attention, multi-head attention, positional encoding, and the difference between encoder and decoder architectures.
  • Compare SGD and Adam as optimizers: how momentum and adaptive learning rates work, when each performs better, and what pitfalls to watch for.
  • How do you approach hyperparameter tuning in practice, and what's your view on grid search versus random search versus Bayesian optimization?
  • Walk through a recommender system you've built end to end: candidate generation, ranking, feature engineering, training/serving skew, and how you evaluated it both offline and online.

“Felt solid here.”

View Post

Tubi·Machine Learning Engineer·Onsite - System Design / Architecture

Jun 2026
AI-assisted system design round at Tubitv for an MLE role, focused on building a full movie recommendation pipeline from scratch. You're expected to write actual scaffolding code while reasoning through design decisions, which is a different vibe than a pure whiteboard session.
  • Design a movie recommendation system for a streaming service end to end, covering data ingestion, feature engineering, model training, evaluation, and low-latency serving.
  • Walk through the latency budget for your two-stage retrieval and ranking design. What gets precomputed offline versus computed live per request?
  • How do you construct training negatives from implicit feedback, and what breaks if you just sample them uniformly from the full catalog?
  • You used an AI tool to generate the training loop. What specific bug or train-serve skew issue would you look for in that generated code, and how would you catch it?
  • How do you prevent the recommender from getting stuck in a feedback loop, where it keeps surfacing the same content and never explores new or niche titles?
  • A brand new movie is added to the catalog with zero watch history. Trace exactly how it could show up in someone's recommendations within minutes.
  • What clarifying questions would you ask before starting this design, and how do the answers change your approach?

“This is basically the whole round in one question.”

View Post

Tubi·Machine Learning Engineer·Technical Phone Screen

May 2026
Tubitv ML Engineer interview had a pretty meaty coding portion centered on unsupervised learning. Two connected problems, K-Means from scratch and then extending it into a GMM with EM, which felt like a lot to cover in one session.
  • Implement K-Means clustering from scratch given an N x D matrix of points and an integer k. Cover centroid initialization, the assignment and update loop, convergence criteria, and write tests to verify correctness.
  • Extend your K-Means implementation to a Gaussian Mixture Model using the EM algorithm, and explain how GMM differs from K-Means conceptually.

“I went with random initialization first and then talked through k-means++ as the better option.”

View Post

Tubi·Data Scientist·Technical Phone Screen

May 2026
Tubi data scientist interview with a meaty causal inference question that honestly felt more like a take-home problem than a live screen. The question was well-constructed but I spent way too long on the bias directions before getting to the fixes.
  • Users can opt into seeing a discount banner (treatment), and treated users show higher conversion. Define selection bias, identify at least three mechanisms causing it and the direction of each bias, propose two methods that produce less biased causal estimates along with their assumptions and how you'd test those assumptions, and walk through a small numerical example where the naive estimate is wrong but the corrected method gets you closer to the truth.

“This is the kind of question that sounds manageable until you're actually in it.”

View Post

Tubi·Data Scientist·Technical Phone Screen

May 2026
Tubi data science interview threw a deep stats question at me that was way more nuanced than I expected. The whole thing was basically a stress test on whether you actually understand p-values or just memorize the definition.
  • Explain to a non-technical product manager what a p-value of 0.03 from a two-sided A/B test actually means, and just as importantly, what it does NOT mean. Use a concrete scenario: baseline conversion 5.0%, observed lift of +0.4 percentage points, pooled standard error 0.18 pp. Cover the null hypothesis setup and the 'extremeness under the null' interpretation, why p is not the probability that the null is true, how p-values relate to confidence intervals and statistical power, the dangers of peeking at results early, and finish with both a plain-English explanation you'd give the PM and a Bayesian reframe of the same result.

“This question is a monster.”

View Post