Senior AI Product Manager
Edward Jones · St Louis, MO · 1 mo ago
RemoteRemoteMarketingFull-time
We need to output HTML fragment with sections: About the role? The posting includes description about company, role description, responsibilities (What You'll Do), requirements (What You'll Need), What Could Set You Apart (maybe Skills or Qualifications), Benefits (Edward Jones' compensation and benefits package...), maybe Schedule (Candidates that live within a commutable distance... expected to work in the office four days per week). Also maybe Pay not mentioned, so omit Pay section. Also maybe include "Qualifications" as heading? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to include sections only when posting has real specific content. So we need to decide which sections to include.
We have:
- About the role: The initial paragraph about Edward Jones and the role description (Senior AI Product Manager shapes...). Could be considered About the role. We'll include.
- Responsibilities: "What You'll Do" list.
- Requirements: "What You'll Need" list.
- Qualifications: maybe combine with Requirements? Could treat "What You'll Need" as Requirements. Qualifications maybe "What Could Set You Apart" as additional qualifications/skills.
- Skills: maybe not separate; we could include Skills under Qualifications? But we can include a Skills section if we have specific skill list. The posting includes many skill items in Requirements and What Could Set You Apart. Could create a Skills section summarizing? But we must not invent or summarize away detail; we must preserve ALL substantive information. So we cannot create a Skills section that just repeats content; we could keep Requirements and Qualifications sections.
- Benefits: The paragraph about benefits.
- Schedule: The sentence about office four days per week.
- Pay: Not mentioned, so omit.
We must not repeat job title as heading. Also must not include Job ID etc.
We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The posting includes EEO statement and some legal bits about criminal history, etc. Those should be removed. Also the "View our Purpose, Inclusion and Citizenship Report." maybe keep? It's part of About the role? It's not boilerplate? It's a link but we can keep as prose? It's not EEO. It's okay.
We must preserve all substantive information: So we need to keep the description of Edward Jones, purpose, etc. Also the note about Fortune 500 footnote. Keep that.
We need to output only HTML fragment, no markdown fences.
Let's structure:
.
Now Requirements: from "What You'll Need":
- Bachelor's degree in a relevant technical, product, analytics, or business field, or equivalent professional experience.
- Five or more years of Product Management experience, including ownership of complex technology, platform, data, digital, or AI products.
- 1+ years of experience with AI, machine learning, generative AI, agentic systems, intelligent automation, AI platforms, or advanced analytics.
- Demonstrated success owning strategic products or reusable capabilities across multiple customers, teams, domains, products, or enterprise workflows.
- Familiarity in at least one AI product specialty, with broad knowledge of enterprise AI technologies, data, platforms, governance, and architecture.
- Product Management skills in strategy, discovery, experimentation, prioritization, roadmaps, analytics, adoption, and lifecycle management.
- Ability to translate complex customer and business needs into product outcomes, technical requirements, evaluation criteria, and prioritized work.
- Experience defining product success measures and evaluating tradeoffs across customer value, feasibility, cost, quality, performance, reuse, risk, and time to value.
- A strong understanding of responsible AI, governance, privacy, security, compliance, model risk, monitoring, and enterprise controls.
- Proven ability to influence leaders, lead cross-functional teams, coach others, and communicate complex topics clearly.
Now Qualifications (What Could Set You Apart):
- Master's degree in a relevant technical, product, or business field.
- Experience leading enterprise AI products or reusable capabilities in financial services or another highly regulated industry.
- Experience with low-code, no-code, and pro-code AI ecosystems, including Microsoft Copilot Studio, Power Platform, Azure AI, Databricks, or comparable technologies.
- Experience defining AI evaluation, monitoring, observability, governance, security, privacy, model-risk,
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to include sections only when posting has real specific content. So we need to decide which sections to include.
We have:
- About the role: The initial paragraph about Edward Jones and the role description (Senior AI Product Manager shapes...). Could be considered About the role. We'll include.
- Responsibilities: "What You'll Do" list.
- Requirements: "What You'll Need" list.
- Qualifications: maybe combine with Requirements? Could treat "What You'll Need" as Requirements. Qualifications maybe "What Could Set You Apart" as additional qualifications/skills.
- Skills: maybe not separate; we could include Skills under Qualifications? But we can include a Skills section if we have specific skill list. The posting includes many skill items in Requirements and What Could Set You Apart. Could create a Skills section summarizing? But we must not invent or summarize away detail; we must preserve ALL substantive information. So we cannot create a Skills section that just repeats content; we could keep Requirements and Qualifications sections.
- Benefits: The paragraph about benefits.
- Schedule: The sentence about office four days per week.
- Pay: Not mentioned, so omit.
We must not repeat job title as heading. Also must not include Job ID etc.
We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The posting includes EEO statement and some legal bits about criminal history, etc. Those should be removed. Also the "View our Purpose, Inclusion and Citizenship Report." maybe keep? It's part of About the role? It's not boilerplate? It's a link but we can keep as prose? It's not EEO. It's okay.
We must preserve all substantive information: So we need to keep the description of Edward Jones, purpose, etc. Also the note about Fortune 500 footnote. Keep that.
We need to output only HTML fragment, no markdown fences.
Let's structure:
About the role
... (company description and role overview)
Responsibilities
- ... each bullet from What You'll Do
Requirements
- ... each bullet from What You'll Need
Qualifications
- ... each bullet from What Could Set You Apart
Benefits
... benefits paragraph
Schedule
... sentence about office four days per week
We need to ensure we don't include filler like "commensurate with experience". Not present. Check for any duplicated lines: The posting repeats some sentences? Not sure. We must remove EEO etc. So we will cut out: - "Edward Jones does not discriminate on the basis of race, color, gender, religion, national origin, age, disability, sexual orientation, pregnancy, veteran status, genetic information or any other basis prohibited by applicable law." - The paragraph about criminal history, background reviews, etc. - The link to Los Angeles County Fair Chance Ordinance. - The "Qualified applicants with arrest or conviction records will be considered..." etc. - Also the "Edward Jones' compensation and benefits package includes..." we keep as Benefits. - The "Edward Jones offers a 401k retirement plan..." keep. - The "Edward Jones observes ten paid holidays..." keep. - The "All associates are eligible for the firm's Employee Assistance Program." keep. - The "For more information on the Benefits available to Edward Jones associates, please visit our benefits page." maybe keep as part of Benefits? It's a reference; we can keep. We must also remove duplicated lines like "Check out our U.S. awards and accolades: Insights & Information Blog Postings about Edward Jones" and same for Canadian. Those are maybe not substantive? They are promotional but could be considered part of About the role? Might be considered boilerplate? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Those award lines might be considered promotional but not boilerplate; they are not duplicated? They appear twice (US and Canada). Could be considered duplicated lines? They are similar but not identical. Might be considered promotional content; but we can keep them as part of About the role? Might be okay. However they are not essential to job description; but they are not explicitly prohibited. Safer to keep them? The instruction says remove duplicated lines. Those two lines are similar but not identical; they mention US and Canada awards. Might be considered duplicated structure but different content. I'd keep them. We also need to remove "Join a financial services firm where your contributions are valued." That's part of About the role. Now craft the About the role paragraph: Should include the initial sentences: "This job posting is anticipated to remain open for 30 days, from 22-Sep-2026. The posting may close early due to the volume of applicants. Join a financial services firm where your contributions are valued. Edward Jones is a Fortune 500¹ company where people come first. With over 9 million clients and 20,000 financial advisors across the U.S. and Canada, we’re proud to be privately-owned, placing the focus on our clients rather than shareholder returns. Behind everything we do is our purpose: We partner for positive impact to improve the lives of our clients and colleagues, and together, better our communities and society. We are an innovative, flexible, and inclusive organization that attracts, develops, and inspires performance excellence and a sense of belonging. People are at the center of our partnership. Edward Jones associates are seen, heard, respected, and supported. This is what we believe makes us the best place to start or build your career. View our Purpose, Inclusion and Citizenship Report. ¹Fortune 500, published June 2024, data as of December 2023. Compensation provided for using, not obtaining, the rating. The Senior AI Product Manager shapes and leads the firm's most complex and strategically significant enterprise AI products and reusable AI capabilities serving multiple products, business domains, customer experiences, and enterprise workflows. This role treats AI as the product and owns strategy, discovery, prioritization, adoption, lifecycle management, and measurable outcomes. Operating with significant autonomy, the Senior Lead sets product direction and ensures scalable AI solutions create measurable value. This role may be accountable for one or more strategic AI product or capability domains. Based on organizational priorities, customer needs, and business strategy, these domains may enable AI creation and adoption; deliver AI-powered experiences; provide trusted information and intelligence; drive automation and decision support; or ensure governance, reliability, and operations. Products and services may evolve over time and can include models, agents, skills, functions, tools, knowledge assets, retrieval capabilities, builder experiences, low-code solutions, platform capabilities, governance services, observability capabilities, and other emerging AI technologies. The role influences strategy across interconnected AI products, helps shape enterprise AI direction, and advises business, technology, product, risk, and operational leaders. You will partner across Engineering, Data, Product Management, Architecture, Experience, Risk, and Business areas to deliver customer and business value while ensuring capabilities are scalable, reusable, explainable, measurable, and aligned with responsible AI practices. The Senior AI Product Manager also strengthens AI Product Management across the organization through product leadership, coaching, mentoring, collaboration, and advancement of best practices." That's a lot but we need to preserve all substantive information. So we include that as About the role. Now Responsibilities: list each bullet from "What You'll Do". Let's extract: - Set the vision, value proposition, outcomes, priorities, and roadmap for strategic AI products and capability domains. - Translate customer needs and business priorities into scalable AI product strategies, investment recommendations, product outcomes, requirements, evaluation criteria, and prioritized work. - Identify opportunities, dependencies, risks, overlaps, and tradeoffs across interconnected AI products and capabilities. - Own strategic AI products across the lifecycle, from discovery and launch through adoption, optimization, and retirement. - Define customers, use cases, value propositions, success measures, constraints, service expectations, and lifecycle plans. - Lead continuous discovery to identify customer problems, unmet needs, reusable patterns, and high-value AI opportunities. - Test product hypotheses through research, prototypes, experiments, evaluations, proofs of concept, and pilots. Use customer evidence, product data, technical findings, and business measures to recommend whether to pursue, change, scale, pause, or stop an opportunity. - Define the product experience, including AI behavior, data and knowledge needs, integrations, human oversight, controls, monitoring, and support. - Partner with Engineering, Data, AI Science, Architecture, Cybersecurity, Experience, and Business teams to evaluate options, challenge assumptions, identify dependencies, and make informed tradeoffs. - Promote reusable, interoperable patterns across models, agents, skills, knowledge assets, workflows, platforms, and governance capabilities. - Recognize and address AI limitations and risks, including unreliable outputs, bias, data leakage, inappropriate actions, security threats, model drift, and workflow failure. - Define and monitor measures for customer value, business outcomes, adoption, reuse, quality, reliability, cost, operational performance, scalability, and risk. - Embed responsible AI, privacy, security, legal, regulatory, accessibility, records, and model-risk requirements throughout the product lifecycle. Define intended uses, limitations, potential misuse or harm, data sensitivity, autonomy, access, human oversight, controls, and escalation paths. - Communicate product outcomes, health, risks, assumptions, dependencies, tradeoffs, and lessons learned to senior technical and nontechnical leaders and stakeholders; serve as a trusted advisor on complex AI opportunities and decisions. We need to ensure each bullet is a