Full-stack engineer building AI-native design tools on the Figma Weave team

Figma Weave is building AI-native craft tools that let designers harness leading AI models without losing precision or soul. This role ships full-stack features across TypeScript/React and Ruby/Go, spanning real-time collaboration, product growth, and platform reliability. Based in Tel Aviv, it's a senior full-stack seat with room to influence architecture and mentor peers.

Practice this interview

Free · a live voice mock calibrated to this exact role

Start the mock interview

What this interview tests

Full-stack system design (React/TypeScript + Ruby/Go/Node/Postgres)
Real-time collaboration and scalability
Production ownership: reliability, security, monitoring
Cross-functional collaboration with product/design/data science
Mentorship and engineering culture

Common question themes

Walk through a complex production system you shipped and maintained end to end

Design a real-time collaborative feature for thousands of concurrent users

How have you worked across frontend and backend in the same project

Tell me about a time you owned reliability/security for a system in production

How have you influenced product direction working with non-engineering partners

Experience with extensibility platforms, plugins, or graphics/rendering (if applicable)

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