Senior Information Security Engineer
for each heading. Only include sections when posting has real specific content. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate, duplicate lines, application instructions, EEO, etc. Also no Job ID/requisition numbers as headings; fold minor metadata into short
or drop it. We need to parse the posting. Content: - About This Role: "Wells Fargo is seeking a Senior Information Security Engineer to join our Application Security Team." - In This Role, You Will: list of bullet points (design and implement repeatable... etc). Those are responsibilities. - Required Qualifications: list. - Desired Qualifications: list. - Job Expectations: includes hybrid work schedule, not eligible for Visa sponsorship, AI usage expectations. - Salary Ranges: multiple locations with ranges. - Benefits: list. - Posting End Date: maybe minor metadata. - EEO etc to drop. We need sections: About the role (maybe
About the role
with paragraph). Responsibilities (Responsibilities
with- ). Requirements (
Requirements
maybe combine Required Qualifications? Could also have Qualifications. The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections to include based on content. We have content for About the role, Responsibilities, Requirements (maybe Required Qualifications), Qualifications (maybe Desired Qualifications?), Skills (maybe list of specific skills like SAST, DAST, etc), Benefits, Pay, Schedule (hybrid work schedule). Also maybe Job Expectations includes schedule and AI expectations; could be part of Schedule or separate but we only have Schedule heading allowed. We need to avoid filler like "commensurate with experience". Not present. We must not repeat job title as heading. We must not put Job ID/requisition numbers as headings; we can drop or put in short. The posting includes "Reference Number R-561938-3". That's minor metadata; we can put in a
maybe at end or drop. Probably drop as per instruction: fold minor metadata into a short
or drop it. We'll drop. We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to include all bullet points exactly as given, but we can format as
- . Must not lose any detail.
Let's extract each piece.
About This Role: "Wells Fargo is seeking a Senior Information Security Engineer to join our Application Security Team."
That's it.
In This Role, You Will: list:
- Design and implement repeatable, scalable, and automated AppSec processes
- Provide hands-on technical leadership in tooling integration, automation, and process execution
- Implement ongoing product (internal and vendor) enhancements and fine-tuning of rules to increase the precision in identifying and prioritizing application security defects.
- Manage upgrades, resiliency, continuity, and compliance with enterprise standards.
- Recommend mitigation strategies for identified application security risks
- Serve as an AppSec representative in cross-functional governance and technical forums
- Support integration of AppSec controls across enterprise tools and CI/CD pipelines
- Support reporting of AppSec processes, execution status, and outcomes
- Collaborate with control management and cybersecurity leadership to design new security controls
- Support internal and external audits, regulatory reviews, and third-party assessments
That's responsibilities.
Required Qualifications:
- 4+ years of Information Security Engineering experience, or equivalent demonstrated through one or a combination of the following: work experience, training, military experience, education
- Expertise across core Application Security domains SAST, DAST, SCA, Secrets management and detection, Infrastructure as Code (IaC)
- Strong experience integrating SAST, DAST, and SCA tools into SDLC workflows and source code repositories
- Advanced knowledge of GitHub, Jira, ServiceNow, Jenkins, Harness, and CI/CD ecosystems
- Strong understanding of OWASP standards and MITRE CVE/CWE frameworks
- Experience implementing and maturing Secure Software Development Lifecycle (SSDLC) practices across Agile and custom development frameworks
- Familiarity with AI/LLM-enabled development tooling (e.g., Cursor, GitHub Copilot, custom LLM integrations), including auto-remediation capabilities using AI, and governance considerations
Desired Qualifications:
- 4 + years - Development experience in more than one language
- 3 + years of using the IaC to configure, build, and deploy
- 2+ years of DevSecOps / Automation experience
- Hands-on experience with vendor tools Checkmarx, Blackduck, Prisma, Trufflehog, Synk, Socket, Invicti, Qualys
- Proven experience with GitHub Advanced Security (GHAS), including secret scanning capabilities
- Experience in API development and custom services
Job Expectations:
- This position offers a hybrid work schedule
- 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
Salary Ranges:
- $100,000 - $163,000 - Charlotte, NC
- $100,000 - $163,000 - Chandler, AZ
- $100,000 - $163,000- Irving, TX (note missing space before hyphen? but keep as is)
- $100,000 - $163,000 - West Des Moines, IA
- $100,000 - $163,000 - Columbus, OH
- $100,000 - $163,000- San Antonio, TX
- $110,000 - $179,000 - Minneapolis, MN
Also note "Pay Range Reflected is the base pay range offered for this position. Pay may vary depending on factors including but not limited to demonstrated examples of prior performance, skills, experience, or work location. Employees may also be eligible for incentive opportunities. $100,000.00 - $179,000.00"
We need to include Pay section with the ranges. Should we list each location? Probably yes, preserve all substantive info. Could combine as a list.
Benefits: list:
- Health benefits
- 401(k) Plan
- Paid time off
- Disability benefits
- Life insurance, critical illness insurance, and accident insurance
- Parental leave
- Critical caregiving leave
- Discounts and savings
- Commuter benefits
- Tuition reimbursement
- Scholarships for dependent children
- Adoption reimbursement
Schedule: hybrid work schedule (from Job Expectations). Also maybe mention not eligible for Visa sponsorship? That's not schedule. Could be part of Job Expectations but we don't have a heading for that; maybe we can include under Schedule? But schedule heading only for schedule info. The visa sponsorship is not schedule; maybe we can put under Requirements? Not appropriate. Could be a separate section like "Additional Information" but not allowed headings. The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings. So we must fit all content into those sections. Visa sponsorship maybe could go under Requirements? Not really. Could be under Qualifications? Not. Could be under About the role? Not. Could be under Responsibilities? Not. Could be under Schedule? Not. Could be under Pay? Not. Could be under Benefits? Not. Could be under Skills? Not. Could be under Qualifications? Not. Maybe we can treat visa sponsorship as part of Job Expectations but we don't have a heading for that; maybe we can omit it? But instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep it. Where to put? Could be under Schedule as a note? Not ideal but maybe we can add a
under Schedule heading that includes both hybrid work schedule and visa sponsorship note. That would be acceptable as schedule-related info? Visa sponsorship is not schedule but we can still include as extra note under Schedule heading; but that might be considered adding unrelated info under wrong heading. However the instruction says "Prefer a few substantive sections over many thin ones." It doesn't forbid mixing unrelated info under a heading as long as we don't create extra headings. So we could put visa sponsorship note under Schedule heading as a paragraph. Similarly AI expectations could go under Skills? Or maybe under Qualifications? But we have Skills heading for specific technical skills; AI expectations could be under Skills or Qualifications. However we already have Required and Desired Qualifications sections; we could combine them into Qualifications heading. The AI expectations could be under Qualifications as well (maybe under Desired Qualifications). But we already have Desired Qualifications list; we could incorporate AI expectations there? Actually AI expectations are under Job Expectations, not qualifications. But we could treat them as part of Qualifications (maybe under Skills). However to preserve all detail, we need to include them somewhere. We have headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map: - About the role: About This Role paragraph. - Responsibilities: In This Role, You Will list. - Requirements: Required Qualifications list. - Qualifications: Desired Qualifications list. - Skills: maybe list of specific technical domains: SAST, DAST, SCA, Secrets management, IaC, GitHub, Jira, ServiceNow, Jenkins, Harness, CI/CD, OWASP, MITRE CVE/CWE, SSDLC, AI/LLM tooling, etc. But those are already in Required Qualifications. Could duplicate but we need to preserve all info; we could keep them under Skills as a concise list of skills/tools. However we risk losing some nuance if we just list them without context. But we could keep the full Required Qualifications under Requirements, and then Skills could be a summary of specific tools/technologies: SAST, DAST, SCA, Secrets management, IaC, GitHub, Jira, ServiceNow, Jenkins, Harness, CI/CD, OWASP, MITRE CVE/CWE, SSDLC, AI/LLM, Checkmarx, Blackduck, Prisma, Trufflehog, Synk, Socket, Invicti, Qualys, GHAS, API development, etc. That would be a lot but okay. But we must not invent or summarize away detail; we can list them as items, preserving the names. That's fine. - Benefits: list. - Pay: list salary ranges per location plus note about base pay range and incentive opportunities. - Schedule: hybrid work schedule and visa sponsorship note and AI expectations? Actually AI expectations could go under Skills? But we already have Skills for technical skills; AI expectations are about using AI-assisted development and analysis tools, which is a skill/expectation. Could be placed under Skills as well. But we already have Skills for technical skills; we could include AI expectations there as bullet points. However the instruction says "Prefer a few substantive sections over many thin ones." So maybe