Design Manager ATS Checklist for Tech Companies (2026)

Design Manager ATS Checklist for Tech Companies (2026)

Design Manager (DM) resumes get filtered by the same ATS engines as IC product-design resumes — Greenhouse, Lever, Workday, Ashby, SmartRecruiters, iCIMS — but the failure modes are inverted. Where an IC PD resume gets rejected for a thin tools/craft surface, a DM resume gets rejected for reading like a senior-IC resume with "manager" in the title: no team-size numbers, no hiring evidence, no business outcomes, no cross-functional partnership signal [1][2][3]. This 22-item checklist walks every Design Manager through the pre-submission audit specific to leadership roles at tech companies — format, structure, scope numbers, hiring signal, DM-vs-IC framing, portfolio coordination, and verification — and names the DM-specific failure modes that take down even strong candidates.

Key Takeaways

• Most Fortune 500 companies route resumes through ATS engines before any human review, and the DM keyword target is fundamentally different from the IC PD target — leadership scope, hiring evidence, business outcomes, and cross-functional partnership replace the IC craft / tools scan [1][2].
• The single most common DM resume failure is the "senior-PD-with-fancy-title" pattern: 80% of bullets are IC craft work, 20% are mentoring — recruiters configured to filter for "managed direct reports" auto-reject these [3][4].
• Team-size numbers are non-negotiable on every recent management role. "Led a design team" without a number reads as IC-still; "Led 6-designer team across 3 product surfaces" passes [3][4].
• Per Julie Zhuo's The Making of a Manager, the DM transition is a shift in purpose, people, and process — and the resume bullets must reflect that shift through outcome verbs, scope nouns, and people-development phrasing rather than craft prose [3].
• Director-and-up roles screen for "manager of managers" or "second-line" explicitly; the level signal lives in the literal phrasing, not in the title alone [3][5].
• 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 [6]; levels.fyi tracks Design Manager and Director of Design comp at top-tier tech companies separately, consistently above the BLS proxy because BLS does not isolate digital design leadership [7].
• The portfolio link must still appear in the header for any senior DM role. Per Bob Baxley's design-leadership essays, design management without active design judgment becomes management of a craft you no longer understand — recruiters and hiring managers verify judgment through the portfolio [8].

Stage 1 — Format and File Prep (Items 1–5)

1. Single-column layout, no exceptions.

Greenhouse and Workday inconsistently parse two-column resumes; the parsed-text version recruiters see often appends the right column after the left, scrambling experience bullets [1][2]. DM resumes are particularly vulnerable because many "design-friendly" templates put a sidebar for direct-report counts, design-system metrics, or color callouts — exactly the column most likely to mis-parse. Use single-column with vertical sections: Header → Summary → Skills → Experience → Education → Optional (Speaking, Writing). Verify by copy-pasting into a plain-text editor; if the order is wrong there, it's wrong in the ATS.

2. Submit as .docx or PDF — both work, with caveats.

.docx is the safer default across Workday and Taleo. PDF works on Greenhouse, Lever, and Ashby with high parse fidelity. The trap most relevant for DMs: PDFs exported from Figma, Sketch, or design tools sometimes embed text as glyphs or vectorized paths rather than parseable characters, breaking ATS extraction [2]. Build the resume in Word, Google Docs, or a plain-text-first tool — not in Figma. If you do export from a design tool, verify the output with pdftotext to confirm the extracted text matches the rendered document.

3. Keep file size under 2 MB.

DM resumes typically run 1–2 pages and don't include images, so this is rarely an issue. Watch for embedded company logos in side projects, headshot photos (skip these — not standard in US tech), or thumbnail screenshots of work (those belong in the portfolio, not the resume). Pure-text DM resumes should be 50–200 KB. Anything over 2 MB has embedded media that should come out and live in the portfolio link instead.

4. Use system fonts only — Calibri, Arial, Helvetica, Georgia, or Times New Roman.

Custom fonts get substituted during ATS parsing, sometimes shifting line breaks and section boundaries unpredictably [2]. DM resumes don't need typographic personality on the document — the leadership signal is in the words, and the typographic personality belongs in the portfolio. Save the custom font for your portfolio site, your speaking-deck template, or your case-study covers.

5. Avoid headers/footers, text boxes, columns, and tables.

Document headers/footers on Workday and older Greenhouse parsers can be ignored entirely [1][2]. DM resumes sometimes use tables to lay out the team-scope summary ("Team size: 9 | Direct reports: 5 | Hires: 4 | Quarters: 8") — this fails ATS parsing universally because the table tokenizer scrambles the cells. The fix: write the same scope summary as a single line of text in the role's first bullet, e.g., "Senior DM, Platform-Design Org — managed 9 designers (5 direct reports + 4 indirect via 1 DM); hired 4 across 8 quarters."

Stage 2 — Structure and Section Order (Items 6–10)

6. Standard section headers — exactly these names.

Use: "Summary" (or "Professional Summary"), "Skills" (or "Core Competencies"), "Experience" (or "Professional Experience"), "Education," "Speaking" or "Writing" (optional, only if substantial). ATS parsers — especially Taleo and older Workday — pattern-match on exact section names [1][2]. Creative section names ("Where I've Led," "What I've Crafted," "How I Work") cause the parser to skip those sections. DM resumes that lean rebellious here lose ATS points without any compensating gain. Save the creative section naming for the portfolio site.

7. Header line: name, location, contact, LinkedIn, portfolio — and that's it.

Format: "Name | City, ST | email | (xxx) xxx-xxxx | linkedin.com/in/firstname-lastname | portfolio-url." The portfolio URL is mandatory for DM resumes — even at the senior-DM and director levels, hiring managers expect the portfolio for the design-judgment check. Skip GitHub (rarely relevant for DM unless you've maintained an open-source design-system project), headshot, address line, and "Open to Work" banner — these read as junior-resume conventions.

8. Lead with a 3–4 line Professional Summary that names scope, hiring, and partnership.

The summary gets the highest scan-weight per word [1][2]. For DM, pack 5–6 Tier-1 DM keywords. Example: "Senior Design Manager with 8 years in design management — led 9-person platform-design org across 3 product surfaces, hired 5 across IC3–IC5 over 18 months, partnered with PM/Engineering/Research on quarterly roadmap, and authored the team's design strategy. Recent: drove the unified-design-system migration across 14 surfaces; design-system and accessibility ownership at the org level." That's 7 Tier-1 DM keywords (managed, led, hired, partnered, roadmap, design strategy, design system) plus 2 Tier-2 (surfaces, accessibility) in 4 lines.

9. Skills section organized for DM, not for IC.

DM skills sections should NOT be a 15-item tools/software dump — that's the most common failure mode. Recommended grouping (4 categories, 16–20 items): Leadership (1:1s, performance reviews, calibration, coaching, hiring, career development, delegation, decision-making), Strategy (OKRs, roadmap, prioritization, design strategy, hiring plan, headcount budget), Cross-functional (PM partnership, engineering partnership, research partnership, executive communication), Craft Context (one line on what the team builds — "consumer-product surfaces across iOS / web / Android; design system + accessibility + motion"). The IC-style 15-item tools dump triggers spam-detection on Greenhouse and Ashby and reads as IC-not-yet-transitioned [1][9].

10. Experience section: reverse-chronological, 5–7 bullets per recent role.

Reverse-chronological is the ATS expectation. For senior DMs and director-and-up, 5–7 bullets at the most recent role, 4–5 at recent prior roles, 3 at older roles. DM bullets carry more signal density than most design roles because each bullet should reference a leadership verb, a quantified scope, and a measured outcome. Don't skimp on bullet count for the most recent role — recency-weighted scoring on Lever and Greenhouse pushes the recent role to the top of recruiter screens [1][10].

Stage 3 — DM-Specific Content Audit (Items 11–16)

11. Every recent role names team size and direct-report count.

This is the single highest-leverage check on the entire DM checklist. For each role in the last 5 years that was a management role, the bullet cluster must include: team size, direct-report count, indirect-report count if applicable, and tenure of the team under your management. Pattern: "Senior DM, Platform-Design Team — 9 designers (5 direct + 4 indirect via 1 DM), 18-month tenure as second-line." Vague phrasing ("led the team") fails the screen because the recruiter is calibrating level on the number, not on the verb [3][4].

12. Every recent role surfaces hiring evidence.

Hiring is the rarest and most-scanned DM signal [3][5]. For each DM role, name a hire count, a portfolio-review interview role, or a hiring-loop redesign you owned. Pattern: "Hired 5 designers across IC3–IC5 over 18 months as primary hiring manager; ran 31 portfolio-review debriefs; partnered with the design-recruiting team on a sourcing-pipeline rebuild." If you've genuinely never hired (e.g., new DM in headcount-frozen org), name the equivalent process work: "owned the loop calibration framework rewrite," "ran 11 portfolio-review norming sessions," "wrote and shipped the design-interview rubric for the platform-design team."

13. Every recent role names a quantified business or scope outcome.

DM bullets without numbers are deprioritized by recruiters specifically trained to scan for outcome metrics [3][4]. Patterns that pass: "scaled design-system adoption from 4 to 14 product surfaces," "delivered 9 of 9 quarterly design milestones across 2 years," "scaled the design team from 3 to 9 designers across 18 months," "drove team retention to a sustained level over 24 months across 6 senior designers" (only with the actual measurable claim you can defend), or "owned the design contribution to the consumer-product activation initiative across 4 quarters." If a bullet has no number, ask whether it deserves to be on the resume at all. Per the editorial-truth bar: empty space beats fabrication. If you don't have a number for a particular bullet, lean on a different bullet that does.

14. Bullets show range across the four DM domains.

Senior-DM and director resumes need range across four domains in each recent role [3][4]: People (1:1s, coaching, performance, career development), Hiring (loops, calibration, sourcing partnership, portfolio review), Strategy / Process (OKRs, roadmap, design strategy, design system, critique), Cross-functional (PM partnership, engineering partnership, research partnership, executive communication). An all-people resume reads as first-line DM. An all-strategy resume reads as IC-strategist with delusions of management. The senior signal is balance — at least one bullet in each domain per recent role.

15. The IC-vs-DM split is intentional and explicit.

If you've been operating as a player-coach DM (still pushing pixels 25%+), the resume should make the split explicit and lead with management. Pattern: 4 management/strategy/scope bullets, then 1 closing 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." If you've been a pure people-manager (zero direct craft work), don't fake IC bullets — own the management focus. The mistake is mixing IC and DM framing without intentionality, which reads as confused career level [3][4][5].

16. Education compressed; portfolio link prominently retained.

DMs more than 5 years out of school should compress Education to 1–2 lines. Degree, school, year. Cut: GPA (irrelevant for DM regardless of value), coursework, dean's list, undergrad clubs. MFAs and BFAs are common on DM resumes but add no ATS-screen value above the line — keep them concise. The portfolio URL, however, stays at the top of the document. Mid-and-senior DM roles still expect a portfolio for the design-judgment check, even when the resume bullets carry the management signal independently. Per Bob Baxley's design-leadership writing, the portfolio is where hiring managers verify the DM still has design judgment they can rely on [8].

Stage 4 — DM Keywords and Mechanics (Items 17–19)

17. Mirror the JD's exact phrasing — title, scope, and process.

If the JD says "Senior Design Manager," use that exact title in your summary even if your formal title is different. If the JD says "manager of managers" or "second-line manager," use those exact phrases somewhere in the resume to pass strict-match Workday and Taleo screens [2][5]. If the JD names specific frameworks ("OKRs," "performance calibration," "design strategy," "design system"), mirror them. The fix: read the JD twice, list the 12–16 highest-frequency leadership/process terms, and verify each appears in your resume in the canonical form. Tools like Jobscan or Resume Worded automate this comparison [11].

18. Don't claim a scope you can't defend in a 30-minute interview.

The ATS rewards scope claims; the DM interview punishes false claims hard. DM hiring loops include questions about hiring decisions, perf-review patterns, conflict resolution, design-org structure, design-system governance, and specific incidents you led through [3][4]. A candidate who claims "managed 14 designers" but turns out to have had 4 direct reports and a vague "dotted line to 10 others" fails the first hiring-manager interview. Limit scope claims to what you've actually done. If your direct-report count is 4, say 4. If your hires are 3, say 3. The numbers don't have to be big — they have to be true.

19. Avoid the "kitchen sink leadership" dump.

DM Skills sections should not list every leadership concept that exists. A skills line that reads "Leadership, Coaching, Mentoring, Performance Management, Career Development, Change Management, Conflict Resolution, Delegation, Decision-Making, Strategic Thinking, Vision Setting, Roadmap Planning, Stakeholder Management, Cross-Functional Collaboration, Executive Communication, Influencing, Negotiating, Hiring, Onboarding, Offboarding, Team Building, Culture Building, Diversity & Inclusion, Remote Leadership, ..." triggers spam-detection on Greenhouse and Ashby and reads as buzzword-stuffing [1][9]. Pick the 12–16 leadership skills you actually do and ship them deep in experience bullets, not as a flat list.

Stage 5 — Verification and Submission (Items 20–22)

20. Run your resume through Jobscan or Resume Worded against the DM JD.

Both tools simulate ATS parsing and produce a match score against the specific JD [11]. DM matches are typically harder than IC matches because the keyword surface is narrower and the level distinctions (first-line vs. second-line vs. director) are tighter — target 75%+ match score for DM roles, with most missing-keywords being legitimate scope-clarification gaps you can fix by adding numbers to bullets. Under 65% match means the resume needs structural rework before submitting. The 10 minutes of running this check is the single highest-ROI step in the entire submission process.

21. LinkedIn and portfolio match the resume on scope, title, and tenure.

Recruiters at every modern tech company cross-reference both LinkedIn and the portfolio during pre-screen [3][10]. The four checks before submitting: (a) every job title on the resume matches the LinkedIn title exactly (or differs only in the "Senior" / "Staff" / "Principal" prefix in a way you can defend), (b) every team-size and hire-count number on the resume is consistent with what LinkedIn says about the company headcount and your role, (c) every dated achievement on the resume falls within your LinkedIn employment dates, (d) the portfolio's case studies are dated within roles where the resume claims you owned them. Inconsistency between resume, LinkedIn, and portfolio reads as a trust failure, and recruiters are explicitly trained to look for it.

22. Final manual parse-test by copying into a plain-text editor.

Open your .docx in Word or Google Docs, select all, copy, paste into TextEdit (Mac), Notepad (Windows), or a plain-text editor. The result approximates what the ATS sees post-parse. Verify: section order is right, bullets aren't scrambled, scope numbers (team size, direct reports, hire counts, surface counts) are intact and correctly attached to their roles, percentage and dollar signs render correctly (no "%" → "â%" artifacts), all links — including the portfolio URL — are still readable as text. If anything looks wrong here, it'll look wrong in the ATS. Fix the source until the plain-text version reads cleanly.

Bonus — DM Resume Failure Modes Beyond the ATS

Even resumes that pass the ATS can fail the recruiter and hiring-manager screens that follow. Six failure modes specific to DM resumes:

1. The "title-without-scope" resume. The candidate has been a DM for 3 years. The resume says "Design Manager." Then every bullet describes IC craft work. Fails the recruiter screen because the level signal in the bullets is junior. Fix: rewrite with team-size numbers, hire counts, and outcome metrics in every recent bullet.
2. The "led / managed" verb monoculture. Every bullet starts with "Led" or "Managed." Reads flat and unspecific. Recruiters skip past it. Fix: rotate verbs aggressively — Hired, Restructured, Drove, Delivered, Scaled, Owned, Influenced, Negotiated, Coached, Authored, Aligned, Set, Partnered.
3. The "people only" resume. All bullets are about 1:1s, performance reviews, and coaching. No business outcomes, no roadmap, no design strategy. Reads as first-line DM and ceiling-stuck. Fix: add at least one strategy/process bullet and one cross-functional bullet per recent role.
4. The "strategy only" resume. All bullets are about OKRs, roadmaps, and design strategy. No 1:1 mechanics, no hiring, no perf calibration. Reads as IC-strategist or PM-pretending-to-be-DM. Fix: add at least one people-management bullet per recent role.
5. The "I personally" voice. Bullets read like the DM did everything themselves: "I designed," "I shipped," "I decided." DM resumes work in implicit-third-person voice describing the team work the DM enabled, not what the DM personally drew. Fix: rewrite with the team or org as the implicit subject ("Drove the team to ship 9 quarterly milestones," not "I shipped 9 milestones").
6. The "no portfolio" resume. A DM resume without a portfolio link in the header gets filtered by hiring managers regardless of the bullets, because design judgment can't be verified from text alone. Per Bob Baxley's design-leadership essays, design management without active design judgment becomes management of a craft you no longer understand [8]. Fix: maintain a portfolio with 4–6 deep case studies that show your design judgment and your team's outcomes — the portfolio carries the craft signal, the resume carries the management signal, and both must hold up independently.

FAQ

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 when framed as deliberate and when recent management work is current. The trap is hiding the IC period or framing it as failure; that reads worse than naming it.

I'm applying to my first DM role from an IC position. What goes on the resume?

Surface every proto-management element from your senior-IC work, framed in DM-resume language. Design-lead scope (with team size), portfolio-review interview participation (with hire count), mentoring (with promotion outcomes), project leadership (with cross-functional partnership), critique facilitation (with cadence), and design-system ownership (with surface-count). Julie Zhuo's The Making of a Manager Chapter 1 (purpose, people, process) is the canonical scaffolding [3]. Then run the resume through Jobscan against a DM JD; aim for 70%+ match by adjusting bullets to mirror the JD's leadership phrasing.

How many years of DM experience do I need for "Senior DM" titles?

The honest range is 4+ years of sustained design-management work, with at least one full hiring cycle, two performance cycles, and one team-restructuring or design-system migration under your direct ownership. Below that, "Senior DM" reads as inflated even if the company gave you the title. Above 6 years, "Senior DM" is the floor; second-line / "manager of managers" or director becomes the next step. Hello Interview's leveling rubrics map these tenure expectations clearly across top-tier tech companies [12].

Should I include team tenure and retention numbers?

Yes, when the numbers are good and you can defend them. "Maintained sustained team retention across 6 reports over 24 months" is a strong bullet when the underlying number is real. The editorial bar: cite numbers you can defend in a hiring-manager interview, and skip the metric if the underlying data is shaky. An unsourced retention claim that a hiring manager probes and you can't substantiate damages the entire resume's credibility — empty space beats fabrication.

Do I need a portfolio as a design manager?

Yes, for nearly every senior DM role at top-tier tech companies. 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 [8]. 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. The portfolio doesn't need to show recent IC craft work — it needs to show that you can still recognize and articulate good design.

How do I handle a layoff on my DM resume?

Don't put "laid off" on the resume itself — that's interview-conversation context, not resume copy. Instead, end the role at the layoff date and let the date do the work. If the gap is more than 6 months, name what you did during the gap (consulting, design advisory work, writing, sabbatical, portfolio refresh) in 1 line. Recruiters at modern tech companies read 2022–2024 design-team layoff gaps as market signal, not candidate signal, especially when the layoff coincided with widely-reported design-org reductions at the company. The framing matters more than the gap length.

Should I list direct reports by level (IC3, IC4, IC5) or just the count?

Both, when relevant. Pattern: "5 direct reports across IC3–IC5" or "managed IC4–IC5 designers and 1 staff designer." The level distribution signals the scope of leveling and calibration work the DM has done. For director-and-up roles, list the DM levels under you ("2 DMs (M1 and M2) and 9 indirect IC reports across IC3–IC5"). For first-line DM roles, the count alone is fine if the levels aren't differentiating. Where the company uses non-numeric leveling (e.g., Senior / Staff / Principal), use that company's actual ladder rather than translating to IC3–IC6.

How do I show design-system leadership on a DM resume?

Design-system ownership is one of the highest-signal DM keywords because it ties together craft, scope, and cross-functional partnership. Patterns: "Owned the design-system roadmap across 14 product surfaces; partnered with the platform-engineering team on the unified-component-library migration over 18 months" or "Led the design-system foundations team (3 designers + 2 design-systems engineers); drove the migration from a fragmented per-product visual language to a unified system across 9 surfaces." Pair with metrics: surface count, component count if substantial, adoption rate. Design-systems DMs at Figma, Atlassian, Shopify, and Adobe rank these claims highly.

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] Workday. "Workday Recruiting — Candidate Search Documentation." https://doc.workday.com/admin-guide/en-us/staffing/recruiting/candidate-experience.html

[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] Marty Cagan. Empowered: Ordinary People, Extraordinary Products (SVPG / Wiley, 2020). https://www.svpg.com/books/empowered-ordinary-people-extraordinary-products/

[6] U.S. Bureau of Labor Statistics. "Art Directors — Occupational Outlook Handbook." https://www.bls.gov/ooh/arts-and-design/art-directors.htm

[7] levels.fyi. "Design Manager and Director of Design Salary Data." https://www.levels.fyi/t/product-designer/levels/design-manager

[8] Bob Baxley. "Design Leadership Essays." https://bobbaxley.com/

[9] Ashby HQ. "How Ashby's AI-Powered Sourcing Works." https://www.ashbyhq.com/resources/guides/ai-powered-sourcing

[10] LinkedIn Talent Solutions. "Recruiter Search Best Practices." https://business.linkedin.com/talent-solutions/recruiter

[11] Jobscan. "ATS Resume Test — Run Your Resume Through Our Free Scanner." https://www.jobscan.co/

[12] Hello Interview. "Design Manager Leveling and Interview Rubrics." https://www.hellointerview.com/

[13] Kim Goodwin. Designing for the Digital Age: How to Create Human-Centered Products and Services (Wiley, 2009). https://www.kimgoodwin.com/