Product Designer ATS Checklist — Pass Every Screen

Product Designer ATS Checklist — Pass Every Screen

Product Designer resumes fail ATS screens at a higher rate than most other roles, because the work is visual but the document gets parsed as plain text [1]. A portfolio-led candidate who relies on links, image-heavy layouts, and "the work speaks for itself" will be filtered out before a recruiter ever sees the file — even at companies actively trying to hire designers. This 21-item checklist walks every Product Designer through the pre-submission audit: format, structure, content, keywords, portfolio handling, and verification. Each item names the specific ATS engine it protects against (Greenhouse, Lever, Workday, Ashby, SmartRecruiters, iCIMS, Taleo) and the worked example for Product Designer specifically.

Key Takeaways

• 97.4% of Fortune 500 companies run an ATS that filters resumes before recruiters see them; design and product roles are not exempt [1].
• The single most common Product Designer ATS failure is a two-column layout — Workday and older Greenhouse configurations parse the right column out-of-order, scrambling experience bullets and tanking keyword extraction [2][3].
• Portfolio URL belongs in the header (not the body) and must be a clean, scannable string that clipboards correctly: "portfolio.com/firstname" beats "https://www.portfolio.behance.net/firstnamelastname?ref=resume."
• Tools like Jobscan, Resume Worded, and the Greenhouse public demo will give you ATS-parse previews — running your resume through at least one before submitting is the single highest-ROI verification step [3][4].
• Design tool keywords (Figma, FigJam, Maze, Dovetail, Storybook) are scanned exact-match on Workday and Taleo; non-canonical capitalization ("FIGMA" or "figma") fails some configurations [5].
• The recruiter spends 7.4 seconds on first-pass review of a Product Designer resume, per Ladders eye-tracking research, so the top third of the document — header, summary, and first experience bullet — must compress your full positioning [6].
• Save and submit as .docx for any application that doesn't explicitly require PDF; older Workday and Taleo configurations parse Word better than PDF, especially for Product Designer resumes that include character-styled content [2][5].

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

1. Use a single-column layout.

Greenhouse and Workday both inconsistently parse two-column resumes; the parsed-text version recruiters see often shows the right column appended after the left, scrambling bullets out of order [2][3]. Lever and Ashby handle two columns better but still down-rank parse quality. For Product Designers specifically, this matters more than for most roles — many design templates ship with a sidebar for "Skills" and "Tools," and that sidebar is the column most likely to scramble. Use a single-column layout with sections in clear vertical order: Header → Summary → Skills → Experience → Education. Verify by copy-pasting your resume into a plain-text editor (TextEdit, Notepad) — if the order is wrong there, it's wrong in the ATS.

2. Submit as .docx unless PDF is explicitly required.

The Microsoft Word format is the most reliable across every major ATS. Workday and Taleo were both built around .docx parsing and handle it cleanest. Greenhouse and Lever support both PDF and .docx equivalently, but PDF parse quality drops when the document was exported from Figma, Sketch, or Canva because those tools generate image-heavy or non-standard PDFs [2][5]. If the application form lets you choose, choose .docx. The exception: if the JD says "PDF only" (some boutique design firms and consulting firms do), follow the instruction.

3. Keep file size under 2 MB.

SmartRecruiters caps uploads at 5 MB; Greenhouse caps at 25 MB; Workday at 10 MB [3][5]. But several applicant portals enforce hidden internal caps lower than the documented limit. A Product Designer resume that includes embedded images of project thumbnails will balloon to 8–15 MB and fail submission silently on some configurations. Strip thumbnails, screenshots, and decorative graphics from the resume — those belong in the portfolio, not the resume document. A pure-text Product Designer resume should be 60–200 KB.

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

Custom fonts (Inter, Söhne, GT America, IBM Plex) get substituted to a default font during ATS parsing, and the substitution can shift line breaks, page breaks, and section boundaries unpredictably [2]. Worse, on Workday and Taleo, custom fonts can fail to render in the recruiter's preview view — leaving them looking at a blank document. Designers hate this rule; ship it anyway. The portfolio is where typographic personality lives. The resume is for parsing.

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

