A ready-made prompt that sweeps every product design title variant on Indeed at once — UX designer, UI/UX designer, product designer, user experience designer — then reports whether each role is UX, UI, or research, and which case study your portfolio is actually being read for.
Indeed ranks by relevance to the query you typed, not by which part of the design process the role owns or which case studies the hiring team will open.
A UX designer runs discovery, interviews, and usability testing and hands off flows. A UI designer executes the visual system against an existing pattern library. A UX researcher runs studies and produces findings for someone else to design from. All three post as "product designer" or "UI/UX designer," and the process expectations are completely different.
A posting that says "strong portfolio required" will get roughly a minute, and the first screen of the work decides it. Postings that name what they want to see — an onboarding flow, a design system, a mobile checkout — are telling you which of your cases to lead with, and almost nobody adjusts their portfolio order per application.
Building a token library, documenting components, and maintaining consistency in an existing system is a distinct skill set from taking a blank page to a validated flow. Both are "product designer," the interviews probe completely differently, and which one you are being considered for is in the requirements rather than the title.
Copy it once, paste it into Zaira, and it runs the entire product design search: it fans out across every design title variant, splits UX from UI and research, matches the portfolio angle each posting asks for, then delivers only the roles worth your time.
Three stages, one goal. Zaira runs the product design search on a schedule, so the only thing left for you is to read the matches it surfaces and apply to the good ones.
The agent reports the case study types a role names and matches them to the ones you say you want to lead with. That is the difference between a portfolio that gets read and one that gets glanced at, and it costs nothing to reorder before you apply.
Remote product design work is frequently posted as "design systems designer," "service designer," or "journey mapper," not as UX designer. Adding those variants is how the agent surfaces greenfield and systems seats that a single-title search leaves out entirely.
UX researcher and UX writer titles stay in the search plan and get classified, because both sit right next to the role you want and both use the same vocabulary. Knowing a seat is research-only rather than design saves an application that was never going to happen.
The practical questions people ask before setting this up.
Anyone hunting for remote product design roles on Indeed who is not finding them with the search tools Indeed already gives them. That usually means you are searching for "UX designer" and getting research-only or marketing page roles, you know which kind of case study you want to be hired on and want roles that match it, or you suspect good systems work is filed under design systems titles. It is not built for graphic design, front-end engineering, or content writing roles.
In practice the two are the same job under different company vocabularies. Some companies use "product designer" to mean the whole design lifecycle — research, flows, and shipped UI — while others use it to mean high-fidelity execution inside an existing system, and use "UX designer" for the discovery-heavy seat. The agent reports the deliverables and the process each posting describes rather than treating either title as authoritative.
You can search Indeed yourself — the difference is breadth and repetition. A good product design search is twenty to thirty distinct queries across UX, UI/UX, product designer, design systems, service design, and sector-specific variants, with no filters on the first pass. Doing that by hand takes an evening and you will not do it again tomorrow. An agent runs the whole set at once, and the schedule in the prompt means it runs again for you every morning and reports only what is new.
Zaira reads Indeed through Indeed's own official MCP server — the permissioned connection Indeed offers to approved AI partners, not a scraper. There is no shadow account and no spoofed browser; the search happens inside the access your Indeed account already has, and you can revoke it from your Indeed settings at any time.
Yes — that is the intended setup. Describe the search once, set the schedule, and each run delivers only the new product design matches with ones you have already seen filtered out. You can point results at Slack, a Google Sheet, or email.
No. Zaira charges per plan rather than per task, so fanning out across every product design title variant does not show up as a separate bill. Set the prompt to a schedule rather than triggering it by hand — that way the wide sweep costs you the same each morning no matter how many queries it runs.
Yes. Sector is a first-class search parameter here, and in design it shapes the work more than in most fields. B2B SaaS onboarding, consumer fintech compliance, and healthcare patient flows are different design problems with different constraints and different research methods. The agent checks each posting's sector against the one you listed and discards the rest.
Yes. Step 2 checks whether the posting describes working inside an existing component library and token set, or taking a flow from nothing, and reports it as a column. The two are hired and interviewed for differently, and plenty of designers deliberately want one over the other, so it reports the split and ranks your stated preference first.