Senior Associate, Product & Solution Design
KPMG US · Providence, RI · 1 mo ago
HybridFull-time
We need to output HTML fragment with headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content.
We need to parse the posting.
First, there is introductory paragraph about KPMG being great place to work etc. That could be "About the role" maybe? Actually "About the role" is typical heading for description of role. The posting includes: "KPMG is currently seeking a Senior Associate Product & Solution Design to join our Digital Office within the Legal, Risk Management and Compliance organization." That's about the role. Also earlier paragraph about KPMG being great place to work etc. Could be part of About the role or maybe we can include as About the role.
We need to avoid repeating job title as heading. So we will not put the title as heading.
We need sections: Responsibilities (list). Qualifications (list). Skills maybe separate? The posting includes Qualifications list with bullet-like sentences. Also there is "Experience facilitating stakeholder discovery sessions..." etc. That's qualifications. There's also "Strong visual communication..." etc. That's also qualifications/skills. There's also "Must be authorized to work in the U.S. without the need for employment-based visa sponsorship..." That's a requirement (maybe Qualifications). Also there is benefits paragraph: "In addition, KPMG is proud to offer a comprehensive, competitive benefits package..." plus details about medical, dental, vision, disability, life insurance, 401(k), personal well-being benefits, PTO, holidays, breaks. That's Benefits section.
Pay: The posting mentions salary ranges: "KPMG LLP and its subsidiaries (“KPMG”) complies with all local/state regulations regarding displaying salary ranges. If required, the ranges displayed below or via the URL below are specifically for those potential hires who will work in the location(s) listed. Any offered salary is determined based on relevant factors..." plus link to salary ranges. There's no explicit numbers but they say ranges displayed below or via URL. There's no actual numbers in the text. The instruction: 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. For Pay, they do mention salary ranges and a link, but no actual numbers. Is that considered stating them? They say "If required, the ranges displayed below or via the URL below are specifically for those potential hires who will work in the location(s) listed." That implies there may be ranges displayed elsewhere (maybe not in this snippet). Since we don't have actual numbers, we might consider that as not specific content. The instruction says never create Pay section unless posting actually states them. It does state that ranges are displayed below or via URL, but not giving them. Might be considered not specific enough. Safer to omit Pay section.
Schedule: They mention "Depending on job classification, standard work hours, and years of service, KPMG provides Personal Time Off per fiscal year. Additionally, each year KPMG publishes a calendar of holidays to be observed during the year and provides eligible employees two breaks each year where employees will not be required to use Personal Time Off; one is at year end and the other is around the July 4th holiday." That's about PTO and holidays, which is more benefits than schedule. There's no explicit schedule like "full-time", "Monday-Friday 9-5". So we should not create Schedule section.
Benefits: we have details about benefits, so include Benefits section.
Skills: Could we separate skills from qualifications? The qualifications list includes many skill-like items. Could we make a Skills section for things like "Strong visual communication, presentation, facilitation, storytelling, analytical, and problem-solving capabilities..." etc. But the instruction: Prefer a few substantive sections over many thin ones. So maybe combine Qualifications and Skills into one Qualifications section. However they ask to use headings for Skills if there is real specific content. We could have Qualifications (education, experience) and Skills (competencies). But we risk thin sections. Let's see if we can split meaningfully.
Qualifications: Minimum five years of recent experience in product design, UX/UI design, digital solution design, business analysis, product management, or related discipline; Bachelor's degree in ... or five years equivalent professional experience; Experience facilitating stakeholder discovery sessions...; Prior experience creating and iterating prototypes using modern design and prototyping tools, with experience in AI-assisted design or development platforms such as Lovable, Microsoft Copilot, or similar technologies; Understanding of modern web applications, AI-enabled solutions, workflow automation, data visualization, and enterprise technology platforms, along with ability to collaborate effectively with developers, architects, product managers, and other technical resources; Must be authorized to work in the U.S. without the need for employment-based visa sponsorship now or in the future. (visa sponsorship note)
Skills: Strong visual communication, presentation, facilitation, storytelling, analytical, and problem-solving capabilities with a user-centered design mindset, ability to work effectively in ambiguous environments and rapidly iterate from concept through prototype, experience with tools such as Figma, Miro, Power Platform, or similar design and collaboration platforms preferred, and familiarity with Agile, product development, or human-centered design practices preferred.
That seems like a distinct set of soft skills and tool experience. Could be a Skills section.
Thus we can have sections: About the role (maybe short paragraph), Responsibilities, Qualifications, Skills, Benefits.
We need to ensure we don't include filler like "commensurate with experience". Not present.
Now we need to output HTML fragment only, no /, no markdown fences.
We'll produce:
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content.
We need to parse the posting.
First, there is introductory paragraph about KPMG being great place to work etc. That could be "About the role" maybe? Actually "About the role" is typical heading for description of role. The posting includes: "KPMG is currently seeking a Senior Associate Product & Solution Design to join our Digital Office within the Legal, Risk Management and Compliance organization." That's about the role. Also earlier paragraph about KPMG being great place to work etc. Could be part of About the role or maybe we can include as About the role.
We need to avoid repeating job title as heading. So we will not put the title as heading.
We need sections: Responsibilities (list). Qualifications (list). Skills maybe separate? The posting includes Qualifications list with bullet-like sentences. Also there is "Experience facilitating stakeholder discovery sessions..." etc. That's qualifications. There's also "Strong visual communication..." etc. That's also qualifications/skills. There's also "Must be authorized to work in the U.S. without the need for employment-based visa sponsorship..." That's a requirement (maybe Qualifications). Also there is benefits paragraph: "In addition, KPMG is proud to offer a comprehensive, competitive benefits package..." plus details about medical, dental, vision, disability, life insurance, 401(k), personal well-being benefits, PTO, holidays, breaks. That's Benefits section.
Pay: The posting mentions salary ranges: "KPMG LLP and its subsidiaries (“KPMG”) complies with all local/state regulations regarding displaying salary ranges. If required, the ranges displayed below or via the URL below are specifically for those potential hires who will work in the location(s) listed. Any offered salary is determined based on relevant factors..." plus link to salary ranges. There's no explicit numbers but they say ranges displayed below or via URL. There's no actual numbers in the text. The instruction: 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. For Pay, they do mention salary ranges and a link, but no actual numbers. Is that considered stating them? They say "If required, the ranges displayed below or via the URL below are specifically for those potential hires who will work in the location(s) listed." That implies there may be ranges displayed elsewhere (maybe not in this snippet). Since we don't have actual numbers, we might consider that as not specific content. The instruction says never create Pay section unless posting actually states them. It does state that ranges are displayed below or via URL, but not giving them. Might be considered not specific enough. Safer to omit Pay section.
Schedule: They mention "Depending on job classification, standard work hours, and years of service, KPMG provides Personal Time Off per fiscal year. Additionally, each year KPMG publishes a calendar of holidays to be observed during the year and provides eligible employees two breaks each year where employees will not be required to use Personal Time Off; one is at year end and the other is around the July 4th holiday." That's about PTO and holidays, which is more benefits than schedule. There's no explicit schedule like "full-time", "Monday-Friday 9-5". So we should not create Schedule section.
Benefits: we have details about benefits, so include Benefits section.
Skills: Could we separate skills from qualifications? The qualifications list includes many skill-like items. Could we make a Skills section for things like "Strong visual communication, presentation, facilitation, storytelling, analytical, and problem-solving capabilities..." etc. But the instruction: Prefer a few substantive sections over many thin ones. So maybe combine Qualifications and Skills into one Qualifications section. However they ask to use headings for Skills if there is real specific content. We could have Qualifications (education, experience) and Skills (competencies). But we risk thin sections. Let's see if we can split meaningfully.
Qualifications: Minimum five years of recent experience in product design, UX/UI design, digital solution design, business analysis, product management, or related discipline; Bachelor's degree in ... or five years equivalent professional experience; Experience facilitating stakeholder discovery sessions...; Prior experience creating and iterating prototypes using modern design and prototyping tools, with experience in AI-assisted design or development platforms such as Lovable, Microsoft Copilot, or similar technologies; Understanding of modern web applications, AI-enabled solutions, workflow automation, data visualization, and enterprise technology platforms, along with ability to collaborate effectively with developers, architects, product managers, and other technical resources; Must be authorized to work in the U.S. without the need for employment-based visa sponsorship now or in the future. (visa sponsorship note)
Skills: Strong visual communication, presentation, facilitation, storytelling, analytical, and problem-solving capabilities with a user-centered design mindset, ability to work effectively in ambiguous environments and rapidly iterate from concept through prototype, experience with tools such as Figma, Miro, Power Platform, or similar design and collaboration platforms preferred, and familiarity with Agile, product development, or human-centered design practices preferred.
That seems like a distinct set of soft skills and tool experience. Could be a Skills section.
Thus we can have sections: About the role (maybe short paragraph), Responsibilities, Qualifications, Skills, Benefits.
We need to ensure we don't include filler like "commensurate with experience". Not present.
Now we need to output HTML fragment only, no /, no markdown fences.
We'll produce:
About the role
KPMG is currently seeking a Senior Associate Product & Solution Design to join our Digital Office within the Legal, Risk Management and Compliance organization. Known for being a great place to work and build a career, KPMG provides audit, tax and advisory services for organizations in today's most important industries. Our growth is driven by delivering real results for our clients. It's also enabled by our culture, which encourages individual development, embraces an inclusive environment, rewards innovative excellence and supports our communities. With qualities like those, it's no wonder we're consistently ranked among the best companies to work for by Fortune Magazine, Consulting Magazine, Seramount, Fair360 and others.
But we need to avoid repeating job title as heading; we are not using it as heading, fine. Now Responsibilities: list items. We need to extract each responsibility sentence from the "Responsibilities:" block. The block: Responsibilities: Develop wireframes, mockups, and interactive prototypes to visualize and validate solution concepts, creating rapid prototypes using AI-assisted design and development tools such as Lovable and similar platformsIterate designs and prototypes based on stakeholder feedback and evolving requirements while communicating solution concepts and user experiences through clear visual storytelling and design artifactsParticipate in client discovery sessions to understand business needs, user pain points, workflows, and desired outcomes, help stakeholders refine and articulate ideas, requirements, and opportunities that may initially be loosely definedTranslate business needs into user journeys, workflows, and solution concepts while identifying appropriate technologies, tools, and capabilities to address business challengesPartner with developers, AI/agent developers, data resources, and solution architects to ensure solutions are practical and buildable, documenting key workflows, functionality, requirements, and design decisions to support development effortsHelp distinguish near-term requirements from future enhancements and evolving capabilities, contributing to reusable design patterns, standards, and practices across the LRMC Digital product portfolioAct with integrity, professionalism, and personal responsibility to uphold KPMG's respectful and courteous work environment Note there are no spaces after commas? Actually the text seems concatenated without spaces after commas? Let's parse manually: "Develop wireframes, mockups, and interactive prototypes to visualize and validate solution concepts, creating rapid prototypes using AI-assisted design and development tools such as Lovable and similar platforms" "Iterate designs and prototypes based on stakeholder feedback and evolving requirements while communicating solution concepts and user experiences through clear visual storytelling and design artifacts" "Participate in client discovery sessions to understand business needs, user pain points, workflows, and desired outcomes, help stakeholders refine and articulate ideas, requirements, and opportunities that may initially be loosely defined" "Translate business needs into user journeys, workflows, and solution concepts while identifying appropriate technologies, tools, and capabilities to address business challenges" "Partner with developers, AI/agent developers, data resources, and solution architects to ensure solutions are practical and buildable, documenting key workflows, functionality, requirements, and design decisions to support development efforts" "Help distinguish near-term requirements from future enhancements and evolving capabilities, contributing to reusable design patterns, standards, and practices across the LRMC Digital product portfolio" "Act with integrity, professionalism, and personal responsibility to uphold KPMG's respectful and courteous work environment" We'll make- for each. Now Qualifications: list items. Qualifications block: Qualifications: Minimum five years of recent experience in product design, UX/UI design, digital solution design, business analysis, product management, or related disciplineBachelor's degree in Product Design, User Experience Design, Human-Computer Interaction, Information Systems, Business, Computer Science, or a related field, or five years equivalent professional experienceExperience facilitating stakeholder discovery sessions, workshops, or requirements gathering activities, with demonstrated ability to translate business needs into user journeys, workflows, wireframes, prototypes, and digital solution conceptsPrior experience creating and iterating prototypes using modern design and prototyping tools, with experience in AI-assisted design or development platforms such as Lovable, Microsoft Copilot, or similar technologiesUnderstanding of modern web applications, AI-enabled solutions, workflow automation, data visualization, and enterprise technology platforms, along with ability to collaborate effectively with developers, architects, product managers, and other technical resourcesStrong visual communication, presentation, facilitation, storytelling, analytical, and problem-solving capabilities with a user-centered design mindset, ability to work effectively in ambiguous environments and rapidly iterate from concept through prototype, experience with tools such as Figma, Miro, Power Platform, or similar design and collaboration platforms preferred, and familiarity with Agile, product development, or human-centered design practices preferredMust be authorized to work in the U.S. without the need for employment-based visa sponsorship now or in the future. KPMG LLP will not sponsor applicants for U.S. work visa status for this opportunity (no sponsorship is available for H-1B, L-1, TN, O-1, E-3, H-1B1, F-1, J-1, OPT, CPT or any other employment-based visa) Again concatenated without spaces. We need to split into logical items. Let's split by capital letters after a period? Actually there are no periods. We'll need to infer items. Better to separate as: - Minimum five years of recent experience in product design, UX/UI design, digital solution design, business analysis, product management, or related discipline - Bachelor's degree in Product Design, User Experience Design, Human-Computer Interaction, Information Systems, Business, Computer Science, or a related field, or five years equivalent professional experience - Experience facilitating stakeholder discovery sessions, workshops, or requirements gathering activities, with demonstrated ability to translate business needs into user journeys, workflows, wireframes, prototypes, and digital solution concepts - Prior experience creating and iterating prototypes using modern design and prototyping tools, with experience in AI-assisted design or development platforms such as Lovable, Microsoft Copilot, or similar technologies - Understanding of modern web applications, AI-enabled solutions, workflow automation, data visualization, and enterprise technology platforms, along with ability to collaborate effectively with developers, architects, product managers, and other technical resources - Strong visual communication, presentation, facilitation, storytelling, analytical, and problem-solving capabilities with a user-centered design mindset, ability to work effectively in ambiguous environments and rapidly iterate from concept through prototype, experience with tools such as Figma, Miro, Power Platform, or similar design and collaboration platforms preferred, and familiarity with Agile, product development, or human-centered design practices preferred - Must be authorized to work in the U.S.