Build across Figma's product stack, from real-time collaborative front ends to scalable back-end systems

A full-stack engineering role spanning Figma's product surfaces (Editor, FigJam, Slides, Sites, Buzz, Growth & Monetization, Internal Tools, Foundations), building features end-to-end from front-end UX through back-end architecture. Figma evaluates for cross-stack technical range, product mindset, and craft rather than a single specialization, with team placement decided during the interview process.

Practice this interview

Free · a live voice mock calibrated to this exact role

Start the mock interview

What this interview tests

End-to-end feature ownership across front end and back end
Performance and architecture tradeoffs in real-time collaborative systems
Cross-functional collaboration with Product, Design, Research, Data
Reliability, security, and scalability of shipped systems
Engineering craft and mentorship/code-review habits

Common question themes

Walk me through a full-stack feature you owned from design through launch

How would you design for performance in a real-time collaborative editing feature

Describe a time you translated an ambiguous user need into a scoped technical solution

How do you balance UX polish against backend scalability when they're in tension

Tell me about mentoring a teammate through code review or design critique

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