Financial Services - Technology Consulting - Product Designer - Senior

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 must not repeat job title as heading. Remove boilerplate, navigation, legal, EEO, etc. Also remove application instructions, duplicated lines. Must preserve all substantive info. We need to parse the posting. Key sections: - About the role / overview: The first paragraph(s) describing EY, purpose, etc. Could be "About the role" or maybe "About EY". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have: Location: Anywhere in Country (maybe ignore as metadata). Then description: "At EY, we’re all in to shape your future with confidence...". That's about the company and role. Could be "About the role". We'll put that in

. Then "The opportunity The Product and Experience Design (PxD) Team..." That's also about role. Could be part of About the role. Then "Your Key Responsibilities" heading in source. We'll map to

Responsibilities

and list bullet points. Then "Skills And Attributes For Success" -> could be Skills section. We'll put

Skills

and list bullet points. Then "To qualify for the role, you must have..." That's Requirements/Qualifications. We'll have maybe

Requirements

or

Qualifications

. The instruction includes both Requirements and Qualifications headings. We need to decide which to use. The content includes degree, experience, portfolio, proficiency, etc. That's qualifications. Could put under Qualifications. Also there is "What We Look For" which is similar to skills/attributes. Might be redundant. Then "What We Offer You At EY..." includes compensation and benefits, base salary range, total rewards, vacation policy. That's Benefits and Pay sections. We need to separate Pay and Benefits if content exists. The posting includes base salary range (Pay) and benefits (medical, dental, pension, 401k, paid time off, flexible vacation). So we can have

Pay

with salary ranges, and

Benefits

