Principal Software Engineer - Security Platforms
JPMorganChase · Columbus, OH · 2 wk ago
On-siteEngineeringFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content.
We need to parse the job description.
Content:
- Intro paragraph: "If you are looking for a game-changing career, working for one of the world's leading financial institutions, you've come to the right place. As a Principal Software Engineer at JPMorganChase within the Consumer & Community Banking CTC, you provide expertise and engineering excellence as an integral part of an agile team to enhance, build, and deliver trusted market-leading technology products in a secure, stable, and scalable way. Leverage your advanced technical capabilities and collaborate with colleagues across the organization to drive best-in-class outcomes across various technologies to support one or more of the firm's portfolios."
That's about the role. So we can have .
- Required Qualifications, Capabilities, And Skills: This section includes qualifications and skills. We need to split maybe into Requirements, Qualifications, Skills? The instruction says we can have sections: Requirements, Qualifications, Skills. We need to decide what content goes where.
The text: "Required Qualifications, Capabilities, And Skills Formal training or certification on software engineering concepts and 7+ years applied experience Hands-on practical experience delivering system design, application development, testing, and operational stabilityExpert in one or more programming language(s)Demonstrated experience designing and leading adoption of agentic AI-enabled development practices (using enterprise-authorized tools within the work environment) across teams, including setting standards for human-in-the-loop validation, auditability/traceability of changes, and secure handling of sensitive data.Strong understanding of responsible AI use and control expectations in engineering workflows, including security/resiliency implications, data sensitivity, and risk-based governance; ability to influence senior technical leaders on safe scaling patterns and reuse.Experience applying expertise and new methods to determine solutions for complex technology problems in one or more technical disciplinesAbility to present and effectively communicate with Senior Leaders and ExecutivesUnderstanding of the businessPractical cloud native experience #CTC"
We need to break into list items.
Let's parse:
- Formal training or certification on software engineering concepts and 7+ years applied experience
- Hands-on practical experience delivering system design, application development, testing, and operational stability
- Expert in one or more programming language(s)
- Demonstrated experience designing and leading adoption of agentic AI-enabled development practices (using enterprise-authorized tools within the work environment) across teams, including setting standards for human-in-the-loop validation, auditability/traceability of changes, and secure handling of sensitive data.
- Strong understanding of responsible AI use and control expectations in engineering workflows, including security/resiliency implications, data sensitivity, and risk-based governance; ability to influence senior technical leaders on safe scaling patterns and reuse.
- Experience applying expertise and new methods to determine solutions for complex technology problems in one or more technical disciplines
- Ability to present and effectively communicate with Senior Leaders and Executives
- Understanding of the business
- Practical cloud native experience
We can treat these as Requirements or Qualifications. The instruction says we can have sections: Requirements, Qualifications, Skills. We need to decide mapping. Typically "Required Qualifications, Capabilities, And Skills" could be split into Qualifications and Skills. But we can also just put all under Requirements or Qualifications. Since we want few substantive sections, we could combine into a single section like "Requirements" (or "Qualifications") and list all. But we need to follow instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can choose to include Requirements and maybe Skills separate if we can differentiate.
We have both qualifications (experience, training) and skills (programming languages, AI expertise, communication, business understanding, cloud native). Could separate: Qualifications: formal training/certification, 7+ years experience, hands-on practical experience delivering system design..., understanding of business, practical cloud native experience? Skills: expert in programming languages, demonstrated experience designing AI-enabled development practices, strong understanding of responsible AI use, ability to present/communicate, experience applying expertise to solve complex tech problems.
But it's somewhat arbitrary. However we must not create sections with filler. We need real specific content for each section we include.
We could include:
- Requirements: maybe the experience and training items.
- Qualifications: maybe the same? Might be redundant.
Better to have just one section: "Requirements" (or "Qualifications") containing all items. Then we could also have a "Skills" section if we can extract distinct skill items.
Let's see if we can separate:
Qualifications (formal): Formal training or certification on software engineering concepts and 7+ years applied experience; Hands-on practical experience delivering system design, application development, testing, and operational stability; Understanding of the business; Practical cloud native experience.
Skills: Expert in one or more programming language(s); Demonstrated experience designing and leading adoption of agentic AI-enabled development practices ...; Strong understanding of responsible AI use and control expectations ...; Ability to present and effectively communicate with Senior Leaders and Executives; Experience applying expertise and new methods to determine solutions for complex technology problems in one or more technical disciplines.
That seems reasonable.
Now Benefits: The posting mentions benefits under "About Us": "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 benefits 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.
Also Pay: base salary determined based on role, experience, skill set and location; commission-based pay and/or discretionary incentive compensation (cash/forfeitable equity). That's pay info.
Schedule: Not mentioned. So we should not include Schedule section.
Thus we will have sections: About the role, Responsibilities, Requirements (or Qualifications), Skills, Benefits, Pay.
We need to decide which heading to use for the combined qualifications/skills split. We'll use Requirements for the experience/training/business/cloud native, and Skills for the technical/programming/AI/communication/problem solving.
Check if any content duplicates: Ensure we don't repeat.
Now we need to strip boilerplate: Remove EEO, equal-opportunity, scam-warning, navigation, cookie, legal, duplicated lines, application instructions. Also remove "About Us" paragraph that is generic about the firm? Actually we need to preserve substantive information. The "About Us" paragraph includes description of JPMorganChase, history, etc. That's substantive? It's about the company, not the role. Might be considered boilerplate? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About Us" description is not explicitly listed as boilerplate, but it's generic corporate description. Might be considered not specific to the job. However the instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The "About Us" paragraph is substantive about the company, but not about the role. The instruction didn't say to remove company overview. It only lists specific boilerplate types. So we might keep it? However the sections we are to output are limited to About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The company overview doesn't fit those headings. So we likely should omit it because it doesn't map to any of those sections. The instruction says "include a section ONLY when the posting has real, specific content for it". So we should not create a section for company overview. So we omit that paragraph.
Also remove "About The Team" paragraph (Corporate Functions). Not relevant to role.
Also remove "#CTC" tag maybe.
Now we need to format.
Let's craft HTML:
About the role
with that paragraph. - Job Responsibilities: bullet list (looks like sentences separated by line breaks). We need to extract each bullet. Responsibilities lines: "Creates complex and scalable coding frameworks using appropriate software design frameworks" "Develops secure and high-quality production code, and reviews and debugs code written by others" "Architects and governs agentic AI-enabled engineering workflows (using enterprise-authorized tools within the work environment) to improve delivery speed, code quality, and operational outcomes at scale (e.g., AI-driven PR review assistance, test generation/maintenance, release readiness checks, incident triage and root-cause acceleration), while defining guardrails for validation, security, resiliency, and reuse across teams." "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 at scale." "Advises cross-functional teams on technological matters within domain of expertise" "Serves as the function's go-to subject matter expert" "Contributes to the development of technical methods in specialized fields in line with the latest product development methodologies" "Creates durable, reusable software frameworks that are leveraged across teams and functions" "Influences leaders and senior stakeholders across business, product, and technology teams" We'll put each asAbout the role
If you are looking for a game-changing career, working for one of the world's leading financial institutions, you've come to the right place. As a Principal Software Engineer at JPMorganChase within the Consumer & Community Banking CTC, you provide expertise and engineering excellence as an integral part of an agile team to enhance, build, and deliver trusted market-leading technology products in a secure, stable, and scalable way. Leverage your advanced technical capabilities and collaborate with colleagues across the organization to drive best-in-class outcomes across various technologies to support one or more of the firm's portfolios.
Responsibilities
- Creates complex and scalable coding frameworks using appropriate software design frameworks
- Develops secure and high-quality production code, and reviews and debugs code written by others
- Architects and governs agentic AI-enabled engineering workflows (using enterprise-authorized tools within the work environment) to improve delivery speed, code quality, and operational outcomes at scale (e.g., AI-driven PR review assistance, test generation/maintenance, release readiness checks, incident triage and root-cause acceleration), while defining guardrails for validation, security, resiliency, and reuse across teams.
- 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 at scale.
- Advises cross-functional teams on technological matters within domain of expertise
- Serves as the function's go-to subject matter expert
- Contributes to the development of technical methods in specialized fields in line with the latest product development methodologies
- Creates durable, reusable software frameworks that are leveraged across teams and functions
- Influences leaders and senior stakeholders across business, product, and technology teams
Requirements
- Formal training or certification on software engineering concepts and 7+ years applied experience
- Hands-on practical experience delivering system design, application development, testing, and operational stability
- Understanding of the business
- Practical cloud native experience
Skills
- Expert in one or more programming language(s)
- Demonstrated experience designing and leading adoption of agentic AI-enabled development practices (using enterprise-authorized tools within the work environment) across teams, including setting standards