Design Manager ATS Keywords for Tech Companies (2026)
Design Manager (DM) hiring is a different keyword target than Senior Product Designer (PD) hiring, and most resume advice conflates the two. Recruiters at tech companies — Stripe, Airbnb, Figma, Notion, Linear, Shopify, Atlassian — configure ATS searches for DM roles around four signal classes that don't appear on IC PD resumes: scope nouns (design-org headcount, team size, design-system ownership), leadership verbs (hired, restructured, scaled, coached, partnered), cross-functional collaboration (worked with eng/PM/research, aligned with product, influenced exec staff), and business-outcome language (activation, retention, conversion, OKRs, roadmap). A resume that reads like a senior-IC PD resume with "manager" in the title gets filtered out for DM roles because the keyword density in those four classes is too low [1][2]. This page lists the DM keywords that pass screens in 2026, grouped by signal class, with worked rewrites and a counter-list of IC craft keywords that backfire when a DM resume leans on them.
Key Takeaways
- DM resumes are scanned for four signal classes — leadership scope, business-impact verbs, cross-functional partnership, and design-strategy/process — that most IC PD resumes have zero density on; missing all four is the #1 reason senior IC designers get filtered out of DM searches [3][4].
- Team-size numbers ("led 6-designer team," "managed 11 designers across 3 product surfaces") are the highest-leverage Tier-1 DM keywords because Greenhouse, Lever, and Ashby all weight quantified scope above unquantified leadership prose [2][5].
- Julie Zhuo's The Making of a Manager frames the DM transition around three shifts — purpose, people, process — and the resume keyword surface mirrors that shift: outcome verbs replace craft verbs, scope nouns replace tool names, and people-development phrasing replaces portfolio prose [3].
- IC craft verbs ("designed," "wireframed," "prototyped," "shipped feature X") backfire on DM resumes after the first 1–2 bullets — they signal the candidate hasn't actually transitioned to management work, even if the title says manager [3][4].
- "Design system," "critique," "career development," "hiring loop," and "design strategy" are the Tier-1 process keywords that distinguish DM resumes from senior-IC PD resumes; their absence reads as "senior-PD-with-a-fancy-title," not DM [3][4].
- BLS reports the median annual wage for Art Directors (SOC 27-1011, the closest BLS proxy for senior design leadership) was $115,690 in May 2024 [5]; levels.fyi salary data tracks Design Manager and Director of Design comp at top-tier tech companies separately and consistently above the BLS proxy because BLS does not isolate digital design leadership [6].
- "Hiring" as a verb is itself a Tier-1 DM keyword — recruiters scan for evidence of headcount ownership ("hired 5 designers across IC3–IC5," "owned hiring loop for the platform-design team") because hiring competence is the rarest DM signal [3][7].
How Design Manager ATS Screens Work
DM hiring runs through the same ATS engines as IC design hiring — Greenhouse, Lever, Workday, Ashby, SmartRecruiters, iCIMS — but the keyword matrix is inverted. Where an IC PD search filters on craft and tools (Figma, prototyping, interaction design, visual design, design systems), a DM search filters on leadership scope, business outcomes, and process, with craft context as a secondary check. The DM ATS scan is mostly looking for evidence that the candidate operates at the right level of abstraction: a candidate whose top three bullets describe screen-level craft will be filtered out for senior DM roles, even if the title is right [3][4].
Engine-specific behavior for DM hiring:
Greenhouse (used at Stripe, Airbnb, Notion, Robinhood, and most Series-B-and-up startups) supports semantic matching, so "managed a team of 6 designers" registers as related to "led 6 designers" or "6-person design team" [2]. Greenhouse weights experience-bullet keywords more than skills-section keywords for DM roles — the bullets carry the load. The recruiter UI lets the filter "managed direct reports within last 2 years" return only candidates whose most recent role had reporting structure [2].
Lever (used at Eventbrite, Shopify, parts of Lyft) emphasizes recency. For DM roles specifically, Lever recruiters often filter by "currently or recently in design management" — a candidate who pivoted from DM back to IC and is now applying to DM roles needs to surface management work in the most recent 24 months prominently [2]. The "people-management within last 2 years" filter is the DM equivalent of the IC "Figma within last 2 years" filter.
Workday (used at Disney, Salesforce, Adobe, large-enterprise DM hires) is the strictest exact-match parser. For DM, Workday filters often require the literal phrase "Design Manager," "Senior Design Manager," "Director of Design," or "Head of Design" in the title block — a candidate titled "Design Lead" who has been operating as a DM for two years gets filtered out unless the resume explicitly clarifies the de-facto management work [8]. The fix: write the company entry as "Design Lead (Acting Design Manager — 5 direct reports)" or similar.
Ashby (used at Notion, Linear, Ramp, Anthropic, and most modern AI-era startups) is the friendliest ATS for nuanced DM resumes because its LLM-based scoring reads bullets and infers level from context. A bullet that describes "ran weekly 1:1s with 5 designers, drove perf calibration across 2 cycles, partnered with PM and Research on the quarterly roadmap" registers as DM signal even if the title is ambiguous [9]. Ashby is where mid-career IC-to-DM transitions get the fairest read.
SmartRecruiters (Visa, Atlassian) and iCIMS (Capital One, Disney non-engineering) lean stricter and more exact-match. Both score the title block heavily for DM searches, and both penalize creative titles ("Design Lead," "UX Lead," "Group Design Lead") for not matching the canonical "Design Manager" string. Taleo (legacy enterprise, Oracle) is the oldest and the strictest; for DM Taleo searches, write defensively with explicit phrases like "people manager," "direct reports," "headcount," "performance reviews" [8].
Tier 1 — Leadership Scope (the non-negotiables)
These keywords appear in the majority of mid-to-senior DM postings across LinkedIn, Built In, and direct careers pages at Stripe, Airbnb, Figma, Notion, Linear, and Atlassian in Q1 2026 [3][4]. If the resume is missing scope numbers or the leadership-verb cluster, it reads as IC even with the right title.
Team size / headcount — Quantify on every recent role. Patterns: "led 6-designer team," "managed 11 designers across 3 product surfaces," "second-line managing 2 DMs and 9 IC designers." Vague phrasing ("led a team," "managed designers") fails the screen because the recruiter is calibrating level on the number, not on the verb [3][4].
Direct reports — The literal phrase "direct reports" is heavily scanned [3][7]. Pattern: "5 direct reports across IC3–IC5" or "direct-reported 4 product designers and 1 design-systems engineer." Pairs with "skip-level" for second-line managers: "ran skip-level 1:1s with 11 designers across 2 DMs."
Hired / hiring — Tier-1 DM verb. Patterns: "hired 5 designers across IC3–IC5 over 18 months," "owned hiring loop for the platform-design team for 11 months," "ran 31 portfolio reviews as hiring-manager interviewer." Hiring competence is the rarest and most-scanned DM signal because most candidates can't name numbers [3][7].
Performance reviews / calibration — Process keyword cluster [3][4]. Patterns: "ran semi-annual perf calibration for 9 designers across 2 cycles," "wrote and delivered 18 performance reviews," "partnered with skip on calibration outcomes across the design org." Distinguishes DM from senior-IC.
1:1s — Specific management mechanic [10]. Patterns: "ran weekly 1:1s with 5 designers using Lara Hogan's feedback equation," "structured 1:1 cadence (career + project + personal) across 6 reports." The keyword "1:1s" itself is what the ATS catches; the depth of the bullet is what the recruiter reads.
Coaching / mentoring / career development — Coaching-stack keywords [3][10]. Patterns: "coached 2 senior designers through promotion to staff (IC4→IC5)," "mentored 3 designers through their first year of independent product ownership." Promotion-outcome numbers are the highest-signal version.
Headcount / budget — Resource-ownership keywords. Patterns: "owned 9-headcount budget across two product surfaces," "managed contractor and tooling budget for the design-systems team." Senior+ DM signal — first-line DMs often don't own budget.
Manager of managers / second-line — Director-of-Design signal. Patterns: "second-line DM with 2 DM reports and 9 IC indirect reports," "manager of managers for the consumer-product design org." Recruiters at top-tier companies explicitly filter for this distinction at director levels [3].
Tier 1 — Business-Impact Verbs (the outcome layer)
DM resumes that read well lead bullets with business-outcome verbs, not craft verbs. The pattern is verb + scope + outcome [3][4][7].
Delivered — Outcome verb. Pattern: "delivered the cross-team checkout redesign across 3 squads and 2 quarters, hitting the planned activation lift." Better than "designed the checkout flow."
Scaled — Growth verb. Patterns: "scaled the design team from 3 to 9 designers across 18 months," "scaled design-system adoption from 2 to 14 product surfaces." Pairs with team-size or surface-coverage numbers.
Restructured / reorganized — Org-design verbs [3]. Patterns: "restructured the platform-design org from 1 horizontal team to 3 product-aligned pods," "reorganized 9 designers across 4 newly-defined product surfaces." Senior-DM and director-level signal.
Drove / drove down / drove up — Outcome verb [4]. Patterns: "drove the redesigned onboarding to a measured activation lift over Q3" (only with the actual number you can defend), "drove the design-system migration to coverage across 14 surfaces." Numbers are the requirement.
Partnered — Cross-functional verb [3][4]. Patterns: "partnered with Product and Engineering to land the Q2 platform roadmap," "partnered with Research on the quarterly insight-to-design pipeline." Pairs with the partner function name.
Owned — Accountability verb [3][4]. Patterns: "owned the platform-design roadmap across 4 quarters," "owned hiring outcomes for the design-systems team." "Owned" reads as DM; "contributed to" reads as IC.
Authored / set — Strategy verbs. Patterns: "authored the design-org Q3 strategy brief and aligned 3 PM partners on the prioritization," "set the design-systems roadmap and aligned engineering on the rollout sequence." Senior-DM signal.
Tier 1 — Cross-Functional Collaboration
The cross-functional dance is the bulk of DM work past the first-line level [3][4][7]. The keyword cluster is heavily scanned at director-and-up roles.
Partnered with PM / Engineering / Research — Cross-functional verb cluster [3][4]. Patterns: "partnered with the PM lead and engineering manager to co-author the Q2 platform roadmap," "partnered with the user-research team on the quarterly insight-to-design feedback loop." Always name the partner function.
Aligned with — Collaboration verb. Patterns: "aligned design and engineering on the component-library migration across 3 squads," "aligned with brand and marketing on the rebrand-to-product-surface rollout." "Aligned with" reads stronger than "worked with."
Influenced / negotiated — Higher-altitude verbs [3]. Patterns: "influenced the executive staff on the design-investment thesis," "negotiated headcount allocation across 3 DM peers in the consumer-product org." Director-and-up signal.
Stakeholder / executive communication — Process keyword [4][7]. Patterns: "presented quarterly design strategy to VP of Product," "drove leadership-team consensus on the design-systems-vs-product-design investment split." Senior-DM and director signal.
Cross-functional roadmap — Joint-process keyword [3]. Patterns: "co-authored the cross-functional design + engineering + product roadmap across 4 quarters," "ran weekly cross-functional standup with PM, engineering, and research leads."
Tier 1 — Strategy and Process
OKRs / KRs — Goal-setting keyword [3][4]. Patterns: "drafted and delivered 9 design-team OKRs across 4 quarters," "owned KR cascade across 3 product-design pods." OKR fluency is a Tier-1 DM signal even at companies that don't use OKRs by name.
Roadmap / roadmapping — Strategy keyword [3][4]. Patterns: "owned the platform-design roadmap across 4 quarters," "co-authored the consumer-product design roadmap with PM and engineering partners." Distinguishes DM from senior-IC.
Hiring plan / headcount plan — Director-and-up keyword. Patterns: "wrote and executed the design-org hiring plan (5 hires across IC3–IC5 over 18 months)," "owned headcount allocation negotiation with finance and design ops." Senior signal.
Design strategy — Senior-DM keyword [3][11]. Patterns: "authored the platform-design strategy (2-page Rumelt-style brief)," "drove design-org strategy alignment across 3 DMs and 1 director." Cite "design strategy" once if you've actually written one.
Design system — Specific-asset keyword. Patterns: "owned the design-system roadmap across 14 product surfaces," "led the migration from a fragmented per-product design language to a unified design system over 18 months." Design-system ownership is one of the highest-signal DM keywords because it ties together craft, scope, and cross-functional partnership.
Design critique — Process keyword [3][12]. Patterns: "ran weekly design critique across 9 designers and 2 senior-IC reviewers," "redesigned the critique process to bias toward decisions rather than discussion." Critique facilitation is a senior-DM signal that surfaces craft authority without claiming IC craft work.
Career development / leveling — People-process keyword [3][4][13]. Patterns: "owned career-development conversations across 6 reports," "ran the design-org leveling rubric refresh for the consumer-product team." Pairs with promotion outcomes.
Prioritization / trade-offs — Decision-making keywords [3][4]. Patterns: "prioritized 9 candidate workstreams down to 3 quarterly bets across 2 product-design pods," "made the explicit trade-off between design-systems investment and product-feature work for Q3."
Tier 2 — Craft Context (the secondary check)
DMs still get scanned for craft context, but secondarily — the recruiter has already filtered on leadership signal first [3][4]. Surface the team's craft, not the DM's IC tools.
Pattern: "led the platform-design team building the consumer-product surface across iOS, web, and Android, with shared component-library ownership in Figma and motion partnership in After Effects." Names what the team builds, not what the DM personally pushes pixels in. Avoid leading with "Senior Design Manager skilled in Figma, Sketch, Principle, After Effects, prototyping" — that's an IC tool-list and reads junior for DM. The same context belongs in a phrase inside an experience bullet.
Allowed Tier-2 craft mentions on DM resumes: Figma (named once or twice), the team's surface coverage (iOS, Android, web, design-system, motion), the team's research partnership (qualitative, quantitative, mixed-methods), and the brand or visual-language ownership when relevant. Cite these once or twice across the resume, not in a Skills-section dump.
Counter-List — Keywords That Backfire on DM Resumes
This is the part most resume advice misses. DM resumes can be sunk by IC craft keywords that read as career-regression signal [3][4][7].
"Designed" — IC verb. On a senior DM resume, more than 1 bullet leading with "designed" reads as IC-still-pretending-to-be-DM. Replace with "delivered," "owned," "drove," or "led the team to ship."
"Wireframed" / "Prototyped" / "Pushed pixels" — IC framing. Even a DM who picks up the pen 20% of the time should not lead bullets with these. Pattern fix: "Set the visual direction for the redesigned onboarding and unblocked the team through 2 critique-led design-decision documents and a paired session with the staff designer on the most ambiguous flow" — owns the design leadership without falsely claiming the IC craft work.
"Built mockups" / "Created visual designs" / "Refined UI" — Pure IC verbs. Skip entirely on DM resumes for senior+ roles.
Long tools list (10+ items) — IC-resume convention. DM resumes that include a 15-item Tools section ("Figma, Sketch, Principle, Framer, After Effects, Lottie, Webflow, Photoshop, Illustrator, Procreate, ...") trigger spam-detection on Greenhouse and Ashby and read as IC-not-yet-transitioned [2][9].
"Led design for the team" without a number — Vague leadership. Always pair "led" with a number: "led 6-designer team" not "led design for the team."
"Was promoted to manager" — Title-only signal. Replace with the actual scope you took on: "Promoted to DM with 5 direct reports across the consumer and platform surfaces."
Heavy-use of first-person singular ("I designed," "I shipped") — IC framing. DM bullets read better in implicit-third-person voice describing the team work the DM enabled, not what the DM personally drew.
Portfolio-only framing — Senior-IC PD convention. A DM resume that points to a portfolio for "what I've shipped" without describing scope, team, hiring, or business outcome reads as senior-IC. The portfolio link still appears (mid-and-senior DM roles still expect a portfolio for the design-judgment check), but the resume bullets must carry the management signal independently.
Worked Examples — DM Keywords in Experience Bullets
Example 1 — Hiring scope
Before (C-grade): Helped hire designers for the team.
After (A-grade): Hired 5 designers across IC3–IC5 over 18 months as primary hiring manager — owned the loop calibration with the broader design org, ran 31 portfolio-review debriefs, and partnered with design recruiting on a sourcing-pipeline rebuild that doubled the qualified-candidate rate.
Keywords hit: Hired, hiring manager, loop, calibration, portfolio review, sourcing, partnered.
Example 2 — Cross-functional partnership
Before: Worked with PM and engineering on the roadmap.
After: Partnered with the PM and engineering leads to land the Q2 platform-design roadmap — co-authored the 2-page strategy brief, drove explicit prioritization of 3 bets out of 9 candidate workstreams, and ran weekly cross-functional standup with research and content-design partners across 3 product surfaces.
Keywords hit: Partnered, PM, engineering, research, content design, roadmap, strategy, prioritization, cross-functional, standup, surfaces.
Example 3 — Performance, calibration, and career development
Before: Did performance reviews for the team.
After: Ran semi-annual performance calibration for 9 designers across 2 cycles — wrote and delivered 18 performance reviews using Lara Hogan's feedback equation, coached 2 senior designers through promotion to staff (IC4→IC5), and partnered with my skip on cross-DM calibration outcomes across the consumer-product org.
Keywords hit: Performance calibration, performance reviews, feedback equation, coached, promotion, partnered, skip.
Example 4 — Strategy and outcome
Before: Owned the team's design direction and shipped projects on time.
After: Authored the platform-design strategy (2-page Rumelt-style brief) and owned the roadmap across 4 quarters — delivered 9 of 9 quarterly milestones, scaled design-system adoption from 4 to 14 product surfaces, and led the team through the unified-component-library migration on the planned timeline.
Keywords hit: Design strategy, roadmap, delivered, scaled, design system, migration, product surfaces, milestones.
Example 5 — Org design
Before: Reorganized the design team to align with product priorities.
After: Restructured the platform-design org from 1 horizontal team to 3 product-aligned pods over Q3 — managed the change with 9 designers across 4 newly-defined product surfaces, partnered with HR on the rebalancing of reporting lines, and drove leadership-team consensus on the new structure.
Keywords hit: Restructured, org, pods, partnered, HR, leadership team, consensus, product surfaces.
Example 6 — Coaching and team development
Before: Maintained team morale and helped designers grow.
After: Owned career-development conversations across 6 reports — coached 2 senior designers through promotion to staff (IC4→IC5), mentored 1 first-time DM through their initial year of management, and partnered with my skip on the design-org leveling-rubric refresh.
Keywords hit: Career development, coached, promotion, mentored, DM, partnered, skip, leveling rubric.
Density and Placement Rules for DM
- Professional Summary: Pack 5–6 Tier-1 DM keywords here. Example: "Senior Design Manager with 8 years of design-management experience — led 9-person platform-design org, hired 5 across IC3–IC5, partnered with PM/Engineering/Research on quarterly roadmap, and authored the team's design strategy."
- Skills section: For DM, skip the long-tools-list and replace with: Leadership (1:1s, performance reviews, calibration, coaching, hiring, career development), Strategy (OKRs, roadmap, prioritization, design strategy, hiring plan), Cross-functional (PM partnership, engineering partnership, research partnership, executive communication), Craft context (design system, critique, motion, brand, accessibility — one line on what the team builds). 4 categories, 16–20 items total.
- Experience bullets: Each recent bullet should pair a leadership verb with a quantified scope (team size, hire count, surface coverage, business outcome). Aim for 1 Tier-1 DM keyword per bullet, embedded naturally.
- Don't: Mix IC craft bullets with DM scope bullets in the same role. Pick one framing per role and commit. Mixed framing reads as confused career level.
- Portfolio link still required. Mid-and-senior DM roles still expect a portfolio link in the header — the design-judgment check happens through the portfolio, the management signal happens through the bullets. Both are mandatory; one without the other reads as imbalanced.
Density rule of thumb for DM: Tier-1 leadership-scope keywords (team size, direct reports, hired) appear 4–6 times across the resume. Tier-1 business-impact verbs (delivered, scaled, drove, partnered) appear 6–10 times. Tier-1 strategy keywords (OKRs, roadmap, design strategy, design system) appear 2–4 times. Tier-2 craft mentions (Figma, surfaces, critique) appear 3–5 times total — not 20.
Anti-Patterns That Fail DM Screens
- The "senior-PD-with-fancy-title" resume: Bullets are 80% IC craft, 20% mentoring. Reads as senior IC, not DM. Recruiters filter against this aggressively for senior+ DM roles [3].
- No team size: "Led a team of designers building the platform." How many? The number is the signal. Vague phrasing is a screen failure [3][4].
- No hiring evidence: The resume describes 3 years of DM work but never names a hire count, a portfolio-review role, or a hiring-loop redesign. Reads as "got the title, didn't do the hiring work" — and hiring is the rarest, most-scanned signal [3][7].
- Vague "led / managed" without outcome: "Led the team to ship features." What features? What outcome? DM bullets need both the verb and the measured result [4].
- Tools-stack Skills dump: A 15-item tools list (Figma, Sketch, Principle, Framer, After Effects, Lottie, Webflow, Photoshop, Illustrator, ...) on a DM resume is anti-signal. Replace with the DM-keyword skill categories above [9].
- Title inflation: Calling a 2-direct-report design-lead role "Design Manager" without clarifying scope, then applying to director roles. Hiring managers cross-check at interview, and the gap shows fast.
- "I personally": First-person singular IC-style framing on a management resume. DM bullets work better in implicit voice describing what the team did under your direction.
- Portfolio-as-resume-substitute: Pointing to the portfolio for everything. The portfolio is for design-judgment evidence; the resume bullets carry the management signal. Both must stand independently.
FAQ
I'm an IC designer applying for my first DM role — how do I write this resume?
Lead with the proto-management work you've already done — design-lead scope, design-system ownership, mentoring, portfolio-review interviewing, project leadership — and frame each in DM-resume language. "Design-led 4-designer feature pod across 3 quarters; ran weekly critique, owned the prioritization conversation with PM, and mentored 2 mid-level designers through their first staff-track project." That bullet hits "design-led," "critique," "prioritization," "PM partnership," "mentored" — Tier-1 DM keywords from a senior-IC role. Julie Zhuo's The Making of a Manager Chapter 1 (purpose, people, process) is the canonical scaffolding for this transition framing [3].
Should I list my tools (Figma, Sketch, etc.) on a DM resume?
Once, briefly, in a "Team Craft Stack" line — not as a 15-item Tools dump. The DM ATS scan does not weight tool fluency heavily, and a long IC-style tools list reads as career-regression. The exception: small startups (<30 designers org-wide) where the DM is expected to push pixels 30%+ of the time. For those roles, list the 3–4 tools the team uses in production, but still as a single line, not a section. Figma fluency is assumed for any working DM in 2026; restating it adds no signal.
How do I handle a designer/manager pendulum on my resume?
Frame the IC stretch as deliberate and recent management as current. Pattern: "Stepped back to senior IC for 12 months to rebuild craft depth on the new platform-design system — returned to management with 6-designer team Q3 2024." Recruiters at modern tech companies (Stripe, Notion, Linear, Anthropic) read pendulum moves as senior-designer signal, not as a red flag — but only if framed as deliberate and recent management work is current. The trap is hiding the IC period or framing it as failure.
How many direct reports do I need to claim "Design Manager"?
The honest floor is 3–4 direct reports, sustained for at least 6 months. Below that, the role is closer to "design-lead with people-management responsibilities" and the resume should frame it accordingly. The signal hiring managers want is "has run a team through at least one hiring cycle, one performance cycle, and one major launch" — that's roughly the 12-month, 4-direct-report mark. Below it, the resume reads as transitional, which is fine if framed honestly.
Do I need to keep a portfolio as a design manager?
Yes, for nearly every senior DM role. The portfolio is where hiring managers verify design judgment — not your IC skill, but your taste, your decision-making, and your ability to articulate why. Per Bob Baxley's design-leadership essays, design management without active design judgment becomes management of a craft you no longer understand [12]. The portfolio for a DM should show selected work where you owned the design direction, with explicit context for what was your decision vs. the team's decision, and what the business outcome was. 4–6 case studies is plenty; depth beats breadth.
How do I list a DM role where I also pushed pixels?
Lead the bullet cluster with management work; close with one bullet on craft contribution if it's relevant. Pattern: 4 management/strategy/scope bullets, then 1 bullet like "Maintained ~25% IC capacity on the most ambiguous design surfaces — co-authored the design-system migration spec and paired with the staff designer through the rollout." Don't lead with the IC work; doing so signals DM-pretending-to-be-IC.
What about Director of Design or Head of Design roles?
The resume needs to surface "second-line" or "manager of managers" explicitly — recruiters filter on those literal phrases [3]. Pattern: "Director of Design (Manager of Managers) — second-line for 2 DMs and 11 IC indirect reports across the consumer-product org. Owned 13-headcount budget, drove org-wide hiring plan, ran cross-DM calibration with 2 peer second-lines." Director-level signal lives in: org size, budget ownership, peer-DM negotiation, executive communication.
Do I need an MFA or design degree for DM screens?
No. Per Marty Cagan's Empowered framing of product-leadership credentialing, the screen at top-tier tech companies is on demonstrated leadership scope and outcomes, not on degree pedigree [11]. Strong DMs land senior-DM roles at Stripe, Figma, Notion, and Linear from a wide range of educational backgrounds — including non-design degrees and self-taught paths. Skip the MFA / BFA discussion in the summary line if it crowds out a scope keyword.
References
[1] Greenhouse Software. "Sourcing and Filtering Best Practices — Greenhouse Help Center." https://support.greenhouse.io/hc/en-us/articles/360051506331-Sourcing-best-practices
[2] Ashby HQ. "How Ashby's AI-Powered Sourcing Works." https://www.ashbyhq.com/resources/guides/ai-powered-sourcing
[3] Julie Zhuo. The Making of a Manager: What to Do When Everyone Looks to You (Penguin Portfolio, 2019). https://www.juliezhuo.com/book/manager.html
[4] Lara Hogan. Resilient Management (A Book Apart, 2019). https://abookapart.com/products/resilient-management
[5] U.S. Bureau of Labor Statistics. "Art Directors — Occupational Outlook Handbook." https://www.bls.gov/ooh/arts-and-design/art-directors.htm
[6] levels.fyi. "Design Manager and Director of Design Salary Data." https://www.levels.fyi/t/product-designer/levels/design-manager
[7] Hello Interview. "Design Manager Leveling and Interview Rubrics." https://www.hellointerview.com/
[8] Workday. "Workday Recruiting — Candidate Search Documentation." https://doc.workday.com/admin-guide/en-us/staffing/recruiting/candidate-experience.html
[9] Ashby HQ. "Recruiting Workflow and Candidate Scoring." https://www.ashbyhq.com/
[10] Lara Hogan. "Feedback Equation." https://larahogan.me/blog/feedback-equation/
[11] Marty Cagan. Empowered: Ordinary People, Extraordinary Products (SVPG / Wiley, 2020). https://www.svpg.com/books/empowered-ordinary-people-extraordinary-products/
[12] Bob Baxley. "Design Leadership Essays." https://bobbaxley.com/
[13] Kim Goodwin. Designing for the Digital Age: How to Create Human-Centered Products and Services (Wiley, 2009). https://www.kimgoodwin.com/