Lead Technical Program Manager -Enterprise Architecture
JPMorganChase · Jersey City, NJ · 3 wk ago
On-siteInformation TechnologyFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements (maybe combine Required Qualifications, Capabilities, And Skills), Skills? The posting includes "Required Qualifications, Capabilities, And Skills" and "Preferred Qualifications, Capabilities, And Skills". Could combine into Requirements (maybe separate Required and Preferred). Also "About Us" maybe not needed? The instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Include a section ONLY when posting has real, specific content for it. So we need sections: About the role (intro paragraph), Responsibilities (list), Requirements (maybe combine required and preferred?), Skills (maybe separate? but we have required qualifications includes skills). Could do "Requirements" for required qualifications, and "Preferred Qualifications" maybe as separate? But they said prefer few substantive sections over many thin ones. Could combine required and preferred into one Requirements section with subheadings? But only allowed headings are
.
Requirements: we need to include Required Qualifications, Capabilities, And Skills and Preferred Qualifications, Capabilities, And Skills. Could split into two subsections? But only allowed. Could have two
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Include a section ONLY when posting has real, specific content for it. So we need sections: About the role (intro paragraph), Responsibilities (list), Requirements (maybe combine required and preferred?), Skills (maybe separate? but we have required qualifications includes skills). Could do "Requirements" for required qualifications, and "Preferred Qualifications" maybe as separate? But they said prefer few substantive sections over many thin ones. Could combine required and preferred into one Requirements section with subheadings? But only allowed headings are . Could have multiple sections: About the role, Responsibilities, Required Qualifications, Preferred Qualifications, Benefits (maybe), etc. Benefits: posting mentions benefits in About Us: "We offer a competitive total rewards package... 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." That's specific benefits. So we can include Benefits section.
Pay: posting mentions "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". That's specific enough to include Pay section.
Schedule: not mentioned. So omit.
Skills: maybe we can omit if covered in qualifications.
We must not repeat job title as heading. No Job ID.
We must remove boilerplate: EEO, equal opportunity, scam warning, etc. Also remove "About Us" maybe? But we can keep "About Us" as a section? The instruction list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Not About Us. But we could incorporate About Us into About the role? The posting has "About Us" paragraph describing firm. Could be considered part of About the role? Might be okay to include as a separate section "About the company"? Not in list. Safer to omit About Us unless we treat as About the role? The instruction says use those headings as examples, not exclusive? It says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those headings; we could also use other headings if needed? Probably better to stick to those. So we can have About the role (intro), Responsibilities, Requirements (maybe combine required and preferred), Benefits, Pay.
We need to preserve all substantive information. So we must include details from About Us? If we omit About Us, we lose that substantive info about firm history, etc. That might be considered substantive. But maybe it's considered boilerplate? It's descriptive of the firm, not boilerplate. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. About Us is not those. So we should keep it. Could place it under About the role? Or maybe a separate section "About the company". But not in list. Could we use "About the role" to include both role description and firm description? The intro already has role description. We could add a paragraph about the firm under About the role as well. That would preserve info.
Thus About the role section will contain the introductory paragraph(s) about opportunity, role description, and also the About Us paragraph.
Now Responsibilities: list each responsibility as
sections: About the role, Responsibilities, Required Qualifications, Preferred Qualifications, Benefits (maybe), etc. Benefits: posting mentions benefits in About Us: "We offer a competitive total rewards package... 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." That's specific benefits. So we can include Benefits section.
Pay: posting mentions "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". That's specific enough to include Pay section.
Schedule: not mentioned. So omit.
Skills: maybe we can omit if covered in qualifications.
We must not repeat job title as heading. No Job ID.
We must remove boilerplate: EEO, equal opportunity, scam warning, etc. Also remove "About Us" maybe? But we can keep "About Us" as a section? The instruction list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Not About Us. But we could incorporate About Us into About the role? The posting has "About Us" paragraph describing firm. Could be considered part of About the role? Might be okay to include as a separate section "About the company"? Not in list. Safer to omit About Us unless we treat as About the role? The instruction says use those headings as examples, not exclusive? It says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those headings; we could also use other headings if needed? Probably better to stick to those. So we can have About the role (intro), Responsibilities, Requirements (maybe combine required and preferred), Benefits, Pay.
We need to preserve all substantive information. So we must include details from About Us? If we omit About Us, we lose that substantive info about firm history, etc. That might be considered substantive. But maybe it's considered boilerplate? It's descriptive of the firm, not boilerplate. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. About Us is not those. So we should keep it. Could place it under About the role? Or maybe a separate section "About the company". But not in list. Could we use "About the role" to include both role description and firm description? The intro already has role description. We could add a paragraph about the firm under About the role as well. That would preserve info.
Thus About the role section will contain the introductory paragraph(s) about opportunity, role description, and also the About Us paragraph.
Now Responsibilities: list each responsibility as
allowed. Could have two sections: Required Qualifications and Preferred Qualifications. That's okay.
But the instruction list includes Qualifications as a possible heading. Could use "Required Qualifications" and "Preferred Qualifications". That seems fine.
Skills: maybe we can omit if covered.
Benefits: list benefits.
Pay: include paragraph about base salary, commission, incentive.
Now we must not include placeholder text like "commensurate with experience". Not present.
Now produce HTML fragment.
Let's extract content.
Intro paragraph: "We have an opportunity to impact your career and provide an adventure where you can push the limits of what's possible. As a Lead Technical Program Manager at JPMorgan Chase within the Global Technology's Enterprise Architecture team, you will drive the successful delivery of complex technology projects and programs that will help reach business goals across the firm. Leveraging your deep knowledge of technical principles, practices, and theories is essential for developing innovative solutions, while simultaneously effectively managing resources, budgets, and high-performing teams. Your strong analytical reasoning and adaptability skills will enable you to navigate through ambiguity and change, ensuring that technology initiatives align with business goals. With advanced communication and stakeholder management abilities, you will foster productive working relationships and influence decision-making to achieve mutually beneficial outcomes. As a subject matter expert, you will contribute to the development of operational plans and risk management strategies, ensuring the highest quality and professionalism in service delivery."
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 recognize that our people are our strength and the diverse talents they bring to our global workforce are directly linked to our success. We are an equal opportunity employer and place a high value on diversity and inclusion at our company. We do not discriminate on the basis of any protected attribute, including race, religion, color, national origin, gender, sexual orientation, gender identity, gender expression, age, marital or veteran status, pregnancy or disability, or any other basis protected under applicable law. We also make reasonable accommodations for applicants' and employees' religious practices and beliefs, as well as mental health or physical disability needs. Visit our FAQs for more information about requesting an accommodation. JPMorgan Chase & Co. is an Equal Opportunity Employer, including Disability/Veterans"
But we need to remove EEO/equal-opportunity boilerplate. The About Us includes EEO statements. We must remove those lines. So we should strip out the EEO sentences: "We are an equal opportunity employer..." and "We do not discriminate..." and "We also make reasonable accommodations..." and "Visit our FAQs..." and "JPMorgan Chase & Co. is an Equal Opportunity Employer, including Disability/Veterans". Also maybe the sentence about competitive total rewards package is part of benefits/pay; we might keep that but we already have Benefits and Pay sections. Could keep some of it but avoid duplication.
Thus we keep the descriptive firm overview: history, leadership, etc. And maybe the sentence about competitive total rewards package we can move to Benefits/Pay.
Thus About Us kept: "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."
Now Responsibilities list: need to extract each bullet.
From posting:
- Develop and execute comprehensive project plans, incorporating technical requirements, resource allocation, and timelines to ensure on-time delivery of technology solutions
- Identify and mitigate risks, proactively addressing potential roadblocks and implementing contingency plans to maintain project and program momentum
- Collaborate with cross-functional teams, including engineering, product, and business stakeholders, to define program scope, objectives, and deliverables, ensuring alignment with overall business goals
- Utilize advanced analytical reasoning to assess program performance, identify areas for improvement, and implement data-driven optimizations to enhance efficiency and effectiveness
- Champion the adoption of agile methodologies and technical solutions, fostering a culture of continuous learning and innovation within the team
- Uses 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.
- Promotes reuse-first, AI-assisted practices for program governance and reporting, ensuring human review and alignment to delivery standards.
Note some have capitalization issues; keep as is.
Now Required Qualifications:
- 5+ years of experience or equivalent expertise in technical program management, leading complex technology projects and programs in a large organization
- Advanced expertise in stakeholder management, with the ability to establish productive working relationships and influence decision-making across cross-functional teams and clients
- Advanced experience in utilizing technical fluency, including knowledge of vendor products and managing vendor relations, to enable on-demand access to shared pools of applications and services
- Proven track record of effectively managing resources, budgets, and high-performing teams in a fast-paced, agile environment
- Demonstrated proficiency in applying analytical reasoning and problem-solving techniques to break down business, technical, or operational objectives into manageable tasks and activities
- 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.
Now Preferred Qualifications:
- 3+ years of experience or equivalent expertise in product management or a relevant domain area
- Proven ability to lead product life cycle activities including discovery, ideation, strategic development, requirements definition, and value management
- Partner with Product Management in discovery efforts and market research to uncover customer solutions and integrate them into the product roadmap
- Assist Technical Leads in maintaining, and developing a product backlog that enables development to support the overall strategic roadmap and value proposition
- Experience with Agile/Lean delivery at scale (e.g., Scrum/Kanban, PI planning concepts) and tooling (e.g., Jira/Confluence equivalents).
- Scrum and/or SAFe certification(s) preferred (e.g., CSM/PSM, SAFe Agilist/POPM/RTE).
Now Benefits: from About Us we have list: 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.
We can list those.
Pay: base salary determined based on 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 can include that.
Now we need to ensure we don't repeat job title as heading. We'll not.
Now produce HTML:
About the role
About the role
We have an opportunity to impact your career and provide an adventure where you can push the limits of what's possible. As a Lead Technical Program Manager at JPMorgan Chase within the Global Technology's Enterprise Architecture team, you