Data Product Studio Technical Product Manager

We need to output HTML fragment with sections: headings

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate like EEO, legal, etc. Also remove application instructions. Keep substantive info. We need to parse the job description. Content: - Job Description paragraph: "As a Principal Technical Program Manager in Corporate Technology, you will lead complex, multi-functional technology projects and programs that will impact experiences for multiple groups across the firm, including clients, employees, and stakeholders. Your advanced analytical reasoning and adaptability skills will enable you to break down business, technical, and operational objectives into manageable tasks, while navigating through ambiguity and driving change. With demonstrated technical fluency, you will effectively manage resources, budgets, and cross-functional teams to deliver innovative solutions that align with the firm's strategic goals. Your exceptional communication and influencing abilities will foster productive relationships with stakeholders, ensuring alignment and effective risk management. In this pivotal role, you will contribute to the development of new policies and processes, shaping the future of our technology landscape." Then there is a paragraph about Chief of Staff (COS) that seems like a separate role? Actually it's part of description: "The Chief of Staff (COS) will serve as a strategic partner and trusted advisor to the CDAS leadership team..." This seems like describing the role? Might be part of responsibilities. We'll treat as part of responsibilities. Then "Job Responsibilities" list bullet points (but they are sentences separated by periods). We'll convert to

• . Then "Required Qualifications, Capabilities, And Skills" list bullet points. Then "ABOUT US" paragraph about JPMorganChase, total rewards, benefits, etc. This includes benefits info: "We offer a competitive total rewards package including base salary determined based on the role, experience, skill set and location. Those in eligible roles may receive commission-based pay and/or discretionary incentive compensation, paid in the form of cash and/or forfeitable equity, awarded in recognition of individual achievements and contributions. We also offer a range of benefits and programs to meet employee needs, based on eligibility. These benefits include comprehensive health care coverage, on-site health and wellness centers, a retirement savings plan, backup childcare, tuition reimbursement, mental health support, financial coaching and more." Thus we have Pay info (base salary determined based on role, experience, skill set and location; commission-based pay etc). Benefits info (list). No explicit schedule. We also have "Additional details about total compensation and benefits will be provided during the hiring process." That's vague; we should not create Pay or Benefits sections with filler like "not specified". However we have some specifics: base salary determined based on role, experience, skill set and location; commission-based pay etc. That's enough for Pay section? The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state base salary determined based on role, experience, skill set and location; commission-based pay etc. So we can include Pay section with that info. Benefits: they list specific benefits. So include Benefits section. Schedule: not mentioned, so omit. About the role: we have initial description; could be "About the role" section. Also "About The Team" paragraph at end. Could be separate "About the team" but not in allowed headings list; allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put team info under About the role or maybe under About the role? The instruction: use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should stick to those headings. We can include About the role (summary), Responsibilities, Requirements (maybe combine Qualifications and Skills?), Qualifications, Skills, Benefits, Pay. We need to decide what to put where. We have "Required Qualifications, Capabilities, And Skills" which includes both qualifications and skills. Could split into Qualifications and Skills sections. But we need to ensure we don't create thin sections. We have enough content for both. We also have "About US" which is company overview; could be part of About the role? Not exactly. But we could include it under About the role? Might be okay. However the instruction: include a section ONLY when the posting has real, specific content for it. The posting does have "ABOUT US" with specifics. So we could create a section "About the role" that includes the initial description and maybe the "About US"? But "About the role" is about the role, not company. However we could treat "About the role" as the initial description; "About US" could be omitted? But we must preserve ALL substantive information; we cannot drop the "ABOUT US" paragraph. So we need to include it somewhere. Since we don't have a heading for company overview, we could put it under About the role as a paragraph (maybe it's okay). Or we could create a custom heading? Not allowed per instruction? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not exclusive list? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings. So we must fit all content under those headings. Thus we can put company overview under About the role (makes sense as context). Or we could put under Responsibilities? Not appropriate. Better under About the role. Now we need to avoid boilerplate: remove EEO, legal, equal-opportunity, scam-warning, duplicated lines, application instructions. The posting includes EEO statements at end: "We recognize that our people are our strength ... We are an equal opportunity employer..." etc. Also "Visit our FAQs for more information about requesting an accommodation." and "JPMorgan Chase & Co. is an Equal Opportunity Employer, including Disability/Veterans". Also "About The Team" paragraph (which is substantive). We'll keep that. We also need to remove duplicated lines: there may be duplicates but not obvious. Now produce HTML. Structure:

  About the role

  As a Principal Technical Program Manager in Corporate Technology, you will lead complex, multi-functional technology projects and programs that will impact experiences for multiple groups across the firm, including clients, employees, and stakeholders. Your advanced analytical reasoning and adaptability skills will enable you to break down business, technical, and operational objectives into manageable tasks, while navigating through ambiguity and driving change. With demonstrated technical fluency, you will effectively manage resources, budgets, and cross-functional teams to deliver innovative solutions that align with the firm's strategic goals. Your exceptional communication and influencing abilities will foster productive relationships with stakeholders, ensuring alignment and effective risk management. In this pivotal role, you will contribute to the development of new policies and processes, shaping the future of our technology landscape. The Chief of Staff (COS) will serve as a strategic partner and trusted advisor to the CDAS leadership team in driving operational excellence, strategic initiatives, and organizational effectiveness. The Chief of Staff will play a key role in coordinating cross-functional activities, managing priorities, and ensuring alignment across the CDAS organization.

  JPMorganChase, one of the oldest financial institutions, offers innovative financial solutions to millions of consumers, small businesses and many of the world's most prominent corporate, institutional and government clients under the J.P. Morgan and Chase brands. Our history spans over 200 years and today we are a leader in investment banking, consumer and small business banking, commercial banking, financial transaction processing and asset management.

  Our Corporate Technology team relies on smart, driven people like you to develop applications and provide tech support for all our corporate functions across our network. Your efforts will touch lives all over the financial spectrum and across all our divisions: Global Finance, Corporate Treasury, Risk Management, Human Resources, Compliance, Legal, and within the Corporate Administrative Office. You'll be part of a team specifically built to meet and exceed our evolving technology needs, as well as our technology controls agenda.

  Then Responsibilities:

  Responsibilities

  • Develop and implement strategic technical program plans, aligning with organizational goals and cross-functional collaboration.
  • Support the Head of CDAS in developing, communicating, and executing strategic plans and priorities.
  • Track progress against key initiatives and ensure timely delivery of objectives.
  • Oversee day-to-day operations, including resource allocation, project tracking, and process improvement.
  • Identify and address operational bottlenecks to enhance team efficiency.
  • Prepare briefing materials, presentations, and reports for senior leadership meetings.
  • Facilitate decision-making by providing relevant data, insights, and recommendations.
  • Act as a liaison between the Head of CDAS and internal/external stakeholders, ensuring clear communication and follow-up on action items.
  • Lead or support key projects and programs, ensuring alignment with organizational goals.
  • Monitor project milestones, risks, and dependencies.
  • Ensure adherence to governance frameworks, compliance standards, and risk management practices within the technology organization.
  • Drive initiatives to foster a positive, inclusive, and high-performing team culture. Organize team communications, events, and recognition programs.
  • Support change management efforts related to technology transformation, process enhancements, and organizational restructuring.
  Then Qualifications:

  Qualifications

  • 7+ years of experience or equivalent expertise in technical program management, leading complex technology projects and programs in large organizations.
  • Proven experience in a Chief of Staff, program management, or technology leadership role.
  • Strong understanding of compliance, risk, and regulatory requirements in a technology context.
  • Ability to manage multiple priorities in a fast-paced environment.
  • Demonstrated ability to influence and collaborate across all levels of the organization.
  • Advanced analytical reasoning skills, applying critical thinking and problem-solving techniques to break down business, technical, and operational objectives.
  • Proven ability in leading through change, managing dependencies, and controlling change in high-pressure, shifting environments.
  • Advanced expertise in stakeholder management, establishing productive relationships, and driving beneficial outcomes aligned with firm objectives.
  • Familiarity with data management practices, including data governance, data lineage, etc., and modern patterns such as lakehouse and data mesh.
  • Champion the adoption of AI/ML tools and apply them to CoS and PM workflows driving measurable productivity gains and establishing governance for responsible use approved solutions.
  Then Skills: maybe we can extract some skills from qualifications that are more skill-oriented: Excellent organizational, communication, and interpersonal skills. Also maybe "Advanced expertise in stakeholder management" etc. But we already included many. Could separate: Skills: Excellent organizational, communication, and interpersonal skills. Also maybe "Ability to manage multiple priorities" is skill. But we already have that in qualifications. To avoid duplication, we could keep qualifications as above and skills as separate short list: Excellent organizational, communication, and interpersonal skills. However we must not repeat content. The qualifications list already includes "Excellent organizational, communication, and interpersonal skills." Actually it's in the qualifications list: "Excellent organizational, communication, and interpersonal skills." Yes it's there. So we could move that to Skills section and keep qualifications more about experience. Let's adjust. Qualifications: focus on experience and expertise. Skills: focus on organizational, communication, interpersonal, analytical reasoning, influencing, stakeholder management, etc. But we need to ensure we don't lose any content. Let's parse the qualifications block: "7+ years of experience or equivalent expertise in technical program management, leading complex technology projects and programs in large organizations. Proven experience in a Chief of Staff, program management, or technology leadership role. Strong understanding of compliance, risk, and