Financial Services - Technology Consulting - Product Designer - Senior
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have "About the role" heading and include the description of the role/team.
Then "The opportunity" paragraph describing Product and Experience Design Team. That could be part of About the role.
Then "Your Key Responsibilities" list: we need to extract bullet points.
Then "Skills And Attributes For Success" list: many bullet points.
Then "To qualify for the role, you must have ..." that's qualifications/requirements.
Then "What We Look For" maybe part of Skills? Could be separate but we can combine.
Then "What We Offer You At EY..." includes benefits and compensation. There's base salary range details -> Pay section. Also benefits: medical/dental, pension/401k, paid time off, flexible vacation policy, holidays, etc. That's Benefits.
Schedule? Not mentioned except travel up to 80% domestic and regional travel. That's not schedule. No explicit schedule. So we should not create Schedule section unless posting actually states it. It does not. So omit Schedule.
Also we need to include Pay section: we have base salary ranges for different locations. Must include that.
We must not include boilerplate like EEO, legal, etc. Remove those at end.
We must not include application instructions like "Apply today", "limit yourself to two applications", etc. Remove.
We must not include duplicated lines.
We need to preserve all substantive information: So we need to keep the description of role, responsibilities, skills, qualifications, benefits, pay.
We need to format using headings, - for lists,
for prose.
We must not invent or summarize away detail. Must keep details like specific tools (Claude, Cursor, Figma Make), etc.
Let's extract.
About the role: combine the introductory paragraphs and "The opportunity" paragraph.
Intro: "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!"
Then "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. Our designers, researchers, technologists and strategists work together to create superior apps, websites and software, supported by research, brand strategy, and a clear understanding of business and user needs. Our clients are at different points in their AI adoption journey, but we design AI first. Our work starts in an LLM, moves quickly into prototypes, and lands in Figma for systems and polish. We also design the AI-enabled and agentic experiences our clients are bringing to market. We’re looking for a talented and collaborative Senior Product Designer who loves working with and learning from a multidisciplinary team, creates exceptional experiences, and excels at communicating with clients."
We can combine into a few paragraphs.
Responsibilities: list from "Your Key Responsibilities". Let's extract bullet points:
- 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 keep each as
- .
Skills And Attributes For Success: many bullet points. Let's extract each bullet:
- 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 need to keep each as separate
- . Some are long sentences; that's fine.
Qualifications: "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."
We need to separate into Requirements and Qualifications? The instruction includes both Requirements and Qualifications headings. We can put the degree/experience etc under Qualifications, and maybe the skills like Figma proficiency etc under Skills? But we already have Skills section for attributes. However the qualifications list includes many items that could be considered requirements. To follow instruction, we can have both Requirements and Qualifications sections if there is distinct content. But we risk duplication. Let's see: The qualifications paragraph includes degree/experience, portfolio, Figma proficiency, LLM use, comfort with AI-assisted tools, experience designing complex data-heavy workflow-driven products, experience delivering in Agile teams using Jira, outstanding communication skills, confidence to present, ability to multitask, travel requirement. Many of these overlap with Skills list (e.g., Figma proficiency, LLM use, Jira, communication). However we can still separate: Qualifications could be the formal education/experience and portfolio; Requirements could be the specific skills/experience like Figma, LLMs, Jira, communication, travel. But the instruction says prefer a few substantive sections over many thin ones. So maybe we combine into one section called "Requirements and Qualifications" but we only allowed headings from list. Could we use "Qualifications" for the degree/experience and portfolio, and "Skills" for the rest? That seems reasonable.
Thus:
Qualifications
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, 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.
Then Skills
we already have from Skills And Attributes For Success. But we also need to include items like "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."
These could be added to Skills list as - items.
But we already have a long Skills list from Attributes. We can merge them, ensuring no duplication.
Let's compile final Skills list items:
From Attributes:
1. 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.
2. 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.
3. 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
- for lists,
for prose. We must not invent or summarize away detail. Must keep details like specific tools (Claude, Cursor, Figma Make), etc. Let's extract. About the role: combine the introductory paragraphs and "The opportunity" paragraph. Intro: "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!" Then "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. Our designers, researchers, technologists and strategists work together to create superior apps, websites and software, supported by research, brand strategy, and a clear understanding of business and user needs. Our clients are at different points in their AI adoption journey, but we design AI first. Our work starts in an LLM, moves quickly into prototypes, and lands in Figma for systems and polish. We also design the AI-enabled and agentic experiences our clients are bringing to market. We’re looking for a talented and collaborative Senior Product Designer who loves working with and learning from a multidisciplinary team, creates exceptional experiences, and excels at communicating with clients." We can combine into a few paragraphs. Responsibilities: list from "Your Key Responsibilities". Let's extract bullet points: - 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 keep each as
- . Skills And Attributes For Success: many bullet points. Let's extract each bullet: - 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 need to keep each as separate
- . Some are long sentences; that's fine.
Qualifications: "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."
We need to separate into Requirements and Qualifications? The instruction includes both Requirements and Qualifications headings. We can put the degree/experience etc under Qualifications, and maybe the skills like Figma proficiency etc under Skills? But we already have Skills section for attributes. However the qualifications list includes many items that could be considered requirements. To follow instruction, we can have both Requirements and Qualifications sections if there is distinct content. But we risk duplication. Let's see: The qualifications paragraph includes degree/experience, portfolio, Figma proficiency, LLM use, comfort with AI-assisted tools, experience designing complex data-heavy workflow-driven products, experience delivering in Agile teams using Jira, outstanding communication skills, confidence to present, ability to multitask, travel requirement. Many of these overlap with Skills list (e.g., Figma proficiency, LLM use, Jira, communication). However we can still separate: Qualifications could be the formal education/experience and portfolio; Requirements could be the specific skills/experience like Figma, LLMs, Jira, communication, travel. But the instruction says prefer a few substantive sections over many thin ones. So maybe we combine into one section called "Requirements and Qualifications" but we only allowed headings from list. Could we use "Qualifications" for the degree/experience and portfolio, and "Skills" for the rest? That seems reasonable.
Thus:
Qualifications
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, 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.
ThenSkills
we already have from Skills And Attributes For Success. But we also need to include items like "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." These could be added to Skills list as - items. But we already have a long Skills list from Attributes. We can merge them, ensuring no duplication. Let's compile final Skills list items: From Attributes: 1. 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. 2. 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. 3. 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