How many rounds is the Tubi Backend Engineer interview process?

Candidates report 3 stages: Recruiter Screen, Hiring Manager Interview, and Deep-Dive Technical Interviews. The interview process section above breaks down what each stage covers.

How much does a Backend Engineer at Tubi make?

Reported compensation for Backend Engineer roles at Tubi ranges from roughly $227k base to $325k total per year, varying by level, team, and location.

What topics come up in the Tubi Backend Engineer interview?

Tubi Backend Engineer interviews most often cover Elixir, System design & architecture, Distributed systems, Backend service development, and Scalability engineering, based on topics extracted from real candidate reports.

What questions does Tubi ask Backend Engineer candidates?

Recent candidates report questions like "Interoperating With Other Languages" and "Traffic Spike High Availability". The question bank above tracks 20 questions for this role, ranked by how often they come up in Tubi interviews.

TubiBackend Engineer

Updated Jul 9, 2019

Tubi Backend Engineer Interview Experiences 2026

Real, anonymous reports from people who interviewed for Backend Engineer at Tubi, newest first and distilled into what to expect across the loop.

Get your personalized Tubi Backend Engineer prep plan

Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.

Build my free plan

Hot & recentNewest first

> 1 year

Average Negative San Francisco, CA

My process took about a week. I had a call with their talent recruiter first, which was basically an intro and resume-forwarding step. A few days later the hiring manager called and we talked about the company, teams, and technologies. He asked about my current job and specifically my experience with Elixir/Erlang/OTP, and while the discussion stayed technical, it wasn’t overly hard.

He did mention they were planning two technical interviews, which sounded promising. But then a few days later the recruiter told me they wouldn’t move forward because their needs didn’t match my skills. The explanation felt questionable to me given my experience deploying Erlang/OTP.

Share your interview experience

Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.