Build Netflix Animation's proprietary renderer (Glimpse) — from raytracer to shading system

Join Netflix Animation Studios' core R&D group in Vancouver to build and extend Glimpse, Netflix's proprietary photorealistic rendering engine used across its animated films. This role sits at the intersection of graphics research and production tooling — you'll own pieces of the render/sampling engine, raytracer, and shading system while building tools that lighting, shading, and compositing artists use daily. Best suited for engineers with deep C++ and computer graphics fundamentals who want production-film impact.

Practice this interview

Free · a live voice mock calibrated to this exact role

Start the mock interview

What this interview tests

C++ systems programming for high-performance rendering
Monte Carlo integration, importance sampling, light transport
Raytracing and spatial data structures (BVH etc.)
Shading languages (RSL/OSL/GLSL) and real-time rendering
Parallel/vectorized programming across CPU and GPU
Collaboration with artists on lighting/shading/compositing tools

Common question themes

Walk through implementing or optimizing a Monte Carlo path tracer

How would you speed up ray-scene intersection with a spatial data structure like a BVH

Explain a global illumination technique you've implemented and its tradeoffs

How do you vectorize or parallelize rendering code across CPU/GPU

Describe a time you built a tool for artists and how you handled their feedback

What shading technologies (RSL/OSL/GLSL) have you worked with and how do they differ

How candidates describe it

Real Software Engineer - Rendering 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