Staff Product Designer, New Bets

We need to output HTML fragment with headings for sections present: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections that have real specific content. The posting includes "About The Role" content (the first paragraph). Then responsibilities? The role description includes many bullet-like sentences but not explicit headings. We need to extract responsibilities, requirements, qualifications, skills, benefits, pay, schedule. We need to parse the posting for these. Let's read the posting: "About The Role At DoorDash we are redefining what it means to be a designer. ... This role offers a unique opportunity to design powerful systems that help workplace admins plan, manage, and operate food programs with confidence, while pioneering new offerings in an evolving market. This position is open for candidates in San Francisco, Seattle, or New York City, and will report to the Head of New Bets Design within our Consumer organization. You will work in a hybrid model, working from one of our offices 1-2 times a week with the rest working from home. Your primary impact is making the team faster and more autonomous. You build reusable workflows, shared tools, and decision frameworks that let every designer on your team operate at a higher level with less coordination overhead. Your secondary impact is revenue: the speed and quality gains you unlock translate directly into more experiments shipped, faster iteration cycles, and measurable business outcomes across your team and adjacent teams. You're excited about this opportunity because you will... Define projects with a clear point of view on what to build, writing briefs that synthesize business and customer inputs into roadmap milestones; balance customer needs, business goals, and feasibility to shape what your team builds and whyBring clarity to ambiguous, cross-team problems and turn them into actionable work that ships; drive prioritization across your team and adjacent teams, making tradeoffs between design quality, speed, and impact so the highest-leverage work moves firstShape key projects from concept through execution — staying close enough to resolve issues during iteration, guiding design direction, and shipping work that drives measurable outcomes across multiple teams; produce high-fidelity designs and production-ready prototypes that set the craft standard for the teamDesign solutions spanning multiple workflows and contribute to shared tools — prompt libraries, component generators, workflow automations — that improve productivity across teams; mentor peers on responsible AI use and contribute reusable frameworks adopted beyond your own teamBuild trusted relationships across your team and adjacent product teams, influencing their roadmaps through evidence-based thinking and live prototypes that make your recommendations concrete; pursue consistent self-improvement and flex into raising team outcomesMultiply team capacity through mentorship, recruiting, and inclusive practices that raise the bar across your product group" That's a lot of responsibilities. Then "We're excited about you because..." lists qualifications/skills: portfolio showing craft excellence, systems thinking, leadership through influence; reach for code editors and LLM-powered tools as naturally as design tools, prototyping in production and contributing meaningfully to the codebase; influence, design, and build solutions that work across teams and workflows; enjoy navigating unclear problems across multiple teams and create clarity through shipped artifacts, not slide decks. Then "Compensation" section: includes pay ranges, equity grants, benefits description. Then benefits: comprehensive benefits package: 401(k) with employer matching, 16 weeks paid parental leave, wellness benefits, commuter benefits match, paid time off and paid sick leave, medical dental vision, 11 paid holidays, disability and basic life insurance, family-forming assistance, mental health program, etc. Also PTO details. Then schedule: hybrid model: work from office 1-2 times a week, rest from home. Thus we have sections: About the role (we have content), Responsibilities (we have many bullet-like sentences), Requirements/Qualifications/Skills (we have qualifications/skills), Benefits, Pay, Schedule. We must not repeat job title as heading. Use

