Senior Director, Technical Program Management - AI (Remote Eligible)

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule as appropriate. Must only include sections where posting has real specific content. We need to parse the posting. First, job title: Senior Director, Technical Program Management - AI (Remote Eligible). Not to be repeated as heading. We need sections: - About the role: likely the paragraph after "Role::" describing the TPM leading complex initiative. Also earlier paragraph about Capital One mission. That could be About the role. - Responsibilities: The bullet list after "Our TPM Sr. Directors have:" includes many items that are responsibilities/qualities. Those could be responsibilities or qualifications. The posting lists: Strong technical backgrounds..., Experience building and leading..., Lead technology focused discussions..., Exceptional communication..., Excellent problem solving..., A quantitative approach..., Experienced TPM leader..., Ability to simplify..., Deep focus on execution..., Exceptional cross-team collaboration..., Highly tuned emotional intelligence... Those are more like qualifications/skills. But we can treat them as Responsibilities? Usually responsibilities are what you will do. The earlier paragraph describes what you will do: lead complex initiative, orchestrate strategy and execution, transform raw metrics, etc. That could be Responsibilities. - Requirements: Basic Qualifications: Bachelor's Degree, At least 9 years of experience managing technical programs. - Preferred Qualifications: list many items: 9+ years experience designing and building data-intensive solutions using distributed computing, 5+ years experience in building distributed systems & highly available services using cloud computing services / architecture - preferably using AWS, 5+ years of building & leading experienced TPM team, 5+ years experience building highly scalable mobile products & platforms, 5+ years of experience with Agile delivery, 5+ years years experience delivering large and complex programs..., Experience in building systems & solutions within a highly regulated environment, Bachelor's degree in a related technical field (Computer Science, Software Engineering) MBA or Master’s Degree in a related technical field (Computer Science, Software Engineering) or equivalent experience. - Skills: maybe the list of abilities: Strong technical backgrounds, ability to identify and mitigate technical risks, experience building and leading team, lead technology focused discussions, exceptional communication, excellent problem solving, quantitative approach, collaborative implementer, systems thinker, ability to simplify technically complex, deep focus on execution, cross-team collaboration, emotional intelligence, good listener, empathy. Could be Skills. - Benefits: The posting mentions "Capital One offers a comprehensive, competitive, and inclusive set of health, financial and other benefits that support your total well-being." Also mentions performance based incentive compensation (cash bonus and/or LTI). Also mentions remote eligible. So we can include Benefits section with that info. - Pay: Salary ranges listed for various locations. Must include Pay section with those specifics. - Schedule: Not mentioned explicitly. There's no schedule info (full-time implied). So we should not create Schedule section. - Also note about remote eligible: mention in About the role or maybe a note. Could include in About the role. We must not include boilerplate like EEO, immigration, accommodation, legal, etc. We must not repeat job title as heading. We must not include Job ID/requisition numbers. We must preserve all substantive information; do not invent or summarize away detail. Must not omit specifics like salary numbers, location specifics, etc. We must not create sections with filler like "commensurate with experience". Not present. We need to output only HTML fragment, no /, no markdown fences. Thus produce something like:

About the role

...

Responsibilities

• ...
...

Requirements

• ...
...

Preferred Qualifications

• ...
...

Skills

• ...
...

Benefits

• ...
...

Pay

• ...
...

We need to ensure we include all specifics. Let's extract exact text. About the role: The posting includes: "At Capital One, we’re changing banking for good. We were founded on the belief that no one should be locked out of the financial system. We’re dedicated to helping foster a world where everyone has an equal opportunity to prosper. We’re a bank, but we don’t think like one. We’re always thinking about what’s next, about how we can innovate and inspire, and about how we can develop the tools our customers need to improve their financial lives - by leveraging best in class technology. That’s where you come in." Then "Role:: This TPM will lead a complex, cross-organizational initiative to transition our engineering environment into its next major evolution: a sophisticated, AI-driven, and self-optimizing ecosystem anchored by robust telemetry and evaluation. You will orchestrate the strategy and execution required to achieve a destination state where data seamlessly drives system-wide experimentation, automated workflows, and holistic operational visibility. This program will transform raw metrics into a proactive AI intelligence layer for measuring impact and accelerating software delivery" Combine into About the role paragraph(s). Could be two paragraphs. Responsibilities: Could be the bullet list after "Our TPM Sr. Directors have:" but those are more like qualifications. However we need a Responsibilities section; we could use the description of what you will lead (the role description) as Responsibilities. But we already used that in About the role. Might be better to split: About the role = company mission and role overview; Responsibilities = the list of what the TPM Sr. Directors have (i.e., what they do). However the list includes "Strong technical backgrounds...", "Experience building and leading...", etc. Those are more qualifications/experience. But we can still treat them as responsibilities (what they are expected to do). The instruction: "Use

