Tubi Software Engineer interviews, per four candidate reports, combine a recruiter call, coding, system design and sometimes a product or project round. Formats varied by candidate, so confirm each round's format in advance.
$225K
Avg. Base Comp
$250K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Four candidates describe Tubi's Software Engineer interviews, and the clearest shared element is a recruiter conversation followed by coding and system design. Beyond that, the format varied from person to person, so confirm what each round will cover before you prepare. One candidate was told the first coding round would use pseudocode but got LeetCode-style problems instead.
Coding questions reported include a sorting problem with input cleaning, lowest common ancestor in a binary tree, and designing a special stack. Another candidate called the coding round easy-to-medium LeetCode style. A candidate who interviewed for an iOS-focused role built a grid of more than 100 tiles where tapping a white tile turned it and its white neighbors blue, which is a flood-fill traversal. Another described the coding as practical rather than algorithm-heavy.
System design questions ranged widely. Reports include an EventLogger class that batches events and sends them at set intervals, a WhatsApp-style chat app at high and low level, and a top-K problem with a machine learning angle. One candidate could choose frontend or backend for system design. Practice thinking aloud and asking clarifying questions early, since two candidates described communication friction in design rounds.
One candidate also had a project retrospective with a senior leader, and another had a product sense interview. For these, prepare a project you can discuss in depth, covering design decisions and collaboration. Outcomes among the four were two no-offer results, one rejection and one withdrawal, and two candidates described slow or unclear communication on timing.
Synthesized from 4 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Tubi process.
I got contacted by a recruiter at Tubi about a Software Engineer role in their Builder's Program. The whole process felt disorganized from the start, which honestly set the tone for everything that followed. The recruitment pipeline consisted of three elimination rounds: a DSA coding interview, a system design round, and a product sense interview. The recruiter coordinated things quickly enough, so at least there wasn't a huge wait between rounds, but the actual interviews were where things got messy.
The DSA round was the strongest part of my experience. It was a fairly straightforward, easy-to-medium difficulty LeetCode-style problem, and the interviewer was engaged and clear. I felt good walking out of that one. The system design round was a different story. You could choose between frontend or backend, which was nice flexibility, but I ran into a communication wall with my interviewer. They seemed to struggle following my explanations, and I couldn't tell if I was being unclear or if we just weren't connecting on the technical level. When I'd reference things we'd discussed earlier, they'd ask me to repeat myself. It felt like I was climbing uphill the entire time.
What really bothered me, though, was the bigger picture. I later found out that the hiring manager who initially reached out to me on LinkedIn—the one who sent this thoughtful message about why I'd be a great fit—didn't think I was right for the role after I'd cleared the technicals. It made me wonder why they even contacted me in the first place. Apparently, they use AI-based sourcing without doing real due diligence, which explains the disconnect. The whole thing felt like a waste of everyone's time. No one seemed to care that I'd spent weeks prepping and going through multiple rounds. Neither the recruiter nor the hiring manager treated the process like it involved actual human effort on my end.
Prep tip from this candidate
The system design round can be a communication minefield—practice articulating your design decisions clearly and get comfortable asking clarifying questions early. Also be aware that this company uses broad AI-based sourcing, so make sure the hiring manager who reaches out has actually reviewed your work before you invest time in their interview loop.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Tubi
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Top Three Salaries | |
| Monthly Customer Report | |
| Merge Sorted Lists | |
| Rolling Bank Transactions | |
| P-value to a Layman | |
| Prime to N | |
| Largest Salary by Department | |
| Top 3 Users | |
| Raining in Seattle | |
| Find the Missing Number | |
| Hurdles In Data Projects | |
| Google Maps Improvement | |
| Address Schema | |
| Retailer Data Warehouse | |
| Permutation Palindrome | |
| Integer to Roman | |
| Liked Pages | |
| Employee Salaries (ETL Error) | |
| Session Difference | |
| One Element Removed | |
| Size of Joins | |
| Basic Regex | |
| The Brackets Problem | |
| String Subsequence | |
| Flatten N-Dimensional Array to 1D Array | |
| Centralized Event Ingestion | |
| Paired Products | |
| Nearest Common Ancestor | |
| Groups of Anagrams |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report starting with a recruiter conversation, which one described as a standard 30-minute screening. Ask the recruiter in writing what format each later round will take, because one candidate found the first coding round differed from what they were told.
Reported problems include sorting with input cleaning, lowest common ancestor, a special stack, and an iOS tile grid with flood-fill behavior. One candidate called the problem easy-to-medium LeetCode style, while another found it practical rather than algorithm-heavy. Difficulty may vary by team.
Candidates report designs such as an event logger that batches and sends events, a WhatsApp-style chat app, and a top-K problem with an ML angle. One candidate was offered a frontend or backend choice. Expect to practice clarifying requirements and explaining trade-offs clearly.
One candidate reported a product sense interview, and another described a project retrospective with a senior leader focused on technical design and collaboration. This round does not appear in every report, so ask whether it applies to your loop and prepare a project example.
One candidate received an automated rejection nearly three weeks after system design, later than the stated timeline, and got no recruiter reply. Another withdrew after a mismatched final round. Candidates may want to ask for explicit timelines and follow up politely.
