Principal Cybersecurity Architect
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. Remove boilerplate.
We need to parse the job description.
Content:
First paragraph: "Take your engineering expertise to new heights by joining a team of exceptionally talented professionals and solidify your place among top performers in the industry. As a Senior Principal Cybersecurity Architect at JPMorganChase within Cybersecurity and Technology Controls, you will be aligned to the Consumer and Community Banking organization, providing deep cybersecurity expertise and working across teams to identify and communicate risk, and create mitigation options and solutions alongside engineering partners. You will leverage your deep cross-domain expertise to bring together talent that will consistently create solutions, processes, and reusable proof-of-concept models for cybersecurity while remaining at the forefront of best practices for cybersecurity policy and technological advances. In this role, you will have the opportunity to shape the firm's cybersecurity posture at scale, influencing strategy and architecture across a broad and complex portfolio."
That's about the role. So we can have About the role
with
containing that paragraph. Next: "Job Responsibilities" then list bullet points: - Advise and lead the cybersecurity strategy and development of multiple products, applications, and technologies across a portfolio - Translate highly complex technical issues, trends, and approaches to leadership to drive the firm's innovation and enable leaders to make strategic, well-informed decisions about target state architecture - Drive the adoption and implementation of new technical methods in cybersecurity in line with the latest product development methodologies - Create durable, reusable cybersecurity frameworks that improve velocity and quality of output across teams and functions - Develop architectures that have applicability across businesses and functions - Identify and communicate risk across engineering teams, creating mitigation options and actionable solutions - Champion the firm's culture of diversity, opportunity, inclusion, and respect Thus
Responsibilities
with- each.
Next: "Required Qualifications, Capabilities, And Skills" then list bullet points:
- Formal training or certification on cybersecurity architecture concepts and 10+ years applied experience
- Practical experience delivering cybersecurity architecture that can be applied and reused across businesses, functions, and systems
- Fluency in one or more programming languages or applications
- Demonstrated experience influencing across functions and teams to deliver modern cybersecurity architecture
- Experience applying expertise and new methods to determine solutions for new and complex cybersecurity problems across various disciplines
- Extensive practical cloud-native experience
- Ability to evaluate current and emerging technologies to recommend the best solutions or approaches to achieve future state cybersecurity architecture
- Experience leading a product as a Product Owner, Product Manager, or Software Engineering Manager
Thus
Required Qualifications
maybe combine with "Qualifications". The instruction says we can have sections: Requirements, Qualifications, Skills. We need to decide which to use. The posting has "Required Qualifications, Capabilities, And Skills". Could treat as Qualifications and Skills combined. We could split into Qualifications and Skills sections if we have distinct content. But we have both qualifications and skills mixed. Could create a singleQualifications
with list. Or we could createRequired Qualifications
andSkills
but we need to avoid thin sections. Probably better to have one Qualifications section containing all those bullet points. Then "Preferred Qualifications, Capabilities, And Skills" bullet list: - Experience with artificial intelligence, machine learning, or mobile technologies - Expertise in API, web, and mobile application security - Prior experience in the banking or financial services industry - Familiarity with regulatory requirements and compliance standards relevant to financial services We could include as another Qualifications section? Could be "Preferred Qualifications". But we have only one Qualifications section allowed? We could have two: Required Qualifications and Preferred Qualifications. Both are substantive. That seems okay. Then "#CTC About Us" paragraph about JPMorganChase. That's company overview; could be considered "About the company" but not in allowed headings. The allowed headings list does not include About the company. So we might omit or incorporate into About the role? Probably we should omit as it's boilerplate? It's not exactly boilerplate but it's generic company description. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This company overview may be considered boilerplate? It's not strictly required to keep. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The company overview is substantive? It describes the firm. Might be considered relevant but not part of the role. However the allowed headings do not have a slot for company overview. We could put it under About the role? But that would be mixing. Better to omit? The instruction says "Prefer a few substantive sections over many thin ones." It didn't say we must include all content; we must preserve ALL substantive information. So we need to keep it somewhere. Perhaps we can include aafter the role description that includes that overview, still under About the role heading? Could add another paragraph after the role description within same section. That would preserve it. Thus About the role section can have multiple paragraphs: first the role description, then the company overview paragraph. Next: "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." This contains Pay and Benefits info. So we need sections for Pay and Benefits if they have specific content. Pay: mention base salary determined based on role, experience, skill set and location; commission-based pay and/or discretionary incentive compensation. That's specific enough. Benefits: list of benefits. Thus we should have
Pay
withcontaining that sentence(s). And
Benefits
with- list.
We also have "We recognize that our people are our strength..." EEO boilerplate; we should remove that as it's equal-opportunity boilerplate. Also "Visit our FAQs..." etc. Remove.
Also "#CTC About Us" we already used.
Also "About The Team" paragraph about corporate functions. That's not directly about the role; could be considered company overview but maybe not needed. It's somewhat generic. Could be omitted as boilerplate? It's describing corporate functions; not specific to role. Likely we can omit as it's not substantive to the job. The instruction says remove duplicated lines, legal/EEO etc. This is not EEO but still generic. Might be considered boilerplate. Safer to omit.
Thus final HTML:
About the role
Take your engineering expertise to new heights by joining a team of exceptionally talented professionals and solidify your place among top performers in the industry. As a Senior Principal Cybersecurity Architect at JPMorganChase within Cybersecurity and Technology Controls, you will be aligned to the Consumer and Community Banking organization, providing deep cybersecurity expertise and working across teams to identify and communicate risk, and create mitigation options and solutions alongside engineering partners. You will leverage your deep cross-domain expertise to bring together talent that will consistently create solutions, processes, and reusable proof-of-concept models for cybersecurity while remaining at the forefront of best practices for cybersecurity policy and technological advances. In this role, you will have the opportunity to shape the firm's cybersecurity posture at scale, influencing strategy and architecture across a broad and complex portfolio.
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.
Responsibilities
- Advise and lead the cybersecurity strategy and development of multiple products, applications, and technologies across a portfolio
- Translate highly complex technical issues, trends, and approaches to leadership to drive the firm's innovation and enable leaders to make strategic, well-informed decisions about target state architecture
- Drive the adoption and implementation of new technical methods in cybersecurity in line with the latest product development methodologies
- Create durable, reusable cybersecurity frameworks that improve velocity and quality of output across teams and functions
- Develop architectures that have applicability across businesses and functions
- Identify and communicate risk across engineering teams, creating mitigation options and actionable solutions
- Champion the firm's culture of diversity, opportunity, inclusion, and respect
Required Qualifications
- Formal training or certification on cybersecurity architecture concepts and 10+ years applied experience
- Practical experience delivering cybersecurity architecture that can be applied and reused across businesses, functions, and systems
- Fluency in one or more programming languages or applications
- Demonstrated experience influencing across functions and teams to deliver modern cybersecurity architecture
- Experience applying expertise and new methods to determine solutions for new and complex cybersecurity problems across various disciplines
- Extensive practical cloud-native experience
- Ability to evaluate current and emerging technologies to recommend the best solutions or approaches to achieve future state cybersecurity architecture
- Experience leading a product as a Product Owner, Product Manager, or Software Engineering Manager
Preferred Qualifications
- Experience with artificial intelligence, machine learning, or mobile technologies
- Expertise in API, web, and mobile application security
- Prior experience in the banking or financial services industry
- Familiarity with regulatory requirements and compliance standards relevant to financial services
Pay
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.
Benefits
- Comprehensive health care coverage
- On-site health and wellness centers
- Retirement savings plan
- Backup childcare
- Tuition reimbursement
- Mental health support
- Financial coaching
- list.
We also have "We recognize that our people are our strength..." EEO boilerplate; we should remove that as it's equal-opportunity boilerplate. Also "Visit our FAQs..." etc. Remove.
Also "#CTC About Us" we already used.
Also "About The Team" paragraph about corporate functions. That's not directly about the role; could be considered company overview but maybe not needed. It's somewhat generic. Could be omitted as boilerplate? It's describing corporate functions; not specific to role. Likely we can omit as it's not substantive to the job. The instruction says remove duplicated lines, legal/EEO etc. This is not EEO but still generic. Might be considered boilerplate. Safer to omit.
Thus final HTML: