Own Figma's build/CI platform across a polyglot monorepo serving thousands of engineers

This is a technical-leadership role on Figma's Build Systems team, responsible for the build pipelines, CI, merge queues, and test frameworks that every Figma engineer depends on. Expect deep questions on monorepo build systems (Bazel-class tooling), AWS-scale CI infrastructure, and how you drive multi-quarter velocity initiatives while mentoring other engineers.

Practice this interview

Free · a live voice mock calibrated to this exact role

Start the mock interview

What this interview tests

Build systems (Bazel/Buck/Pants/Gradle) at monorepo scale
CI/CD reliability and developer tooling
AWS infrastructure for build pipelines
Technical leadership and mentorship
Cross-team roadmap ownership

Common question themes

Walk through a build system or CI migration you led end to end

How do you diagnose and fix flaky tests or slow CI at scale

Tell me about mentoring an engineer through a hard architectural decision

How do you balance a multi-quarter platform bet against quarterly delivery pressure

Describe a time you had to influence senior stakeholders on technical direction

How candidates describe it

Real Software Engineer 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 Figma Software Engineer interviews

All Figma interviews