Month-by-month feed of what shifted, who was hiring, and how Starter, Scaler, and Titan teams actually worked.
57 synthesized monthsin the data layer. Stage breakdowns (Starter / Scaler / Titan) are available for 2026 only — earlier months show under the All segment but won’t appear under stage filters until the design-context pipeline runs further back.
Solo founders and tiny teams ship full products without hiring a designer. They direct agents themselves.
Figma Make → Lovable → Cursor
At <10 people, one person still owns product, brand, and code. The agents make that physically possible.
Series A–B teams hire one AI Creative Director and zero mid-level designers. Agent operators fill the gap.
Figma Agent → Adobe agentic suite → Cursor
Solo and pre-seed founders ship full products without hiring a designer. They hire a creative director on retainer for taste calibration.
Figma Agent → Lovable → Cursor
Pre-seed teams can't afford a full-time senior designer and don't need one. They need taste injected on a schedule. This is the new freelance shape.
Series A/B teams hire their first AI Creative Director instead of their fifth Senior Product Designer.
Figma Agent → internal brand agents → Linear + agent-driven PR review
Founders ship product and brand themselves with agent suites. Design hires happen later than they used to.
Figma Agent → Cursor → Lovable
At pre-seed and seed, one person who can direct agents across product, brand, and code replaces the old three-person design team.
Series A to B teams hire their first AI Creative Director and build pods around agents, not around designers.
Figma Agent → Adobe agentic suite → Cursor
Solo founders and tiny teams run agent stacks instead of hiring designers. The founder is the creative director by default.
Figma Make → Lovable → Cursor
At <10 people, you need one person who can hold taste and ship code. Pure visual roles don't get hired here anymore.
Series A–C teams build a thin Creative Direction layer over an agent stack and hire design engineers to ship. Mid-level execution roles compress.
Figma + Make → Cursor → Linear
Solo founders and tiny teams run on agent suites. The founder is still the designer. Taste is the entire moat.
Figma Make → Cursor → Lovable
At pre-seed and seed, one person still owns design, code, and shipping. Agents amplify them but don't replace them.
Series A to C teams hire their first AI Creative Director. Mid-level IC design roles thin out. Design Engineers own the agent-to-code path.
Figma + Make → Cursor → Adobe agent stack
Solo and seed-stage teams ship more surface area per person than ever. One designer, three agents, a real product.
Figma Agent → Cursor → Cognition/Devin-class coding agents
At this stage one person still owns the whole stack. Agents make that viable for more surface area, not fewer people.
Series A–C teams formalize the orchestration layer. New title: someone owns the agent stack and the brief-to-ship pipeline.
Figma Agent → Linear + agent integrations → Custom brand agents
Vibe-code the brand, own the judgment layer
Figma → v0 → Midjourney
At seed stage, the designer who can prompt-to-production without a handoff compresses the roadmap by weeks and owns both taste and velocity.
First design system, first real governance debate
Figma → Figma Make → Maze
One prompt, full brand kit, ship tomorrow
Canva AI 2.0 → Claude Design → Framer
Vibe-coding via Claude Design collapses the design-to-code handoff, making hybrid builder-designers the highest-leverage single hire at seed stage.
Design system becomes agent rulebook
Figma (with Agent Canvas / Skills) → Claude Code → Canva AI 2.0
One generalist, agent co-pilot, zero art department
Figma → Midjourney → ChatGPT
Vibe-coding tools collapsed the handoff, so the most valuable hire codes and designs from the same prompt.
First design system, agent-accelerated, brand rules required
Figma → Adobe Firefly → Framer
Frames-to-PR: founders ship design without handoff
Figma → v0 → Cursor
Vibe-coding tools eat the handoff entirely at seed scale, so the person who designs and ships the branch in the same session is the only design hire that makes sense.
First design system, AI-augmented from day one
Figma → Storybook → v0
Vibe-code your MVP, skip the handoff
v0 → Lovable → Figma
At seed stage, shipping a working product matters more than a polished Figma file; vibe-coding makes a designer who can deploy the single most valuable hire.
First design system, now it ships real code
Figma → Figma Make → v0
At this stage the bottleneck is judgment, not output. One sharp director plus agents beats five mid-level designers.
Enterprises run dual stacks: an agent-first production line and a small protected craft studio for the work that defines the brand.
Figma Enterprise + Agent → Adobe Firefly enterprise → internal agent platforms
Someone has to own the agent fleet, the brand rules they run against, and the humans who audit them. That's a VP job by late 2027.
At this stage the bottleneck is taste consistency across a growing surface area. One person owns that. They don't make screens. They reject them.
Big cos run design as a thin direction layer over agent fleets. Design headcount stops growing. Director-and-above titles grow.
Figma Agent enterprise → Adobe agentic suite → custom in-house brand agents
At scale the question is governance: which agents touch which surfaces, who signs off on brand drift, how taste stays consistent across thousands of generated assets. That's a leadership job, not an IC one.
This is where the title gets formalized. Comp bands attach. Recruiters start searching for it specifically.
Big companies split design into two clear tracks: AI orchestration teams that do volume, and small craft teams that own brand and signature moments.
Figma Agent enterprise → Adobe agentic suite → internal model platforms
At titan scale this role sits above orchestration pods and reports into the CMO or CPO. The Head of Craft is the counterweight, not the default.
This is where the title shows up in job posts first and most. The role owns the brief, the brand agent, and the bar.
Big companies govern agents like they govern code. Brand agents, design systems, and evals all live in one stack. Craft becomes a premium signal.
Figma enterprise + Make → Adobe agentic suite → internal model gateways
At scale, someone has to own the bar across dozens of agents and product surfaces. That's the new senior IC and director-tier job.
This is the segment where the title actually shows up in postings. They need someone to hold the line on taste as agent output scales.
Large orgs run agent fleets against locked-down brand and system rules. Design leadership becomes a governance job. The craft backlash shows up as premium hand-crafted surfaces inside otherwise AI-generated products.
Adobe agent suite → Figma enterprise + Make → internal model platforms
At scale, the role becomes about taste governance — what ships, what doesn't, what the brand sounds like across thousands of agent outputs.
Growth-stage teams need someone who can hold the brand line while production volume goes up 10x. That role keeps rising.
Big companies hit the craft backlash hardest. Output is up. Quality is uneven. Senior taste roles get pulled in to clean up.
Figma Enterprise + Agent → Adobe agentic suite → Internal model gateways
At scale, the cost of bad agent output is brand damage. Someone senior has to own that risk. The title sticks because the problem is real.
At Series A–C velocity, a coherent design system is the only thing preventing AI-accelerated teams from producing inconsistent product experiences at scale.
Design-system AI gets enterprise governance
Figma (Enterprise) → Adobe Creative Cloud → Runway
At Titan scale, the synthesis of strategy, narrative, and system-level coherence beats execution speed — AI handles production, humans set the story.
Figma's Agent Canvas makes your component library the grammar agents speak — whoever maintains that grammar controls every screen the agent ships.
Agent governance is the new design ops
Figma Enterprise (Skills + Agent Canvas) → Adobe Firefly for Enterprise → Canva Enterprise AI 2.0
At scale, the risk isn't under-production — it's off-brand agent output at volume; the CD role owns the taste layer and liability for every agent-generated asset.
Agents need rails — this role writes them, making every downstream AI output on-brand by default.
Agent governance is the new brand governance
Adobe Creative Cloud → Adobe Firefly → Figma
At scale, agents produce fast; the brand storyteller decides what the brand should actually say — synthesis beats execution.
Scalers need the person who owns the design-system-to-code bridge—without them the Codex integration creates token chaos rather than velocity.
Design-system AI gets enterprise governance
Figma → Adobe Firefly → Runway
At Titan scale, AI handles execution volume; the role gaining leverage is the one synthesizing brand narrative into the prompts, tokens, and guardrails that govern all of it.
At scaler stage, a well-structured design system is the prompt infrastructure that keeps AI-generated components coherent as the team ships faster.
Governance layer arrives for AI-generated brand output
Figma → Adobe Firefly → Adobe Acrobat Studio
Mature orgs have no shortage of generated output; they need someone with taste and authority to decide what gets approved and shipped at scale.