[Hiring] Staff Product Designer, Guest & Discovery @Getmyboat & Boatsetter

Role Description

The end-to-end guest discovery experience — search, filtering and refinement, results, map and list, the listing page, and the paths in from organic search and AI assistants. Coherence across both brands and web plus mobile is yours.

• The information hierarchy of the results card, defended with evidence, across guest intents and every state the data actually produces: missing photos, no reviews yet, a price range instead of a price, partial availability.
• Interfaces over a system that infers. Make what it inferred legible, make correcting it easy, and reduce verification labor rather than creating it.
• Surfaces we don't render. With engineering, shape the structured expression of an experience, an offer, and an operator so it survives being summarized, quoted, or laid out by someone else's assistant.
• Continuous discovery with your pod — a Product Manager and an engineering tech lead. Choose the cheapest artifact that answers the open question; spend fidelity when a decision is actually being committed.

How we work

• Problem, then system, then experience: We frame the problem, then settle the shape of the system — entities, states, edge cases — and only then design the experience within it.
• Discovery is ongoing, not a handed off spec: You talk to guests and operators directly. You bring opportunities forward rather than receiving them.
• We ask what moved, not what shipped: You define the signal before release and watch it after. Hitting the number you set is the floor, not the finish.
• We ship in days, not quarters: Work goes live the day it's ready — no launch calendar, no approval chain.
• We cross lines, and we bet on each other: Titles and team boundaries carry little weight here. You'll be inside the domain model with an engineer.
• We work inside the design system by default; a new pattern has to earn itself against what already exists.

Qualifications

• Held substantial ownership of search, browse, or discovery in a two-sided marketplace — relevance surfaces, faceted filtering, availability and pricing display, map plus list, comparison.
• Designed information you can defend.
• Walked through a dense comparison surface you built: why each element is there, why it's ordered that way, what you removed, and what removing it cost.
• Designed over a system that infers, ranks, or predicts — communicating state and confidence in real time, and designing the correction path for when the system is wrong.
• Formed a point of view on search in an AI-driven world, including where conversation doesn't belong.

What also helps

• Fluency with entities, states, and contracts alongside your tech lead.
• Restraint and typographic craft in high-information surfaces.
• AI tools in your own practice.
• Search relevance literacy, structured data and schema work, third-party assistant surfaces, or travel, hospitality, and local-services search at scale are each a plus rather than a requirement.

Your portfolio

• Send work, not a slide deck about process. Two or three cases at depth.
• For at least one: the problem and how you knew it was real, what you tried and abandoned, the hierarchy decisions and their rationale, the states you designed for, what shipped, and what it changed.
• Include something that didn't work. Roughness is fine — we care about the reasoning.

Practicals

• Remote, with high overlap in United States Eastern hours.
• You'll join a five-person design team, report to our Director of Design, and be the dedicated designer in this pod.
• Relevant degrees in design, HCI, or information architecture are welcome and not required — portfolio and shipped, measured work outweigh credentials.