Lead Software Engineer - Databricks/PySpark/AI
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should include sections only if posting has real specific content.
We have content for Responsibilities (list). We have Required Qualifications, Capabilities, And Skills (list). We have Preferred Qualifications, Capabilities, And Skills (list). We have About US (company description) maybe as "About the role"? Actually "About the role" could be the introductory paragraph describing role. We have "Job Description" intro paragraph: "We have an exciting and rewarding opportunity...". That could be About the role.
We have Benefits: The posting mentions "competitive total rewards package including base salary... commission-based pay... discretionary incentive compensation... 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." That's benefits and pay info. So we can include Benefits section with list of benefits. Pay: 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 can include Pay section.
Schedule: not mentioned. So omit.
We need to avoid repeating job title as heading. So no heading for Lead Software Engineer - Databricks/PySpark/AI.
We need to use for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve all substantive information, not invent or summarize away detail. Must not include boilerplate like EEO, equal-opportunity, scam-warning, cookie/navigation/legal, duplicated lines, application instructions. The posting includes EEO statements etc. We must remove those. Also remove "About Us" maybe we keep as part of About the role? Actually "About US" is company description; we could include as part of About the role or maybe a separate section "About the company". But only allowed headings are those listed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "About US" could be considered "About the role"? Not exactly. But we could incorporate company description into About the role paragraph. Or we could omit it if not fitting headings. However we must preserve ALL substantive information; we cannot drop company description unless we put it somewhere allowed. The allowed headings include "About the role". We could put company description there as part of the role description. That seems acceptable.
Similarly "About The Team" could be part of About the role or maybe omitted? It's substantive about team. We could include in About the role as well.
We need to avoid duplication.
Let's extract sections:
- About the role: introductory paragraph + maybe description of team and company.
Paragraph: "We have an exciting and rewarding opportunity for you to take your data engineering career to the next level. As a Lead Software Engineer - Databricks/PySpark/AI at JPMorganChase within the Corporate Sector-Global Finance team, you will serve as a senior hands-on developer and technical leader within an agile team, responsible for building, delivering, and optimizing cutting-edge data products that power agentic AI systems — autonomous AI agents capable of planning, reasoning, and executing multi-step tasks. In this role, you will write production-quality code daily, drive implementation of essential technology solutions including data infrastructure, tool integrations, and retrieval systems that enable AI agents to access, interpret, and act on enterprise data in support of the firm's business goals. You will be expected to mentor junior engineers, collaborate with cross-functional stakeholders, and champion engineering excellence through hands-on delivery."
Then maybe add about team: "Our professionals in our Corporate Functions cover a diverse range of areas from finance and risk to human resources and marketing. Our corporate teams are an essential part of our company, ensuring that we're setting our businesses, clients, customers and employees up for success."
And about US: "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 can combine.
- Responsibilities: list each bullet. The responsibilities paragraph is long with many sentences; we need to split into list items. The posting has sentences separated by line breaks? It appears as a paragraph with many clauses. We need to extract each duty as list item. Let's parse:
"Building and optimizing data pipelines and workflows that serve as the backbone for agentic AI systems, ensuring agents have reliable, real-time access to high-quality, structured and unstructured data"
"Drives team adoption of enterprise-authorized AI-assisted engineering practices within the work environment to improve code quality, delivery speed, and operational outcomes (e.g., AI-assisted code review/refactoring, test strategy acceleration, incident/root-cause analysis support), while establishing consistent validation standards (secure coding, peer review, automated testing) and promoting reuse of effective patterns across the team."
"Applies knowledge of tools within the Software Development Life Cycle toolchain, including enterprise-authorized AI-assisted development and automation capabilities, to improve the value realized by automation."
"Developing data retrieval and indexing layers that enable AI agents to autonomously search, query, and synthesize information across multiple data sources"
"Building and maintaining tool-use infrastructure — APIs, data services, and function endpoints — that AI agents invoke to execute tasks, retrieve data, and interact with enterprise systems"
"Implementing and enforcing best practices for data management, ensuring data quality, security, and compliance, including governance of data consumed and generated by autonomous AI agents"
"Hands-on development of secure, high-quality production code following AWS best practices, and deploying efficiently using CI/CD pipelines; Building orchestration and state management layers that support multi-step agent workflows, including memory, context persistence, and task chaining"
"Writing and reviewing code daily, conducting thorough code reviews, and raising the technical bar across the team; Mentoring and guiding junior and mid-level engineers through pairing, code reviews, and technical coaching"
"Collaborating with product owners, data scientists, and business stakeholders to translate business requirements into working, production-ready agentic AI solutions; Evaluating and adopting emerging agentic AI frameworks, tools, and data engineering practices to continuously improve the team's development capabilities"
We need to keep all details.
- Requirements: maybe combine Required Qualifications, Capabilities, And Skills as Requirements section. Use heading "Requirements". Or we could have "Qualifications". The allowed headings include Requirements, Qualifications, Skills. We need to decide. Since we have both required and preferred qualifications, we could have "Required Qualifications" under Requirements, and "Preferred Qualifications" under Skills? But better: Use "Requirements" for required qualifications, and "Skills" for preferred qualifications? However the instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can have multiple of those. We'll include Requirements (required qualifications), Qualifications (maybe also required?), Skills (preferred). To avoid duplication, we could put required qualifications under Requirements, and preferred qualifications under Skills. Or we could put required under Qualifications and preferred under Skills. Let's choose: Requirements = Required Qualifications, Capabilities, And Skills. Skills = Preferred Qualifications, Capabilities, And Skills. We'll not duplicate.
Thus:
Requirements
with ul list of required qualifications.
Skills
with ul list of preferred qualifications.
- Benefits: list benefits.
- Pay: list pay details.
We must not include headings with filler like "commensurate with experience". The posting includes base salary determined based on role, experience, skill set and location; commission-based pay and/or discretionary incentive compensation. That's specific enough.
Now produce HTML.
We need to ensure we don't include any markdown fences. Just raw HTML.
Let's craft.
First, About the role: we need
for prose. Could combine multiple paragraphs into one
or separate
tags. Use
for each paragraph.
We'll do:
About the role
We have an exciting and rewarding opportunity for you to take your data engineering career to the next level. As a Lead Software Engineer - Databricks/PySpark/AI at JPMorganChase within the Corporate Sector-Global Finance team, you will serve as a senior hands-on developer and technical leader within an agile team, responsible for building, delivering, and optimizing cutting-edge data products that power agentic AI systems — autonomous AI agents capable of planning, reasoning, and executing multi-step tasks. In this role, you will write production-quality code daily, drive implementation of essential technology solutions including data infrastructure, tool integrations, and retrieval systems that enable AI agents to access, interpret, and act on enterprise data in support of the firm's business goals. You will be expected to mentor junior engineers, collaborate with cross-functional stakeholders, and champion engineering excellence through hands-on delivery.
Our professionals in our Corporate Functions cover a diverse range of areas from finance and risk to human resources and marketing. Our corporate teams are an essential part of our company, ensuring that we're setting our businesses, clients, customers and employees up for success.
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:
Responsibilities
- Building and optimizing data pipelines and workflows that serve as the backbone for agentic AI systems, ensuring agents have reliable, real-time access to high-quality, structured and unstructured data
- Drives team adoption of enterprise-authorized AI-assisted engineering practices within the work environment to improve code quality, delivery speed, and operational outcomes (e.g., AI-assisted code review/refactoring, test strategy acceleration, incident/root-cause analysis support), while establishing consistent validation standards (secure coding, peer review, automated testing) and promoting reuse of effective patterns across the team.
- Applies knowledge of tools within the Software Development Life Cycle toolchain, including enterprise-authorized AI-assisted development and automation capabilities, to improve the value realized by automation.
- Developing data retrieval and indexing layers that enable AI agents to autonomously search, query, and synthesize information across multiple data sources
- Building and maintaining tool-use infrastructure — APIs, data services, and function endpoints — that AI agents invoke to execute tasks, retrieve data, and interact with enterprise systems
- Implementing and enforcing best practices for data management, ensuring data quality, security, and compliance, including governance of data consumed and generated by autonomous AI agents
- Hands-on development of secure, high-quality production code following AWS best practices, and deploying efficiently using CI/CD pipelines; Building orchestration and state management layers that support multi-step agent workflows, including memory, context persistence, and task chaining
- Writing and reviewing code daily, conducting thorough code reviews, and raising the technical bar across the team; Mentoring and guiding junior and mid-level engineers through pairing, code reviews, and technical coaching
- Collaborating with product owners, data scientists, and business stakeholders to translate business requirements into working, production-ready agentic AI solutions; Evaluating and adopting emerging agentic AI frameworks, tools, and data engineering practices to continuously improve the team's development capabilities
Now Requirements (required qualifications):
We need to extract list items from the
- for any list of duties/requirements/benefits. Use
for prose. We must preserve all substantive information, not invent or summarize away detail. Must not include boilerplate like EEO, equal-opportunity, scam-warning, cookie/navigation/legal, duplicated lines, application instructions. The posting includes EEO statements etc. We must remove those. Also remove "About Us" maybe we keep as part of About the role? Actually "About US" is company description; we could include as part of About the role or maybe a separate section "About the company". But only allowed headings are those listed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "About US" could be considered "About the role"? Not exactly. But we could incorporate company description into About the role paragraph. Or we could omit it if not fitting headings. However we must preserve ALL substantive information; we cannot drop company description unless we put it somewhere allowed. The allowed headings include "About the role". We could put company description there as part of the role description. That seems acceptable. Similarly "About The Team" could be part of About the role or maybe omitted? It's substantive about team. We could include in About the role as well. We need to avoid duplication. Let's extract sections: - About the role: introductory paragraph + maybe description of team and company. Paragraph: "We have an exciting and rewarding opportunity for you to take your data engineering career to the next level. As a Lead Software Engineer - Databricks/PySpark/AI at JPMorganChase within the Corporate Sector-Global Finance team, you will serve as a senior hands-on developer and technical leader within an agile team, responsible for building, delivering, and optimizing cutting-edge data products that power agentic AI systems — autonomous AI agents capable of planning, reasoning, and executing multi-step tasks. In this role, you will write production-quality code daily, drive implementation of essential technology solutions including data infrastructure, tool integrations, and retrieval systems that enable AI agents to access, interpret, and act on enterprise data in support of the firm's business goals. You will be expected to mentor junior engineers, collaborate with cross-functional stakeholders, and champion engineering excellence through hands-on delivery." Then maybe add about team: "Our professionals in our Corporate Functions cover a diverse range of areas from finance and risk to human resources and marketing. Our corporate teams are an essential part of our company, ensuring that we're setting our businesses, clients, customers and employees up for success." And about US: "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 can combine. - Responsibilities: list each bullet. The responsibilities paragraph is long with many sentences; we need to split into list items. The posting has sentences separated by line breaks? It appears as a paragraph with many clauses. We need to extract each duty as list item. Let's parse: "Building and optimizing data pipelines and workflows that serve as the backbone for agentic AI systems, ensuring agents have reliable, real-time access to high-quality, structured and unstructured data" "Drives team adoption of enterprise-authorized AI-assisted engineering practices within the work environment to improve code quality, delivery speed, and operational outcomes (e.g., AI-assisted code review/refactoring, test strategy acceleration, incident/root-cause analysis support), while establishing consistent validation standards (secure coding, peer review, automated testing) and promoting reuse of effective patterns across the team." "Applies knowledge of tools within the Software Development Life Cycle toolchain, including enterprise-authorized AI-assisted development and automation capabilities, to improve the value realized by automation." "Developing data retrieval and indexing layers that enable AI agents to autonomously search, query, and synthesize information across multiple data sources" "Building and maintaining tool-use infrastructure — APIs, data services, and function endpoints — that AI agents invoke to execute tasks, retrieve data, and interact with enterprise systems" "Implementing and enforcing best practices for data management, ensuring data quality, security, and compliance, including governance of data consumed and generated by autonomous AI agents" "Hands-on development of secure, high-quality production code following AWS best practices, and deploying efficiently using CI/CD pipelines; Building orchestration and state management layers that support multi-step agent workflows, including memory, context persistence, and task chaining" "Writing and reviewing code daily, conducting thorough code reviews, and raising the technical bar across the team; Mentoring and guiding junior and mid-level engineers through pairing, code reviews, and technical coaching" "Collaborating with product owners, data scientists, and business stakeholders to translate business requirements into working, production-ready agentic AI solutions; Evaluating and adopting emerging agentic AI frameworks, tools, and data engineering practices to continuously improve the team's development capabilities" We need to keep all details. - Requirements: maybe combine Required Qualifications, Capabilities, And Skills as Requirements section. Use heading "Requirements". Or we could have "Qualifications". The allowed headings include Requirements, Qualifications, Skills. We need to decide. Since we have both required and preferred qualifications, we could have "Required Qualifications" under Requirements, and "Preferred Qualifications" under Skills? But better: Use "Requirements" for required qualifications, and "Skills" for preferred qualifications? However the instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can have multiple of those. We'll include Requirements (required qualifications), Qualifications (maybe also required?), Skills (preferred). To avoid duplication, we could put required qualifications under Requirements, and preferred qualifications under Skills. Or we could put required under Qualifications and preferred under Skills. Let's choose: Requirements = Required Qualifications, Capabilities, And Skills. Skills = Preferred Qualifications, Capabilities, And Skills. We'll not duplicate. Thus:
Requirements
with ul list of required qualifications.Skills
with ul list of preferred qualifications. - Benefits: list benefits. - Pay: list pay details. We must not include headings with filler like "commensurate with experience". The posting includes base salary determined based on role, experience, skill set and location; commission-based pay and/or discretionary incentive compensation. That's specific enough. Now produce HTML. We need to ensure we don't include any markdown fences. Just raw HTML. Let's craft. First, About the role: we needfor prose. Could combine multiple paragraphs into one
or separate
tags. Use
for each paragraph. We'll do:
About the role
We have an exciting and rewarding opportunity for you to take your data engineering career to the next level. As a Lead Software Engineer - Databricks/PySpark/AI at JPMorganChase within the Corporate Sector-Global Finance team, you will serve as a senior hands-on developer and technical leader within an agile team, responsible for building, delivering, and optimizing cutting-edge data products that power agentic AI systems — autonomous AI agents capable of planning, reasoning, and executing multi-step tasks. In this role, you will write production-quality code daily, drive implementation of essential technology solutions including data infrastructure, tool integrations, and retrieval systems that enable AI agents to access, interpret, and act on enterprise data in support of the firm's business goals. You will be expected to mentor junior engineers, collaborate with cross-functional stakeholders, and champion engineering excellence through hands-on delivery.
Our professionals in our Corporate Functions cover a diverse range of areas from finance and risk to human resources and marketing. Our corporate teams are an essential part of our company, ensuring that we're setting our businesses, clients, customers and employees up for success.
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:Responsibilities
- Building and optimizing data pipelines and workflows that serve as the backbone for agentic AI systems, ensuring agents have reliable, real-time access to high-quality, structured and unstructured data
- Drives team adoption of enterprise-authorized AI-assisted engineering practices within the work environment to improve code quality, delivery speed, and operational outcomes (e.g., AI-assisted code review/refactoring, test strategy acceleration, incident/root-cause analysis support), while establishing consistent validation standards (secure coding, peer review, automated testing) and promoting reuse of effective patterns across the team.
- Applies knowledge of tools within the Software Development Life Cycle toolchain, including enterprise-authorized AI-assisted development and automation capabilities, to improve the value realized by automation.
- Developing data retrieval and indexing layers that enable AI agents to autonomously search, query, and synthesize information across multiple data sources
- Building and maintaining tool-use infrastructure — APIs, data services, and function endpoints — that AI agents invoke to execute tasks, retrieve data, and interact with enterprise systems
- Implementing and enforcing best practices for data management, ensuring data quality, security, and compliance, including governance of data consumed and generated by autonomous AI agents
- Hands-on development of secure, high-quality production code following AWS best practices, and deploying efficiently using CI/CD pipelines; Building orchestration and state management layers that support multi-step agent workflows, including memory, context persistence, and task chaining
- Writing and reviewing code daily, conducting thorough code reviews, and raising the technical bar across the team; Mentoring and guiding junior and mid-level engineers through pairing, code reviews, and technical coaching
- Collaborating with product owners, data scientists, and business stakeholders to translate business requirements into working, production-ready agentic AI solutions; Evaluating and adopting emerging agentic AI frameworks, tools, and data engineering practices to continuously improve the team's development capabilities