Technical Project Manager II - Data/Controls
for sections: 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. Must not include Job ID etc. Must preserve all substantive info, no boilerplate, no EEO, etc. Must not include sections with placeholder/filler like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. The posting mentions: "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."
Thus we have content about Pay (base salary, commission-based pay, discretionary incentive compensation) and Benefits (list). So we can include Pay and Benefits sections. Schedule not mentioned, so omit.
We also have "About Us" and "About The Team" sections. Those could be considered "About the role"? Actually "About the role" is a generic heading for role description. The posting includes a job description paragraph at start: "Embrace the challenge of steering complex tech projects..." That's about the role. So we can put that under About the role
. Then Responsibilities: list of responsibilities. Then Required Qualifications, Capabilities, And Skills: that's qualifications. Then Preferred Qualifications, Capabilities, And Skills: could be under Skills or Qualifications? The instruction: Use headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have Required Qualifications etc. That's qualifications. Preferred qualifications could be under Skills? Or we could combine them under Qualifications (maybe separate sub-sections not needed). But we must not create thin sections; we can combine required and preferred into Qualifications and Skills sections. However we need to preserve all substantive info. We could put Required Qualifications under Qualifications
and Preferred Qualifications under Skills
(since they are skills). Or we could put both under Qualifications and have Skills empty? Better to split: Qualifications for required, Skills for preferred. That seems reasonable.
We also have "About Us" and "About The Team". Those could be considered extra info but not in the prescribed headings. Should we include them? The instruction: Use headings for those specific section headings. It didn't forbid other headings, but says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings for sections. It didn't say we cannot add other headings, but likely they want only those. However "About Us" and "About The Team" are substantive info about company and team. Should we include them? Possibly under "About the role"? But that would mix. Better to include them as separate sections? The instruction 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 exhaustive. But they also say "Prefer a few substantive sections over many thin ones." So we could include About Us and About The Team as separate sections if they are substantive. However they might be considered boilerplate? Not exactly boilerplate; they describe the firm and team. Might be relevant. But the instruction also says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." About Us and About The Team are not those. So we could keep them.
But we need to decide headings. Could use About the company
and About the team
. However the instruction didn't list those as examples but didn't forbid. Safer to stick to the listed headings only, and incorporate About Us and About The Team into existing sections like About the role (maybe as a brief note). However that would dilute the role description. But we could add a paragraph after the role description about the firm and team. That seems acceptable.
Thus sections: About the role (includes initial paragraph plus maybe a note about firm/team). Responsibilities (list). Qualifications (required). Skills (preferred). Benefits (list). Pay (description). No Schedule.
We must not include headings with empty content. Ensure each heading has substantive content.
Now format: Use for each section heading. Use - for lists. Use
for prose.
We must not include markdown code fences. Output only HTML fragment.
Let's extract content.
About the role: The first paragraph: "Embrace the challenge of steering complex tech projects, fostering growth and technical excellence in a dynamic environment. As a Technical Project Manager II - Data/Controls in Commercial & Investment Bank (CIB) Chief Data Office (CDO), you will join a team incorporating leading practices and collaborating with data management professionals to ensure data quality and controls meet CIB Data Standards across applications and platforms. This role is controls and lineage-focused (control implementation support, control testing/monitoring, and evidencing). You will leverage your broad knowledge of technical principles and practices to develop innovative solutions, while effectively managing resources, budgets, and cross-functional teams. Your analytical reasoning and adaptability skills will enable you to navigate through ambiguity and embrace change. By fostering productive relationships with stakeholders and clients, you will contribute to the firm's overall growth and success. Your excellent communication skills and ability to influence others will be crucial in driving mutually beneficial outcomes and managing risks in line with the firm's policies and practices."
We could also add a brief about firm/team: maybe incorporate after that: "JPMorganChase, one of the oldest financial institutions, offers innovative financial solutions..." and "J.P. Morgan's Commercial & Investment Bank is a global leader..." But that is more about company/team. Could add as a paragraph after role description. That would be part of About the role section.
Responsibilities: list bullet points from "Job Responsibilities". Let's capture each line:
- Provide subject matter expertise for data-related technology control procedures, including (but not limited to) data retention and destruction, technical data quality, data use, and data description and authority controls
- Apply enterprise-authorized AI capabilities within the data lineage and controls landscape to minimize risk and support key business and regulatory control-driven outcomes, validating outputs and handling data according to sensitivity and security requirements
- Support Application Owners and Information Owners in adopting and producing evidence for data-related technology control procedures
- Perform and/or coordinate control testing and ongoing monitoring activities for data-related technology controls, including tracking results, exceptions, and remediation progress with stakeholders
- Maintain a knowledge base for data-related technology control procedures, including best practices, standards, guidelines, and training materials
- Contribute to continuous improvement by incorporating feedback, incidents, and regulatory/audit themes; Proactively identify and analyze hidden problems and patterns in data, using these insights to drive process improvements; Contribute to CIB data lineage and control tooling requirements, including proposing new features to increase the efficiency and effectiveness of controls
- Partner with data owners, data architects, and technologists to validate lineage and control evidence completeness/accuracy needed to support control objectives and traceability expectations
- Uses enterprise-authorized AI capabilities within the work environment to accelerate project planning and risk synthesis (e.g., drafting plans, RAID, and status narratives), validating outputs and handling data according to sensitivity requirements.
- Assist in risk management by making informed decisions in line with the firm's risk management practices and policies, ensuring project success and compliance
- Promotes reuse-first, AI-assisted practices for project governance artifacts and reporting, ensuring human review and alignment to delivery standards.
Note some lines have capitalization issues; we keep as is.
Qualifications (Required): list bullet points from "Required Qualifications, Capabilities, And Skills":
- 2+ years of experience or equivalent expertise in technical program management, leading complex technology projects and programs
- Demonstrated experience using enterprise-authorized AI capabilities within the work environment to support technical 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.
- Working knowledge of data risk management, data lineage, and data quality controls
- Understanding of controls testing/monitoring concepts (e.g., evidence collection, control execution validation, issue/exceptions tracking)
- Strong communication and stakeholder engagement skills, with the ability to work with business and technology teams, including application owners, data owners, data architects, and information owners
- Ability to collaborate across diverse stakeholders and drive outcomes
- Good understanding of modern delivery and engineering practices and technical disciplines (e.g., SDLC, CI/CD, application resiliency, and security fundamentals)
- Demonstrated knowledge of software applications and technical processes within a technical discipline (e.g., cloud, artificial intelligence, machine learning, mobile, etc.)
- Demonstrated technical proficiency and experience with relevant platforms and approved tools/technologies
- Prior experience managing diverse sets of stakeholders, establishing productive working relationships with cross-functional teams and clients, and managing project governance
Skills (Preferred): list bullet points from "Preferred Qualifications, Capabilities, And Skills":
- Familiarity with data management and architecture frameworks such as DAMA, TOGAF
- Knowledge of financial regulations such as GDPR, BCBS, PRA, and other relevant standards as applicable
- Experience in Financial Services, including markets, securities services, payments and banking
Benefits: list from "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."
We can make a list: comprehensive health care coverage, on-site health and wellness centers, a retirement savings plan, backup childcare, tuition reimbursement, mental health support, financial coaching.
Pay: from "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 can make a paragraph.
We should not include "Additional details about total compensation and benefits will be provided during the hiring process." That's somewhat generic but still substantive? It's a statement about process; could be included but it's not specific detail. Might be considered filler? It's not placeholder like "TBD". It's a statement. Could keep but maybe it's okay. However it's somewhat generic; but we can include as part of Pay or Benefits paragraph.
We must not include boilerplate like EEO etc. Already removed.
Now construct HTML.
We'll have:
About the role
... (role description) ...
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.
J.P. Morgan's Commercial & Investment Bank is a global leader across banking, markets, securities services and payments. Corporations, governments and institutions throughout the world entrust us with their business in more than 100 countries. The Commercial & Investment Bank provides strategic advice, raises capital, manages risk and extends liquidity in markets around the world.
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exhaustive. But they also say "Prefer a few substantive sections over many thin ones." So we could include About Us and About The Team as separate sections if they are substantive. However they might be considered boilerplate? Not exactly boilerplate; they describe the firm and team. Might be relevant. But the instruction also says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." About Us and About The Team are not those. So we could keep them.
But we need to decide headings. Could use About the company
and About the team
. However the instruction didn't list those as examples but didn't forbid. Safer to stick to the listed headings only, and incorporate About Us and About The Team into existing sections like About the role (maybe as a brief note). However that would dilute the role description. But we could add a paragraph after the role description about the firm and team. That seems acceptable.
Thus sections: About the role (includes initial paragraph plus maybe a note about firm/team). Responsibilities (list). Qualifications (required). Skills (preferred). Benefits (list). Pay (description). No Schedule.
We must not include headings with empty content. Ensure each heading has substantive content.
Now format: Use for each section heading. Use - for lists. Use
for prose.
We must not include markdown code fences. Output only HTML fragment.
Let's extract content.
About the role: The first paragraph: "Embrace the challenge of steering complex tech projects, fostering growth and technical excellence in a dynamic environment. As a Technical Project Manager II - Data/Controls in Commercial & Investment Bank (CIB) Chief Data Office (CDO), you will join a team incorporating leading practices and collaborating with data management professionals to ensure data quality and controls meet CIB Data Standards across applications and platforms. This role is controls and lineage-focused (control implementation support, control testing/monitoring, and evidencing). You will leverage your broad knowledge of technical principles and practices to develop innovative solutions, while effectively managing resources, budgets, and cross-functional teams. Your analytical reasoning and adaptability skills will enable you to navigate through ambiguity and embrace change. By fostering productive relationships with stakeholders and clients, you will contribute to the firm's overall growth and success. Your excellent communication skills and ability to influence others will be crucial in driving mutually beneficial outcomes and managing risks in line with the firm's policies and practices."
We could also add a brief about firm/team: maybe incorporate after that: "JPMorganChase, one of the oldest financial institutions, offers innovative financial solutions..." and "J.P. Morgan's Commercial & Investment Bank is a global leader..." But that is more about company/team. Could add as a paragraph after role description. That would be part of About the role section.
Responsibilities: list bullet points from "Job Responsibilities". Let's capture each line:
- Provide subject matter expertise for data-related technology control procedures, including (but not limited to) data retention and destruction, technical data quality, data use, and data description and authority controls
- Apply enterprise-authorized AI capabilities within the data lineage and controls landscape to minimize risk and support key business and regulatory control-driven outcomes, validating outputs and handling data according to sensitivity and security requirements
- Support Application Owners and Information Owners in adopting and producing evidence for data-related technology control procedures
- Perform and/or coordinate control testing and ongoing monitoring activities for data-related technology controls, including tracking results, exceptions, and remediation progress with stakeholders
- Maintain a knowledge base for data-related technology control procedures, including best practices, standards, guidelines, and training materials
- Contribute to continuous improvement by incorporating feedback, incidents, and regulatory/audit themes; Proactively identify and analyze hidden problems and patterns in data, using these insights to drive process improvements; Contribute to CIB data lineage and control tooling requirements, including proposing new features to increase the efficiency and effectiveness of controls
- Partner with data owners, data architects, and technologists to validate lineage and control evidence completeness/accuracy needed to support control objectives and traceability expectations
- Uses enterprise-authorized AI capabilities within the work environment to accelerate project planning and risk synthesis (e.g., drafting plans, RAID, and status narratives), validating outputs and handling data according to sensitivity requirements.
- Assist in risk management by making informed decisions in line with the firm's risk management practices and policies, ensuring project success and compliance
- Promotes reuse-first, AI-assisted practices for project governance artifacts and reporting, ensuring human review and alignment to delivery standards.
Note some lines have capitalization issues; we keep as is.
Qualifications (Required): list bullet points from "Required Qualifications, Capabilities, And Skills":
- 2+ years of experience or equivalent expertise in technical program management, leading complex technology projects and programs
- Demonstrated experience using enterprise-authorized AI capabilities within the work environment to support technical 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.
- Working knowledge of data risk management, data lineage, and data quality controls
- Understanding of controls testing/monitoring concepts (e.g., evidence collection, control execution validation, issue/exceptions tracking)
- Strong communication and stakeholder engagement skills, with the ability to work with business and technology teams, including application owners, data owners, data architects, and information owners
- Ability to collaborate across diverse stakeholders and drive outcomes
- Good understanding of modern delivery and engineering practices and technical disciplines (e.g., SDLC, CI/CD, application resiliency, and security fundamentals)
- Demonstrated knowledge of software applications and technical processes within a technical discipline (e.g., cloud, artificial intelligence, machine learning, mobile, etc.)
- Demonstrated technical proficiency and experience with relevant platforms and approved tools/technologies
- Prior experience managing diverse sets of stakeholders, establishing productive working relationships with cross-functional teams and clients, and managing project governance
Skills (Preferred): list bullet points from "Preferred Qualifications, Capabilities, And Skills":
- Familiarity with data management and architecture frameworks such as DAMA, TOGAF
- Knowledge of financial regulations such as GDPR, BCBS, PRA, and other relevant standards as applicable
- Experience in Financial Services, including markets, securities services, payments and banking
Benefits: list from "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."
We can make a list: comprehensive health care coverage, on-site health and wellness centers, a retirement savings plan, backup childcare, tuition reimbursement, mental health support, financial coaching.
Pay: from "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 can make a paragraph.
We should not include "Additional details about total compensation and benefits will be provided during the hiring process." That's somewhat generic but still substantive? It's a statement about process; could be included but it's not specific detail. Might be considered filler? It's not placeholder like "TBD". It's a statement. Could keep but maybe it's okay. However it's somewhat generic; but we can include as part of Pay or Benefits paragraph.
We must not include boilerplate like EEO etc. Already removed.
Now construct HTML.
We'll have:
About the role
... (role description) ...
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.
J.P. Morgan's Commercial & Investment Bank is a global leader across banking, markets, securities services and payments. Corporations, governments and institutions throughout the world entrust us with their business in more than 100 countries. The Commercial & Investment Bank provides strategic advice, raises capital, manages risk and extends liquidity in markets around the world.
- for lists. Use
for prose. We must not include markdown code fences. Output only HTML fragment. Let's extract content. About the role: The first paragraph: "Embrace the challenge of steering complex tech projects, fostering growth and technical excellence in a dynamic environment. As a Technical Project Manager II - Data/Controls in Commercial & Investment Bank (CIB) Chief Data Office (CDO), you will join a team incorporating leading practices and collaborating with data management professionals to ensure data quality and controls meet CIB Data Standards across applications and platforms. This role is controls and lineage-focused (control implementation support, control testing/monitoring, and evidencing). You will leverage your broad knowledge of technical principles and practices to develop innovative solutions, while effectively managing resources, budgets, and cross-functional teams. Your analytical reasoning and adaptability skills will enable you to navigate through ambiguity and embrace change. By fostering productive relationships with stakeholders and clients, you will contribute to the firm's overall growth and success. Your excellent communication skills and ability to influence others will be crucial in driving mutually beneficial outcomes and managing risks in line with the firm's policies and practices." We could also add a brief about firm/team: maybe incorporate after that: "JPMorganChase, one of the oldest financial institutions, offers innovative financial solutions..." and "J.P. Morgan's Commercial & Investment Bank is a global leader..." But that is more about company/team. Could add as a paragraph after role description. That would be part of About the role section. Responsibilities: list bullet points from "Job Responsibilities". Let's capture each line: - Provide subject matter expertise for data-related technology control procedures, including (but not limited to) data retention and destruction, technical data quality, data use, and data description and authority controls - Apply enterprise-authorized AI capabilities within the data lineage and controls landscape to minimize risk and support key business and regulatory control-driven outcomes, validating outputs and handling data according to sensitivity and security requirements - Support Application Owners and Information Owners in adopting and producing evidence for data-related technology control procedures - Perform and/or coordinate control testing and ongoing monitoring activities for data-related technology controls, including tracking results, exceptions, and remediation progress with stakeholders - Maintain a knowledge base for data-related technology control procedures, including best practices, standards, guidelines, and training materials - Contribute to continuous improvement by incorporating feedback, incidents, and regulatory/audit themes; Proactively identify and analyze hidden problems and patterns in data, using these insights to drive process improvements; Contribute to CIB data lineage and control tooling requirements, including proposing new features to increase the efficiency and effectiveness of controls - Partner with data owners, data architects, and technologists to validate lineage and control evidence completeness/accuracy needed to support control objectives and traceability expectations - Uses enterprise-authorized AI capabilities within the work environment to accelerate project planning and risk synthesis (e.g., drafting plans, RAID, and status narratives), validating outputs and handling data according to sensitivity requirements. - Assist in risk management by making informed decisions in line with the firm's risk management practices and policies, ensuring project success and compliance - Promotes reuse-first, AI-assisted practices for project governance artifacts and reporting, ensuring human review and alignment to delivery standards. Note some lines have capitalization issues; we keep as is. Qualifications (Required): list bullet points from "Required Qualifications, Capabilities, And Skills": - 2+ years of experience or equivalent expertise in technical program management, leading complex technology projects and programs - Demonstrated experience using enterprise-authorized AI capabilities within the work environment to support technical 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. - Working knowledge of data risk management, data lineage, and data quality controls - Understanding of controls testing/monitoring concepts (e.g., evidence collection, control execution validation, issue/exceptions tracking) - Strong communication and stakeholder engagement skills, with the ability to work with business and technology teams, including application owners, data owners, data architects, and information owners - Ability to collaborate across diverse stakeholders and drive outcomes - Good understanding of modern delivery and engineering practices and technical disciplines (e.g., SDLC, CI/CD, application resiliency, and security fundamentals) - Demonstrated knowledge of software applications and technical processes within a technical discipline (e.g., cloud, artificial intelligence, machine learning, mobile, etc.) - Demonstrated technical proficiency and experience with relevant platforms and approved tools/technologies - Prior experience managing diverse sets of stakeholders, establishing productive working relationships with cross-functional teams and clients, and managing project governance Skills (Preferred): list bullet points from "Preferred Qualifications, Capabilities, And Skills": - Familiarity with data management and architecture frameworks such as DAMA, TOGAF - Knowledge of financial regulations such as GDPR, BCBS, PRA, and other relevant standards as applicable - Experience in Financial Services, including markets, securities services, payments and banking Benefits: list from "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." We can make a list: comprehensive health care coverage, on-site health and wellness centers, a retirement savings plan, backup childcare, tuition reimbursement, mental health support, financial coaching. Pay: from "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 can make a paragraph. We should not include "Additional details about total compensation and benefits will be provided during the hiring process." That's somewhat generic but still substantive? It's a statement about process; could be included but it's not specific detail. Might be considered filler? It's not placeholder like "TBD". It's a statement. Could keep but maybe it's okay. However it's somewhat generic; but we can include as part of Pay or Benefits paragraph. We must not include boilerplate like EEO etc. Already removed. Now construct HTML. We'll have:
About the role
... (role description) ...
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.
J.P. Morgan's Commercial & Investment Bank is a global leader across banking, markets, securities services and payments. Corporations, governments and institutions throughout the world entrust us with their business in more than 100 countries. The Commercial & Investment Bank provides strategic advice, raises capital, manages risk and extends liquidity in markets around the world.