Staff Product Designer, Receipt & Rewards Experience

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. No Job ID. Remove boilerplate. Must preserve all substantive info. We need to parse the posting. Key sections: - "What we’re building and why we’re building it." This is introductory description. Could be placed under maybe "About the role"? Actually "About The Role" heading appears later. The intro before that is about company. Could be part of "About the role"? But the instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should have headings exactly those strings if content exists. We have content for: - About the role: The paragraph after "About The Role" heading: "Fetch is looking for a Staff Product Designer...". So we can put that under

About the role

. - Responsibilities: The "What You’ll Do At Fetch (Role Responsibilities)" section with bullet list. So

Responsibilities

with

• items. - Requirements: The "In Your Toolbox (Minimum Requirements)" section with bullet list. That's requirements. So

  Requirements

  . - Qualifications: There's also "Nice To Haves/Bonus Points (Preferred Requirements)" which could be Qualifications or Skills? The instruction includes Qualifications and Skills as possible headings. We have "Nice To Haves/Bonus Points (Preferred Requirements)" which are preferred qualifications. Could map to

  Qualifications

  or

  Skills

  . Since they are "Nice To Haves/Bonus Points", maybe treat as Qualifications. But we also have a separate "Skills"? Not explicit. We could put them under Qualifications. Or we could have both Qualifications and Skills sections if content fits. The "Nice To Haves" includes items like personalization, smart camera, AI-powered guidance, accessible experiences. Those are skills/experience. Could be Skills. But we already have Requirements (minimum). The Nice To Haves could be Qualifications (preferred). Let's decide: Use

  Qualifications

  for Nice To Haves. - Benefits: The section after compensation: "At Fetch, we'll give you the tools to feel healthy, happy and secure through:" then list equity, 401k match, benefits for humans and pets, continuing education, ERGs, PTO, holidays, week-long break, robust leave policies, Calvin Care Cash, flexible work environment. That's benefits. So

  Benefits

  with list. - Pay: The compensation line: "Compensation: At Fetch, we offer competitive compensation packages including base, equity, and benefits to the exceptional folks we hire. The base salary range for this position is [$173,742 - $204,402]." So we have pay info. So

  Pay

  with that sentence (maybe just the range). Should we include the preceding sentence? It's part of compensation. We'll include the full sentence. - Schedule: Not mentioned. No schedule info. So we omit Schedule section. - Also there is a "What Success Looks Like In your first 12 months," which could be considered part of Responsibilities or maybe a separate section like "Success Metrics"? Not in allowed headings. Could be included under Responsibilities or maybe under About the role? But we must not invent headings. We could incorporate that content into Responsibilities or maybe under a separate

  Responsibilities

  as additional bullet points? The instruction: Use
  • for any list of duties/requirements/benefits. The success looks like is a list of outcomes; could be considered responsibilities or expectations. We could add them under Responsibilities as additional items. However we must preserve all substantive info; we can add them as part of Responsibilities list. Also there is a paragraph "What we’re building and why we’re building it." That's introductory company description. Where to place? Could be part of About the role? Actually About the role already includes description of role. The intro is about company mission. Could be placed under a heading like "About the role"? But that heading is specifically about the role. However we could add a preceding

    before the headings (intro). The instruction: Use

    for prose. So we can have an opening

    with that intro text. Then headings. We must not include boilerplate like EEO, equal opportunity, etc. At the end there is EEO statement; we must remove that. Also remove application instructions, cookie/navigation/legal etc. The posting ends with EEO statement and accommodation contact; we must drop that. Also remove duplicated lines. Now craft HTML. Structure:

    Intro paragraph: "What we’re building and why we’re building it. Fetch helps people live rewarded every day, with a vision to become the rewards destination for everyone. We turn everyday activities into meaningful rewards, whether it’s grocery shopping, grabbing a quick meal, or playing a favorite mobile game. To date, we’ve awarded more than $1 billion in Fetch Points to our users. Each day, more than 13 million receipts are submitted on Fetch, providing visibility into over $212 billion in gross merchandise value. This creates the largest retail-agnostic, SKU-level view of household spending, powering Fetch as an outcomes-based advertising platform that helps brands acquire and retain lifelong consumers. The Fetch app is available on the App Store and Google Play, with more than 6 million five-star reviews from a highly engaged and loyal user base. It’s not just our users who believe in Fetch: with investments from Softbank, ICONIQ, DST, Greycroft, and partnerships ranging from challenger brands to Fortune 500 companies, Fetch is reshaping how brands and consumers connect in the marketplace. When you work at Fetch, you play a vital role in a platform that drives brand loyalty and creates lifelong consumers with the power of Fetch points. User and partner success are at the heart of everything we do, and we extend that same commitment to our employees. At Fetch, we value curiosity, adaptability, and the confidence to explore new tools, especially AI, to drive smarter, faster work. You don’t need to be an expert, but you should be ready to learn quickly and think critically. We welcome learners who move fast, challenge the status quo, and shape what’s next, with us. Ranked as one of America’s Best Startup Employers by Forbes for two years in a row, Fetch fosters a people-first culture rooted in trust, accountability, and innovation. We encourage our employees to challenge ideas, think bigger, and always bring the fun to Fetch." Then

    About the role

    with paragraph: "Fetch is looking for a Staff Product Designer to lead experience design for our Receipt & Rewards experience, the foundation that helps us understand everyday purchases and reward users accurately. As part of the Receipt Intelligence design team, you’ll shape how users submit and connect purchases, understand what happened, resolve problems, and ultimately receive value for their activity. This is a complex design space spanning consumer experience, machine learning, data quality, processing, and platform integrity. Your challenge is to make that complexity feel simple, useful, and trustworthy for users, while helping Fetch turn receipt evidence into reliable purchase intelligence. This is a senior individual-contributor role with influence beyond individual features. You’ll define problems, lead complex initiatives, and connect decisions across the receipt journey and broader Fetch experience. You’ll partner closely with Product, Engineering, User Research, and Data Science to balance user needs, business outcomes, data quality, and technical constraints." Then

    Responsibilities

    with
    list items from "What You’ll Do At Fetch (Role Responsibilities)" plus the success looks like items. Let's extract responsibilities list: - Lead complex, high-ambiguity initiatives across Receipt Intelligence, connecting receipt capture, digital account linking, recognition, matching, and rewarding into a clear and cohesive user experience. - Own experience quality and outcomes across the journey. Identify gaps between a user’s action, how Fetch interprets it, the value they receive, and what they should do next. - Define design direction by framing problems, identifying opportunities, defining hypotheses and success measures, and shaping solution strategy with Product and Engineering. - Design beyond individual features. Ensure receipt & reward experiences connect coherently to the broader Fetch ecosystem. - Design the relationship between users and intelligent systems. Create clear signals, feedback, guidance, and recovery experiences that help people understand what the system is doing and build confidence in the outcome. - Navigate complex trade-offs between user simplicity, accessibility, data quality, business outcomes, and technical constraints, using research, data, experimentation, and structured thinking to drive decisions. - Raise the quality and coherence of the experience by evolving interaction patterns, systems, and frameworks that make Fetch easier to understand and use. - Drive alignment across teams and disciplines, proactively identifying dependencies and resolving ambiguity across Product, Engineering, Research, Data Science, and adjacent teams. - Elevate the design team through critique, mentorship, feedback, and stronger ways of working. Success looks like items (first 12 months): - Build a deep understanding of the receipt & rewards ecosystem, user lifecycle journey, user needs, business goals, and the technical systems behind receipt collection and rewarding. - Establish strong partnerships with Product, Engineering, Research, Data Science, and the teams responsible for receipt quality, models, platform infrastructure, and integrity. - Identify and shape opportunities that reduce friction, prevent errors, improve understanding, and strengthen user trust across physical and digital receipt experiences. - Launch meaningful improvements to the receipt journey informed by research, data, experimentation, and system performance. - Improve how Receipt Intelligence connects to progress, rewarding, and the broader user lifecycle rather than optimizing individual interactions in isolation. - Raise the quality of design thinking and decision-making through critique, mentorship, and cross-functional collaboration. - Influence decisions beyond your immediate team by bringing clarity to ambiguous problems and connecting user needs to technical and business outcomes. We can combine them all under Responsibilities as list items. Now Requirements (minimum): List: - 8+ years of product design experience. - Proven product leadership at Staff-level scope. A track record of leading complex, ambiguous, multi-quarter initiatives from problem definition through launch, learning, and iteration, with meaningful customer and business impact. - Exceptional product design craft. A high bar for interaction and visual design, usability, accessibility, and production quality, with the ability to make technically complex systems feel simple, intuitive, and trustworthy. - Strong systems thinking. You see beyond individual features, connect user behavior, product experiences, data, technology, and business needs, and identify where in the system a problem should actually be solved. - Strong judgment with AI and intelligent systems. You have experience designing ML or AI-powered consumer experiences and know when intelligence improves an experience, when it doesn’t, and where human control, transparency, or simpler approaches should take precedence. - Evidence-led product thinking. You partner deeply with User Research and use research, behavioral data, prototyping, and experimentation to turn ambiguous problems into hypotheses, learn quickly, and iterate toward better outcomes. - Influence without authority. You bring clarity to ambiguity, build trust across disciplines, navigate disagreement, and influence product direction, priorities, and trade-offs through strong reasoning and relationships. - A multiplier for the team. You raise the quality of both the work and the people around you through critique, mentorship, frameworks, standards, and better ways of working. Now Qualifications (Nice To Haves/Bonus Points): List: - Personalization and adaptive experiences, including implicit and explicit signals. - Smart camera or computer-vision experiences, including guidance, feedback, error prevention, and recovery. - AI-powered guidance and support that helps people understand, decide, act, or resolve issues. - Accessible consumer experiences operating at a meaningful scale. Now Benefits: List from "At Fetch, we'll give you the tools to feel healthy