with medical/dental etc. Also there is mention of travel up to 80% (maybe Schedule? Actually travel is not schedule. Could be under Requirements? Might be a note. But we only create Schedule if posting states schedule (like full-time, part-time, shift). Not present. So omit Schedule. We must not include boilerplate like EEO, equal opportunity, scam warning, etc. Also remove duplicated lines, navigation, cookie, legal. Also remove "Apply today", "To make the most of your application experience..." etc. Also remove "EY | Building a better working world" etc. Now we need to preserve all substantive information. Let's extract. First, location: "Location: Anywhere in Country". Might be considered metadata; we can fold into a short

or drop. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So we can include a short

for location maybe. But location is not a heading. We'll include a

with location. Now the descriptive paragraphs: - "At EY, we’re all in to shape your future with confidence. We’ll help you succeed in a globally connected powerhouse of diverse teams and take your career wherever you want it to go. Join EY and help to build a better working world. EY is a leader in serving the global financial services marketplace and the only professional services firm with a separate business unit dedicated to the financial services industry – the Financial Services Organization (FSO). Our focused model and bold ambition have put us at the center of the events that continue to reshape and redefine our industry, working side by side with a range of clients from our most venerable institutions to dynamic new entrants across Banking and Capital Markets, Wealth and Asset Management, Insurance, and Real Estate, Hospitality and Construction. Our purpose is to help build a financial services industry in which financial institutions are trusted and flourish, and the global economy is healthy, growing, and secure. If you have a passion for rallying together to solve complex challenges, then join our dynamic FSO team!" That's about EY and the team. - "The opportunity The Product and Experience Design (PxD) Team, part of the Platforms competency within FSO Technology Consulting, works collaboratively with clients to transform their businesses through disruptive innovation and human-centered design..." etc. We can combine these into About the role. Now Responsibilities: bullet list from "Your Key Responsibilities". Let's extract each bullet: - As a Senior Product Designer, you are the design lead for a workstream. - You work within a multidisciplinary team of researchers, technologists, product managers, and engagement team members. - You own the design of a workstream end to end, from framing the problem with the client to writing specifications engineers can build from. - You are the designer the client works with day to day, and you mentor junior designers. - You use AI to move faster through framing, options, prototypes and synthesis, and stay accountable for every decision that reaches a client. - Outside client engagements, you have experience supporting business development activities, such as pursuits and proposals, and practice-building activities such as mentoring colleagues and developing or delivering training. We need to preserve all. We'll output as

• each. Now Skills And Attributes For Success: bullet list (some are long sentences). Let's extract: - AI-first design craft: Take work from research, problem framing, user flows and high-fidelity design to production-ready Figma files with end-to-end coverage. Use LLMs and AI-assisted prototyping tools such as Claude, Cursor or Figma Make to frame problems, generate first-pass options, build live-coded prototypes, iterate collaboratively with users and stakeholders, and speed up synthesis. Judgment stays with you: decide which problem is worth solving, which option is right and why, and review everything for accuracy, accessibility, bias and brand before a client sees it. - Designing AI-enabled and agentic experiences: Design how people hand work to an AI or agentic system, supervise it, and check and correct what it produces. Design how they decide whether to trust it with a financial decision. Treat uncertainty, confidence, error, correction and handoff as states that need designing. Do not simply add a chat window to an existing flow. Build explainability, transparency and human-in-the-loop control into the design from the start, and know when to bring risk, compliance or technology owners into the conversation. - Design systems: Leverage, contribute to, and evolve client design systems and brand guidelines. - Complexity: Design data-heavy, role-based experiences that are used by various client internal and external teams. - Agile delivery and collaboration: Deliver in Agile teams using Jira and other collaborative software platforms. Write clear specifications and acceptance criteria, and flex into requirements of definition when delivery demands it. - Research, evidence, and outcomes: Run lean research to keep work moving. Drive consensus on success measures with product owners and client stakeholders. Follow how features actually perform in use and propose improvement ideas, as necessary. - Client communication: Own the day-to-day client relationship for your workstream. Present clearly to engineers, product owners, and senior business stakeholders. Adjust the level without diluting the argument and taking challenges and feedback well. - Making the case for design: Explain to client stakeholders and internal engagement teams why the design work is needed. Explain what it costs to skip it and what it returns. Use their language, especially with people who have not worked with designers before. - Meeting clients where they are: Assess a client’s design and technology maturity, then tailor your approach. That can range from foundational UX to AI-enabled products. Facilitate workshops and coaching client teams, so the work is sustainable after we leave. We'll put these under Skills. Now Qualifications/Requirements: "To qualify for the role, you must have Bachelor's degree in graphic design, UX Design, Interaction Design, Industrial or Product Design or related field, and 3 years of progressive, post-baccalaureate work experience. Alternatively, will accept a master's degree and 2 years of work experience. A portfolio that shows end-to-end product design: problem framing, interaction design, visual craft and outcomes. Not only finished screens. Advanced proficiency in Figma, including prototyping, components, and design system contribution. Regular use of LLMs in your design process. Comfort working in AI-assisted design and prototyping tools such as Claude, Cursor or Figma Make, even if you do not write production code by hand. Experience designing complex, data-heavy or workflow-driven products. Experience delivering in Agile teams using Jira or equivalent tool. Outstanding written and verbal communication skills. The confidence to present and defend design decisions to senior client stakeholders. The ability to multitask in a fast-paced, collaborative team environment. Requires domestic and regional travel up to 80% to serve client needs. Ideally, you’ll also have Experience in financial services: banking and capital markets, wealth and asset management, insurance, or real estate, hospitality and construction. Experience designing AI-powered or agentic product features that reach production. Familiarity with accessibility standards (WCAG) as they affect design decisions. Experience coaching client teams or building design capability in another organization." We'll put under Qualifications (or Requirements). Since we have both headings available, we could split: Requirements (education/experience) and Qualifications (portfolio, skills). But to keep simple, we can use Qualifications heading and include all. However instruction: "Prefer a few substantive sections over many thin ones." So maybe combine into one Qualifications section. Now Benefits and Pay: From "What We Offer You At EY, we harness our collective strength...". Let's extract: - "We offer a comprehensive compensation and benefits package where you’ll be rewarded based on your performance and recognized for the value you bring to the business." - "The base salary range for this job is: New York City, Boston, and Washington DC Metro Areas, Washington State, and Southern California offices – $120,200 to $180,600 Bay Area California offices – $125,300 to $188,100 All other offices locations in the US, including Sacramento – $100,200 to $165,400 Individual salaries within these ranges are determined through a wide variety of factors including but not limited to education, experience, knowledge, skills and geography." - "In addition, our Total Rewards package includes medical and dental coverage, pension and 401(k) plans, and a wide range of paid time off options." - "Under our flexible vacation policy, you’ll decide how much vacation time you need based on your own personal circumstances. You’ll also be granted time off for designated EY Paid Holidays, Winter/Summer breaks, Personal/Family Care, and other leaves of absence when needed to support your physical, financial, and emotional well-being." Thus Pay: base salary ranges. Benefits: medical/dental, pension/401k, paid time off, flexible vacation policy, holidays, etc. We'll create

  Pay

  with

  containing salary ranges. And

  Benefits

  with
  • for each benefit. Now we must not include sections like "What We Look For" (similar to skills) but we can omit as it's redundant. Also "Are you ready to shape your future with confidence? Apply today." etc - remove. Now we need to output only HTML fragment, no /, no markdown fences. We'll start with location

    . Then

    About the role

    with paragraphs (maybe combine into one

    or multiple). We'll keep as

    . Then

    Res