Director, Product Design

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 job description. The posting includes: - Job title: Director, Product Design (but we don't repeat as heading) - Location: New York, NY (metadata) - Description: "We’re seeking a future team member for the role of Director, Product Design to join our Fund and Investor Solutions team. This role is based in New York, NY. In this role, you’ll make an impact in the following ways: We are seeking a Senior Product Designer with experience working with, defining, and designing complex systems to bring creativity, strategic insight, and user-centered thinking to our team. This role requires an individual who excels in collaboration, design execution, and the ability to drive impactful user experiences." Then sections: - "The Ideal Candidate Will Bring the Following Expertise" then bullet-like paragraphs: Craft User-Centered Design, Journey Mapping, Interaction and UI Design, Proficiency in Design Tools, Systems thinking Design System Knowledge, Complex Systems Knowledge, Collaboration and Communication Cross-Functional Collaboration, Effective Communication and Storytelling, Mentorship and Leadership. - Then "A portfolio is required to be considered for this position" repeated. - Then "Experience Typically, a candidate at this level will have 12+ years of experience designing digital products, including time spent on complex, enterprise, or regulated systems. Prior domain expertise is less important than demonstrated ability to learn new domains and apply strong design principles effectively." - Then "About Us" paragraph. - Then "About The Team" paragraph with BNY newsroom etc. - Then "Our Benefits And Rewards" paragraph describing benefits, compensation, etc. - Then EEO etc (boilerplate to remove). - Then "BNY assesses market data..." etc (compensation details). This includes base salary info: "The expected base salary for this position when employment commences can be found in the Job Info section at the bottom of the posting. Base salary offered may vary depending on multiple individualized factors, including market location, job-related knowledge, skills, and experience. Base salary is only part of the total rewards package, which may include eligibility for an annual discretionary incentive award. Subject to the terms and conditions of the applicable plans then in effect, eligible employees may enroll in a 401(k) plan as well as participate in Company-sponsored medical, dental, vision, and basic life insurance plans for the employee and the employee’s eligible dependents. Eligible employees also may receive other benefits (including various paid time off benefits, such as vacation and sick time), dependent on the position offered. Details of participation in these benefit plans will be provided if an employee receives an offer of employment. If hired, the employee will be in an “at will” position and the Company reserves the right to modify base salary (as well as any other discretionary payments or compensation programs) at any time, including for reasons related to individual performance, Company or individual department/team performance, and market factors." We need to remove boilerplate: EEO, legal, etc. Also remove duplicated lines (like portfolio repeated). Also remove navigation/cookie etc (none). Also remove application instructions (none). Also remove "About Us", "About The Team" maybe we keep as sections? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to these standard headings if applicable. But we can also create other headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings when appropriate. Probably we should include sections like About the role (maybe the initial description), Responsibilities (the impact ways), Requirements/Qualifications/Skills (the expertise), Benefits (the benefits paragraph), Pay (if salary info present). Schedule not present, so omit. We must not repeat job title as heading. Also not put Job ID/requisition numbers as headings. We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to keep the details but we can format them as

or

• . For lists, we need to use
  • for any list of duties/requirements/benefits. Thus we need to decide what constitutes a list. The "Ideal Candidate Will Bring the Following Expertise" includes multiple bullet-like items each with a heading (bold?). We can treat each as a list item under a section like Requirements or Skills. We also have "Experience" paragraph. We have "About Us" and "About The Team" maybe combine into About the role? Or we could have separate sections: About the role (maybe includes description and team). But the instruction says prefer a few substantive sections over many thin ones. So we could combine About Us and About The Team into an "About the role" or "About the company". However the heading list includes "About the role". So we can use that for the initial description plus maybe team info. Responsibilities: The "In this role, you’ll make an impact in the following ways:" then a sentence: "We are seeking a Senior Product Designer with experience working with, defining, and designing complex systems to bring creativity, strategic insight, and user-centered thinking to our team. This role requires an individual who excels in collaboration, design execution, and the ability to drive impactful user experiences." That's not a list but could be responsibilities. Could also treat as a paragraph. Requirements/Qualifications/Skills: The expertise list. Benefits: The "Our Benefits And Rewards" paragraph. Pay: The compensation paragraph (base salary info). We need to include Pay section only if posting actually states them. It does mention base salary info but says "The expected base salary for this position when employment commences can be found in the Job Info section at the bottom of the posting." That's not a specific number, but it's still stating that base salary info exists. However the instruction says: 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. Here they say base salary can be found in Job Info section; not a specific number. Is that considered filler? It's not a specific number but it's stating that info exists elsewhere. Might be considered placeholder. Safer to omit Pay section because no specific salary figure is given. However they also mention "Base salary offered may vary depending on multiple individualized factors..." That's still vague. According to instruction, we should not create Pay section unless posting actually states them (i.e., gives a number or range). Since they don't, we should omit Pay. Benefits: They do state benefits: flexible global resources, health, personal resilience, financial goals, generous paid leaves, paid volunteer time, 401(k), medical/dental/vision/basic life insurance, other benefits like paid time off. That's substantive. So we include Benefits. Schedule: none. Thus sections: About the role (maybe combine initial description and team), Responsibilities, Requirements (or Skills), Benefits. We need to use

    for each section heading. Inside each section, we need to use

    for prose and

    • for any list. Let's extract content. About the role: Should include the initial description: "We’re seeking a future team member for the role of Director, Product Design to join our Fund and Investor Solutions team. This role is based in New York, NY. In this role, you’ll make an impact in the following ways: We are seeking a Senior Product Designer with experience working with, defining, and designing complex systems to bring creativity, strategic insight, and user-centered thinking to our team. This role requires an individual who excels in collaboration, design execution, and the ability to drive impactful user experiences." Also maybe include About The Team paragraph: "At BNY, our culture speaks for itself, check out the latest BNY news at BNY Newsroom & BNY LinkedIn Here’s a Few Of Our Recent Awards America’s Most Innovative Companies, Fortune, 2025World’s Most Admired Companies, Fortune 2025“Most Just Companies”, Just Capital and CNBC, 2025". That's a bit messy but we keep. Also About Us paragraph: "At BNY, our culture allows us to run our company better and enables employees’ growth and success. As a leading global financial services company at the heart of the global financial system, we influence nearly 20% of the world’s investible assets. Every day, our teams harness cutting-edge AI and breakthrough technologies to collaborate with clients, driving transformative solutions that redefine industries and uplift communities worldwide. Recognized as a top destination for innovators, BNY is where bold ideas meet advanced technology and exceptional talent. Together, we power the future of finance – and this is what is all about. Join us and be part of something extraordinary." We can combine these into About the role section. Responsibilities: The impact ways sentence maybe we can treat as responsibilities. Could also include the bullet points under "The Ideal Candidate Will Bring the Following Expertise" as responsibilities? Actually those are qualifications/skills. So responsibilities: maybe the initial impact sentence. We'll put that as a

      . Requirements/Skills: The list of expertise items. We'll make a

      • for each. We need to preserve all substantive information: each bullet includes a bold heading and description. We'll keep the text as is. List items: - Craft User-Centered Design – Lead with a user-first approach, ensuring all design choices address user needs, behaviors, and insights from research. Drive a seamless and intuitive product experience by deeply understanding our users. - Journey Mapping – Map and analyze end-to-end user journeys across customers, operations, servicing teams and systems to identify pain points, key moments, and opportunities for improvement. Use journey maps to align teams on a shared vision of user needs, ensuring a cohesive and supportive experience at each stage. - Interaction and UI Design – Demonstrates mastery in designing complex web interfaces and workflows, creating products that are both highly functional and visually engaging. Skilled in developing intuitive layouts, navigation patterns, and interaction models for intricate systems. Thoughtfully uses animation and micro-interactions to guide users, making complex tasks more approachable and enhancing the overall product experience. - Proficiency in Design Tools – Possess advanced skills in tools such as Figma and Miro, to create high-fidelity wireframes, prototypes, and mockups that clearly communicate interaction models and UI specifications. - Systems thinking Design System Knowledge – Experience with and contribute to a global design system that ensures visual consistency across interfaces. Develop workflow patterns and components that can then be reused by other teams. - Complex Systems Knowledge – Bring an understanding of the unique challenges of designing and maintaining complex systems, with an ability to distill intricate requirements into clear design solutions that facilitate user understanding and interaction. - Collaboration and Communication Cross-Functional Collaboration – Work closely with product managers, engineers, and stakeholders to align design efforts with business goals, transforming complex requirements into clear, functional design solutions that respect technical constraints. - Effective Communication and Storytelling – Articulate design concepts and rationale to diverse stakeholders, making complex ideas accessible. Use storytelling to engage others in the product vision, fostering alignment and enthusiasm. - Mentorship and Leadership – Skilled in guiding junior designers, providing constructive feedback, and elevating team standards. Fosters a culture of continuous learning, innovation, and collaboration within the team. Also "A portfolio is required to be considered for this position A portfolio is required and should demonstrate strong interaction design, systems thinking, and experience working in complex or ambiguous problem spaces. A Figma link with view access is acceptable." This is a requirement; we could include under Requirements as a separate bullet or paragraph. Since it's a requirement, we can add a bullet: "A portfolio is required to be considered for this position; should demonstrate strong interaction design, systems thinking, and experience working in complex