How Crisan's First Year at Figma Created the AI & Context Director Role

Dylan Field disclosed on Figma's Q2 earnings call (August 5) that CPO Yuhki Yamashita was leaving after seven years and that Crisan would lead Figma's product function alongside design. The Director, Product Design — AI & Context posting appeared on September 22. The forty-eight days between those two events tell you more about the role's real authority scope than anything in the posting itself.

Three events that changed the trajectory

September 2025 — CDO appointment. Figma's Q3 2025 SEC filing recorded Crisan's arrival from Meta, where she'd spent nine years across Messenger, Instagram, and GenAI. Her CDO scope, per her own published biography: design, UX writing, brand studio, and research.

August 5, 2026 — CPO departure and scope expansion. Field's earnings-call remarks described a broader leadership transition: CTO Kris Rasmussen moved to a Chief Architect role focused on Figma Agent; CMO Sheila Vashee departed; security leader Dev Akhawe became Figma's first CSO. Crisan absorbed the product function. Her LinkedIn post said she would remain CDO while leading product and would "champion the distinct roles design and product play." Neither her statement nor Field's remarks described the arrangement as temporary. Neither named a CPO search.

September 22, 2026 — AI & Context director posting. The role oversees Figma's Context Platform Pillar: Design Systems, Code, MCP, CMS, Community, "and more." US base range: $290,000–$376,000 plus equity and bonus. The posting names no hiring manager, no predecessor, no existing team size.

What Crisan was building before her scope expanded

Her first ten months as CDO produced a specific, recoverable pattern of public activity. Pay attention to what she chose to own publicly, then compare it to the director posting's scope.

Design systems as AI infrastructure. At Schema in October 2025, Figma introduced Make Kits for importing component libraries into Make and npm-package imports for React components. Crisan was a named speaker. The framing: design systems as the context layer that AI tools consume.

MCP and code connectivity. Figma launched remote MCP server access in September 2025 and expanded Code Connect mapping in beta. By Q1 2026, MCP weekly active users grew fivefold quarter over quarter, with agents reading from and writing to Figma files using components, variables, and tokens.

AI model evaluation as a design judgment. Crisan personally authored the November 2025 post announcing Gemini 3 Pro in Make. She framed evaluation criteria in design terms — fidelity, busywork removal, creative expansion — positioning AI model selection as a design decision rather than a technical one.

Taste as organizational authority. Her February 2026 amplification of Figma's State of the Designer report and her June 2026 essay on taste built the argument that AI expands creative range but cannot supply human judgment. That argument does organizational work: it claims the design function's authority over AI-mediated workflows.

The AI & Context director posting's scope — Design Systems, Code, MCP, CMS, Community — maps directly onto every product area Crisan was publicly championing during her first year as CDO. She built this mandate personally, and the role exists to carry it.

What the pattern predicts

Authority is higher than the posting reads. A director inheriting products the CDO personally championed carries more organizational weight than a director slotted into a pre-existing pillar under an established leader. Crisan scoped this territory herself. The director walks into it with her sponsorship. For scope expandability, the ceiling is wherever Crisan decides to set it, and she has shown she invests personally in this surface area.

The search is urgent. Crisan has been operating with expanded scope for nearly two months without a visible delegate for the context pillar. In a July interview, she described her leadership philosophy as team ownership and agency — letting work move in unexpected directions. That philosophy requires someone in the room making daily calls on the context pillar. Without a director, the pillar runs on whatever momentum it had before August 5.

The adjacent hiring cluster

The AI & Context director posting isn't isolated. Figma's current board shows a connected set of openings across the same infrastructure territory:

• Director, Research — AI Evals (July 13)
• Product Designer, CMS (July 29)
• Manager, Design — Systems & Infrastructure (August 14)
• Product Designer, Design Systems (August 14)
• Product Designer, Roundtripping (September 16)

Two of these — AI Evals and CMS — predate the August 5 announcement. The leadership transition was decided internally before Field disclosed it on the earnings call. The remaining postings cluster afterward. The design-infrastructure layer is being staffed up, and the director posting arrived last in the sequence.

The person hired into this role will likely inherit at least some of these hires as direct or skip-level reports. A director who arrives while the build-out is still in progress has more influence over the pillar's composition than one who arrives after the supporting roles are filled.

What would have to be true for this to be wrong

Two scenarios break the pattern.

Crisan has already delegated the context pillar to someone not visible in public records — a VP or senior director who owns the hiring decision and whose name doesn't appear on LinkedIn, Figma's blog, or the posting. Possible at any company. Unlikely at a public company where leadership changes surface within weeks.

Or the role reports into a product organization rather than design, despite being posted in Figma's Design category and despite Crisan now leading both functions. Someone else — possibly a product VP — could be the actual buyer. The posting's category and Crisan's dual scope make this less probable, but the absence of a named reporting line means it can't be eliminated.

Confidence: high that Crisan is the buyer. Moderate that no intermediate layer exists between her and this role.

Contact recommendation

Who: Loredana Crisan, CDO (now also leading product).

Channel: LinkedIn. She maintains an active posting cadence and publicly amplified the expanded-scope announcement. Check your mutual-connection count before sending. Three or more mutuals: reference them in the close of the message, not the opening.

Why now: The posting is eleven days old. The leadership transition is fifty-nine days old. Crisan is operating across both product and design without a visible delegate for the context pillar. The adjacent hiring cluster says the team is being assembled now. Each week that passes, supporting roles fill and the director's ability to shape the pillar's composition narrows.

What the role spans: The posting says the director will work across "new-product creation and the evolution and scaling of existing products." The product timeline confirms this: Design Systems, Code Connect, and MCP are established and growing, while Agent, Code Layers, generative plugins, and Weave tools are still in beta or rolling out and not yet consuming paid AI credits. Your positioning needs to address both the scaling layer and the new-build layer. The Opportunity Brief will map your background to each.

Timing prediction: This search will move faster than a typical director search at a company Figma's size. Crisan needs someone carrying the mandate she built, and the forty-eight-day gap between her scope expansion and the posting suggests the role was scoped and approved quickly. Expect a compressed timeline.