Lead the team building Figma's AI-powered developer workflows and cloud agent platform

Figma is hiring an Engineering Manager for its AI Tools team, which builds the sandbox runtime, cloud agent platform, and workflow orchestration that power AI-assisted developer workflows (agentic CI, code review, background agents) across the engineering org. The role requires Staff-level technical depth before moving into management plus 3+ years managing infra/platform/DevEx teams. Based in SF, NYC, or remote in the US.

Practice this interview

Free · a live voice mock calibrated to this exact role

Start the mock interview

What this interview tests

Cloud agent platform architecture & reliability
Evaluation frameworks for AI-generated code quality/cost/impact
Engineering management: hiring, team culture, execution cadence
Build vs. buy decisions on AI/agent frameworks
Distributed systems & platform architecture depth
Cross-functional partnership (product eng, security, infra, DevEx)

Common question themes

How would you architect a reliable, observable cloud agent platform at scale

Design an evaluation framework to measure AI-generated code quality and cost

Tell me about scaling a platform/infra team from 0 to 1

How do you decide what AI tooling to build in-house vs adopt (e.g. Temporal, Cursor)

Describe a hard architectural tradeoff you made balancing speed vs sustainability

How do you coach engineers through ambiguity in a fast-moving AI tooling space

How candidates describe it

Real Manager 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 interviews