Financial Services - Technology Consulting - Product Manager - Manager
EY · Arlington, VA · 1 mo ago
Hybrid$151k–$252k/yrFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule only if present. The posting includes location line, description, etc. No explicit Benefits, Pay, Schedule. There's travel requirement but not schedule. No benefits listed. So we should not create those sections.
We need headings: About the role, Responsibilities, Requirements, Skills (maybe Skills And Attributes For Success). Also maybe Qualifications? The posting includes "To qualify for the role you must have..." that's qualifications. Could put under Requirements or Qualifications. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can choose which sections have content.
We have About the role: description of team, opportunity. We'll put that.
Responsibilities: "Your Key Responsibilities" block.
Requirements: qualifications (education, experience) plus maybe travel? Travel is requirement? Could be under Requirements.
Skills: "Skills And Attributes For Success" block.
We should not repeat job title. No Job ID.
We must preserve all substantive information, not invent. Remove boilerplate: location line? It's location: Anywhere in Country. That's minor metadata; we can fold into short p or drop. Probably include as a short p at top? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we can include location as a short p. We need to output only HTML fragment, no html/body tags. Let's craft:
Location: Anywhere in Country
About the role
... paragraphs from the opportunity section ...
Responsibilities
- ... each responsibility ...
Requirements
- ... education/experience ...
- ... travel up to 80% ...
Skills
- ... each skill bullet ...
- ...
- for any list of duties/requirements/benefits. The Skills section is a list of attributes; we should make list items. However the text is not clearly delimited. We could still make each sentence as a li by inserting periods. But we need to preserve all substantive information; we can keep as a paragraph inside
maybe acceptable? The rule says use
- for any list of duties/requirements/benefits. Skills is a list; we should use list. We'll try to parse. Let's manually split based on known headings: "Strategy and Organization", "Technology Delivery", "Product Enablement", "Core Consulting". Each heading seems to start a new category. We'll create list items under each heading. Strategy and Organization bullet points: - Develop product and AI strategies that align with business objectives, identify where AI can create differentiated customer or business value, and account for technology, data, experience design, risk and adoption considerations. - Define product organization and operating models, including product taxonomy, organizational structure, funding methods, product delivery processes, governance models and decision rights, that help clients allocate funding, prioritize work and improve delivery quality and efficiency. - Incorporate the roles, skills, human and agent authorities, controls and ways of working required for AI-enabled product development. - Improve portfolio management by using product metrics, OKRs and AI-enabled insight generation to compare opportunities, test assumptions, align investment to business objectives and increase the transparency and traceability of decisions and outcomes. Technology Delivery: - Drive technology delivery by using AI-enabled research synthesis and requirements tools to translate product vision, customer insights, business rules, process information and enterprise knowledge into traceable business requirements, user stories and acceptance criteria; validate generated outputs with subject-matter experts; and prioritize backlogs and maintain roadmaps. - Lead cross-functional teams of designers, engineers, data and AI specialists, risk professionals and testers through the product and software development lifecycles, using AI-assisted prototyping and simulation to test concepts, workflows and value hypotheses before scaling implementation and deployment. - Advocate for and operationalize cross-functional practices including user testing, experimentation, functional and regression test automation, AI model and agent evaluations, and alignment with industry, client, risk and regulatory standards. Product Enablement: - Use traditional and AI-enabled product management tools (JIRA, Azure DevOps, Aha!, Productboard and requirements repositories, as well as AI assistants, enterprise knowledge tools and prototype-driven development platforms) to support discovery, prioritize opportunities, develop requirements, test concepts and deliver technology solutions. - Use product analytics software and frameworks, such as Pendo and Amplitude, together with AI-enabled qualitative and quantitative analysis, to synthesize user feedback, research,