Controls / Governance Lead Technical Program Manager

We need to output HTML fragment with sections: About the role? The description includes "Job Description" paragraph, then "Job Responsibilities", then "Required Qualifications, Capabilities, And Skills", then "Preferred Qualifications, Capabilities, And Skills", then "ABOUT US", then "About The Team". We need to use

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should map headings accordingly. The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we need to decide which sections to include based on content. We have: - Job Description (intro paragraph) – could be "About the role". Use

About the role

then

with that paragraph. - Job Responsibilities – heading "Responsibilities". Use

Responsibilities

then

• for each bullet. - Required Qualifications, Capabilities, And Skills – could be "Requirements" or "Qualifications". The instruction includes "Requirements, Qualifications". We could combine? Probably "Qualifications". Use

  Qualifications

  then
  • for each required qualification bullet. - Preferred Qualifications, Capabilities, And Skills – could be "Preferred Qualifications" maybe also under Qualifications? But we could have separate section "Preferred Qualifications". However instruction says prefer few substantive sections over many thin ones. Could combine required and preferred into one Qualifications section with subheadings? But they said use

    for section headings, not subheadings. Could we have two

    sections: "Required Qualifications" and "Preferred Qualifications"? That might be okay but they said prefer few substantive sections. However we have distinct content; we could merge them into one "Qualifications" section with both required and preferred listed, but we need to preserve all info. Could list required then preferred under same

    but differentiate? Might be okay to have two sections: "Required Qualifications" and "Preferred Qualifications". But they said "Prefer a few substantive sections over many thin ones." Having two qualification sections may be okay if they are substantive. Could also have one "Qualifications" section and inside we have two

    ? Not allowed. Only

    for section headings. So we could have one "Qualifications" section and within it we could have two

    paragraphs: one for required, one for preferred. That preserves info and reduces number of sections. That seems better. - ABOUT US – could be "About the company" maybe not required but we could include as "About the company". However instruction says include a section ONLY when the posting has real, specific content for it. The ABOUT US section has substantive content about JPMorganChase. Could be included as "About the company". But they gave examples of headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They didn't list About the company. But we could still use "About the company" as a heading? The instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those are typical. Safer to stick to those headings. However we have content about the company and about the team. Could we fold that into "About the role"? Probably not appropriate. Could we omit those sections? The instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." So we must keep that info. If we omit a section, we lose info. So we need to include it somewhere. Could we include under "About the role" as a paragraph? That would mix role description with company info, but still preserve. Might be acceptable. However they said "Prefer a few substantive sections over many thin ones." So we could have sections: About the role (includes intro paragraph + company + team info), Responsibilities, Qualifications (includes required and preferred). That's three sections. We must not include Benefits, Pay, Schedule unless present. Not present. We must not include cookie/navigation/legal/EEO etc. Remove boilerplate. The posting includes EEO statements etc. We must remove those. Also remove "About The Team" maybe we incorporate into About the role. We need to ensure we don't repeat job title as heading. Not. We need to output only HTML fragment. Let's extract content. Job Description paragraph: "Leverage your expertise and leadership to guide cutting-edge projects, fostering growth and innovation in a dynamic environment. As a Controls / Governance Lead Technical Program Manager in the Consumer and Community Bank- Business Banking Technology, you will help senior leaders run a large-scale technology organization with discipline, transparency, and accountability. You will drive technology projects and programs end-to-end, connect work across teams, and translate execution details into clear updates that support decisions, strengthen controls, and drive measurable outcomes. You will use your program management expertise, analytical reasoning, and communication skills to bring structure to ambiguous priorities, create clear execution plans, and ensure stakeholders remain aligned on objectives, decisions, risks, and next steps. This role requires strong ownership, sound judgment, and the ability to communicate effectively with technical and business audiences while managing stakeholders effectively. This is an opportunity to help shape and scale a growing organization while working closely with executive leadership, have broad visibility across Business Banking Technology, play a key role in driving execution, support strategic initiatives, coordinate across teams, and help leaders make informed decisions through effective governance, controls, and reporting." That's the intro. Now Responsibilities bullet list (from "Job Responsibilities" section). Let's extract each bullet: - Oversee portfolio-wide controls, risk, governance, and risk reporting, partnering with Technology, Product, Controls, Compliance, and Audit teams to manage risks, issues, remediation commitments, and technical action plans. - Ensure effective issue management, audit and regulatory remediation, control commitments tracking, and executive reporting are delivered accurately and on time. - Lead planning and execution for technology programs and leadership priorities across Business Banking Technology. - Develop program plans, governance cadence, milestones, and action plans that establish clear ownership, accountability, and measurable progress. - Use enterprise-authorized AI capabilities within the work environment to accelerate program planning and risk synthesis (e.g., consolidating inputs into integrated plans, RAID, and executive-ready updates), validating outputs and handling data according to sensitivity requirements. - Drive issue management and remediation plans, Coordinate controls reviews and audit responses, Track action plans and commitments, Manage cross-functional dependencies, Escalate risks and blockers, Provide executive transparency into status, risks, and outcomes - Partner with engineering, product, controls, and business management teams to define program scope, objectives, deliverables, and dependencies aligned to technology and organizational priorities. - Prepare executive-ready materials, leadership updates, business reviews, governance forums, and communications that summarize status, decisions, risks, and next steps. - Drive continuous improvement across operating processes, reporting, controls governance, issue management, and execution routines to improve transparency, efficiency, and follow-through. - Support change execution by coordinating communications, readiness activities, follow-ups, and stakeholder alignment as teams adopt new processes, priorities, and ways of working. - Promote reuse-first, AI-assisted practices for program governance and reporting, ensuring human review and alignment to delivery standards. Note some bullets are long and may have commas; we keep as

    . Now Qualifications: Required Qualifications bullet list: - 5+ years of experience or equivalent expertise in technical program management, leading complex technology projects and programs in a large organization - Experience with Cross-functional execution, Governance, controls, and issue management, Executive communications and leadership support, Change navigation in a growing organization - Experience with Technology controls, Risk management, Audit remediation, Technical program Management, Regulatory programs, PMO/program governance, Large financial institution experience - Demonstrated ability to lead complex, cross-functional initiatives with multiple stakeholders, dependencies, risks, and competing priorities. - Demonstrated stakeholder management and influencing skills, including the ability to build productive relationships and drive alignment across senior leaders and distributed teams. - Demonstrated experience using enterprise-authorized AI capabilities within the work environment to support program management workflows with strong validation habits and awareness of data sensitivity. - Ability to review and validate AI-assisted plans, risks, and recommendations before use, escalating when uncertain and following data handling expectations. - Experience in preparing executive communications, business reviews, governance materials, dashboards, and status updates for senior business and technology audiences. - Proficiency with PowerPoint, Excel, project tracking, and collaboration tools; strong written and verbal communication skills. Preferred Qualifications bullet list: - Experience in financial services, portfolio governance, or large-scale technology operating environments. - Experience supporting senior leadership forums, including staff meetings, business reviews, governance meetings, executive communications, and cross-functional decision-making discussions. - Experience across technical program management, business management, technology governance, or related execution roles; candidates with transferable skills across these disciplines are encouraged to apply. Now About US paragraph: "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. 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. Additional details about total compensation and benefits will be provided during the hiring process." We need to remove EEO boilerplate etc. The About US includes benefits info; we could keep that as part of About the role? But we have no Benefits section; we could keep benefits info inside About the role paragraph. However the instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state benefits (health care, wellness centers, retirement savings plan, backup childcare, tuition reimbursement, mental health support, financial coaching). So we could create a Benefits section. But they said prefer few substantive sections over many thin ones. However we have benefits info; we could include a Benefits section. The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD') and never create Pay/Schedule/Benefits sections unless the posting actually states them." So we can create a Benefits section because the posting states them. Good. Similarly, Pay: they mention base salary determined based on role, experience, skill set and location; commission-based pay and/or discretionary incentive compensation. That's pay info. So we could create a Pay section. However they said prefer few substantive sections over many thin ones. But we have both Pay and Benefits; we could combine into a "Compensation and Benefits" section? But they gave examples of headings: Benefits, Pay, Schedule. Could we create a "Compensation" section? Not in examples but could be okay. However to follow instruction, we could create separate Pay and Benefits sections if they have substantive content. That would increase sections but still okay. However they said prefer few substantive sections over many thin ones. Having Pay and Benefits separate may be considered thin? Each has substantive content. Could combine into "Compensation and Benefits". But the instruction didn't forbid other headings; they gave examples. I think it's safe to create a "Compensation and Benefits" section as one heading, maybe