Senior Cloud Security Infrastructure Engineer
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content.
We need to parse the posting.
Content:
- Intro paragraph about U.S. Bank mission etc. Could be "About the role" maybe? Actually "About the role" heading would contain description of role. The posting includes "Job Description This position is not eligible for visa sponsorship. Location expectations: This role requires working from a U.S. Bank location three (3) or more days per week. U.S. Bank is seeking a Senior Cloud Security Infrastructure Engineer to support the cloud infrastructure and security platforms that protect sensitive enterprise data. This role sits within the Database Protection Team and will support database activity monitoring, tokenization, and related database-security capabilities across a large, complex technology environment. This person will serve as a senior technical resource responsible for supporting and enhancing security platforms hosted across AWS, Azure, and Kubernetes environments. They will troubleshoot complex infrastructure and connectivity issues, onboard databases and applications into protection platforms, implement platform improvements, and work independently to maintain stable, scalable, and secure services."
That's description. So we can put that under About the role
with
. Then "Main Responsibilities:" list bullet points. So
Responsibilities
with- each.
Then "Must Have Skills:" list bullet points. Could be under Requirements or Skills. The instruction: Use headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide where to put Must Have Skills and Nice to Have Skills. Likely "Skills" heading for both must have and nice to have? Or separate Requirements and Qualifications? Usually Must Have = Requirements, Nice to Have = Qualifications. But we have both. We'll put Must Have under
Requirements
and Nice to Have underQualifications
. Or we could put Must Have under Skills and Nice to Have under Qualifications. But we have both sections available. Let's map: - Requirements: Must Have Skills. - Qualifications: Nice to Have Skills (or maybe also include Basic Skills/Experience Typically a Bachelor's degree...). There's also "Basic Skills/Experience Typically a Bachelor's degree, or equivalent work experience Typically five or more years of relevant experience Advanced technical and functional subject matter expert knowledge across security domain areas". That seems like generic requirements. Could be part of Requirements as well. But we can incorporate into Requirements. We'll include Requirements with bullet list of Must Have Skills plus maybe the basic skills paragraph as abefore list? But we should preserve all substantive info. The basic skills paragraph is somewhat repetitive of Must Have. We'll include as a
under Requirements before the list. Then Qualifications: Nice to Have Skills list. Then Benefits: list bullet points from Benefits section. Then Pay: we have Pay Range: $119,765.00 - $140,900.00. So include
Pay
withcontaining that. Schedule: we have location expectations: This role requires working from a U.S. Bank location three (3) or more days per week. That's schedule info. So
Schedule
with. We should not repeat job title as heading. No Job ID etc. We need to remove boilerplate: EEO, E-Verify, disability accommodations, etc. Also remove "If there’s anything we can do to accommodate a disability..." etc. Also remove "Review our full benefits available by employment status here." (link). Also remove "U.S. Bank is an equal opportunity employer..." etc. Also remove "The salary range reflects figures based on the primary location..." etc. Also remove background check details, etc. Also remove "Posting may be closed earlier due to high volume of applicants." etc. We must preserve all substantive information: mission statement? The first paragraph about U.S. Bank journey etc. That's generic but maybe considered part of About the role? It's about company, not role. Might be considered boilerplate? It's not specific to role but it's part of posting. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep that intro paragraph as part of About the role? It's about the company mission. Could be considered part of About the role. We'll include it. Also "Location expectations: This role requires working from a U.S. Bank location three (3) or more days per week." appears twice; we can include once under Schedule. Also "This position is not eligible for visa sponsorship." That's substantive; we should keep it maybe under About the role or a separate note. We'll include in About the role paragraph. Now craft HTML. Structure:
About the role
At U.S. Bank, we’re on a journey to do our best. Helping the customers and businesses we serve to make better and smarter financial decisions and enabling the communities we support to grow and succeed. We believe it takes all of us to bring our shared ambition to life, and each person is unique in their potential. A career with U.S. Bank gives you a wide, ever-growing range of opportunities to discover what makes you thrive at every stage of your career. Try new things, learn new skills and discover what you excel at—all from Day One. This position is not eligible for visa sponsorship. Location expectations: This role requires working from a U.S. Bank location three (3) or more days per week. U.S. Bank is seeking a Senior Cloud Security Infrastructure Engineer to support the cloud infrastructure and security platforms that protect sensitive enterprise data. This role sits within the Database Protection Team and will support database activity monitoring, tokenization, and related database-security capabilities across a large, complex technology environment. This person will serve as a senior technical resource responsible for supporting and enhancing security platforms hosted across AWS, Azure, and Kubernetes environments. They will troubleshoot complex infrastructure and connectivity issues, onboard databases and applications into protection platforms, implement platform improvements, and work independently to maintain stable, scalable, and secure services.
Responsibilities
- Administer, support, and enhance database protection and database activity monitoring platforms.
- Build, configure, and maintain cloud-hosted infrastructure across AWS and Azure.
- Administer and support Kubernetes clusters used by security and data-protection services.
- Troubleshoot complex cloud, infrastructure, networking, application, and connectivity issues.
- Onboard databases, applications, and systems into security monitoring and protection platforms.
- Partner with database security, cloud, infrastructure, and data-protection teams to deliver secure and scalable solutions.
- Improve platform reliability, stability, performance, monitoring, and operational support.
- Implement platform upgrades, enhancements, and new technical capabilities.
- Support infrastructure-as-code, cloud automation, and deployment-pipeline initiatives.
- Serve as an L3 technical resource and independently lead complex problem resolution.
Requirements
Basic Skills/Experience Typically a Bachelor's degree, or equivalent work experience. Typically five or more years of relevant experience. Advanced technical and functional subject matter expert knowledge across security domain areas.
- Five or more years of relevant cloud infrastructure, security engineering, platform engineering, or related experience.
- Hands-on experience supporting information security, cybersecurity, or data-protection technologies.
- Strong production experience with AWS and Azure.
- Experience administering or providing advanced support for Kubernetes clusters.
- Cloud infrastructure engineering and operational support experience.
- Demonstrated ability to troubleshoot infrastructure, networking, application, and connectivity issues.
- Experience building, configuring, and maintaining cloud-hosted environments.
- Strong understanding of enterprise infrastructure, networking, and operational practices.
- Experience supporting large, complex enterprise environments.
- Ability to work independently and function as a senior L3 technical resource with minimal oversight.
Qualifications
- Database Activity Monitoring experience.
- Tokenization, encryption, data masking, or other data-protection platform experience.
- Database-security experience.
- Infrastructure-as-code and cloud automation experience.
- Experience with deployment pipelines and automated platform implementations.
- Experience onboarding databases or applications into enterprise security platforms.
- CISSP or another relevant security certification.
- Familiarity with ITIL or service-management practices.
- Financial-services or another highly regulated industry background.
Benefits
- Healthcare (medical, dental, vision)
- Basic term and optional term life insurance
- Short-term and long-term disability
- Pregnancy disability and parental leave
- 401(k) and employer-funded retirement plan
- Paid vacation (from two to five weeks depending on salary grade and tenure)
- Up to 11 paid holiday opportunities
- Adoption assistance
- Sick and Safe Leave accruals of one hour for every 30 worked, up to 80 hours per calendar year unless otherwise provided by law
Pay
Pay Range: $119,765.00 - $140,900.00
Schedule
This role requires working from a U.S. Bank location three (3) or more days per week.
Check for any duplicated content: we included location expectations in About the role and Schedule. Might be duplicate but it's okay; we could remove from About the role to avoid duplication. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." If we remove it from About the role, we lose that detail (though it's duplicated elsewhere). But we still have it in Schedule, so the info is preserved. However, the About the role paragraph originally included that sentence; removing it would be omitting that sentence from that paragraph, but the info still appears elsewhere. Is that allowed? The instruction says preserve ALL substantive information; does not require it to be in original location, just not to lose it. So we can omit duplicate to avoid redundancy. Safer to keep it only once. Let's remove the location expectations sentence from About the role paragraph. Also "This position is not eligible for visa sponsorship." we kept. Now ensure no boilerplate: we removed EEO, E-Verify, disability accommodations, etc. Also removed "Review our full benefits available by employment status here." etc. Also removed "The salary range reflects figures based on the primary location..." etc. Also removed background check details, etc. Also removed "Posting may be closed earlier due to high volume of applicants." etc. Check remaining text: we kept the mission paragraph, the not eligible for visa sponsorship, the role description, responsibilities, requirements, qualifications, benefits, pay, schedule. Check if any other substantive info like "U.S. Bank will consider qualified applicants with arrest or conviction records for employment." That's substantive but maybe considered EEO/boilerplate? It's about hiring practice. Might be considered substantive but could be considered boilerplate. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This line is about arrest/conviction records, which is a fair chance hiring statement; could be considered EEO/legal. Safer to remove. Also remove "U.S. Bank conducts background checks consistent with applicable local laws..." etc. That's legal boilerplate. Remove. Also remove "U.S. Bank is subject to, and conducts background checks consistent with the requirements of Section 19 of the Federal