Staff Product Designer, Merchant Marketing

We need to output HTML fragment with sections: About the team? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the posting and extract sections: About The Team, About The Role, You're Excited About This Opportunity Because You Will…, We're Excited About You Because…, Compensation, Benefits, About DoorDash, Our Commitment to Diversity and Inclusion, Statement of Non-Discrimination, Pursuant to the San Francisco Fair Chance..., Notice to Applicants for Jobs Located in NYC..., Beware of recruitment scams... etc. We need to remove boilerplate: EEO, diversity statements, non-discrimination, fair chance, scam warnings, notice about Covey, etc. Also remove "About DoorDash" maybe? It's not a required heading but could be considered "About the company". The instruction says we can include sections only when posting has real, specific content. "About DoorDash" is substantive but not one of the listed headings. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It says "e.g." meaning those are examples, not exclusive? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely we should stick to those headings where applicable. But we could also use other headings if needed? The instruction: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are typical headings; we can use others if needed but better to stick to those. However we have content like "About The Team" and "About The Role". "About The Role" matches allowed heading. "About The Team" maybe not needed; could be merged into About the role? But we should preserve substantive information. Could create a section "About the team" using

  About the team? Not in list but maybe acceptable as it's similar to About the role. The instruction says "e.g." so it's not exhaustive; we can use other headings as needed. But to be safe, we can use headings: About the team, About the role, Responsibilities (maybe from "You're Excited About This Opportunity Because You Will…" which are duties), Requirements/Qualifications/Skills (from "We're Excited About You Because…" which are qualifications), Benefits, Pay, Schedule (hybrid model). Also we have location info: "This role can be based in New York City, San Francisco, or Seattle and reports to the Design Manager for Ads & Promotions (Restaurant Experience Team). We follow a hybrid model: 1–2 days per week in a Design Hub, with the remainder remote." That's schedule/location. We need to avoid duplicating lines. Also remove boilerplate like "Compensation The successful candidate's starting pay will fall within the pay range listed below..." We'll keep compensation details. We need to output only HTML fragment. Let's extract content: About The Team At DoorDash, design means making experiences for the people who order, the people who prepare, and the people who deliver. As a Designer at DoorDash, you want to build things that matter to real people. You're at your best when you can move from idea to shipped product quickly, bringing experiences to life that reach and influence users at massive scale. You'll care about whether the product you make solved a real problem for real people, or changed how someone experiences their day. About The Role At DoorDash, we’re redefining what it means to be a designer. We’re building a team of makers, builders, and doers. Over the past decade, “web designer” evolved into “product designer” as the scope expanded. Now, that shift is happening again — LLMs are broadening the role further, pushing design toward both strategic thinking and direct execution. As a Staff Product Designer, you’ll help lead this evolution: not only practicing build-first design, but scaling it across people, processes, and systems. In this role, you’ll join the Ads & Promos Design team — one of DoorDash’s fastest-growing businesses — owning end-to-end campaign experience design and shaping the strategic vision for our marketing tooling system. This platform powers both SMB and enterprise restaurants across DoorDash’s global markets and connects local businesses with over 40 million consumers globally. Your impact will span both team effectiveness and business growth. You’ll increase team velocity and autonomy by building reusable workflows, shared tools, and decision frameworks that enable designers to operate at a higher level with less coordination overhead. In parallel, you’ll drive measurable business outcomes by unlocking faster experimentation, shorter iteration cycles, and higher-quality execution across your team and adjacent teams. This role can be based in New York City, San Francisco, or Seattle and reports to the Design Manager for Ads & Promotions (Restaurant Experience Team). We follow a hybrid model: 1–2 days per week in a Design Hub, with the remainder remote. You're Excited About This Opportunity Because You Will… Define projects with a clear point of view, writing briefs that synthesize customer insights and business goals into actionable roadmapsBring clarity to ambiguous, cross-team problems and turn them into work that ships; drive prioritization and make thoughtful tradeoffs between quality, speed, and impactLead projects from concept through execution, staying close during iteration to ensure high-quality outcomes; deliver high-fidelity designs and production-ready prototypes that set the standard for craftDesign across systems and workflows, contributing to shared tools (e.g., prompt libraries, component generators, workflow automations) that improve team productivityMentor peers on responsible AI usage and contribute reusable frameworks that scale beyond your teamBuild strong cross-functional relationships and influence roadmaps through evidence-based thinking and tangible prototypesMultiply team impact through mentorship, recruiting, and inclusive practices We're Excited About You Because… You have a portfolio demonstrating craft excellence, systems thinking, and leadership through influenceYou use data to inform decisions, prioritize effectively, and deliver high-impact outcomesYou’re comfortable working in code and with LLM-powered tools, prototyping in production, and contributing to implementation when neededYou design and build solutions that scale across teams and workflowsYou thrive in ambiguity and create clarity through shipped work—not just presentationsDevelop AI-assisted or LLM-powered workflows that support component creation, documentation, evaluation, automation, and broader design system scalability.Produce clear design specifications, system documentation, governance artifacts, and reusable implementation guidance so that cross-functional teams can build, maintain, and extend completed work.Balance user needs, accessibility standards, business goals, and technical constraints in order to create feasible, polished, and scalable digital experiences.Analyze product usage, workflow effectiveness, and user feedback to iterate on launched designs and improve metrics such as efficiency, consistency, conversion, retention, and customer satisfaction. Compensation 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. Benefits DoorDash cares about you and your overall well-being. That’s why we offer a comprehensive benefits package to all regular employees, which includes a 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). DoorDash also offers medical, dental, and vision benefits, 11 paid holidays, disability and basic life insurance, family-forming assistance, and a mental health program, among others. To learn more about our benefits, visit our careers page here. See Below For Paid Time Off 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). Pay: The national base pay ranges for this position within the United States, including Illinois and Colorado. I4 $124,500—$183,000 USD I5 $148,200—$218,000 USD I6 $176,800—$260,000 USD Schedule: hybrid model: 1–2 days per week in a Design Hub, with the remainder remote. We need to avoid duplication: The compensation paragraph already mentions pay ranges; we also have separate Pay section with ranges. We should combine? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. We can keep both but avoid duplication. The compensation paragraph mentions ranges but not specific numbers; the Pay section gives specific ranges. We could keep the Pay section with the numbers and maybe drop the generic compensation paragraph? But the compensation paragraph also mentions equity grants, talk to recruiter, base salary localized, etc. That's substantive. So we should keep both but ensure not duplicate the same info. The compensation paragraph mentions "starting pay will fall within the pay range listed below". Then later we have the pay ranges. That's not duplicate; it's referencing. So we can keep both. We need to format lists where appropriate. For responsibilities (You're Excited About This Opportunity Because You Will…) we have a list of items separated by semicolons? Actually the text: "Define projects with a clear point of view, writing briefs that synthesize customer insights and business goals into actionable roadmapsBring clarity to ambiguous, cross-team problems and turn them into work that ships; drive prioritization and make thoughtful tradeoffs between quality, speed, and impactLead projects from concept through execution, staying close during iteration to ensure high-quality outcomes; deliver high-fidelity designs and production-ready prototypes that set the standard for craftDesign across systems and workflows, contributing to shared tools (e.g., prompt libraries, component generators, workflow automations) that improve team productivityMentor peers on responsible AI usage and contribute reusable frameworks that scale beyond your teamBuild strong cross-functional relationships and influence roadmaps through evidence-based thinking and tangible prototypesMultiply team impact through mentorship, recruiting, and inclusive practices" It seems missing punctuation; but we can split by semicolons and maybe by line breaks? The original likely had bullet points but got merged. We'll treat each clause separated by semicolon as a list item. Also there are some missing spaces. We'll parse: - Define projects with a clear point of view, writing briefs that synthesize