Designer, Web Creative, Collabs - Pottery Barn Kids & Teen

We need to output only HTML fragment, no html/body tags, no markdown fences. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only when posting has real specific content. We need to parse the job description. First, "About the Team" is a section but not in allowed headings list? The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "About the Team" is not listed; we should not create a heading for it. However we need to preserve substantive information. The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples, but we should use those headings for sections. Probably we should map content to those headings where appropriate. "About the Team" could be considered "About the role"? Not exactly. But we could treat "About the Team" as part of "About the role"? Might be better to omit that heading and just include its content under appropriate sections (maybe as a paragraph under "About the role"?). However the instruction: "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." It doesn't forbid other headings not in list, but says use

for section headings (e.g. About the role, Responsibilities...). Likely they expect us to use those headings only. So we should not output a heading for "About the Team". Instead we could incorporate that info into a

maybe under a generic section? But they said "Prefer a few substantive sections over many thin ones." So we could combine team description into "About the role" section? The "About the role" section already exists later. We could put team description as a paragraph before responsibilities. Let's extract substantive content: - About the Team: description of team, dynamic team of art directors, photographers, producers, digital designers, production artists, copywriters. Work closely with counterparts to make websites, emails, digital assets come alive with Pottery Barn Kids and Teen’s brand voice and vision. Collaborate with cross-functional partners in eCom, Development, Brand Marketing. Sharing creative ideas, supporting each other, building community. Come join our team! - About The Role: The Digital Designer will design and produce content and marketing creative across site, emails, social and emarketing supporting our Licensed and Collabs partners. You’re excited about this opportunity because you will... (list bullet points): * Design assets from concept to execution for our licensed and collab partners creating on-brand and exciting content across site, emails and social platforms. * Work with Creative Manager and Senior Designer to design, wireframe and create visually stunning and innovative landing pages, web and mobile pages, emails, and social, while working within our branding and style guidelines. * Work with Senior Designer to maintain daily and weekly creative needs for licensed, vendor and collab partners. * Self-manage the design process from initial concept, final design, hand off to developers, user testing and launch. * Maintain and support creative process, workflow and relationships between creative, editorial, marketing and developers. * Work and communicate efficiently and effectively with business and creative teams to fulfill designs and deliverables. * Collaborate and support design team members on Pottery Barn Kids and Teen Creative US and Global teams. * Ensure design teams and projects meet business and creative deadlines. * Follow and maintain brand identity standards and process guides. - Why you will love working at Williams-Sonoma, Inc.: bullet list: * We’re a successful, fast-growing company with an entrepreneurial vibe * A technologically and data-driven business * Competitive salaries and comprehensive health benefits * We’re at the forefront of tech and retail, redefining technology for the next generation * We’re passionate about our internal and external clients and live/breathe the client experience * We get to be creative on a daily basis * A smart, experienced leadership team that wants to do it right and is open to new ideas * We believe in autonomy and reward taking initiative * We have fun! - We’re excited about you because... (qualifications/requirements): * You have a Bachelor’s degree in Visual, Web or Graphic Design * You have a demonstrated record of bringing new ideas to fruition. * Extremely proficient in Adobe Creative Suite. * Outstanding communication skills. * Meticulous attention to detail and work well within tight deadlines. * Familiarity with current online advertising practices and functionality. * Strong verbal and written communication skills * Strong organization skills; must be highly detail-oriented * Strong ability to manage and prioritize multiple tasks * 2+ years of digital/web design experience. - Technical Competencies Required: * Proficient in Figma, Photoshop, After Effects and Illustrator * Clear knowledge of content management systems * Basic HTML coding * Familiarity with social platforms: Instagram, TikTok, Pinterest, Facebook, etc. - About Williams-Sonoma, Inc.: company description (history, brands, etc). This is substantive but maybe not needed as a section? Could be "About the Company" but not in allowed headings. Could be omitted? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include that info somewhere. Could be placed under a heading like "About the Company" but not in list. However they said use

