Staff Producer Studio Central
for each heading. Use - for any list of duties/requirements/benefits. Use
for prose. Do not repeat job title. Do not include Job ID etc. Remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Include a section only when posting has real, specific content for it. Avoid filler like "commensurate with experience". So we need to extract content.
Let's parse the posting.
First part: "About The Team Producers at DoorDash, Deliveroo, Wolt, and 7Rooms are strategic and creative problem solvers, crafting scalable solutions that empower transformative and high-quality design. By driving innovation and excellence, they play a key role in shaping the future of Design at our companies, making a lasting impact on our community and beyond."
That's about the team. Could be "About the team" but not required heading. We have headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to map content.
"About The Role Studio Central is a global team within Studio, DoorDash's Product Design organization, supporting DoorDash, Wolt, Deliveroo, and 7Rooms. We own how brand shows up in the product experience, partnering closely with Marketing and Product teams to shape cohesive, high-quality work and to help define the foundations, vision, and future state of design across our portfolio. Our work spans major brand moments, merchandising, and the systems that connect it all. There's no finished playbook here, and that's intentional. As the Staff Producer for Studio Central, we're looking for someone who thrives building structure from scratch: getting our design standards documented, adopted, and evolving across every brand and surface, and keeping work moving from brief to delivery across in-house teams, agencies, and cross-functional partners in Product Design, Marketing, and Engineering. You'll help build Studio Central's operating model as we go, setting the standard for how a distributed design organization stays aligned as it scales."
That's about the role. So we can put that in
About the role
with paragraphs.
Then bullet list of responsibilities: The bullet points after "You’re excited about this opportunity because you will…" then list of items each starting with a bold phrase? Actually they are sentences: "Own the Studio Central operating model, defining how brand and design expression work gets requested, scoped, prioritized, and delivered across DoorDash, Deliveroo, Wolt, and 7Rooms", "Thrive in the blank-canvas work as much as the day-to-day: standing up how design operates for a brand-new vertical or business line from zero, not inheriting someone else's playbook.", "Produce high-visibility design expression work end to end — writing briefs, building timelines, resourcing teams, running reviews, and shepherding assets through final handoff", "Art direct the work, not just the schedule — giving creative direction on briefs and reviews, weighing creative tradeoffs against time and budget, and holding the visual quality bar from concept through handoff", "Steward our design expression across brand and product, partnering with Brand, Product Design, and Marketing to keep experiences consistent where it matters and intentionally distinct where it should be", "Build the governance model for how Studio Central works day to day, including contribution paths, review rituals, decision rights, and a clear escalation path when brand and product needs diverge", "Drive cross-functional alignment with Marketing, Engineering, Product, and Localization, translating brand-in-product design decisions into work partner teams can actually execute against", "Own vendor and agency partnerships, from selection and onboarding to procurement and performance management, ensuring external partners seamlessly support evolving brand and product needs", "Create and maintain the source of truth — playbooks, guidelines, templates, and documentation that make our foundation and expression work easy to find, easy to use, and hard to misapply", "Define the tooling and workflow strategy for creative production, ensuring designers and producers have best-in-class platforms for asset management, review, and handoff", "Drive AI fluency across the studio, partnering with design and technology leaders to responsibly integrate AI into production workflows, asset generation, and design language maintenance", "Measure what’s working, instrumenting adoption, throughput, and quality so we can show the impact of design language investment and unlock operational efficiencies for the teams we serve".
These are responsibilities. So we can put them under
Responsibilities
with - .
Next: "We’re excited about you because…" then bullet list of qualifications/experience. Those are requirements/qualifications/skills. We need to decide which heading to use. The spec includes Requirements, Qualifications, Skills. We can combine or separate. Probably we can put under Requirements (or Qualifications). Since they are experience requirements. Let's put under
Requirements
with - . Items:
- You have 12+ years of experience in creative production, design program management, or design operations — with real time spent producing the work, not only running the process around it — including defining operating models rather than inheriting someone else’s, and a track record of taking 0→1 initiatives from concept to adoption at scale and speed
- You’ve produced brand and product design work end to end — briefs, budgets, timelines, resourcing, reviews, and delivery — and you know how to protect creative quality while the schedule holds
- You can art direct, not just coordinate — you give creative direction that senior designers act on, and you are treated as a creative peer by design leadership rather than the person tracking the schedule
- You own the quality bar and can defend it — you know what “good enough to ship” actually means, when to hold the line, and when more polish stops adding value
- You hold the line on visual systems, because you can tell a real design problem from an asset request — and you will push back on the latter even when it comes from someone senior
- You’ve defined governance and enablement systems for design expression, design systems, or brand guidelines from the ground up — documentation, contribution models, decision rights, and adoption rituals that outlast any single project or reorg — and you’ve done it without letting the system flatten the craft
- You set direction in cross-functional ambiguity, building org-wide alignment across Brand, Product, Engineering, Marketing, and Localization entirely through influence rather than formal authority
- You’ve owned design budgets and agency relationships at scale, setting the standards partner teams operate against while balancing creative excellence with operational rigor
- You’re a clear communicator and scrappy problem solver, passionate about improving design culture, team rituals, and embracing new tools—including AI—to help designers and producers do their best work
These are requirements/qualifications/skills. Could split: Requirements (experience), Skills (art direction, communication). But spec says prefer few substantive sections over many thin ones. So maybe combine into one section "Requirements". Or we could have "Qualifications" and "Skills". But we need to avoid thin sections. Let's combine into one "Requirements" section.
Next: Benefits: The posting includes compensation and benefits details. There's a "Compensation" section with base salary range, equity grants, benefits package details. Also "Benefits" details: 401(k) plan 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. So we should have a Benefits section with list.
Pay: The posting includes base salary range: "$176,800—$260,000 USD". Also mentions equity grants. So we need a Pay section. Should we include both base salary and equity? Yes.
Schedule: No explicit schedule info (full-time? Not mentioned). There's no schedule details. So we should not create a Schedule section because no specific content.
Also there is "About DoorDash" etc. That's boilerplate about company; could be omitted as not required heading. Also "Our Commitment to Diversity and Inclusion" etc is EEO boilerplate; remove. Also "Statement of Non-Discrimination" etc remove. Also "Pursuant to the San Francisco Fair Chance Ordinance..." remove. Also "Notice to Applicants for Jobs Located in NYC..." remove. Also "Beware of recruitment scams" remove.
Also "Applications for this position are accepted on an ongoing basis" - that's application instruction; remove.
Now we need to output only HTML fragment, no /, no markdown fences.
We'll produce:
About the role
...
Responsibilities
- ...
...
Requirements
- ...
...
Benefits
- ...
...
Pay
...
We need to ensure we preserve all substantive information. Let's extract the About the role paragraph(s). There's also first paragraph about the team; maybe we can include that under About the role as context. But the spec says About the role heading for section headings e.g. About the role, Responsibilities, etc. The "About The Team" could be considered part of About the role? Might be okay to include as part of About the role paragraph. We'll combine.
Let's craft About the role paragraph:
"Producers at DoorDash, Deliveroo, Wolt, and 7Rooms are strategic and creative problem solvers, crafting scalable solutions that empower transformative and high-quality design. By driving innovation and excellence, they play a key role in shaping the future of Design at our companies, making a lasting impact on our community and beyond. Studio Central is a global team within Studio, DoorDash's Product Design organization, supporting DoorDash, Wolt, Deliveroo, and 7Rooms. We own how brand shows up in the product experience, partnering closely with Marketing and Product teams to shape cohesive, high-quality work and to help define the foundations, vision, and future state of design across our portfolio. Our work spans major brand moments, merchandising, and the systems that connect it all. There's no finished playbook here, and that's intentional. As the Staff Producer for Studio Central, we're looking for someone who thrives building structure from scratch: getting our design standards documented, adopted, and evolving across every brand and surface, and keeping work moving from brief to delivery across in-house teams, agencies, and cross-functional partners in Product Design, Marketing, and Engineering. You'll help build Studio Central's operating model as we go, setting the standard for how a distributed design organization stays aligned as it scales."
That seems good.
Now Responsibilities list as above.
Now Requirements list as above.
Now Benefits list: Let's extract benefits details:
From "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
for prose. Do not repeat job title. Do not include Job ID etc. Remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Include a section only when posting has real, specific content for it. Avoid filler like "commensurate with experience". So we need to extract content. Let's parse the posting. First part: "About The Team Producers at DoorDash, Deliveroo, Wolt, and 7Rooms are strategic and creative problem solvers, crafting scalable solutions that empower transformative and high-quality design. By driving innovation and excellence, they play a key role in shaping the future of Design at our companies, making a lasting impact on our community and beyond." That's about the team. Could be "About the team" but not required heading. We have headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content. "About The Role Studio Central is a global team within Studio, DoorDash's Product Design organization, supporting DoorDash, Wolt, Deliveroo, and 7Rooms. We own how brand shows up in the product experience, partnering closely with Marketing and Product teams to shape cohesive, high-quality work and to help define the foundations, vision, and future state of design across our portfolio. Our work spans major brand moments, merchandising, and the systems that connect it all. There's no finished playbook here, and that's intentional. As the Staff Producer for Studio Central, we're looking for someone who thrives building structure from scratch: getting our design standards documented, adopted, and evolving across every brand and surface, and keeping work moving from brief to delivery across in-house teams, agencies, and cross-functional partners in Product Design, Marketing, and Engineering. You'll help build Studio Central's operating model as we go, setting the standard for how a distributed design organization stays aligned as it scales." That's about the role. So we can put that in
About the role
withparagraphs. Then bullet list of responsibilities: The bullet points after "You’re excited about this opportunity because you will…" then list of items each starting with a bold phrase? Actually they are sentences: "Own the Studio Central operating model, defining how brand and design expression work gets requested, scoped, prioritized, and delivered across DoorDash, Deliveroo, Wolt, and 7Rooms", "Thrive in the blank-canvas work as much as the day-to-day: standing up how design operates for a brand-new vertical or business line from zero, not inheriting someone else's playbook.", "Produce high-visibility design expression work end to end — writing briefs, building timelines, resourcing teams, running reviews, and shepherding assets through final handoff", "Art direct the work, not just the schedule — giving creative direction on briefs and reviews, weighing creative tradeoffs against time and budget, and holding the visual quality bar from concept through handoff", "Steward our design expression across brand and product, partnering with Brand, Product Design, and Marketing to keep experiences consistent where it matters and intentionally distinct where it should be", "Build the governance model for how Studio Central works day to day, including contribution paths, review rituals, decision rights, and a clear escalation path when brand and product needs diverge", "Drive cross-functional alignment with Marketing, Engineering, Product, and Localization, translating brand-in-product design decisions into work partner teams can actually execute against", "Own vendor and agency partnerships, from selection and onboarding to procurement and performance management, ensuring external partners seamlessly support evolving brand and product needs", "Create and maintain the source of truth — playbooks, guidelines, templates, and documentation that make our foundation and expression work easy to find, easy to use, and hard to misapply", "Define the tooling and workflow strategy for creative production, ensuring designers and producers have best-in-class platforms for asset management, review, and handoff", "Drive AI fluency across the studio, partnering with design and technology leaders to responsibly integrate AI into production workflows, asset generation, and design language maintenance", "Measure what’s working, instrumenting adoption, throughput, and quality so we can show the impact of design language investment and unlock operational efficiencies for the teams we serve". These are responsibilities. So we can put them under
Responsibilities
with- .
Next: "We’re excited about you because…" then bullet list of qualifications/experience. Those are requirements/qualifications/skills. We need to decide which heading to use. The spec includes Requirements, Qualifications, Skills. We can combine or separate. Probably we can put under Requirements (or Qualifications). Since they are experience requirements. Let's put under
Requirements
with- . Items:
- You have 12+ years of experience in creative production, design program management, or design operations — with real time spent producing the work, not only running the process around it — including defining operating models rather than inheriting someone else’s, and a track record of taking 0→1 initiatives from concept to adoption at scale and speed
- You’ve produced brand and product design work end to end — briefs, budgets, timelines, resourcing, reviews, and delivery — and you know how to protect creative quality while the schedule holds
- You can art direct, not just coordinate — you give creative direction that senior designers act on, and you are treated as a creative peer by design leadership rather than the person tracking the schedule
- You own the quality bar and can defend it — you know what “good enough to ship” actually means, when to hold the line, and when more polish stops adding value
- You hold the line on visual systems, because you can tell a real design problem from an asset request — and you will push back on the latter even when it comes from someone senior
- You’ve defined governance and enablement systems for design expression, design systems, or brand guidelines from the ground up — documentation, contribution models, decision rights, and adoption rituals that outlast any single project or reorg — and you’ve done it without letting the system flatten the craft
- You set direction in cross-functional ambiguity, building org-wide alignment across Brand, Product, Engineering, Marketing, and Localization entirely through influence rather than formal authority
- You’ve owned design budgets and agency relationships at scale, setting the standards partner teams operate against while balancing creative excellence with operational rigor
- You’re a clear communicator and scrappy problem solver, passionate about improving design culture, team rituals, and embracing new tools—including AI—to help designers and producers do their best work
These are requirements/qualifications/skills. Could split: Requirements (experience), Skills (art direction, communication). But spec says prefer few substantive sections over many thin ones. So maybe combine into one section "Requirements". Or we could have "Qualifications" and "Skills". But we need to avoid thin sections. Let's combine into one "Requirements" section.
Next: Benefits: The posting includes compensation and benefits details. There's a "Compensation" section with base salary range, equity grants, benefits package details. Also "Benefits" details: 401(k) plan 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. So we should have a Benefits section with list.
Pay: The posting includes base salary range: "$176,800—$260,000 USD". Also mentions equity grants. So we need a Pay section. Should we include both base salary and equity? Yes.
Schedule: No explicit schedule info (full-time? Not mentioned). There's no schedule details. So we should not create a Schedule section because no specific content.
Also there is "About DoorDash" etc. That's boilerplate about company; could be omitted as not required heading. Also "Our Commitment to Diversity and Inclusion" etc is EEO boilerplate; remove. Also "Statement of Non-Discrimination" etc remove. Also "Pursuant to the San Francisco Fair Chance Ordinance..." remove. Also "Notice to Applicants for Jobs Located in NYC..." remove. Also "Beware of recruitment scams" remove.
Also "Applications for this position are accepted on an ongoing basis" - that's application instruction; remove.
Now we need to output only HTML fragment, no /, no markdown fences.
We'll produce:
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Benefits
- ... ...
Pay
...
We need to ensure we preserve all substantive information. Let's extract the About the role paragraph(s). There's also first paragraph about the team; maybe we can include that under About the role as context. But the spec says About the role heading for section headings e.g. About the role, Responsibilities, etc. The "About The Team" could be considered part of About the role? Might be okay to include as part of About the role paragraph. We'll combine. Let's craft About the role paragraph: "Producers at DoorDash, Deliveroo, Wolt, and 7Rooms are strategic and creative problem solvers, crafting scalable solutions that empower transformative and high-quality design. By driving innovation and excellence, they play a key role in shaping the future of Design at our companies, making a lasting impact on our community and beyond. Studio Central is a global team within Studio, DoorDash's Product Design organization, supporting DoorDash, Wolt, Deliveroo, and 7Rooms. We own how brand shows up in the product experience, partnering closely with Marketing and Product teams to shape cohesive, high-quality work and to help define the foundations, vision, and future state of design across our portfolio. Our work spans major brand moments, merchandising, and the systems that connect it all. There's no finished playbook here, and that's intentional. As the Staff Producer for Studio Central, we're looking for someone who thrives building structure from scratch: getting our design standards documented, adopted, and evolving across every brand and surface, and keeping work moving from brief to delivery across in-house teams, agencies, and cross-functional partners in Product Design, Marketing, and Engineering. You'll help build Studio Central's operating model as we go, setting the standard for how a distributed design organization stays aligned as it scales." That seems good. Now Responsibilities list as above. Now Requirements list as above. Now Benefits list: Let's extract benefits details: From "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
- . Items:
- You have 12+ years of experience in creative production, design program management, or design operations — with real time spent producing the work, not only running the process around it — including defining operating models rather than inheriting someone else’s, and a track record of taking 0→1 initiatives from concept to adoption at scale and speed
- You’ve produced brand and product design work end to end — briefs, budgets, timelines, resourcing, reviews, and delivery — and you know how to protect creative quality while the schedule holds
- You can art direct, not just coordinate — you give creative direction that senior designers act on, and you are treated as a creative peer by design leadership rather than the person tracking the schedule
- You own the quality bar and can defend it — you know what “good enough to ship” actually means, when to hold the line, and when more polish stops adding value
- You hold the line on visual systems, because you can tell a real design problem from an asset request — and you will push back on the latter even when it comes from someone senior
- You’ve defined governance and enablement systems for design expression, design systems, or brand guidelines from the ground up — documentation, contribution models, decision rights, and adoption rituals that outlast any single project or reorg — and you’ve done it without letting the system flatten the craft
- You set direction in cross-functional ambiguity, building org-wide alignment across Brand, Product, Engineering, Marketing, and Localization entirely through influence rather than formal authority
- You’ve owned design budgets and agency relationships at scale, setting the standards partner teams operate against while balancing creative excellence with operational rigor
- You’re a clear communicator and scrappy problem solver, passionate about improving design culture, team rituals, and embracing new tools—including AI—to help designers and producers do their best work
These are requirements/qualifications/skills. Could split: Requirements (experience), Skills (art direction, communication). But spec says prefer few substantive sections over many thin ones. So maybe combine into one section "Requirements". Or we could have "Qualifications" and "Skills". But we need to avoid thin sections. Let's combine into one "Requirements" section.
Next: Benefits: The posting includes compensation and benefits details. There's a "Compensation" section with base salary range, equity grants, benefits package details. Also "Benefits" details: 401(k) plan 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. So we should have a Benefits section with list.
Pay: The posting includes base salary range: "$176,800—$260,000 USD". Also mentions equity grants. So we need a Pay section. Should we include both base salary and equity? Yes.
Schedule: No explicit schedule info (full-time? Not mentioned). There's no schedule details. So we should not create a Schedule section because no specific content.
Also there is "About DoorDash" etc. That's boilerplate about company; could be omitted as not required heading. Also "Our Commitment to Diversity and Inclusion" etc is EEO boilerplate; remove. Also "Statement of Non-Discrimination" etc remove. Also "Pursuant to the San Francisco Fair Chance Ordinance..." remove. Also "Notice to Applicants for Jobs Located in NYC..." remove. Also "Beware of recruitment scams" remove.
Also "Applications for this position are accepted on an ongoing basis" - that's application instruction; remove.
Now we need to output only HTML fragment, no /, no markdown fences.
We'll produce: