The Teams Absorbing Figma's Growth
Figma's hiring bar is a hybrid: you don't reach the top of the band for code alone, or craft alone. You reach it for making the two indistinguishable in the shipping artifact. That constraint — design-first, multiplayer by default — now governs a workforce that has more than doubled since 2022, from 800 (CNBC reported) to nearly 1,900 people (Wikipedia's data shows), even as the stock has fallen from a $56 billion IPO valuation to below $20.
The job board shows six engineering openings across San Francisco and New York: Software Engineer for Traffic and Mobile Web; Engineering Manager for Payload, Storage Platform, Growth Platform, and DevEx AI Tools. That spread maps to Figma's architectural priorities. Traffic and Mobile Web sit at the edge: the multiplayer cursor layer, the WebGL renderer, the WebAssembly modules that make a browser feel like a native app. Payload and Storage Platform own the document model: the CRDT-based sync engine, the version history that never conflicts, the permission graph that scales to enterprise tenants. Growth Platform builds the loops that turn free editors into paid seats. DevEx AI Tools is the newest bet: internal tooling that lets Figma's own engineers ship the Claude- and Codex-powered features announced at Config 2025.
The product roadmap implies hiring in three other clusters. Figma Sites, Make, Buzz, and Draw — the four Config 2025 launches — each need product engineers who understand both the design surface and the code generation pipeline. The enterprise tier, at $75 per editor, counts Microsoft's tens of thousands of designers as its anchor tenant. That tier requires security engineers, compliance specialists, and sales engineers who can navigate procurement reviews at Google, Oracle, and Salesforce.
Design hiring follows a different rhythm. Figma's own product is the portfolio. Candidates who get through the door typically ship work built in Figma, for Figma-adjacent workflows: design systems at scale, plugin ecosystems, developer handoff automation. The company's early traction came from Microsoft's Xamarin team (350 people who became power users overnight) and spread to Airbnb, Dropbox, Stripe, and Twitter through organic adoption. That history means the design team hires people who have lived the migration from file-based tools to multiplayer clouds. They know the friction points because they've hit them.
Go-to-market functions professionalized alongside the IPO. Praveer Melwani moved from head of business operations to CFO in June 2022. Kate DeLeo, formerly of Deutsche Bank and Goldman Sachs, joined the next month as VP of investor relations and business operations. The enterprise sales motion (built around the $75/editor tier with dedicated account managers and advanced password management) now fields a team that speaks procurement language, not just design language. Marketing hires tend to come from product-led companies where the product is the primary acquisition channel.
What connects these functions is the "design-first" constraint in the job descriptions. Engineering managers review design specs with the same rigor they apply to architecture diagrams. Product managers write RFCs that include Figma files as appendices. Sales engineers prototype customer workflows in the tool they're selling.
Two Tiers Share a Ceiling
Figma's compensation runs wide: $115k to $376k base across 112 salaried roles, median $303k. That spread reflects a company hiring both individual contributors and engineering managers across multiple product surfaces, from core collaboration infrastructure to the AI-powered tooling launched at Config 2025. The board data shows two clear tiers: senior IC roles clustering around $153k–$376k, and engineering-manager positions starting at $258k with the same $376k ceiling.
| Role | Location | Base Salary Range (USD/year) |
|---|---|---|
| Software Engineer, Traffic | San Francisco, CA • New York, NY • United States | $153,000 – $376,000 |
| Software Engineer, Mobile Web | Same locations | $153,000 – $376,000 |
| Manager, Software Engineering - Payload | Same locations | $258,000 – $376,000 |
| Manager, Software Engineering - Storage Platform | Same locations | $258,000 – $376,000 |
| Manager, Software Engineering - Growth Platform | Same locations | $258,000 – $376,000 |
| Manager, Software Engineering - DevEx AI Tools | Same locations | $258,000 – $376,000 |
The $153k floor for senior ICs aligns with Bay Area and New York market rates for engineers who ship real-time collaboration features: multiplayer cursors, conflict-free replicated data types, the Dev Mode bridge between design and code. The $258k manager floor reflects scope: these leads own platform areas (Payload, Storage, Growth, DevEx AI Tools) that underpin Figma's user base and the new AI workflows like Figma Make and Figma Sites. Both tiers share the same $376k ceiling, suggesting Figma caps base cash and uses equity to differentiate above that line.
Geography matters less than it used to. Every listing shows San Francisco, New York, and "United States" as concurrent locations, signaling a hybrid-first model where the same band applies whether you're in SoMa, Flatiron, or a remote hub. The board's low end likely covers earlier-career or non-engineering roles not detailed in the current postings (design, product, go-to-market), but the engineering data is the only grounded slice available.
Equity is the missing variable. Figma's post-IPO stock has swung from its debut valuation to under $10 billion by June 2026, per public filings. That volatility means offer letters written today carry very different upside scenarios than ones written a year ago. Candidates should ask for the grant-date valuation assumptions and refresh cadence; the board data doesn't capture either.
The median tells its own story: most hires land in the upper half of the band. That's consistent with a hiring bar that demands portfolio depth, systems design fluency, and cross-functional communication. If you're negotiating, anchor to the median, not the floor, and clarify whether the ceiling is a hard cap or a guideline for exceptional candidates.
Inside the Hiring Filter
Figma does not publish a step-by-step interview playbook, and the public record contains no authoritative breakdown of its pipeline stages. What exists instead is a pattern visible in the roles the company advertises, the compensation bands it posts, and the product philosophy its leadership repeats. That pattern points to a hiring bar built around three measurable filters: craft depth, systems fluency, and the ability to ship inside a multiplayer environment.
The spread between the floor and ceiling of each band is wide enough to cover senior ICs through staff-plus levels, which means the same interview loop must discriminate across a broad experience range. Companies that operate this way typically front-load a portfolio or code-review screen, follow with a systems-design session that mirrors the actual architecture candidates would touch, and finish with a cross-functional panel that includes a designer or product manager.
Recruiters at design-tool companies routinely screen for two signals that map directly to Figma's stated priorities. First, evidence that the candidate has owned a feature end-to-end in a collaborative, browser-based product: real-time sync, conflict resolution, or offline-first architecture are the specific technical scars that matter. Second, a portfolio or GitHub history that shows design-system thinking: component libraries, token structures, or plugin APIs that other teams actually adopted. The emphasis on "portfolio depth" and "systems design" is not aspirational; it is the filter that separates applicants who have built for multiplayer from those who have only built for single-player.
The compensation data reinforces this. A floor for IC roles in San Francisco and New York is above market for generic full-stack work but consistent with roles that demand fluency in WebGL, WebAssembly, or the WASM-based rendering pipeline Figma pioneered. The manager bands imply scope over platform-level surfaces (storage, payload, developer-experience tooling) where a bad architectural call ripples across millions of users. Candidates who reach those levels typically demonstrate they have debugged production incidents in a collaborative editor, not just read about them.
What distinguishes successful applicants, based on the company's public product decisions, is comfort with ambiguity that has a user-visible deadline. The four Config 2025 launches shipped as a cohort, each leaning on the same real-time kernel. Engineers who joined those projects had to negotiate API contracts with designers in Figma files, not Jira tickets. An acquisition added an AI-native video and image pipeline; the hires who integrated it did so while the core canvas was still evolving. That environment selects for people who prototype in the product they are building, then iterate in public: exactly the behavior Dylan Field described in 2019 when he said he wanted Figma to be "a place where people work openly."
No leaked interview rubric confirms these weights. But the roles posted, the pay bands attached, and the product velocity required to ship four AI-first products in a single conference cycle form a coherent picture: Figma hires people who treat the design file as a living spec, the browser as a runtime, and the teammate across the table as a co-author. The interview process, whatever its formal stages, is built to surface that profile.
Three Hubs, One Salary Band
Figma operates from three primary hubs — San Francisco, New York, and Tel Aviv — with a distributed workforce that spans the United States and a visible presence in London. The company's first-party job board lists every open role across those two hubs and a generic "United States" remote option, signaling that these two U.S. cities anchor the organization while remote eligibility extends the talent pool nationally.
San Francisco remains the center of gravity. The board's highest-paid engineering management roles (Manager, Software Engineering across the four platform areas) all list San Francisco first. These positions carry the manager band, and the concentration of platform and infrastructure leadership there suggests the city hosts the core systems that keep Figma's multiplayer canvas online for 13 million users, as Wikipedia found.
New York functions as a full peer, not a satellite. The same engineering and management titles appear with identical salary bands in New York, and the board formats locations as the same three-way split: a deliberate equivalence. This mirrors a pattern across design-tool companies where product, growth, and go-to-market teams cluster on the East Coast to sit closer to enterprise customers and agency partners. The Config 2025 conference ran simultaneously in San Francisco and London, not New York, but the job data makes clear that New York hires for the same technical depth as the headquarters.
Tel Aviv entered the map in October 2025 when Figma acquired Israeli AI startup Weavy for over $200 million and converted the team into a dedicated R&D center branded Figma Weave. The acquisition brought a node-based AI platform that now powers image and video editing workflows inside Figma's canvas. An R&D center implies a different mandate than a sales office: the Weave team builds foundational AI primitives (model routing, professional editing tools, workflow orchestration) that the San Francisco and New York product teams then surface in features like Figma Make, Figma Sites, and Figma Draw. The research notes the technology was "integrated into Figma's platform to enhance AI-powered image and video editing tools and creative workflows," which positions Tel Aviv as an upstream engine for the AI-native canvas the company now markets.
London appears in the research only as a Config venue, but the choice of a dual-city launch for the company's biggest product announcement suggests a meaningful European footprint: likely sales, solutions engineering, and community teams. The board does not yet list London roles, so the scale remains qualitative.
Remote eligibility across the United States rounds out the model. The "United States" label on every posting means a candidate in Austin, Seattle, or Atlanta can interview for the same Traffic or Mobile Web role as a Bay Area local. This flexibility predates the IPO and survived the Adobe merger attempt; it reflects a product that is itself browser-based and collaborative, so the company practices what its tool enables.
The geographic split maps to the product architecture: San Francisco owns the real-time kernel and platform infrastructure; New York mirrors that depth while facing customers; Tel Aviv drives the AI substrate that now differentiates the canvas; London and remote extend reach without diluting the technical bar.
The Profile That Lasts
Figma's product philosophy — browser-native, real-time, multiplayer by default — shapes the internal culture as much as the roadmap. The company's public communications consistently frame collaboration as a technical primitive, not a soft skill. "Teammates and AI agents work in the same space with shared context," the marketing copy reads, and that same expectation applies to human colleagues: design, engineering, product, and research operate in a single canvas where handoffs are anti-patterns. People who thrive here treat the file as the source of truth and the conversation, not an artifact to be tossed over a wall.
Dylan Field has repeatedly emphasized autonomy as a founding principle. When the Adobe acquisition was announced, he told The Verge: "We plan to continue to run Figma the way we have always run Figma, continuing to do what we believe is best for our community, our culture and our business." That stance survived the deal's collapse and the subsequent IPO. Employees who last tend to be self-directed operators who can navigate ambiguity without waiting for a spec to land in their inbox. The pace of shipping (four products launched in a single Config cycle in 2025) rewards engineers and designers who can move from prototype to production-grade code in weeks, not quarters.
The first-party board data shows a hiring bar clustered around those six systems-level roles. The salary bands signal that Figma pays for senior judgment, not just feature velocity. Candidates who stay typically bring portfolio depth that demonstrates end-to-end ownership: a designer who wrote the design-system tokens, an engineer who debugged the WebSocket layer that keeps millions of concurrent users in sync.
Cross-functional fluency is non-negotiable. Dev Mode exists because the design-to-code boundary is where Figma wins or loses enterprise seats; the people who thrive are the ones who volunteer to sit on the other side of that boundary for a sprint. The Tel Aviv acquisition (rebranded Figma Weave) and the Claude Code / Codex integrations via Model Context Protocol extend that expectation into AI tooling: researchers, ML engineers, and product designers now share a node-based canvas where prompt chains and vector brushes are first-class citizens. If you treat AI as a black box you consume, you'll struggle; if you treat it as a material you shape, you'll fit.
Finally, the company's user base — 95% of the Fortune 500, per Figma's own figures — means enterprise reliability is a cultural value, not a compliance checkbox. The operating loss of $1.29 billion on $1.06 billion revenue (2025), as Wikipedia's data shows, reflects heavy R&D investment, not neglect of stability. Engineers who have run control planes at scale, designers who have shipped design systems to thousands of internal consumers, and product managers who have negotiated security reviews with CISOs tend to ramp fastest. The common thread: they build for the person in the next tab, not the pixel on their own screen.
Working in frontier tech? Zero G Talent tracks the openings: see every open Figma role, browse frontier tech jobs, the companies hiring, and the people building the field.