Build the agent infrastructure and platform primitives behind every Figma AI feature

Figma's AI Platform team builds the shared frameworks other AI product teams build on — agent infrastructure, agentic search/context retrieval, the Figma MCP server, and the preview/publishing platform for Figma Make. This is a senior infrastructure/platform role (5+ years SWE, 3+ years in AI/search/dev-platforms) requiring strong system design and cross-team technical leadership.

Practice this interview

Free · a live voice mock calibrated to this exact role

Start the mock interview

What this interview tests

Agent infrastructure: sandboxes, harnesses, and tools for AI coding agents
Agentic search, context retrieval, and ranking for LLM-powered features
Designing platform APIs/primitives with contracts other teams adopt
Preview and publishing platforms for AI-generated code (Figma Make)
System design for scalable, reliable, performant AI infrastructure
Cross-team technical strategy and mentorship

Common question themes

Design an agentic search system that retrieves relevant context for an AI coding agent.

Tell me about a platform API or primitive you built that other teams adopted — what made the contract work?

Walk me through debugging a production issue that spanned multiple services.

How would you build evaluation frameworks for AI-generated design or code quality?

Describe a time you set technical direction across multiple teams and how you documented the decision.

What tradeoffs would you make designing a sandbox environment for untrusted agent-generated code?

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