Principal Systems Architect - Application Security
Wells Fargo · Chandler, AZ · 1 mo ago
Engineering$159k–$254k/yrFull-time
We need to output HTML fragment with sections: About the role? Actually the posting starts with "About this role:" then description. We need to use for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. We have content for About the role (the paragraph). Responsibilities: bullet list of duties (starting with "In this role, you will:" then list). Requirements: maybe "Required Qualifications". Qualifications: maybe "Desired Qualifications". Skills: maybe not explicit separate; but we could combine? The instruction: Use headings for those categories if content exists. We have "Required Qualifications" and "Desired Qualifications". Could map Required Qualifications to Requirements heading, Desired Qualifications to Qualifications heading. Skills maybe not separate; we could omit if no specific skills list. Benefits: we have benefits list. Pay: we have salary ranges. Schedule: we have "This position offers a hybrid work schedule". Also job expectations include AI usage etc. Those could go under Responsibilities or maybe a separate section? But we should follow headings only if content.
We must not repeat job title as heading. No Job ID etc. Remove boilerplate like EEO, etc. Also remove "Posting End Date", "Job posting may come down early", "We Value Equal Opportunity", etc. Also remove "Reference Number". Also remove "Job Expectations" maybe we can incorporate into Responsibilities or a separate section? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings. Job Expectations could be part of Responsibilities or maybe a separate "Responsibilities". The bullet list after "In this role, you will:" are responsibilities. The later "Job Expectations:" includes hybrid work schedule, visa sponsorship, AI usage expectations. Those could be considered part of Responsibilities or maybe a separate "Schedule" for hybrid work schedule, and maybe "Skills" for AI usage? But better to keep them under Responsibilities as they are expectations. However we have a specific Schedule heading for hybrid work schedule. So we could extract hybrid work schedule into Schedule section. The rest of Job Expectations (visa sponsorship not eligible, AI usage) could be considered Responsibilities or maybe omitted? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep visa sponsorship statement and AI usage expectations. Where to place? Could be under Responsibilities as bullet items. Or we could create a separate section like "Expectations" but not allowed headings unless from list. So we must fit into allowed headings. Could put them under Responsibilities as additional bullet points.
Thus sections:
- About the role: paragraph from "About this role: Wells Fargo is seeking ..." up to "This role is ideal for a security architect ..." maybe also include the sentence "As a senior technical leader, you will influence enterprise security strategy..." That's part of About.
- Responsibilities: bullet list from "In this role, you will:" plus the Job Expectations bullet points (hybrid work schedule? Actually hybrid goes to Schedule). We'll keep hybrid in Schedule. Visa sponsorship statement and AI usage expectations go under Responsibilities.
- Requirements: Required Qualifications content.
- Qualifications: Desired Qualifications content.
- Skills: maybe not present; we could omit.
- Benefits: list of benefits.
- Pay: salary ranges.
- Schedule: hybrid work schedule.
We must not include placeholder text like "commensurate with experience". Not present.
We must not include duplicated lines.
We must output only HTML fragment, no markdown fences.
Let's extract content precisely.
About this role paragraph:
"About this role: Wells Fargo is seeking a Principal Security Architect - Application Security to help shape the future of secure software development across one of the world's largest financial institutions. As a senior technical leader, you will influence enterprise security strategy, define architecture standards, and drive secure-by-design practices across modern application platforms, cloud-native technologies, software supply chains, and emerging technologies, including AI-enabled systems. This role is ideal for a security architect who combines deep technical expertise, strong engineering fundamentals, and strategic influence to solve complex security challenges at enterprise scale."
We should strip the leading "About this role:" maybe keep as part of paragraph? The heading will be About the role, so we can start paragraph after that. We'll output:
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. We have content for About the role (the paragraph). Responsibilities: bullet list of duties (starting with "In this role, you will:" then list). Requirements: maybe "Required Qualifications". Qualifications: maybe "Desired Qualifications". Skills: maybe not explicit separate; but we could combine? The instruction: Use headings for those categories if content exists. We have "Required Qualifications" and "Desired Qualifications". Could map Required Qualifications to Requirements heading, Desired Qualifications to Qualifications heading. Skills maybe not separate; we could omit if no specific skills list. Benefits: we have benefits list. Pay: we have salary ranges. Schedule: we have "This position offers a hybrid work schedule". Also job expectations include AI usage etc. Those could go under Responsibilities or maybe a separate section? But we should follow headings only if content.
We must not repeat job title as heading. No Job ID etc. Remove boilerplate like EEO, etc. Also remove "Posting End Date", "Job posting may come down early", "We Value Equal Opportunity", etc. Also remove "Reference Number". Also remove "Job Expectations" maybe we can incorporate into Responsibilities or a separate section? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings. Job Expectations could be part of Responsibilities or maybe a separate "Responsibilities". The bullet list after "In this role, you will:" are responsibilities. The later "Job Expectations:" includes hybrid work schedule, visa sponsorship, AI usage expectations. Those could be considered part of Responsibilities or maybe a separate "Schedule" for hybrid work schedule, and maybe "Skills" for AI usage? But better to keep them under Responsibilities as they are expectations. However we have a specific Schedule heading for hybrid work schedule. So we could extract hybrid work schedule into Schedule section. The rest of Job Expectations (visa sponsorship not eligible, AI usage) could be considered Responsibilities or maybe omitted? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep visa sponsorship statement and AI usage expectations. Where to place? Could be under Responsibilities as bullet items. Or we could create a separate section like "Expectations" but not allowed headings unless from list. So we must fit into allowed headings. Could put them under Responsibilities as additional bullet points.
Thus sections:
- About the role: paragraph from "About this role: Wells Fargo is seeking ..." up to "This role is ideal for a security architect ..." maybe also include the sentence "As a senior technical leader, you will influence enterprise security strategy..." That's part of About.
- Responsibilities: bullet list from "In this role, you will:" plus the Job Expectations bullet points (hybrid work schedule? Actually hybrid goes to Schedule). We'll keep hybrid in Schedule. Visa sponsorship statement and AI usage expectations go under Responsibilities.
- Requirements: Required Qualifications content.
- Qualifications: Desired Qualifications content.
- Skills: maybe not present; we could omit.
- Benefits: list of benefits.
- Pay: salary ranges.
- Schedule: hybrid work schedule.
We must not include placeholder text like "commensurate with experience". Not present.
We must not include duplicated lines.
We must output only HTML fragment, no markdown fences.
Let's extract content precisely.
About this role paragraph:
"About this role: Wells Fargo is seeking a Principal Security Architect - Application Security to help shape the future of secure software development across one of the world's largest financial institutions. As a senior technical leader, you will influence enterprise security strategy, define architecture standards, and drive secure-by-design practices across modern application platforms, cloud-native technologies, software supply chains, and emerging technologies, including AI-enabled systems. This role is ideal for a security architect who combines deep technical expertise, strong engineering fundamentals, and strategic influence to solve complex security challenges at enterprise scale."
We should strip the leading "About this role:" maybe keep as part of paragraph? The heading will be About the role, so we can start paragraph after that. We'll output:
About the role
Wells Fargo is seeking a Principal Security Architect - Application Security to help shape the future of secure software development across one of the world's largest financial institutions. As a senior technical leader, you will influence enterprise security strategy, define architecture standards, and drive secure-by-design practices across modern application platforms, cloud-native technologies, software supply chains, and emerging technologies, including AI-enabled systems. This role is ideal for a security architect who combines deep technical expertise, strong engineering fundamentals, and strategic influence to solve complex security challenges at enterprise scale.
Responsibilities: start after "In this role, you will:" list items: - Advise senior technology and cybersecurity leaders on application security strategy, architecture, and risk management. - Define and drive enterprise security standards, reference architectures, design patterns, and security requirements. - Lead security architecture reviews, threat modeling, and risk assessments for strategic initiatives, enterprise platforms, and emerging technologies. - Champion secure-by-design practices across application development, APIs, cloud-native platforms, DevSecOps pipelines, and software supply chain ecosystems. - Lead enterprise initiatives related to secure software development, software supply chain security, developer security platforms, application security modernization, and secure AI adoption. - Influence enterprise technology strategy, architectural direction, and investment decisions that advance secure software development and technology modernization. - Evaluate technologies through architecture analysis, design reviews, prototyping, automation, and technical experimentation. - Drive adoption of automation and AI-enabled capabilities that improve security outcomes, engineering productivity, and operational efficiency. - Mentor architects and senior engineers while fostering technical excellence and innovation. Then Job Expectations bullet points (excluding hybrid schedule maybe): - This position is not eligible for Visa sponsorship - Demonstrate proficiency in using AI‑assisted development and analysis tools (e.g., GitHub Copilot and approved code‑centric agents) - Leverage AI to accelerate system design, coding, testing, analysis, and troubleshooting - Apply strong technical judgment when validating and integrating AI‑assisted outputs into solutions - Understand and account for model limitations, security risks, and operational considerations - Apply AI responsibly in development and production environments - Ensure AI usage aligns with security, compliance, privacy, and ethical standards We could combine these as bullet list under Responsibilities. Thus Responsibilities section:Responsibilities
- Advise senior technology and cybersecurity leaders on application security strategy, architecture, and risk management.
- Define and drive enterprise security standards, reference architectures, design patterns, and security requirements.
- Lead security architecture reviews, threat modeling, and risk assessments for strategic initiatives, enterprise platforms, and emerging technologies.
- Champion secure-by-design practices across application development, APIs, cloud-native platforms, DevSecOps pipelines, and software supply chain ecosystems.
- Lead enterprise initiatives related to secure software development, software supply chain security, developer security platforms, application security modernization, and secure AI adoption.
- Influence enterprise technology strategy, architectural direction, and investment decisions that advance secure software development and technology modernization.
- Evaluate technologies through architecture analysis, design reviews, prototyping, automation, and technical experimentation.
- Drive adoption of automation and AI-enabled capabilities that improve security outcomes, engineering productivity, and operational efficiency.
- Mentor architects and senior engineers while fostering technical excellence and innovation.
- This position is not eligible for Visa sponsorship.
- Demonstrate proficiency in using AI‑assisted development and analysis tools (e.g., GitHub Copilot and approved code‑centric agents).
- Leverage AI to accelerate system design, coding, testing, analysis, and troubleshooting.
- Apply strong technical judgment when validating and integrating AI‑assisted outputs into solutions.
- Understand and account for model limitations, security risks, and operational considerations.
- Apply AI responsibly in development and production environments.
- Ensure AI usage aligns with security, compliance, privacy, and ethical standards.
- for any list of duties/requirements/benefits. So we should convert each sentence into list items. However the block includes some combined statements like "7+ years of architecture experience, or equivalent demonstrated through one or a combination of the following: work experience, training, military experience, education". That's a bit complex. We could split into items: "7+ years of architecture experience, or equivalent demonstrated through work experience, training, military experience, or education". Then "7+ years of Architecture, Application Security, Software Security, or related cybersecurity experience." Actually that seems duplicate. Might be a mistake in posting. We'll preserve as separate items maybe.
Better to keep as paragraphs? But instruction says use
- for any list of duties/requirements/benefits. The Required Qualifications is a list of requirements. So we should list each requirement as
- . We'll break down: - 7+ years of architecture experience, or equivalent demonstrated through work experience, training, military experience, or education. - 7+ years of Architecture, Application Security, Software Security, or related cybersecurity experience. - Deep expertise in application security architecture, secure software development, software supply chain security, threat modeling, and modern application architectures. - Experience establishing enterprise security standards, architecture patterns, governance frameworks, or strategic initiatives adopted across multiple organizations. - Experience leading enterprise-scale transformation initiatives involving application security, secure software development, software supply chain security, developer security platforms, or secure adoption of emerging technologies. - Strong technical and engineering background with the ability to evaluate architectures, review technical designs, assess application code, and validate solutions through prototyping or proof-of-concept development. - Experience securing modern application ecosystems, including APIs, cloud-native platforms, software delivery pipelines, open-source software, and distributed architectures. - Proven ability to influence senior technology leaders, architects, engineering organizations, and cybersecurity stakeholders. We'll output that. Qualifications (Desired Qualifications): Block: "Desired Qualifications: Expertise in cloud-native security, API security, DevSecOps, and software supply chain security. Experience with modern application security capabilities, including SAST, DAST, SCA, secrets detection, infrastructure-as-code security, container security, SBOM management, and CI/CD security controls. Experience developing secure software, automation, security tooling, reusable frameworks, prototypes, or proof-of-concepts. Demonstrated engineering depth sufficient to engage credibly with software engineers and evaluate application code, development practices, and emerging technologies. Knowledge of secure AI development practices, AI-assisted development technologies, AI application architectures, and security approaches for AI-enabled systems. Ability to translate complex technical challenges into enterprise standards, architecture patterns, and strategic