for section headings (e.g. About the role, Responsibilities...). It might be okay to add other headings if needed, but they gave examples. Safer to include it as a paragraph under a generic section like "About the Company" but that is not in the list; maybe we can treat it as part of "About the role"? Not ideal. But maybe we can treat "About Williams-Sonoma, Inc." as part of "About the role" or "Why you will love working at Williams-Sonoma, Inc." Actually the "Why you will love working at Williams-Sonoma, Inc." already covers culture/benefits. The "About Williams-Sonoma, Inc." is more generic company overview. Could be placed under a heading "About the Company" but not in allowed list. However the instruction says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says use

for section headings (e.g. those). Likely they expect us to only use those headings. So we need to map the company overview into one of those sections. Which fits best? Maybe "About the role" includes some company context? Not really. Could be "About the Team"? Not allowed. Could be "Qualifications"? No. Maybe we can treat the company overview as a paragraph under "About the role" as a preamble. But that would mix. Alternatively, we could create a section "About the Company" using

but it's not in the list; risk of being marked wrong. However the instruction says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exhaustive. So we can use other headings as long as they are

. But they also say "Prefer a few substantive sections over many thin ones." So we could add a section for company overview. But also they said "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." So they only restrict those. Thus we can use headings for About the Team, About the Role, Why you will love working..., Technical Competencies Required, About Williams-Sonoma, Inc., Benefits, Pay, etc. However they gave a list of headings to use for sections; maybe they want us to map content to those specific headings only. Let's read again: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This could be interpreted as: you should use those exact headings for sections, and you should not create other headings. The "e.g." might just be illustrative but they expect those headings. Usually in such tasks, they want you to use those headings exactly. So we should produce sections only for those headings that have content. Thus we need to map content to: - About the role - Responsibilities - Requirements - Qualifications - Skills - Benefits - Pay - Schedule We need to decide which content goes where. About the role: likely the paragraph describing the role (the "About The Role" section). That includes the introductory sentence and maybe the bullet list of what you will do? Actually the bullet list under "You’re excited about this opportunity because you will..." could be responsibilities. So we could split: About the role = general description; Responsibilities = bullet list of duties. Requirements vs Qualifications vs Skills: Usually Requirements = mandatory qualifications (education, experience). Qualifications = preferred? Skills = technical skills. We need to decide based on content. We have: - Bachelor’s degree in Visual, Web or Graphic Design (education) - Demonstrated record of bringing new ideas to fruition (experience/ability) - Extremely proficient in Adobe Creative Suite (skill) - Outstanding communication skills (skill) - Meticulous attention to detail and work well within tight deadlines (skill/attribute) - Familiarity with current online advertising practices and functionality (skill) - Strong verbal and written communication skills (skill) - Strong organization skills; must be highly detail-oriented (skill) - Strong ability to manage and prioritize multiple tasks (skill) - 2+ years of digital/web design experience (experience) Technical Competencies Required: - Proficient in Figma, Photoshop, After Effects and Illustrator (skill) - Clear knowledge of content management systems (skill) - Basic HTML coding (skill) - Familiarity with social platforms: Instagram, TikTok, Pinterest, Facebook, etc (skill) Thus we could categorize: Requirements: education, experience (Bachelor's degree, 2+ years experience). Possibly also "demonstrated record of bringing new ideas to fruition" as a requirement. Qualifications: maybe the "demonstrated record" etc? But we need to avoid duplication. Skills: technical competencies (Adobe Suite, Figma, etc) plus soft skills (communication, organization, attention to detail, etc). We could also have a separate "Skills" section for technical skills, and "Qualifications" for education/experience. But we have both Requirements and Qualifications headings; we need to decide which to use. Maybe we treat: - Requirements: Bachelor’s degree, 2+ years digital/web design experience. - Qualifications: Demonstrated record of bringing new ideas to fruition, proficiency in Adobe Creative Suite, strong communication skills, attention to detail, organization, multitasking, familiarity with online advertising practices. - Skills: Technical competencies (Figma, Photoshop, After Effects, Illustrator, CMS, basic HTML, social platforms). But there is overlap. Alternatively, we could combine Requirements and Qualifications into one section if content thin, but they said prefer few substantive sections over many thin ones. So we could have just Requirements (including education, experience, key qualifications) and Skills (technical). Or we could have Requirements and Skills only. But we must use headings only when posting has real specific content for it. So we need to decide which headings have content. Let's see if we have content for each: - About the role: yes (int