Header and footer regions on Workday and older Greenhouse parsers are sometimes ignored entirely [2][5]. If your name, phone, or portfolio URL lives in the document header, the ATS may not extract it — and the recruiter sees an unnamed application. Text boxes and tables similarly produce parse errors. The workaround is to put contact info as plain text on the first line of the body, not in the document header element. For Product Designers used to grid layouts, this feels primitive — but the ATS doesn't grade aesthetic.

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

6. Standard section headers — exactly these names.

Use: "Summary" (or "Professional Summary"), "Skills" (or "Core Skills"), "Experience" (or "Professional Experience"), "Education," "Certifications," "Projects." ATS parsers — especially Taleo and older Workday — pattern-match on exact section names to know where to extract data [2][5]. Creative section names like "Where I've Been" instead of "Experience" or "Stuff I Know" instead of "Skills" cause the parser to skip those sections entirely. Designers love clever headers. The ATS doesn't read clever.

7. Place the portfolio URL in the header, not the body.

For Product Designers, the portfolio is the single most important external link. Put it in the contact line at the very top of the resume (not in the document header element — see Item 5). Format: "Name | City, ST | [email protected] | (xxx) xxx-xxxx | portfolio.com/firstname | linkedin.com/in/firstname." Use a clean, short URL — preferably your own domain. Avoid: "https://www.portfolio.behance.net/firstnamelastname?ref=resume" or shortened links (bit.ly, tinyurl) — recruiters distrust shorteners and ATS parsers sometimes mangle them.

8. Lead with a 3–4 line Professional Summary.

The summary gets the highest scan-weight per word in every major ATS [3][5]. For a Product Designer, the summary should compress: years of experience, type of products shipped (consumer, B2B SaaS, marketplace, fintech), three highest-weighted Tier-1 keywords (Figma, Design Systems, User Research), and one or two outcomes. Example: "Senior Product Designer with 7 years shipping consumer and B2B SaaS — leads end-to-end design from research through high-fi Figma prototypes, contributed 23 components to a public design system, and partnered cross-functionally with PM and Eng on activation experiments lifting Day-7 from 31% to 44%."

9. Skills section organized into 2–3 categories.

Group skills by category for both ATS scanning and recruiter readability. Recommended grouping for Product Designer: Design Tools (Figma, FigJam, Storybook, Principle), Research Tools (Maze, Dovetail, Lyssna, UserTesting), Methods & Disciplines (User Research, Usability Testing, Information Architecture, Design Systems, Service Blueprinting, Heuristic Evaluation), and optionally Frontend Awareness (HTML, CSS, React component literacy). Total 10–14 distinct items — listing more triggers spam-detection on Greenhouse and Ashby [3][7].

10. Experience section: reverse-chronological, 3–6 bullets per role.

Reverse-chronological is the default ATS expectation. Functional resumes (skills-grouped without dates) are penalized on Workday and Taleo because the parser cannot extract a clean employment history [5]. Each role: company name, role title, dates (Mon YYYY – Mon YYYY), location (city, state or "Remote"). Then 3–6 bullets per role, each starting with an action verb. Product Designers should have 4–6 bullets at the most recent role and 3–4 at older ones — reflecting that recent work matters more.

Stage 3 — Content and Bullet Craft (Items 11–16)

11. Each bullet pairs an action verb with a measured outcome.

The ATS itself doesn't grade outcome density, but the recruiter does — and Product Designer recruiters are explicitly trained to deprioritize craft-only bullets [6]. Action verbs Product Designers should rotate: "Designed," "Led," "Shipped," "Researched," "Prototyped," "Tested," "Architected," "Specced," "Audited," "Mentored," "Established." Pair with metric: not "Improved checkout," but "Lifted checkout-completion from 67% to 78% across a 1.2M-MAU consumer iOS app." If a bullet has no number, ask whether it deserves to be on the resume at all.

12. Embed Tier-1 keywords inside experience bullets, not just in Skills.

