Manager, Product Manager, Audit Insights & Innovation, AI and Data Engineering

We need to output only HTML fragment, no markdown fences. Must include sections only when posting has real specific content. We need to extract sections: About the role (maybe "About The Role And Team"), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to parse the posting. First, job title: "Product Management at Capital One". Not to repeat as heading. We need to include headings for sections that have content. Let's identify content: - About the role and team: The paragraph starting "About The Role And Team" and subsequent paragraphs describing role, responsibilities, etc. This could be considered "About the role". Could also be "Responsibilities". But we need to decide. The posting includes: "As a Product Manager, you will bridge the gap..." etc. Also bullet-like paragraphs about learning essentials: Human Centered, Business Focused, Technology Driven, Transformational Leadership. Those are like responsibilities/skills. Then "We want you if you are:" list of traits: Intellectually Curious, Communicator & Influencer, Do-er, Passionate & Customer Focus, Learner, Team Player. Those are like qualifications/skills. Then "Basic Qualifications:" with degree requirements. Then "Preferred Qualifications:" with experience translating business strategy. Then salary info: Pay ranges for locations. Then benefits: mention of comprehensive benefits, incentive compensation. No explicit schedule. Thus we can create sections: - About the Role (maybe combine role description) - Responsibilities (maybe the Human Centered etc bullet points) - Qualifications (Basic and Preferred) - Skills (traits list) - Benefits (benefits + incentive) - Pay (salary ranges) We must not create sections with filler like "Schedule" if not present. We must not repeat job title as heading. We must not include metadata like Job ID. We must not include boilerplate like EEO, etc. Remove those. We must preserve all substantive info; not invent. We need to use

for section headings. Use

• for any list of duties/requirements/benefits, and

  for prose. We need to decide what is a list. The "Human Centered", "Business Focused", etc each have sub-bullets. Could treat each as a list item with subpoints? Might be easier to treat each as a