for each section heading. We need to output only HTML fragment, no /. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate etc. We need to decide how to split content into lists. For Responsibilities: we can extract bullet points from the "You're excited about this opportunity because you will..." list and also earlier sentences about primary/secondary impact, building workflows, etc. We'll create a list. For Requirements/Qualifications/Skills: we have "We're excited about you because..." bullet points. Also maybe mention location (San Francisco, Seattle, or New York City) and hybrid model? That's schedule. Also reporting line maybe not needed. We could combine qualifications and skills into one section "Requirements" or separate "Qualifications" and "Skills". The instruction says use headings for those categories if content exists. We have content for qualifications (portfolio, experience) and skills (tools, influence). Could split but risk thin sections. Better to combine into one section "Requirements" (or "Qualifications") that includes both. But we have separate headings possible: Qualifications and Skills. However we need to avoid thin sections. The instruction: "Prefer a few substantive sections over many thin ones." So maybe combine into one section "Requirements" that includes both qualifications and skills. But we have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose to include only those with substantive content. We could include Requirements (covering qualifications and skills) and skip Qualifications and Skills separate. Or we could include Qualifications and Skills separately if we have enough content. Let's see. Qualifications: portfolio showing craft excellence, systems thinking, leadership through influence. Also maybe location? Not qualification. Could be considered qualification. Skills: reach for code editors and LLM-powered tools, prototyping in production, contributing to codebase; influence, design, build solutions across teams; enjoy navigating unclear problems and create clarity through shipped artifacts. We could split: Qualifications bullet list: portfolio..., leadership..., etc. Skills bullet list: tools..., influence..., navigating unclear problems. That seems substantive enough. Thus we will have sections: About the role, Responsibilities, Qualifications, Skills, Benefits, Pay, Schedule. We must not include Requirements if we split. Now we need to extract content precisely, preserving all substantive information, not inventing. Let's gather About the role prose: The first paragraph up to "This position is open for candidates in San Francisco, Seattle, or New York City, and will report to the Head of New Bets Design within our Consumer organization." That's about the role. Could also include hybrid model? That's schedule. We'll keep about role as description of role and mission. We'll put that in

  . Now Responsibilities: list items from "Your primary impact..." and "You're excited about this opportunity because you will..." plus earlier sentences about building workflows etc. Let's extract bullet points: - Your primary impact is making the team faster and more autonomous. - You build reusable workflows, shared tools, and decision frameworks that let every designer on your team operate at a higher level with less coordination overhead. - Your secondary impact is revenue: the speed and quality gains you unlock translate directly into more experiments shipped, faster iteration cycles, and measurable business outcomes across your team and adjacent teams. - Define projects with a clear point of view on what to build, writing briefs that synthesize business and customer inputs into roadmap milestones; balance customer needs, business goals, and feasibility to shape what your team builds and why. - Bring clarity to ambiguous, cross-team problems and turn them into actionable work that ships; drive prioritization across your team and adjacent teams, making tradeoffs between design quality, speed, and impact so the highest-leverage work moves first. - Shape key projects from concept through execution — staying close enough to resolve issues during iteration, guiding design direction, and shipping work that drives measurable outcomes across multiple teams; produce high-fidelity designs and production-ready prototypes that set the craft standard for the team. - Design solutions spanning multiple workflows and contribute to shared tools — prompt libraries, component generators, workflow automations — that improve productivity across teams; mentor peers on responsible AI use and contribute reusable frameworks adopted beyond your own team. - Build trusted relationships across your team and adjacent product teams, influencing their roadmaps through evidence-based thinking and live prototypes that make your recommendations concrete; pursue consistent self-improvement and flex into raising team outcomes. - Multiply team capacity through mentorship, recruiting, and inclusive practices that raise the bar across your product group. We need to ensure we keep semicolons etc as part of prose; but we can keep as list items. Now Qualifications: bullet list: - You have a portfolio that shows projects that demonstrate craft excellence, systems thinking, and leadership through influence. Maybe also mention location? Not qualification. We could also include "You are located in San Francisco, Seattle, or New York City" but that's location requirement; could be qualification. But we might keep location in schedule? Actually schedule is hybrid model. Location is separate. Could be a qualification: "This position is open for candidates in San Francisco, Seattle, or New York City." That is a location requirement. We'll include in Qualifications. Thus Qualifications bullets: - Portfolio demonstrating craft excellence, systems thinking, and leadership through influence. - Located in San Francisco, Seattle, or New York City (or willing to relocate? The posting says open for candidates in those cities). We'll keep as stated. Now Skills bullets: - You reach for code editors and LLM-powered tools as naturally as design tools, prototyping in production and contributing meaningfully to the codebase. - You influence, design, and build solutions that work across teams and workflows. - You enjoy navigating unclear problems across multiple teams and create clarity through shipped artifacts, not slide decks. Now Benefits: list from benefits paragraph. We need to extract list items: - 401(k) plan with employer matching - 16 weeks of paid parental leave - wellness benefits - commuter benefits match - paid time off and paid sick leave in compliance with applicable laws (e.g. Colorado Healthy Families and Workplaces Act) - medical, dental, and vision benefits - 11 paid holidays - disability and basic life insurance - family-forming assistance - mental health program - (maybe also premium healthcare, wellness expense reimbursement, paid parental leave already mentioned; but we can keep as listed.) Also PTO details: For salaried roles: flexible paid time off/vacation, plus 80 hours of paid sick time per year. For hourly roles: vacation accrued at about 1 hour for every 25.97 hours worked (e.g. about 6.7 hours/month if working 40 hours/week; about 3.4 hours/month if working 20 hours/week), and paid sick time accrued at 1 hour for every 30 hours worked (e.g. about 5.8 hours/month if working 40 hours/week; about 2.9 hours/month if working 20 hours/week). This is part of benefits. We'll include as list items. Now Pay: we have compensation section: "The successful candidate's starting pay will fall within the pay range listed below and is determined based on job-related factors including, but not limited to, skills, experience, qualifications, work location, and market conditions. Base salary is localized according to an employee’s work location. Ranges are market-dependent and may be modified in the future. In addition to base salary, the compensation for this role includes opportunities for equity grants. Talk to your recruiter for more information." Then pay ranges: I4 $124,500—$183,000 USD; I5 $148,200—$218,000 USD; I6 $176,800—$260,000 USD. We need to include Pay section with that info. Should we list the ranges as list? Could be prose. We'll put as

  with the ranges. Now Schedule: hybrid model: "You will work in a hybrid model, working from one of our offices 1-2 times a week with the rest