Greenhouse and Lever both weight keywords found inside experience bullets higher than the same keyword in a flat Skills list [3][7]. The Skills section gets your foot in the door; the bullets win the screen. For each experience bullet, ask: does this contain at least one Tier-1 Product Designer keyword (Figma, Design Systems, User Research, Prototyping, Usability Testing, Wireframing, UX Design, UI Design, Cross-Functional, Information Architecture)? If not, rewrite. Aim for 2–3 keywords naturally embedded in each bullet.

13. Show range — research, craft, and outcome bullets in the same role.

A Product Designer resume that's all-craft ("Designed checkout flow in Figma" repeated 6 times) reads as junior. A resume that's all-strategy ("Aligned stakeholders on roadmap") reads as PM-not-PD. The senior signal is range: per role, mix one research bullet (interviews, usability tests, diary studies), 2–3 craft bullets (Figma, prototypes, components), and 1–2 outcome bullets (activation, conversion, retention metrics). Hiring managers explicitly look for this range in 7-second skims [6].

14. Quantify portfolio scope — but skip the screenshots.

Don't include screenshots, mockups, or "selected work" thumbnails on the resume itself. Reference the portfolio link instead. Inside experience bullets, quantify scope in words: "Owned design for 3 product surfaces serving 1.2M MAU," "Designed 27 screens across the B2B onboarding flow," "Contributed 23 components to a public design system used by 4 engineering teams." This gives the recruiter the scale signal without breaking the ATS parser.

15. Include a tightly-scoped Projects section if you're early-career or pivoting.

For designers with under 4 years of professional experience, or for those pivoting from a different role (Product Manager → Product Designer, Marketer → Product Designer), a Projects section adds keyword density and demonstrates scope. List 2–3 projects, each with: project name, role (e.g., "Lead Designer"), 1–2 lines describing the work and outcome, plus the link if it's a public case study. Senior+ resumes generally cut the Projects section unless a specific project carries unusual signal (open-source design system contribution, named conference talk, public side-project with traction).

16. Education section: degree, school, year — and prune everything else.