• containing the description. Similarly the "We want you if you are:" list can be
  • . Basic Qualifications: could be a
    • for each bullet (degree options). Preferred Qualifications: one bullet. Benefits: mention of comprehensive benefits, incentive compensation. Could be a

      describing. Pay: salary ranges: we can list each location as

    • . We must not include fluff like "Learn more at the Capital One Careers website." That's maybe boilerplate but it's substantive? It's a link to learn more about benefits. Might be considered part of benefits section. We can keep it as part of benefits description. We must remove EEO, equal-opportunity, scam-warning, etc. Also remove "No agencies please." etc. Also remove "This role is expected to accept applications for a minimum of 5 business days." That's application instruction? Might be considered boilerplate; we should remove application instructions. The instruction says: remove application instructions. So we should drop that line. Also remove "Capital One is an equal opportunity employer..." etc. Also remove "Capital One promotes a drug-free workplace." etc. Also remove "Capital One will consider for employment qualified applicants with a criminal history..." etc. Also remove accommodation contact lines etc. Also remove "For technical support or questions about Capital One's recruiting process..." etc. Also remove "Capital One does not provide, endorse nor guarantee..." etc. Also remove the note about entities in Canada etc. Now produce HTML. Structure:

      About the Role

      ... description ...

      Maybe we need to include the initial paragraph about product management at Capital One being booming etc. That's also about role? Could be part of About the Role. Let's gather prose for About the Role: First paragraph: "Product Management at Capital One is a booming, vibrant craft that requires reimagining the status quo, finding value creation opportunities, and driving innovative and sustainable customer experiences through technology. We believe our portfolio of businesses and investments in growth and transformation will result in a company with the scale, brand, capabilities, talent, and values to succeed as the digital revolution transforms our society and our industry. Do you dream of well-designed and intuitive products and customer experiences? Do you want to be the one who introduces change to help tens of millions of customers make smarter financial choices? Do you want to change the way people manage their money? If you answered yes to all of these questions, then product management at Capital One may be a fit for you" That's more like a motivational intro; could be part of About the Role. Then "About The Role And Team" heading and following paragraphs: "The Audit Insights and Innovation (I&I) team at Capital One is at the cutting edge of AI, data management, and machine learning, to deliver key risk insights for internal auditors shaping the risk management landscape. You will join a cross-functional team dedicated to modernizing internal audit workflows, by working with full-stack engineering teams and dedicated UI/UX designers. Our team is building products that focus on surfacing critical, real-time insights for auditors throughout the audit lifecycle. As a Product Manager, you will bridge the gap between generative AI capabilities, enterprise-scale design, and specialized domain expertise, navigating a complex regulated landscape to deliver high-impact solutions. This high-visibility role offers the chance to build foundational AI-assisted auditing experiences at one of the nation's leading digital banks. You will own the vision and roadmap of your experience within the Audit Compass application, driving immediate value to auditors." Then "To be successful in this role, you will have experience with understanding and building complex data pipelines and build foundational AI capabilities for all of audit engineering." Then the learning sections: "In this role, you’ll learn the essentials of being a product manager, and we’ll invest in you to grow in four key areas:" followed by Human Centered, Business Focused, Technology Driven, Transformational Leadership each with subpoints. We could treat the four areas as Responsibilities. Thus:

      Responsibilities

      • Human Centered: Collaborate with tech teams to build comprehensive acceptance criteria, identifying and elevating any need for additional research to define future feature design; Breakdown business epics into features and further into user stories, driving your team towards lowest effort or Minimal Viable Product (MVP) for a valid feature test
      • Business Focused: Demonstrating a growth mindset, you’ll effectively use hypothesis-driven assessment of data to ensure your product or feature delivers on real business needs; Own and prioritize feature development roadmaps, ensuring all necessary processes and procedures are followed to manage risk
      • Technology Driven: Work autonomously in an agile environment, to conduct research and develop features that utilize new and evolving technology; Collaborate with designers, technologists, data scientists and subject-matter experts to build cutting edge solutions to help customers; Deliver well-managed product platforms for customers by seeking to understand technology trends and architecture strategy
      • Transformational Leadership: By actively participating in horizontal forums, you’ll harness a network of trusted relationships among tech teams, designers, key internal stakeholders and partner teams; Articulate a succinct product roadmap to deliver business value and share with w (the text cuts off? It says "share with w". Probably incomplete; we should keep as is? It's incomplete but it's substantive? It's cut off; maybe it's a typo. We should preserve as given: "share with w". We'll keep it.
      But we need to avoid inventing; we must keep the exact text. The original text for Transformational Leadership: "By actively participating in horizontal forums, you’ll harness a network of trusted relationships among tech teams, designers, key internal stakeholders and partner teamsYou’ll articulate a succinct product roadmap to deliver business value and share with w". There's missing space between "teamsYou’ll". We'll keep as is. Now Skills: the "We want you if you are:" list. We'll make

      Skills

      with
      • each trait. Traits: - Intellectually Curious. You ask why, you explore, you're not afraid to blurt out your crazy idea or follow an email chain for weeks to find someone with an answer. Comfortable with ambiguity, a hunger to learn and a seeker of new challenges - Communicator & Influencer. You can communicate complex ideas clearly regardless of your audience. Our team knows their priorities and why they’re doing what they’re doing. You always can rally associates to work with you - Do-er. You’re biased toward action, you try things and sometimes you fail. You can get around roadblocks and stay focused on your goals. You’re well organized, able to multitask and able to prioritize your work - Passionate & Customer Focus. You care about growing others and bringing them together around what’s possible. You get a thrill from the journey of building and shipping products, and you have a desire and ability to connect with our external or internal customers to fully understand their needs - Learner. You have an appetite to learn new things or new technologies all while exhibiting humbleness when the time comes to ask for help - Team Player. You enjoy working with diverse people and driving the team toward a common goal. You have the ability to put the team before yourself and establish long-lasting relationships We need to keep punctuation as is. Now Qualifications: Basic and Preferred. We can combine into one

        Qualifications

        with two sub-sections? But we must use headings only for sections; we could have

        Basic Qualifications

        and

        Preferred Qualifications

        . That's allowed. Thus:

        Basic Qualifications

        • Currently has, or is in the process of obtaining one of the following with an expectation that the required degree will be obtained on or before the scheduled start date: A Bachelor's or Master’s Degree in a quantitative field (Statistics, Economics, Operations Research, Analytics, Mathematics, Computer Science, Computer Engineering, Software Engineering, Mechanical Engineering, Information Systems or a related quantitative field), Business or Marketing OR Bachelor's degree in any field and at least 3 years of Product Management experience
        But the text is long; we can keep as one
      • . Preferred Qualifications:

        Preferred Qualifications

        • Experience translating business strategy and analysis into consumer facing digital products
        • At this time, Capital One will not sponsor a new applicant for employment authorization for this position
        But the sponsorship line maybe considered metadata? It's a qualification about sponsorship; it's substantive. We'll keep. Now Benefits: We have paragraph: "Capital One offers a comprehensive, competitive, and inclusive set of health, financial and other benefits that support your total well-being. Learn more at the Capital One Careers website. Eligibility varies based on full or part-time status, exempt or non-exempt status, and management level." Also earlier: "This role is also eligible to earn performance based incentive compensation, which may include cash bonus(es) and/or long term incentives (LTI). Incentives could be discretionary or non discretionary depending on the plan." We can combine into Benefits section. Thus:

        Benefits

        • Capital One offers a comprehensive, competitive, and inclusive set of health, financial and other benefits that support your total well-being.
        • Eligibility varies based on full or part-time status, exempt or non-exempt status, and management level.
        • This role is also eligible to earn performance based incentive compensation, which may include cash bonus(es) and/or long term incentives (LTI). Incentives could be discretionary or non discretion