Every company says it values design. Most of them are lying, though not always on purpose. "Design-led" is a self-description that means nothing until you cross-reference it against structural evidence. The companies that actually are design-led rarely bother saying so. The ones that say it loudest usually have the least to back it up.
The proof is structural. It's visible before you send a single message. Five signal categories, ordered from highest confidence to lowest, that you can run against any target company in ten to fifteen minutes using only public sources. No single signal is reliable alone. Two or three in combination give you a read you can act on. If the first two categories produce a clear answer, stop or proceed. If they're ambiguous, the remaining three help you triangulate.
Three companies anchor the diagnostic: Maven Clinic (VP Design search with claimed executive access), Atlassian (mature enterprise design function with a Chief Design Officer), and Anthropic's Education Labs (builder-stage design engineering posting at a frontier AI company). Three different authority profiles. The signals read differently for each, and those differences do the diagnostic work.
Signal 1: Leadership Page Presence
Confidence: High. Directly observable. Hard to misread.
Check whether a design leader appears on the company's public leadership or about page. Note the title, the position relative to other named executives, and whether "design" appears as a named function alongside engineering, product, and the rest.
This is the single most reliable external signal. Companies choose who goes on that page. A VP Design or Chief Design Officer listed alongside the CTO and CPO means design has a seat. A leadership page with nine named executives and zero design titles means design does not have that seat. Full stop. Regardless of what a job posting promises. Regardless of what the careers page says about being "design-driven."
Presence means design is recognized as an executive function. The company is willing to publicly associate its leadership identity with a design leader. This does not guarantee decision rights. It establishes organizational altitude.
Absence means design is structurally subordinate, pre-functional, or culturally invisible. Could be any of the three. All of them should change how you read every signal that follows.
The three anchors:
Maven Clinic's leadership page lists nine senior leaders: CEO, Chief Medical Officer, Chief Product and Operating Officer, SVP Engineering, CFO, Chief Marketing Officer, Chief Communications Officer, Chief Revenue Officer, General Counsel. No design title of any kind among them. Meanwhile, Maven's VP of Design posting promises a "direct line to the CEO and CPO" and leadership of roughly 15 designers. Flag this gap. The posting is selling executive access the leadership page does not yet reflect. The authority is aspirational. You would be building the seat, not sitting in one that exists. That can be the right job. But you need to know that's what it is.
Atlassian's leadership page lists Charlie Sutton as Chief Design Officer alongside the Chief Product and AI Officer, CTO, and other C-suite leaders. Design named at the same altitude as product and engineering. Cleanest possible read.
Anthropic's company page lists board members and describes team categories (Research, Policy, Product, Operations) but names no design leader. Design is not a listed category. When Anthropic announced Labs, the post named Mike Krieger and Ben Mann. No design leader. The Education Labs Design Engineer posting is consistent with this absence: design at Anthropic is a contributing skill inside product and research teams, not a standalone function.
If the leadership page has no design leader and the company has more than 500 employees, design is structurally subordinate. Proceed only if you want to build authority from scratch and the posting's mandate language explicitly supports that.
Signal 2: Job Posting Language
Confidence: Moderate-high. Observable, but remember: postings are wish lists filtered through HR language, often written by people who don't fully understand the role.
Check whether the posting describes decision rights or responsibilities. Look for who the role reports to, what the role owns versus influences, and whether the language frames the hire as someone who shapes direction or someone who executes within existing direction.
The most diagnostic phrases are the ones that reveal scope boundaries. Read for the verbs. Own, define, set, lead suggest authority. Support, partner, collaborate, align suggest influence without control. "Partner with product and engineering" is collaboration language. Neutral. "Define the design vision and strategy" is ownership language. "Support the product team's goals" is subordination language. You need to know which one you're walking into.
Four things to check:
- Reporting line. Reports to CEO or a C-level design leader = high authority signal. Reports to CPO or VP Product = moderate, depends entirely on that person's design fluency. Reports to VP Engineering = you already have your answer.
- Team-building language. "Hire and develop a world-class design team" means the function is being built. "Lead a team of 15 designers" means the function exists. No mention of hiring or team at all means elevated IC, regardless of title. The posting language tells you the actual role. The title does not.
- Scope markers. Does the posting mention design systems, research, content design, brand? Broader scope signals a true functional leader. Narrow scope (product design only) signals a team lead.
The three anchors:
Maven's VP of Design posting uses ownership language: design is "central to member trust" and "clinical mission at scale," with a "direct line to the CEO and CPO" and leadership of roughly 15 designers. Strong posting language. But cross-reference against Signal 1: the leadership page doesn't reflect this altitude yet. Moderate-high confidence the mandate is real. Low confidence the structural support exists. A real mandate with no existing structure is a fundamentally different job than a real mandate with infrastructure already in place. Price accordingly.
Atlassian's Principal Designer posting (the AI-focused IC role) carries strategic language but zero people-management scope. Read the posting, not the company reputation. The CDO's presence tells you design has authority at Atlassian. The posting tells you this particular role is an IC with strategic AI influence, not a people leader. Atlassian distributes significant design authority through craft seniority rather than management hierarchy. You'll encounter this pattern at other mature design orgs. The company can be deeply design-empowered while the specific role carries no people-leadership scope whatsoever.
Anthropic's Education Labs Design Engineer posting describes the hire as "part researcher, part product builder, part interaction designer," the second technical builder on a small team, with no people management "off the bat." Builder-stage language. High confidence this is a hands-on building role. If you want to lead a design function, this is not your entry point.
Signal 3: LinkedIn Org Shape
Confidence: Moderate. Observable but interpretable multiple ways. LinkedIn data has lag, profiles go stale, and search results are incomplete without a premium account.
Check whether you can identify the most senior design title at the company, approximate design team size, and infer reporting relationships from profile data.
A company with 1,000+ employees and only three to five people with "design" in their LinkedIn titles has a thin design function. A company where the most senior design title is Senior Manager has a low design ceiling. A company where the top design title reports to a product leader (visible through profile descriptions or tools like The Org) has design nested under product. None of this is surprising. What's useful is how fast you can see it.
Four things to look for:
- Title ceiling. The most senior design title visible. Staff Designer suggests IC maturity. Director suggests mid-level leadership. VP or CDO suggests executive function.
- Team density. Rough count of design-titled profiles relative to company size. Under 2% of headcount in design at a product company is thin.
- IC-to-manager ratio. Multiple Staff and Principal design titles but few Director or VP titles relative to team size means the company distributes design authority through craft seniority, not management hierarchy. Atlassian is the clearest example: CDO at the top, IC-heavy below by design. Structural choice, not a weakness. But it tells you the path to influence runs through craft credibility, not headcount.
- Self-description language. This takes two minutes and delivers high signal. Scroll through how existing designers describe their own work. Mid-level designers who write "defining product strategy" or "leading 0-to-1 initiatives" suggest design has real scope at every level. Designers who write "delivering designs for the product team" or "supporting engineering sprints" are telling you, in their own words, that design is a service function.
Reporting signals from profiles or third-party org tools can corroborate but are often unverified. Treat as inference-only.
Anchor example: Maven Clinic shows approximately 1,175 employees on LinkedIn. Third-party org data (unverified) surfaces a Senior Manager of Product Design, Lead Product Designer, Staff Product Designer, and several Senior Product Designers. The title ceiling before this VP search was Senior Manager. Consistent with the leadership-page absence: design existed as a mid-level function inside product, and the VP posting represents a genuine altitude increase. Moderate confidence this is a real elevation of design, not a title upgrade on existing scope.
Signal 4: Design Blog and Public Content
Confidence: Moderate-low. Presence is a positive signal. Absence is ambiguous.
Check whether the company maintains a public design blog, design-focused Medium publication, or equivalent content channel. If it exists, check when it was last updated.
Publishing design content requires organizational permission and resource allocation. Someone approved designer time for content creation, which means someone decided design's perspective was worth putting in front of the public. An active design blog is not proof of decision rights. It is proof that design has enough standing to claim time, attention, and editorial real estate. That distinction matters.
Absence is harder to read. Some companies with strong design functions simply don't publish about it. At AI-native companies in particular, designers may publish as part of product and research teams rather than under a design banner. You cannot distinguish deep embedding from marginalization using this signal alone. That's why it sits at moderate-low. It matters most in combination with the signals above it.
The anchors: Atlassian Design maintains a dedicated publication with blog posts, leadership talks, and behind-the-scenes stories updated through July 2026. Strongest possible signal in this category. Maven Clinic's blog focuses on healthcare, clinical research, and employer resources. No design-specific channel. Anthropic's newsroom publishes product announcements, including the April 2026 Claude Design launch, but has no design publication. Both absences are consistent with the structural reads from earlier signals. They corroborate. They don't change the picture.
Signal 5: Design System Investment
Confidence: Split. Inference-only when no public system exists (you can't distinguish "internal system" from "no system" from outside). Moderate when a public system is visible (scope and recency are directly observable).
Check whether the company has a publicly documented design system. If so, check its scope (component count, platform coverage) and recency of updates.
Maintaining a public design system is expensive and cross-functional. It only happens when design has enough organizational weight to invest in infrastructure that serves the entire company, not just the design team. A public system with active maintenance signals design is treated as a platform. The investment is a proxy for institutional commitment.
Atlassian is the anchor that matters here. Their design system is publicly documented with 60+ named components, covers foundations, components, patterns, and tooling, and is actively evolving for AI. A May 2026 post describes the system adding structured content files, an MCP server, and unified templates for AI code generation, plugging into AI agents like Rovo and prototyping tools like Figma Make. A 15-year-old system being repositioned as AI infrastructure. That level of strategic investment only happens when design has real organizational weight.
Maven and Anthropic have no publicly visible design systems. At Maven's scale, an internal system likely exists. At Anthropic's stage of design maturity, a formal system would be premature. Neither absence is damning. Neither provides the corroborating signal that Atlassian's does.
The Composite Read
Single signals mislead. Combinations are where the confidence lives.
| Signal | Atlassian | Maven Clinic | Anthropic Education Labs |
|---|---|---|---|
| 1. Leadership page | CDO listed at C-suite altitude | No design title among 9 leaders | No design leader or category |
| 2. Posting language | IC with strategic AI scope, no people mgmt | Ownership language, executive access claimed | Builder-stage, hands-on role |
| 3. LinkedIn org shape | IC-heavy under CDO, craft-authority model | Title ceiling was Sr. Manager pre-search | Design as contributing skill, not function |
| 4. Design blog | Active, updated July 2026 | No design content | No design publication |
| 5. Design system | Public, 60+ components, AI-era investment | No public system | No public system |
| Composite read | Design authority is structural | Authority is aspirational, mandate-building | Builder-stage, not a leadership role |
Atlassian reads clean across all five. Design has authority here. The only question worth asking is whether the specific role you're looking at carries the scope you actually want.
Maven Clinic reads as a company investing in design authority it doesn't yet have. Mandate-building role. That can be exactly right if you want to build. It's a trap if you expect to inherit.
Anthropic Education Labs reads as builder-stage across every signal. Exciting company. Not a design leadership mandate.
Run this in order. Leadership page first. If design is absent from the leadership page at a company with 500+ employees, you already know the most important thing: design does not currently have executive altitude. Everything after that is calibration. The posting tells you what they want to build. LinkedIn tells you what exists today. Content and systems tell you how seriously design is treated as an organizational identity.
Five minutes. Run Signal 1 and Signal 2. The leadership page tells you where design sits. The posting tells you what the company thinks it's hiring for. Together, they're enough to decide whether this company is worth the next eight minutes of digging.
Ten to fifteen minutes. Five signals. You'll know more about a company's actual design authority than most candidates learn across three rounds of interviews, and you'll know it before you've spent a single minute on outreach you can't take back.
- Design systems as AI infrastructure: Atlassian's design team published a detailed account of how they're rebuilding their 15-year-old design system as a context engine for AI agents, MCP servers, and code generation templates.
- Ramp's player-coach mandate language: Ramp's Director of Product Design posting describes a role that includes shipping PRs, designing agent memory, and rethinking process as new AI capabilities unlock, which is useful comparison language for reading builder-stage versus org-stage postings.
- Gusto's published AI principles: Gusto published explicit AI design principles naming customer control, visible AI roles, intelligent escalation, and preserved agency in consequential payroll and benefits decisions, which is rare public evidence of how a growth-stage company frames AI trust internally.
- McKinsey's design authority research: McKinsey's business-value-of-design research argues that high-performing companies treat design as a top-management issue and measure it with revenue-grade rigor, while most companies leave design stuck in middle management.