For Product Designers more than 5 years out of school, the Education section should be 1–2 lines total. Degree, school, year. Optionally the design-relevant minor or program name. Cut: GPA (unless 3.8+ and you're under 3 years out), coursework, dean's list, undergrad activities. The most senior Product Designer hires often have non-design degrees (architecture, journalism, computer science, even literature) — own that, don't apologize for it. A clean one-line Education entry signals confidence; an over-padded one signals junior.

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

17. Mirror the JD's exact keyword phrasing — including capitalization.

If the JD says "Design Systems" (capital D, capital S), use that capitalization. If it says "design systems" (lowercase), use that. Workday and Taleo are case-sensitive in some configurations [5]. The fix: read the JD twice, list the 12–15 highest-frequency skill terms, and verify each appears in your resume in the canonical form. For abbreviations with a common expansion (WCAG, JTBD, IA, OKR), use both forms once each — covering exact-match parsers (Taleo) and semantic ones (Greenhouse, Lever, Ashby).

18. Don't list a tool you can't defend in an interview.

The ATS rewards keyword matches; the human interview punishes false claims. A Product Designer who lists Sketch, Adobe XD, Figma, Framer, Principle, ProtoPie, Origami, and Rive — but only actually uses Figma — fails the first technical question. Limit the tools list to what you've used professionally or in significant side projects within the last 3 years. If the JD mentions a tool you don't know, don't list it; reference an adjacent tool you do know in the same paragraph: "Prototyping in Framer (familiar with similar workflow in Principle and Origami)."

19. Avoid the "white-text keyword stuffing" hack.

Old advice told candidates to hide keywords in white text or 1px font at the bottom of the resume. Modern ATS spam detection at Greenhouse, Ashby, and increasingly Lever flags this — the parsed text reveals the keywords even though the rendered document hides them, and the discrepancy gets the resume auto-rejected [3][7]. Same for hidden text in document metadata, comments, or off-page text boxes. If you can't earn the keyword honestly through experience or skills, don't try to smuggle it in.

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

20. Run your resume through Jobscan or Resume Worded before submitting.

Both tools simulate ATS parsing and produce a match score against the specific JD you're applying to [4]. Jobscan's free tier gives 5 scans per month and shows the keyword match percentage, missing critical keywords, and parse-quality warnings (two-column detection, font issues, table parsing failures). For Product Designers, target a 75%+ match score — anything below 60% means you're missing critical keywords. Resume Worded is the alternative, with similar functionality. The 10 minutes of running this check is the highest-ROI step in the entire submission process.

21. Do a final manual parse-test by copying the resume into a plain-text editor.

Open your .docx in Word or Google Docs, select all, copy, and paste into TextEdit (Mac), Notepad (Windows), or a plain-text web editor. The result is approximately what the ATS sees after parsing. Verify: section order is right, bullets aren't scrambled, contact info is intact, no garbled characters. If anything looks wrong here, it'll look wrong in the ATS. Fix the source .docx until the plain-text version reads cleanly. This is a 90-second test that catches most parse failures.

Bonus — Portfolio Link Best Practices for Product Designers

The portfolio is the single most-clicked link on a Product Designer resume, but most candidates fumble it. Six rules:

1. Own a domain. "firstname.com" or "firstnamedesign.com" reads more senior than "behance.net/firstname" or "dribbble.com/firstname." Domain registration is $12/year; the signal is worth it.
2. Lead with case studies, not screenshots. A Product Designer portfolio that opens with a grid of 24 thumbnails is junior-coded. A portfolio that opens with 4 case-study cards (problem → process → outcome) reads senior. Pick 3–6 strong case studies, not 20 weak ones.
3. Each case study has an outcome. "Designed onboarding flow" is incomplete. "Designed onboarding flow that lifted Day-7 activation from 31% to 44%" is a case study. The outcome is the entire reason hiring managers click through.
4. Make case studies skim-able. Hiring managers spend 90 seconds on a portfolio in first pass. Each case study needs a TL;DR up top — context, role, outcome — before the deep-dive content.
5. Password-protect NDA work appropriately. If you must password-protect a case study, list the password on the case-study card itself ("Password: contact me") or include it in the resume cover note. A locked portfolio with no path to access kills the application.
6. Test on mobile. Recruiters often skim portfolios on phones during commutes. A portfolio that's beautiful on desktop but unreadable on mobile loses opportunities. Run through it on an actual phone before linking.

FAQ

Should I include a photo of myself on my Product Designer resume?

No, for US and Canadian applications. Headshots on resumes can trigger anti-bias filters at large employers and prompt the ATS or HR to deprioritize the application to avoid discrimination claims [2]. The exception: international markets where photos are standard (Germany, Japan, parts of Europe). For US/Canada, the LinkedIn profile is where your face goes; the resume stays text-only.

What if the job application asks for PDF but I want to submit .docx?

Submit PDF. Application instructions reflect either ATS configuration (the system was tuned for PDF) or recruiter preference (they want a fixed-format document). Ignoring the instruction is a downstream signal that you don't read carefully, which Product Designers especially can't afford. The fix is to make sure your PDF parses cleanly: export from Word as PDF (not from Figma or Sketch), keep it under 2 MB, and run it through Jobscan to verify ATS extracts the text correctly.

How do I handle employment gaps on a Product Designer resume?

Be honest and brief. A 6-month gap can sit between roles without explanation — most recruiters won't flag it. A 12+ month gap typically warrants one line of context: "Career break — caregiving, sabbatical, freelance design work, etc." For Product Designers, freelance work during a gap can be listed as a separate role: "Independent Product Designer — Jun 2024 – Mar 2025." List 2–3 client engagements with the same metric structure as full-time roles. The ATS doesn't care; the recruiter does, and clear framing wins.

Should the resume be one page or two pages for a Product Designer?

One page for designers with under 7 years of experience. Two pages for senior, staff, and principal designers with 7–15+ years where you genuinely have more shipped work, leadership, and systems impact to document. The trap: padding a 4-year resume to two pages with hobbies, irrelevant volunteering, and verbose education entries — that signals junior and gets penalized. The opposite trap: cramming a 12-year resume into one page by deleting outcomes — that signals you don't have measurable wins.

Do I need a cover letter for a Product Designer application?

Sometimes. Greenhouse and Lever both let recruiters mark cover letters as required, optional, or hidden. If the application form asks for one, write one — a 4-paragraph note specific to the company's product, why you want to work there, and the 1-2 specific case studies in your portfolio that align with the role. If the form doesn't ask for one, skip it — modern recruiters at most tech companies won't read it. The portfolio is doing the work the cover letter used to do.

Should I list my Design Thinking or design leadership certifications?

List Nielsen Norman Group UX Certifications (NN/g UX-PM, UX Master) — these have name recognition with hiring managers and recruiters. List IDEO U or Stanford d.school programs if completed. Skip Coursera, LinkedIn Learning, and Udemy certifications unless they directly relate to a specific tool the JD requires (e.g., a Figma Advanced certification when applying to Figma's product team). Filler certifications dilute the resume; targeted ones add signal.

What about listing a side project or personal design work?

List it if it has scope, audience, or unusual signal. A weekend Figma file titled "Dashboard concept" has no signal. An open-source design system you built that has 200+ stars on GitHub, a side product with 1,000 users, or a published design article on Smashing Magazine or A List Apart all have signal. The bar: would a hiring manager find this interesting enough to ask about in an interview? If yes, list it; if no, leave it off.

Is there an ATS-friendly template for Product Designers?

Yes — single-column, system-font, plain-text-first templates work across every major ATS. Resume Worded, Jobscan, and Reddit's r/UXDesign all maintain free ATS-friendly templates [4]. Avoid Canva, design-tool exports from Figma or Sketch, and any template that includes a sidebar, two-column layout, or graphic elements. The "ugly" plain template will outperform the beautiful Figma export every time. Your portfolio is where typography and craft show up; your resume is where keywords and structure show up.

How do I make the resume stand out if it has to look plain?

Through the writing. The boring-format constraint is universal; every Product Designer applicant faces it. The differentiation lives in the bullets — specific, measured, evidence of range across research, craft, and outcomes. A plain-format resume with 12 strong bullets (each with a metric, named tools, named scope) reads as senior. A beautifully-typeset resume with 12 generic bullets reads as junior. Spend the time on the writing, not on the layout.

What do I do if I keep getting rejected by the ATS?

Three diagnostic steps. First, run the resume through Jobscan against 3 different JDs and check the keyword match score — if it's under 65% across all three, you have a keyword problem (rewrite the Skills and Summary sections). Second, copy-paste the resume into TextEdit and check parse quality — if sections are scrambled or content is missing, you have a format problem (rebuild on a single-column ATS-friendly template). Third, ask 2–3 recruiters or designers in your network to review the resume — if they flag the same issues, fix those. If you've done all three and still get auto-rejected, the issue may be experience-fit rather than ATS-fit — apply to roles where your shipped work matches the JD seniority and product type.

References

[1] Jobscan. "Fortune 500 ATS Usage — 97.4% of Companies Use Applicant Tracking Systems." https://www.jobscan.co/blog/fortune-500-use-applicant-tracking-systems/

[2] Greenhouse Software. "Sourcing and Filtering Best Practices — Greenhouse Help Center." https://support.greenhouse.io/hc/en-us/articles/360051506331-Sourcing-best-practices

[3] Workday. "Workday Recruiting — Candidate Search Documentation." https://doc.workday.com/admin-guide/en-us/staffing/recruiting/candidate-experience.html

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

[5] Lever. "How Lever's Search and Filtering Work — Lever Help Center." https://help.lever.co/hc/en-us/articles/360050103552-Search-overview

[6] Ladders. "Ladders Eye-Tracking Study: How Recruiters Read Resumes." https://www.theladders.com/career-advice/you-only-get-6-seconds-of-fame-make-it-count

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

[8] Nielsen Norman Group. "User Research Methods — Cheat Sheet." https://www.nngroup.com/articles/which-ux-research-methods/