Figma

Getting hired at Figma

Figma sits in an unusual position in the industry. It's a company with genuine product love — the kind where designers and engineers who use the product daily have real feelings about the company — that's also navigating the aftermath of a $20B acquisition that didn't happen. The Adobe deal falling apart in 2023 left Figma independent and, by most accounts, energized. They're still one of the most interesting design-adjacent technical roles you can take, but understanding what they're actually selecting for requires looking past the brand.

Platform engineering depth behind the design tool

The common perception of Figma is a design tool company, which makes people assume the engineering work is primarily product/frontend focused. That's wrong enough to be worth correcting explicitly.

Figma runs one of the more technically ambitious real-time collaboration systems in production. The multiplayer architecture — built on CRDTs (conflict-free replicated data types) and a custom operational transformation approach — is genuinely sophisticated. The rendering engine is written in C++ and compiled to WebAssembly. The plugin system has to be both sandboxed enough to be safe and permissive enough to be useful, which is a hard balance. The enterprise features require serious thinking about access control, audit logging, and performance at scales most product companies never think about.

This means that strong infra engineers, systems programmers, and engineers who've worked on real-time or collaborative systems are not just welcome at Figma — they're specifically sought. If you have a background in CRDTs, distributed consensus, or high-performance graphics, Figma is one of the few product companies where that background has direct relevance to core product challenges.

How collaborative culture shows up in hiring

Figma has a genuinely collaborative internal culture, not as a stated value but as a described operating mode. The company was built around the idea that design should be collaborative (that's the product thesis), and that product development works the same way. Designers, PMs, and engineers work in closer proximity there than at most companies.

In hiring, this manifests as explicit evaluation of how you collaborate under conditions of ambiguity. Figma interviewers are specifically looking for candidates who don't just wait for a spec to arrive and execute it — who push back, suggest alternatives, flag issues early, and bring genuine product thinking to their domain.

For engineers, this means being able to talk about your relationship with design and product as something more textured than "I implement what's in the mocks." The engineers who do well at Figma can describe times they shaped product decisions, improved designs before implementation, or caught a product problem before it became a build problem.

For designers, the bar is similarly high on the technical side — not "can code" as a checkbox, but "understands the constraints your engineers are working within and designs accordingly."

The Adobe acquisition context and independence reality

The attempted acquisition — Adobe announced it, regulators blocked it, it fell apart at the end of 2023 — is worth understanding because of how it affected Figma's culture and direction.

The year of regulatory limbo was genuinely disruptive. Uncertainty about the company's future led to some attrition among people who didn't want to wait and see. The deal's collapse, while disappointing in the immediate term, left the company independently controlled and with a clarity of mission that had been somewhat muddied during the acquisition process.

The post-acquisition Figma is pushing into new territory: AI-assisted design, developer-facing tools, enterprise features, the FigJam whiteboard product. The bet is that the core design tool market is theirs and the expansion surface is large. That's a reasonable bet — but it also means the company is in a different phase than it was when it was primarily focused on winning the design tool market.

For people considering Figma: you're joining a company with real scale (millions of users, significant enterprise revenue) that's navigating what independent growth looks like after nearly being acquired. That's an interesting moment to be there, but go in with clear eyes about what stage of company this is.

What craft means to them

Figma's product is used by people who are professionally expert at evaluating the quality of designed interfaces. This creates a specific kind of culture — the people at Figma are hyperaware that their users would immediately notice if the product's own interface was lazy or inconsistent.

Craft at Figma means the same thing it means in design generally: getting the details right not because someone is checking, but because the details are part of the work. This applies to the engineering just as much as the design. Code review at Figma reportedly takes naming, API clarity, and long-term maintainability seriously in ways that are sometimes surprising to engineers coming from companies where "does it work and is it tested" is the primary bar.

The hiring process reflects this. The code you write during a work sample, the case study you present as a designer, the product spec you walk through as a PM — these are evaluated with an eye toward quality signals, not just completeness. Taking time on things reads well. Roughness that seems like it would have been easy to address reads badly.

The PM/designer/engineer intersection

Figma has one of the more interesting PM cultures in tech, specifically because of the domain. PMs there have to understand design deeply — not just as a stakeholder who reviews mocks, but as someone who can speak fluently about design decisions and evaluate tradeoffs. The best Figma PMs tend to have either design backgrounds or unusually deep practice with design tools.

For engineers interested in PM roles, or PMs interested in moving more technical: Figma is a place where the boundary between these roles is somewhat porous. There are PMs who came from engineering and bring that to the product thinking; there are engineers who become increasingly PM-adjacent as they grow. This is a cultural feature, not a formal program.

If you're a designer thinking about Figma: the bar is high and the pool is competitive, specifically because working at the company that makes the tool is a dream job for many designers. The candidates who stand out tend to have genuinely interesting perspectives on design systems, or have worked at the intersection of design and engineering in ways that most portfolio work doesn't capture. Show the process and the decisions, not just the outcome.

---

Figma doesn't open senior roles frequently, and when they do, the positions fill fast with a pool of deeply motivated candidates. Follow Figma on Crush to get notified the moment a role opens that matches what you're looking for.