Senior Product Designer

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 need to parse the posting. Content: - Location(s): US (remote), Boston (hybrid), or New York (hybrid) – location info. Not a heading; we can put in a

. - About This Role: paragraph describing role. That's "About the role" heading. - A Day In The Life (Responsibilities): list of responsibilities bullet points. So heading "Responsibilities" with

• . - What You'll Need To Thrive (Requirements): list of requirements. Heading "Requirements". - How You Use AI: description about AI usage. Could be a section maybe "How You Use AI" but not in allowed headings list; allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could map "How You Use AI" maybe under Skills? Or maybe we can create a section "Skills"? The posting includes "Fluency with AI prototyping tools and Figma, with a strong handle on accessibility" etc. Also "Nice to haves". Could be part of Requirements or Skills. Since we have Skills heading allowed, we could put skill-related content there. But we need to preserve all substantive info; we can't omit. We could include a section "Skills" for the skill details (AI prototyping tools, Figma, accessibility, UX fundamentals, etc.) and maybe "Nice to haves". Also "How You Use AI" could be part of Skills or separate but not allowed heading. We could embed within Skills. - "AI at Toast": description about AI usage at company; could be part of About the role or maybe not needed as separate heading. It's substantive but could be placed under About the role? Might be okay to include as a paragraph under About the role. - "Our Total Rewards Philosophy": includes benefits description, base salary range, zones, etc. This includes Pay and Benefits info. So we need Pay and Benefits sections if they have specific content. The posting includes base salary ranges for zones A, B, C. That's pay info. Also mentions total rewards components: cash compensation, equity, benefits. Also link to benefits. So we should create Pay section with salary ranges. Benefits section with description of benefits philosophy and link. - "How Toast Uses AI In Its Hiring Process": could be omitted? It's about hiring process; maybe not needed but it's substantive. Could be placed under About the role? Might be okay to include as a paragraph under About the role or maybe a separate section not in allowed headings; but we should avoid creating extra headings not in list. Could embed within About the role. - "Our Approach to Hybrid Working": could be part of About the role or maybe Schedule? Actually schedule/hybrid working info. Could be placed under Schedule heading if we have schedule info. The posting mentions hybrid work model, location expectations. So we can create Schedule section with that info. - "People Are the Secret Ingredient...": culture description; could be part of About the role. - "Apply today!" and EEO etc: boilerplate to remove. Thus we need to output HTML with sections: About the role, Responsibilities, Requirements, Skills (maybe), Pay, Benefits, Schedule. Also maybe Qualifications? The posting has Requirements; Qualifications maybe same as Requirements; we can skip Qualifications if not distinct. We'll include Requirements. We need to use

  for each section heading. Use

  • for lists. Use

    for prose. We must not repeat job title as heading. No Job ID. We must not include placeholder text like "commensurate with experience". Not present. We must ensure we only include sections with real content. Let's extract content. About the role: combine paragraphs from "About This Role" and maybe "AI at Toast", "People Are the Secret Ingredient", "Our Approach to Hybrid Working"? Actually hybrid working could be schedule. People Are the Secret Ingredient could be about culture; could be part of About the role. We'll craft About the role paragraph(s) summarizing the role description. Responsibilities: list from "A Day In The Life (Responsibilities)". Items: - Thinking: Take an ambiguous problem and come back with a point of view and a prototype - Design the whole loop, not just the booking screen - Hold both sides in your head. A guest booking a table and a restaurant running a floor want different things - Use behavioral data and guest feedback to shape what's next - Prototyping: Build working prototypes fast, in whatever tool gets you there (Figma Make, Cursor, Replit, Magic Patterns, Lovable) - Get something testable in front of people within days. Rough is fine, invisible isn't - Run small experiments and think in phases - Craft: Own visual and interaction quality end to end. Real opinions on type, spacing, hierarchy, motion - Design native mobile and responsive web that holds up against the best apps people use - Contribute to our design systems - Working together: Partner closely with product, eng, research, and marketing - Raise the bar for the designers around you through crit and pairing (not a management role, but a senior one) - Advocate for the guest even when the pressure runs the other way, and explain why in terms the business cares about We can keep as list items. Requirements: list from "What You'll Need To Thrive (Requirements)": - 5 to 7+ years designing consumer or consumer-grade products, with shipped work in your portfolio - Range across native and responsive, guest-facing and operator-facing - Bonus for scheduling, availability, transactional, or marketplace flow experience, or anything where a guest action has to land cleanly in someone else's operations - Fluency with AI prototyping tools and Figma, with a strong handle on accessibility - Solid UX fundamentals and the judgment to know which one a problem needs Also "Nice to haves" list: - You design in code, or close enough that engineers trust your handoff - You've built or stewarded a design system - You've shipped consumer at scale and know what breaks there - Front-end and performance literacy. You know why your beautiful transition is dropping frames - You're a tinkerer. You build things nobody asked for just to see if they'd work We could incorporate nice-to-haves into Requirements or Skills. Since we have Skills heading, we could put the nice-to-haves there. But we also have fluency with AI prototyping tools etc. That's also skill. Let's decide: Requirements: the core requirements (5-7 years, range, bonus, fluency, UX fundamentals). Skills: the nice-to-haves plus maybe also mention AI prototyping tools etc. But we already have fluency in requirements; could move to Skills. However we need to preserve all info; we can duplicate? Better to split: Requirements: the bullet points (5-7 years, range, bonus, fluency, UX fundamentals). Skills: the nice-to-haves list. But we also have "How You Use AI" description: "We use these tools constantly, and we're specific about why. We want work that's better because of how you use AI: sharper concepts, more options explored, more of the unglamorous states actually designed. You know where it helps and where it produces confident mush." This could be part of Skills or About the role. Let's put under Skills as a paragraph. Also "AI at Toast" description: could be under About the role. Now Pay: we have base salary ranges for zones A, B, C. Also mention total rewards components: cash compensation (overtime, bonus/commissions if eligible), equity, benefits. So we can put Pay section with salary ranges and note total rewards components. Benefits: description: "Our Total Rewards Philosophy ... Learn more about our benefits at https://careers.toasttab.com/toast-benefits." Also mention flexible benefits etc. We'll put Benefits section with that description and link. Schedule: hybrid working description: "Our Approach to Hybrid Working ... Please visit the Locations page on our career site to learn more about our in-office expectations by region: https://careers.toasttab.com/locations-toast". Also location info: US (remote), Boston (hybrid), or New York (hybrid). So schedule section can include location and hybrid expectations. Now we need to ensure we don't create sections with filler. All sections have content. Now produce HTML. We'll start with a

    for location? Actually location could be part of Schedule section. We'll include location inside Schedule. Let's craft:

    About the role

    Toast is shifting from B2B powerhouse to consumer innovator, using restaurant and guest data with AI to make dining feel personal and frictionless. You’ll own reservations and booking end‑to‑end, from ambiguous problem to shipped pixels, working across consumer surfaces as needed. You’ll join a small, ambitious Consumer Design team that operates like a startup within a larger company, with autonomy to reimagine dining and a culture that values rolling up sleeves and collaborating.

    At Toast, AI is embraced as a tool to build faster and with higher quality; the company provides AI tools across disciplines and encourages learning new tools to deliver more value for customers.

    Toast’s culture is grounded in authenticity, respect, and humility, viewing employees as the secret ingredient that drives success for both the team and its customers.

    That covers About the role.

    Responsibilities

    • Take an ambiguous problem and come back with a point of view and a prototype
    • Design the whole loop, not just the booking screen
    • Hold both sides in your head – a guest booking a table and a restaurant running a floor have different needs
    • Use behavioral data and guest feedback to shape what’s next
    • Build working prototypes fast, using whatever tool gets you there (Figma Make, Cursor, Replit, Magic Patterns, Lovable)
    • Get something testable in front of people within days; rough is fine, invisible isn’t
    • Run small experiments and think in phases
    • Own visual and interaction quality end to end, with real opinions on type, spacing, hierarchy, and motion
    • Design native mobile and responsive web that holds up against the best apps people use
    • Contribute to our design systems
    • Partner closely with product, engineering, research, and marketing
    • Raise the bar for the designers around you through critique and pairing (a senior, non‑management role)
    • Advocate for the guest even when business pressure runs the other way, explaining why in terms the business cares about

    Requirements

    • 5 to 7+ years designing consumer or consumer‑grade products, with shipped work in your portfolio
    • Experience ranging across native and responsive, guest‑facing and operator‑facing products
    • Bonus for scheduling, availability, transactional, or marketplace flow experience, or any area where a guest action must land cleanly in someone else’s operations
    • Fluency with AI prototyping tools and Figma, with a strong handle on accessibility
    • Solid UX fundamentals and the judgment to know which approach a problem needs

    Skills

    • You design in code, or close enough that engineers trust your handoff
    • You’ve built or stewarded a design system
    • You’ve shipped consumer at scale and know what breaks there
    • Front‑end and performance literacy – you know why a beautiful transition might drop frames
    • You’re a tinkerer who builds things just to see if they work

    How you use AI: we expect you to leverage AI tools to