“understanding”
Appeared in 36% of designer job listings the week of 2026-11-02 (31 of 86 postings).
First tracked 2026-04-13 · 21 weeks of collected data · peak prevalence 51% · no data collected Jul 27 – Sep 27
“understanding” prevalence in designer JDs, by week
2026-04-13 → 2026-11-02% of each week's designer postings that mention this term · 21 collected weeks · peak 51% · 26 earlier weeks from before collection began not shown · hatched rows: no data collected, not 0%
Where the conversation happens
View as table
| Role | Total mentions |
|---|---|
| Senior Product Designer | 990 |
| Design Engineer | 363 |
| Product Designer | 347 |
| Staff Product Designer | 322 |
| UX Designer | 245 |
| Design Lead | 125 |
| UX Researcher | 104 |
| Principal Product Designer | 85 |
| AI Product Designer | 75 |
| Content Designer | 74 |
| Design Systems Engineer | 52 |
| UX Writer | 43 |
| Growth Designer | 27 |
| Junior Product Designer | 23 |
| Product Design Manager | 23 |
| Associate Product Designer | 15 |
| Brand Designer | 13 |
| Design Director | 12 |
| Head of Design | 11 |
| Design Generalist | 2 |
Roles where “understanding” appears most
Ranked by share of the role's active listings that include this term. Roles with fewer than 20 active listings are left out.
- UX Researcher79% · 165 of 208 listings · 185 mentions
- Junior Product Designer64% · 29 of 45 listings · 48 mentions
- Product Design Manager57% · 25 of 44 listings · 34 mentions
- Design Systems Engineer55% · 51 of 92 listings · 59 mentions
- Design Director53% · 30 of 57 listings · 41 mentions
- AI Product Designer51% · 63 of 123 listings · 77 mentions
- Content Designer50% · 54 of 107 listings · 81 mentions
- UX Designer50% · 179 of 356 listings · 271 mentions
- UX Writer48% · 31 of 65 listings · 44 mentions
- Design Lead43% · 110 of 256 listings · 133 mentions
About this tracker
Every active designer listing in our corpus is tokenized: HTML stripped, stopwords (common English words + job-posting boilerplate) removed, pure numbers dropped. The remaining tokens are bucketed into Monday-anchored weeks based on when each listing was first seen. Counts are weekly totals across every listing for that week. A week only counts as collected if our LinkedIn scrape (about 80% of volume) ran that week; weeks when it didn't are shown hatched as gaps, never as zeros.