Is the Zhao-direct-design-feedback pattern still in place in 2026, or has the org scaled past it?

Based on the 2025 and 2026 public output (Notion Mail launch framing, Zhao's X account, his podcast appearances), the pattern is still in place. Whether it is in place on the specific team you are interviewing for is the in-loop question to ask. Some teams report deeper founder involvement than others; this differs by surface and by launch cycle. Ask the hiring manager for a concrete recent example of how a design decision on their team was shaped by founder feedback.

How much design autonomy does the platform and extensibility design team have versus the core product design team?

This is not externally documented and the answer differs by year. The platform surface (API, integrations, developer tools) has historically been treated as a serious craft discipline at Notion (the API quality is itself a public signal), but the team structure and reporting line into design leadership is not publicly known. Ask in loop. The shape of the answer also tells you how seriously the company takes the platform surface relative to the core editor.

What is the practical equity story for a design manager joining at the current valuation cycle?

Notion's 409A trajectory has moved through several private rounds and tender offers since 2021. The secondary market prices visible on Forge and EquityZen, and the press coverage of past tenders, are the most useful outside signal. The practical equity story for a new design manager is: large grant size denominated in shares at a current 409A price, four-year vest with one-year cliff in the standard structure, value locked until secondary or IPO. Ask the recruiter for the current 409A and the most recent tender price; both are negotiable to discuss even if not negotiable to change.

How much Notion-product fluency is actually expected in interview?

More than at peer companies for an analogous role. The hiring manager screen and the portfolio review both probe at this directly. Candidates who have never built a non-trivial Notion workspace (a database with relations, formulas, a working integration) are visibly behind. The fluency you need is product-power-user fluency, not developer-deep-API fluency, unless you are interviewing for platform design management specifically.

Which of the four design-manager surfaces should I be most cautious about taking?

Design systems design management at a company whose design system is younger than Figma's or Linear's is the highest execution risk, because the canonical primitives are still being settled and the team has less prior art to reuse. Brand and marketing design management is the most self-contained and the most distant from the founder-designer dynamic. Product design management is the canonical role and the one with the most public-signal calibration. Platform design management is the highest-impact role if the platform story is core to the company's next five years; ask the hiring manager whether it is.

When should I not take a Notion design management role?

Three cases. One, you want a highly documented org with explicit leveling and a published perf cycle; Meta and Google are better fits. Two, you do not want to partner directly with a founder-designer who has the standing to override design decisions; FAANG-tier or larger private companies put a layer between you and the CEO. Three, you want a mature, stable design system you can build on; Linear, Figma, and post-DLS Airbnb have more mature internal systems by most public reports.

Who at Notion is worth following publicly for context?

Ivan Zhao on X at @ivanhzhao remains the most consistent public-design-fluent founder signal. The Notion blog at notion.so/blog publishes the rare design essay around product launches. Senior Notion designers and design managers maintain moderate external presence on X and occasional conference talks; LinkedIn search is the fastest way to assemble the current list of names.

Design Manager Hub

Design Manager at Notion (2026): What Is and Is Not Publicly Knowable

By Blake Crosley · Last verified 2026-05-28

In short

Design management at Notion in 2026 is shaped by one structural fact and one missing-evidence fact. The structural fact: Notion is a primitive-design product, meaning every UI decision is also a tool-system decision (blocks, databases, properties, formulas, API). The design manager at Notion runs the team that decides what user-extensible primitives exist, not just what screens look like. The missing-evidence fact: Notion has published materially less about its design management practice than peer private companies (Figma, Linear, Stripe). Compensation per levels.fyi 2026 is sparse for design-manager rows specifically; the bands below are extrapolations from the engineering ladder and analogous private-SaaS comp benchmarks. Read this page knowing the public surface is thin; the right move is to ask in-loop, not assume from outside.

Key takeaways

Notion design management is primitive-design management. The product is blocks, databases, properties, formulas, the API and integrations, the Notion Mail and Calendar surfaces. The design manager makes tool-system decisions, not screen decisions. If you have only run feature-velocity orgs, the recalibration is real.
Total comp per levels.fyi 2026 design-manager bands are author-mapped extrapolations, not direct Notion DM-specific data. Sparse data point: line-design-manager approximately $320,000 to $480,000 total comp, senior-design-manager approximately $460,000 to $700,000. Private equity component dominates the multi-year picture. Verify against the live Levels.fyi page and the offer specifically before negotiating.
Ivan Zhao (co-founder, CEO; @ivanhzhao on X) retains direct design involvement in 2026. The design management challenge at Notion is partnering with a founder who has direct design opinions and intervenes at the craft level. This is the same founder-designer pattern that shaped early Airbnb under Brian Chesky, Figma under Dylan Field, and Linear under Karri Saarinen and Tuomas Artman. It has worked at some of those companies, crashed at others, and is the single largest in-loop question you should be asking.
What is and is not public-knowable. Public-knowable: Ivan Zhao's design-fluent founder posture (Twitter/X, podcasts, the rare Notion Labs essay), the design-team headcount via LinkedIn, the platform-product roadmap via the API docs and the Notion Mail, Calendar, and AI launches. Not public-knowable: the specific perf cycle mechanics, the design-leadership offsite cadence, how scope is calibrated across product design, platform design, brand design, and design systems.
There are at least four distinct design-manager surfaces at Notion in 2026 (some named on the careers page, some inferred): product design management (canonical, core editor and AI), platform and extensibility design management (the API, integrations, developer-facing surfaces), brand and marketing design management (separate org), and design-systems design management. Which one you are interviewing for changes the job materially. Confirm in the recruiter screen.
When NOT to take a Notion design management role. If you want highly-documented org clarity (Meta or Google publish more). If you do not want to negotiate directly with a founder-designer (Apple or Stripe have a layer between you and the CEO). If you want a stable, mature design system (Notion's is younger than peer companies; Linear and Figma have more mature internal systems by most public reports).

Primitive-design is the design discipline at Notion

Most design management writing assumes the product is a set of screens. At Notion the product is a set of primitives: blocks, databases, properties, page types, relations, formulas, the API surface, the integrations runtime. Every UI decision is also a tool-system decision. The block model from 2018 is still the core architectural commitment of the product in 2026, and every new surface (Notion AI, Notion Calendar from the Cron acquisition in 2022, Notion Mail from the Skiff team acquired in 2024) has to negotiate with it.

The operational consequence for a design manager is that you are running a team whose work is more like API design than screen design. Three concrete differences from running a feature-velocity design team:

Decisions compound across surfaces. A property type added to the database block changes what is possible in formulas, in the API, in integrations, in the AI prompt context, and in every template a user can build. Design managers who optimize for the current sprint and defer the system-level question accumulate debt the team cannot pay back later.
The user is partly a developer. A real fraction of Notion's power users build internal tools, run production databases of customer or HR data, and write automations. The design manager whose team treats power-user depth as a polish concern, rather than the core craft, produces a flatter product. Designing for power users is not designing for developers exactly, but it is closer to Stripe's developer-UX discipline than to consumer-product design.
You ship vocabulary, not just visuals. The words Notion uses (block, page, database, property, relation, rollup, formula, integration) are part of the design. Renaming a primitive breaks every YouTube tutorial, every template, every customer-built workflow. The design manager owns the vocabulary decision in a way that does not apply at companies whose primitives are not user-visible.

This is the position the rest of the page argues from. If primitive-design is not the differentiator, then most of Notion design management collapses into generic SaaS design management at a private company. We do not think it does.

Working with a founder-designer is the management challenge

Ivan Zhao (co-founder with Simon Last; CEO) retains direct design involvement at Notion in 2026. This is well documented in his public output: the @ivanhzhao X account, podcast appearances (Lenny's Podcast, How I Built This, the rare Notion Labs essay), the visible founder presence on product launches. The 2024 Notion Mail launch and the 2025 follow-on positioning around AI-as-default both carry his direct framing.

The design management challenge at Notion is therefore not the one peer companies write about. It is not calibration logistics. It is not the perf cycle. It is the specific challenge of partnering with a founder-designer who has direct opinions about your team's work and the standing to override them.

This is a recurring pattern in tech, and the public history of how it has played out at named companies is the best preparation we can offer:

Early Airbnb under Brian Chesky. Chesky's RISD industrial-design background and his publicly-stated 'I am a designer' 2022 essay made this the publicly canonical case of founder-designer-as-CEO. It has produced strong product-craft outcomes and famously high expectations of design management. The cost is that design directors who want to operate without CEO involvement are in the wrong company.
Figma under Dylan Field. Field is not an industrial designer, but he is a design-tool-fluent founder with public skin in the design-systems community (Config keynotes, the public Figma blog). The Figma model of design management has the CEO present in design-strategy conversations and accepting design as a peer of engineering and product, not a stakeholder.
Linear under Karri Saarinen and Tuomas Artman. Saarinen is a designer-founder (previously principal designer at Airbnb, the canonical author of the 2016 'Building a Visual Language' Airbnb DLS essay). Linear is the closest peer to Notion on the founder-designer dimension and on the primitive-design discipline. The public reporting on Linear design culture (Lenny's Newsletter, Pragmatic Engineer occasional coverage) is the best peer reference for what working with a designer-founder looks like at sustained product scale.
Cases where the pattern crashed. Founder-designer-as-CEO has also produced public flameouts (WeWork's Adam Neumann was not a designer but ran design by intuition; Quibi's product design was overruled by executive taste with poor outcomes). We will not name private cases we do not have public evidence for.

The in-loop question every Notion design manager candidate should ask, in some form: what does the CEO's direct design involvement look like on a normal week, in a normal review, on a normal sprint? The answer differs between teams inside Notion, and the candidate's choice of which team to take an offer from depends on it.

What we can and cannot tell you about Notion design management

This section is shorter than the equivalent section on peer at-* pages on this site, because Notion has published less. We would rather be short and accurate than long and speculative.

What the public surface tells us.

The Notion careers page at notion.so/careers lists open design roles, design-manager roles where they exist, and the city or remote eligibility. This is the authoritative headcount and intent signal for any given month.
The Notion blog at notion.so/blog publishes product-design essays on an irregular cadence, more during launches (Notion AI, Notion Mail) and quiet between them. These essays are the closest public surface to internal design thinking.
Ivan Zhao's X account and selected podcast appearances give the founder-CEO design framing in his own words. The Lenny's Podcast interview with Zhao remains a good single source.
The Notion API documentation at developers.notion.com is the most honest public surface for what primitive-design means at Notion in practice. Read it before any platform or extensibility design-manager interview.
LinkedIn gives you the names and tenures of current design managers and design leadership. This is the route to a backchannel reference, which is the most valuable due diligence channel for a private-company senior offer.

What the public surface does not tell us.

The specific perf cycle mechanics (cadence, rating scale, calibration shape). Meta publishes its PSC structure via Pragmatic Engineer coverage; Stripe's writing culture is documented through Patrick Collison's interviews; Notion's analog is not externally documented at that specificity.
The design-leadership offsite cadence, the design-systems team structure, the relationship between core product design and platform design management. Ask in loop; do not assume.
The internal leveling rubric and scope expectations per level. Levels.fyi rows for Notion design-manager are sparse and not credible as a complete rubric in 2026; the extrapolations in this page are explicit guesses based on the engineering ladder and analogous private-company patterns.

The honest framing is that this is a private company whose design management practice has not been written up the way Meta's, Stripe's, Airbnb's, or even Linear's has. Treat the in-loop conversation as the primary source, not as a supplement to public reading.

Compensation: what levels.fyi shows, what it does not

Notion is private as of 2026, so total comp is base plus bonus plus equity grants whose value depends on a 409A valuation that lags secondary market prices. The levels.fyi page for Notion has sparse data for design-manager specifically. We are not going to pretend otherwise.

Author-mapped extrapolations. The bands below are built from the Notion engineering ladder, the analogous private-SaaS design-manager bands at peer companies (Figma, Linear, Airbnb pre-IPO comparison), and the visible Notion product designer rows on levels.fyi. They are not direct observations.

Level	Scope	Total comp (extrapolated)
DM (line-design-manager)	3 to 8 reports	$320,000 to $480,000
Sr-DM (senior-design-manager)	10 to 25 reports	$460,000 to $700,000
GDM (group-design-manager)	25 to 60 reports	$700,000 to $1,100,000
Director of Design	50 to 150 reports	$1,000,000 to $1,500,000
VP Design	150+ reports	$1,400,000 to $2,400,000+

Three structural facts about Notion design-manager comp that the table does not show:

Equity is the dominant lever. At senior-design-manager and above, the equity grant size and the 409A trajectory dominate multi-year total comp. The secondary market price of Notion shares (visible on Forge, EquityZen, occasional press coverage of tender offers) is the most useful signal for an outside candidate trying to estimate equity value.
Liquidity-event timing matters. Notion has not announced an IPO timeline as of this page's publication. The equity component is locked until secondary or IPO. Run the comp comparison against a private-comp benchmark, not a public-comp benchmark.
The management premium is small or zero. Consistent with peer private companies, the design-manager total comp at a given level is close to the staff/principal design IC total comp at the equivalent level. If you are moving from IC to manager only for the comp delta, the math is rarely worth it. Move for the work.

The interview at Notion: what candidates report

Public sources for the design-manager interview at Notion are thinner than the at-Stripe or at-Meta equivalents. We pull from candidate reports on Glassdoor (search 'Notion design manager interview'), the rare Notion Labs blog writeup of hiring philosophy, and structural inference from Notion's public design-leadership posture. Treat the shape below as approximate, not authoritative.

Recruiter screen, 30 minutes. Calibration of seniority, role context, which of the four design-manager surfaces (product, platform, brand, design systems) you are being considered for. Confirm this in writing before the next round; the surfaces are different jobs.
Hiring manager screen, 60 minutes. Behavioral plus a light portfolio walkthrough. Expect Notion-specific probing on your familiarity with the product (blocks, databases, formulas, API). Candidates who have not used Notion as a power user are visibly behind in this round.
Portfolio review, 60 to 90 minutes. Three to five case studies. Notion-distinctive lean: the panel probes at the primitive-design layer, not just the screen layer. A case study that documents 'we shipped this feature' without naming the underlying system choice and the trade-offs ages badly here.
Onsite, four to six rounds, 60 minutes each. Expect craft and taste rounds, a behavioral/leadership round, a cross-functional partnership round with PM and engineering peers, and a design-strategy round. The cross-functional round is unusually substantive at Notion because product, design, and engineering are structured closer to the Stripe triadic pattern than to engineering-led FAANG.
Founder or senior-leadership round, conditional. For senior-design-manager and above, expect a round with Ivan Zhao or a member of the senior leadership team. This is the round where the founder-designer working relationship is calibrated in both directions. Prepare for it.

Frequently asked questions

Is the Zhao-direct-design-feedback pattern still in place in 2026, or has the org scaled past it?: Based on the 2025 and 2026 public output (Notion Mail launch framing, Zhao's X account, his podcast appearances), the pattern is still in place. Whether it is in place on the specific team you are interviewing for is the in-loop question to ask. Some teams report deeper founder involvement than others; this differs by surface and by launch cycle. Ask the hiring manager for a concrete recent example of how a design decision on their team was shaped by founder feedback.
How much design autonomy does the platform and extensibility design team have versus the core product design team?: This is not externally documented and the answer differs by year. The platform surface (API, integrations, developer tools) has historically been treated as a serious craft discipline at Notion (the API quality is itself a public signal), but the team structure and reporting line into design leadership is not publicly known. Ask in loop. The shape of the answer also tells you how seriously the company takes the platform surface relative to the core editor.
What is the practical equity story for a design manager joining at the current valuation cycle?: Notion's 409A trajectory has moved through several private rounds and tender offers since 2021. The secondary market prices visible on Forge and EquityZen, and the press coverage of past tenders, are the most useful outside signal. The practical equity story for a new design manager is: large grant size denominated in shares at a current 409A price, four-year vest with one-year cliff in the standard structure, value locked until secondary or IPO. Ask the recruiter for the current 409A and the most recent tender price; both are negotiable to discuss even if not negotiable to change.
How much Notion-product fluency is actually expected in interview?: More than at peer companies for an analogous role. The hiring manager screen and the portfolio review both probe at this directly. Candidates who have never built a non-trivial Notion workspace (a database with relations, formulas, a working integration) are visibly behind. The fluency you need is product-power-user fluency, not developer-deep-API fluency, unless you are interviewing for platform design management specifically.
Which of the four design-manager surfaces should I be most cautious about taking?: Design systems design management at a company whose design system is younger than Figma's or Linear's is the highest execution risk, because the canonical primitives are still being settled and the team has less prior art to reuse. Brand and marketing design management is the most self-contained and the most distant from the founder-designer dynamic. Product design management is the canonical role and the one with the most public-signal calibration. Platform design management is the highest-impact role if the platform story is core to the company's next five years; ask the hiring manager whether it is.
When should I not take a Notion design management role?: Three cases. One, you want a highly documented org with explicit leveling and a published perf cycle; Meta and Google are better fits. Two, you do not want to partner directly with a founder-designer who has the standing to override design decisions; FAANG-tier or larger private companies put a layer between you and the CEO. Three, you want a mature, stable design system you can build on; Linear, Figma, and post-DLS Airbnb have more mature internal systems by most public reports.
Who at Notion is worth following publicly for context?: Ivan Zhao on X at @ivanhzhao remains the most consistent public-design-fluent founder signal. The Notion blog at notion.so/blog publishes the rare design essay around product launches. Senior Notion designers and design managers maintain moderate external presence on X and occasional conference talks; LinkedIn search is the fastest way to assemble the current list of names.

Sources

About the author. Blake Crosley founded ResumeGeni and writes about design management, hiring technology, and ATS optimization. More writing at blakecrosley.com.