• for any list of duties/requirements/benefits". So if it's a list of duties, we put in
  . The list after "Our TPM Sr. Directors have:" is a list of attributes/experience. Could be considered duties/requirements. We'll put them under Responsibilities. But we also have a separate Requirements section (Basic Qualifications). And Preferred Qualifications separate. Thus: Responsibilities: list items from "Our TPM Sr. Directors have:" (the bullet-like sentences). We'll need to extract each item. Let's extract them exactly as they appear: "Strong technical backgrounds (ideally building highly scalable platforms, products, or services) with the ability to proactively identify and mitigate technical risks throughout delivery life-cycle" "Experience building and leading a world-class team of technical program managers with a mission to power real-time, intelligent experiences for our customers and associates" "Lead technology focused discussions with senior leadership by providing valuable insights and recommendations that guide technology-based decisions" "Exceptional communication and collaboration skills" "Excellent problem solving and influencing skills" "A quantitative approach to problem solving and a collaborative implementer to holistic solutions; a systems thinker" "Experienced TPM leader to grow and develop a team of TPMs, while also building the foundations for the TPM practice" "Ability to simplify the technically complex and drive well-educated decisions across product, engineering, design, and data science representatives" "Deep focus on execution, follow-through, accountability, and results" "Exceptional cross-team collaboration; able to work across different functions, organizations, and reporting boundaries to get the job done." "Highly tuned emotional intelligence, good listener, and deep seated empathy for teams and partners" We need to keep punctuation as is. Now Requirements (Basic Qualifications): "Bachelor's Degree" and "At least 9 years of experience managing technical programs". That's it. Preferred Qualifications: list items: "9+ years of experience designing and building data-intensive solutions using distributed computing." "5+ years of experience in building distributed systems & highly available services using cloud computing services / architecture - preferably using AWS" "5+ years of building & leading experienced TPM team" "5+ years experience building highly scalable mobile products & platforms" "5+ years of experience with Agile delivery" "5+ years years experience delivering large and complex programs - where you own the business or technical vision, collaborate with large cross-functional teams, secure commitments on deliverables and unblock teams to land business impact" "Experience in building systems & solutions within a highly regulated environment" "Bachelor's degree in a related technical field (Computer Science, Software Engineering)" "MBA or Master’s Degree in a related technical field (Computer Science, Software Engineering) or equivalent experience" Note there is a typo "5+ years years". We must preserve exactly as posted? The instruction: preserve ALL substantive information; do not invent or summarize away detail. So we should keep the text as is, including the duplicate "years". We'll copy exactly. Now Skills: Could be derived from the same list as Responsibilities? But we already used that list for Responsibilities. Maybe we should not duplicate. Better to have Skills separate: maybe the abilities like "Strong technical backgrounds", "Ability to proactively identify and mitigate technical risks", etc. But that's same as responsibilities list. However we need to avoid duplication? The instruction does not forbid duplication, but we should aim to not repeat same content in multiple sections unless it's naturally separate. However the list appears under "Our TPM Sr. Directors have:" which is more like qualifications/skills. Could treat that as Skills, and Responsibilities could be the description of what you will do (lead initiative, orchestrate strategy, transform metrics). Let's decide. We have two narrative paragraphs: the mission paragraph and the Role:: paragraph. Those describe what you will do. That could be Responsibilities. The list of attributes could be Skills/Qualifications. But we already have Requirements and Preferred Qualifications sections for qualifications. So we could put the list under Skills. Thus: - About the role: company mission paragraph (maybe short). - Responsibilities: the Role:: paragraph describing leading initiative, orchestrating strategy, transforming metrics. - Skills: the list of attributes (Our TPM Sr. Directors have:). - Requirements: Basic Qualifications. - Preferred Qualifications: list. - Benefits: mention of benefits, incentive compensation. - Pay: salary ranges. We must not include Schedule. Now let's craft the HTML. We need to wrap each section in

  heading and then content. For prose, use

  . For lists, use

  • . We need to ensure we don't include any extra text outside the fragment. Let's write. About the role: combine the two paragraphs? Could be two

    elements. First paragraph: "At Capital One, we’re changing banking for good. We were founded on the belief that no one should be locked out of the financial system. We’re dedicated to helping foster a world where everyone has an equal opportunity to prosper. We’re a bank, but we don’t think like one. We’re always thinking about what’s next, about how we can innovate and inspire, and about how we can develop the tools our customers need to improve their financial lives - by leveraging best in class technology." Second paragraph: "That’s where you come in." Actually that's a separate sentence after the mission paragraph. Could combine. But we can just put the mission paragraph and then the "That’s where you come in." as part of same

    or separate. Better to keep as one

    containing both. Then Responsibilities: the Role:: paragraph. Let's extract exactly: "Role:: This TPM will lead a complex, cross-organizational initiative to transition our engineering environment into its next major evolution: a sophisticated, AI-driven, and self-optimizing ecosystem anchored by robust telemetry and evaluation. You will orchestrate the strategy and execution required to achieve a destination state where data seamlessly drives system-wide experimentation, automated workflows, and holistic operational visibility. This program will transform raw metrics into a proactive AI intelligence layer for measuring impact and accelerating software delivery" Note there is double colon after Role. We'll keep as is. Now Skills: list items as above. Now Requirements: list items: "Bachelor's