Design and secure the edge network handling Figma's growing customer traffic

Interview for Figma's Server Platform Foundation team, building the next-generation edge and network layer that all other Figma infrastructure runs on. Covers distributed systems design on AWS, service mesh, and DDoS detection/mitigation at scale. Best suited to engineers with 4+ years building cloud infrastructure who can speak concretely about traffic systems serving millions of users.

Practice this interview

Free · a live voice mock calibrated to this exact role

Start the mock interview

What this interview tests

Distributed systems design on AWS
Internal/edge network and service mesh architecture
DDoS detection and auto-scaling mitigation
Production debugging across stack layers
Network protocols (TCP/HTTP/DNS/SSL) and proxies (Envoy/HAProxy)

Common question themes

Design a service mesh to support a growing set of internal services

How would you detect and auto-mitigate a DDoS attack against edge infrastructure

Describe a distributed traffic system you built or scaled as an IC or lead

Debugging a cross-layer production incident and reducing MTTR

Tradeoffs between TypeScript/Go for infrastructure services

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