I Read 58 Live Product Designer Job Postings So You Don't Have To
When I was recruiting, I wrote product designer job descriptions for a living. I knew exactly how much of a req was real and how much was a wish list a hiring manager copy-pasted from a competitor’s posting the night before it went live. Now I’m on the other side of that document, reading them as a designer trying to figure out what a job actually is before I apply to it.
So I pulled 58 live Product Designer postings, open on Greenhouse, Lever, and Ashby this month, and read every line of every one. Not a survey, not a LinkedIn poll about what people think companies want. The actual postings companies are running right now, for roles from a first design hire at a seed-stage startup to a Principal seat at a public company.
I read each one top to bottom, not just the bolded “Requirements” section. The mission paragraph nobody skips reading twice. The buried “other requirements” line near the bottom. The compensation range that some states force a company to publish and others let it skip entirely. For every posting I logged the years-of-experience floor, the salary range, the work arrangement, every named tool, and every requirement that had nothing to do with design at all.
In this post
What 58 real Product Designer postings actually ask for: the years-of-experience floor and what companies actually pay, where you’re expected to sit and what’s in your toolbox, the requirements, hidden and stated, that decide whether you’re a fit, and how to turn all of it into a resume that matches what’s actually being asked.
What it takes, and what it pays
Nobody in this sample is hiring an entry-level Product Designer. 53 of 58 postings with readable content stated an explicit years-of-experience minimum. Not one of them asked for fewer than 2 years.
Stated years-of-experience minimum, by bucket (n=53)
| 5–8 years | 30 |
|---|---|
| 2–5 years | 12 |
| 8+ years | 11 |
The most common single phrase was “5+ years,” used in 13 postings, followed by “6+ years” (8) and “3+ years” (7). Five postings gave no number at all and described level only in words. Zero postings asked for under 2 years.
The floor moves in a fairly clean line as the title gets heavier, except for one title that doesn’t behave like a level at all.
Roughly +1 to +3 years per rung, Product Designer through Principal. “Founding Product Designer” postings are excluded here because they don’t follow this ladder at all — see below.
Two “Founding Product Designer” postings. One wants 2+ years. The other wants 12+. Same title, same word “founding,” completely different job.
“Founding Product Designer” is the one title in the sample that isn’t a seniority signal at all. One seed-stage startup is hiring its first-ever design hire and asking for 2+ years, because at that stage “founding” means you’re the whole design department starting tomorrow. Another, a 22,000-person company standing up a new financial-services vertical, is hiring a Founding Product Designer and asking for 12+ years plus 5 in design leadership, because at that scale “founding” means you’re standing up a new pillar inside a machine that already exists. Read “founding” as a stage descriptor, not a level, or you’ll misjudge half the postings that use it.
The pay data has its own version of that same trap: some of it disclosed, some of it deliberately vague, and the label at the top of a posting tells you less than the actual number does. 76% of the postings I read, 44 of 58, disclosed a real compensation figure. The other 24% said nothing more specific than “competitive salary and equity,” and that gap is almost entirely explained by geography: companies hiring across Colorado, New York, California, and Washington are legally required to publish a number, so the multi-state remote postings publish one and the single-city postings often don’t bother.
76% of the 58 readable postings (44) disclosed a figure of some kind; 24% (14) disclosed nothing beyond “competitive.”
One posting handed me something more useful than any single range: a full transparent ladder across every level. One govtech consultancy publishes this exact table in the job posting itself.
| Level | Range |
|---|---|
| Associate Product Designer | $90,000–$125,000 |
| Product Designer I | $120,000–$140,000 |
| Product Designer II | $135,000–$160,000 |
| Senior Product Designer | $150,000–$185,000 |
| Staff Product Designer | $170,000–$203,000 |
| Principal Product Designer | $180,000–$230,000 |
That’s what a real, internally-consistent leveling structure looks like next to the median I pulled across 41 different companies’ guesses at the same rungs. If you’re trying to figure out whether an offer is low, this table is a better yardstick than any “average product designer salary” number you’ll find in a generic survey.
Same title, wildly different number, isn’t only a level problem. It’s a geography problem too. One UK-based fintech posted a Senior Product Designer role based in Lithuania at €45,600–€71,000, roughly $49,000–$77,000 at the time I pulled it. The US-based Senior Product Designer postings in this same sample had a median floor around $150,000.
Same title. Same seniority word. A gap of roughly $100,000 at the floor, before you’ve even compared the ceilings.
Where you work, and what you work in
69% of this sample is remote, but “remote” turned out to be the least trustworthy label in the entire set.
Work arrangement (n=58)
| Remote | 40 |
|---|---|
| Hybrid | 14 |
| On-site only | 4 |
69% remote, 24% hybrid, 7% on-site. But “remote” and “hybrid” both cover more ground than the label suggests, below.
The four on-site-only companies are the ones you’d guess: an early-stage startup making its first design hire, a defense-adjacent maritime-tech company, a famously intense sleep-tech startup, and one company that states outright that employees are expected to work from the office five days a week, the most rigid policy in the set.
If you’re hunting for remote product designer jobs specifically, know that “remote” is doing a lot of unexamined work in the other 40 postings. One “remote” Senior Product Designer role only requires being in an office once or twice every six months, the loosest definition here by a wide margin. On the opposite end, two other postings name the exact states you have to live in to qualify for remote work, one listing 23 states and the other 22 states plus Washington, D.C., and another restricts its remote role to the Eastern time zone, not just “US-based.” Hybrid schedules ranged from 2 days a week in office to 3, with one posting going as far as naming the exact days: Tuesday through Thursday in office, Monday and Friday remote.
If you’re only reading the “Remote” or “Hybrid” label at the top of a posting, you’re reading a summary someone else wrote. Read the actual sentence about where you’re expected to be.
The same don’t-trust-the-label rule applies to what’s in the toolbox, not just where you sit. A posting that names Figma might really mean pixel-pushing. A posting that names no tool at all might still expect you to prototype in code.
Tools & skills, by mentions across 58 readable postings
| Design systems | 44 |
|---|---|
| Prototyping (any form) | 43 |
| Figma (named explicitly) | 29 |
| User research (named) | 20 |
| Accessibility | 19 |
| Usability testing | 13 |
| Claude / Claude Code | 7 |
| Cursor | 6 |
| Sketch | 2 |
”Design systems” and “prototyping” are near-universal, whether owning one from scratch or extending an existing one. Figma’s count is a floor, not a ceiling: several more postings say “modern design tools” without naming a specific one. Sketch appears in just 2 of 58, a tool that used to be the default now reads as a legacy signal.
The AI split is the real story in this section. 67% of postings mention AI tools as part of the actual design workflow, prototyping, research synthesis, ideation. But only some of those make it a requirement rather than a mention.
| Mention AI tools at all | 67% |
|---|---|
| Require AI fluency outright | 38% |
Two-thirds of postings expect a designer to use AI as part of the craft. More than a third treat it as a hard bar, not a bonus.
AI tools named by brand (n=58)
| Claude / Claude Code | 7 |
|---|---|
| Cursor | 6 |
| Figma Make | 4 |
Replit, v0, ChatGPT, and Gemini each show up once, all inside one AI-focused posting’s single tool-stack bullet. Bolt and Codex each show up once too, in two unrelated postings elsewhere in the sample. Claude, Claude Code, and Cursor are the only tools more than one company named independently.
One AI-focused posting names seven different tools in a single bullet: Figma Make, Cursor, Claude Code, Replit, v0, ChatGPT, and Gemini, the densest tool name-drop in the sample. Another posting put it more bluntly than any in the set: candidates need “working fluency with AI tools in your design process, demonstrated by how you actually use them today,” and adds, in case that wasn’t clear enough, “be ready to show this, not just name tools.” A line about AI on your resume isn’t what’s being screened for. Being able to open your own file and walk through how you actually used it is.
What the job actually asks of you
Design systems and a product designer portfolio are the two things every hiring manager wants proof of. Almost everything past that is negotiable, or unevenly enforced. Ranking every product designer job requirement by how often it showed up across the 58 readable postings:
Requirement frequency, ranked (n=58)
| Design systems (contribute to, extend, or build from scratch) | 76% |
|---|---|
| A portfolio required | 76% |
| “End-to-end” ownership language, discovery through shipped | 67% |
| AI tools mentioned somewhere in the workflow | 67% |
| Comfort with ambiguity, named explicitly | 55% |
| Cross-functional collaboration with PM and Engineering, the exact phrase | 53% |
| Mentoring or “raising the bar” for other designers | 33% |
| Accessibility, named as a design responsibility | 33% |
| Explicit “0-to-1” phrasing | 19% |
Mentoring is almost entirely concentrated in Senior-and-above titles. Several postings that skip the phrase “0-to-1” describe the same expectation with “ambiguity” instead.
Mentoring shows up almost exclusively once you cross into Senior, which is the cleanest evidence in the whole sample that “senior” in this market means “raises everyone else’s floor,” not just “does the same work faster.”
Ranking by frequency tells you what’s common. It doesn’t tell you what’s easy to miss, and this is where reading job postings line by line actually pays off, because these details never make it into the title or the first paragraph.
Visa sponsorship is ruled out in 7 of the 58 postings. If you need sponsorship, that’s a filter worth applying before you spend an evening on a cover letter.
Some restrictions have nothing to do with design at all. One defense-adjacent maritime-tech company requires “U.S. Person” export-control status and the ability to lift 20 pounds, an unusual physical-demands clause for a Product Designer role. One UK fintech makes offers conditional on a criminal record and an adverse credit history check, because it’s a regulated financial business. Two other postings require professional English fluency, one listing Portuguese and Spanish as a plus, the other also requiring you already be based in the US, no relocation.
One posting states outright that employees report working up to 60 hours a week and invokes “Kobe Bryant’s mamba mentality.” Most companies bury culture like that. This one put it in writing.
A few postings will auto-reject you for a mistake you wouldn’t think to avoid. One rejects any candidate who applies to more than one open role there, so apply only to the single posting you’re most qualified for. Another requires you to disclose any AI-generated text in your own application by prefixing it with “Generated with AI assistance,” the inverse of the usual story about companies using AI to screen candidates. A third discloses that it uses an automated tool called Metaview to screen NYC-based applicants, required under NYC’s Local Law 144, complete with a public link to the independent audit. If you’ve read what it’s like to be interviewed by an AI, this is the hiring-side mirror of that: the tool doing the first pass on your resume, disclosed in the fine print.
A handful of smaller, human details rounded out the list: one posting offers token rights as part of comp, not just salary and equity. Another pays a $100-a-month “dogfooding stipend” just to get designers using their own product. One fitness app is looking for “a 10x Designer,” the only posting in the sample to use that phrase without irony. And three postings set a coding bar unusual for a design title: HTML/CSS/JS or a CS-adjacent background at minimum, real production PRs expected at one, and deep React/TypeScript/WebGL fluency expected at a Staff Design Engineer posting where the role reads closer to “engineer who designs” than “designer who codes.”
Strip the flowery mission statements out of the “What You’ll Do” sections and the job comes down to a short list of categories. Partnering with PM and Engineering showed up in some form in nearly every posting, too universal to rank. Here’s how the rest breaks down:
What the job actually is, day to day (n=58)
| Design system contribution or ownership | 76% |
|---|---|
| Prototyping | 74% |
| End-to-end ownership, discovery through shipped | 70–75% |
| Running your own research | 55–60% |
| Mentoring other designers | 33% |
| Designing AI-powered product features | 25% |
Design systems scales from “use and extend” at junior levels to “own the visual and interaction language” at Staff and Principal. Prototyping is increasingly indistinguishable from “prototype in code with an AI coding tool.” Mentoring concentrates almost entirely in Senior and above. The bottom row, roughly 15 postings spanning health, fintech, infrastructure, and productivity products, is a different skill than using AI as a tool, below.
That last row is worth pulling apart, because postings conflate two different things under the word “AI.” One is a designer using AI tools to work faster: Cursor for prototyping, Claude for research synthesis. The other is a designer designing AI-powered features for end users: confidence signals for an agent’s output, citations in a chat response, the interface for a human reviewing an AI-generated draft. About a quarter of this sample wants the second thing, a genuinely different skill from being fast with a coding assistant, and worth naming clearly on your resume if it’s actually what you’ve done.
One more thing worth naming before any of this turns into advice: who this sample actually represents. This sample skews senior, hard. 64% of the 58 postings, 37 of them, are Senior, Staff, Principal, or a title that spans both. Only 14, 24%, are a plain, unmodified “Product Designer.” Zero postings in the entire set are explicitly entry-level.
I already wrote about what’s actually happening to entry-level design jobs using labor-market data from the Fed, Stanford, and the BLS. This sample is the same story from a different angle. I went looking for open product design jobs on live job boards, and the market simply isn’t posting the entry-level version of this role right now. This is the finding, not a gap in how I collected the data. If you’re early in your career, the median $150,000-$192,000 and the “5+ years” floor above aren’t your market. They’re the market for the designer three rungs ahead of you, and the honest read is that the rung you’re standing on has fewer open doors than it used to.
Zero of 58 postings were explicitly entry-level. I looked. The market simply isn’t posting it.
Turning this into your product designer resume
I used to read resumes against reqs exactly like the 58 above. The ones that moved forward mirrored the language of the posting. The ones that got skimmed and set aside didn’t.
Match your resume to the frequency data, not to what feels impressive to write. Design systems and a portfolio link show up in 76% of postings each, more than anything else in this sample. They don’t belong three bullets down under a generic “Skills” header. They’re what the first line under your most recent role should already be proving.
- Design systems, in 76% of postings. “Contributed to the design system” tells a recruiter nothing. “Extended a 240-component design system across 12 product surfaces” tells them the scope. Every design-system bullet needs a number in it.
- A portfolio link, required in 76%. Put it at the top of the resume, not buried in a header nobody clicks. Make sure what’s behind it matches what these postings actually screen for: process and outcome, not just polished screens.
- End-to-end ownership, in 67%. This is the single most overused phrase on a product designer resume, so back it up. Name where you started, a support ticket, a stakeholder ask, a blank doc, and name where you ended: a shipped feature, a metric that moved.
- AI fluency, mentioned in 67%, required outright in 38%. Don’t just list “Figma, Cursor, Claude” and move on. One posting in this sample states outright that you need to be ready to demonstrate how you used the tool, not just name it. Put an actual AI-assisted workflow in a bullet: what you prototyped, what got faster, by how much.
- Cross-functional collaboration with PM and Engineering, the exact phrase in 53%. Name the partner function and the artifact you shipped together, not just “collaborated cross-functionally.”
- Mentoring, in 33%, almost entirely concentrated at Senior and above. If the title you’re applying to says Senior, Staff, or Principal, mentoring needs its own line. Leaving it out reads like a level you haven’t reached yet.
None of this works as one static resume you send to every posting. The same way “remote” meant six different things across the 40 postings in this sample, “portfolio required” and “AI fluency” mean different things at a two-person seed-stage team than at a 22,000-person company standing up a new vertical. Read the actual posting the way you’d want a recruiter to read your resume, then tailor the resume to the job description in front of you, every time, not the version you already had saved.
Reflective Coda
I used to write these documents. The real surprise is how much of what actually matters sits outside the bullet points: the year gap hiding inside “founding,” the state list hiding inside “remote,” the auto-reject hiding inside “apply here.” A job posting is a document written by a hiring manager, edited by a recruiter, and legally reviewed by someone in HR, and every one of those hands leaves something in the text that the title alone won’t tell you.
If you’re applying right now, read past the first paragraph. The requirements that actually decide whether you’re a fit are usually three sections down, in a sentence nobody wrote to be memorable. And if the numbers above feel discouraging, the tactics for getting through a market like this one haven’t changed just because the reqs got pickier.
Sources
- Affirm
- Afresh
- Alt
- Applied Intuition
- Arkestro
- Assemble
- BJAK
- Checkr (Senior Product Designer, Mortgage)
- Checkr (Staff Product Designer, Growth)
- ClickUp
- Clera
- CodePath
- Constant Contact
- Courtyard
- Current
- Discord
- Eight Sleep
- Ethos
- Extend
- Fanatics
- Follett Software
- GC AI
- GoFundMe
- Grüns
- Gusto
- Headspace
- Hightouch
- Hone Health
- Instacart
- Jeeves
- Kettle
- Kong
- Ladder
- Lattice
- Mercury
- Mindgrub
- Miro
- Moneybox
- Nex
- NinjaTrader
- Nova Credit
- Omada Health
- Ondo Finance
- Owner.com
- Planera
- Render
- Saronic
- SimplePractice
- Skylight
- Spotify
- Super.com
- Tatari
- Tide
- UpDoc
- Upstart
- Via
- WeightWatchers
