Build 0-to-1 privacy-safe conversion attribution systems for Netflix's new Ads Measurement team

This role is on Netflix's brand-new Ads Measurement team, building conversion attribution systems from scratch in a privacy-safe way as third-party cookie signal is lost. You'll need broad ad-tech and programmatic advertising knowledge, strong cloud/object-oriented engineering skills, and comfort operating on a fast-moving, newly formed team in the rapidly growing Connected TV advertising space.

Practice this interview

Free · a live voice mock calibrated to this exact role

Start the mock interview

What this interview tests

Privacy-safe conversion attribution modeling
0-to-1 system design on a newly formed team
Programmatic advertising / CTV measurement landscape
Cloud-based, object-oriented application development
Navigating signal loss from third-party cookie deprecation

Common question themes

How would you design a privacy-safe attribution system without third-party cookies

Describe a 0-to-1 system you built and how you scoped the first version

What attribution modeling approaches have you used and their tradeoffs

Tell me about your familiarity with ad tech standards like VAST or OpenRTB, or clean rooms

How do you prioritize and communicate on a fast-moving, newly formed team

How candidates describe it

Real Software Engineering 5 - Ads Conversion Attribution interview stories — retold from candidates' public write-ups, with sources.

Google · L3 Software EngineerOffer

Google L3 software engineer interview: phone screen, four coding rounds, and the Googleyness round

A candidate with two years of experience went from recruiter outreach to offer over about four months. The onsite was four 45-minute coding rounds — three of them featuring binary trees — and one round turned into a 25-minute chain of follow-ups about approximating an optimal solution at scale.

Interviewed June 2020 · Bangalore, IN

Google · L4 Software EngineerNo offer

Google L4 Software Engineer Interview: Eight Rounds, No Offer

An L4 Software Engineer candidate went through two phone screens, three onsite rounds, a culture conversation, and a team-matching call with a Google hiring manager, then watched the process stall for about a month and a half over a tightened experience requirement before an added extended round ended without an offer.

Interviewed February 2024 · Not specified

Google · L5 Software EngineerNo offer

Google L5 software engineer interview: phone screening, three onsite rounds, system design, and a late rejection

A candidate interviewing for an L5 role went through a phone screening, three onsite coding rounds, a mobile system design round, and a Googleyness and Leadership round. Two of the four technical rounds went poorly by the candidate's own assessment, and after roughly two months of silence the recruiter reported that the role had been closed.

Interviewed January 2023 · Not specified

View the original posting

All Netflix Software Engineer interviews

All Netflix interviews