Cloud Engineering, Senior Specialist

We need to output HTML fragment with sections: headings using

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting. The posting includes: - Intro: "Provides senior expert level technical support for the most critical and complex projects. Troubleshoots, diagnoses, and resolves hardware or software issues for new and existing technologies and tools." This is about role description. - Then description of GR&S etc. Might be about the role context. - Then "The Cloud Security Engineer will provide expert level system analysis, design, development, and implementation of Identity Solutions. Identifies, resolves, or escalates security and software opportunities, vulnerabilities, and defects." - Then "In this role, you will:" followed by bullet list of duties. - Then "What it takes:" with requirements. - Then "Special Factors This is a hybrid role with Tues, Wed, Thurs in the office and Mon, Fri is remote." That's schedule. - "Special Factors Sponsorship Vanguard is not offering visa sponsorship for this position." That's maybe a note but not required. - Then "About Vanguard" etc. That's company description, maybe "About the role"? Actually "About Vanguard" is company overview, not role. Might be considered "About the role"? But we have "About the role" heading for role description. Could put company description under "About Vanguard"? Not in allowed headings. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include "About the role" for role overview. "Responsibilities" for duties list. "Requirements" for experience/education. "Qualifications" maybe overlapping; but we can combine. "Skills" maybe for technical skills. "Schedule" for hybrid schedule. "Benefits" not mentioned. "Pay" not mentioned. So we should not include Benefits or Pay. We must not repeat job title as heading. No Job ID. We need to preserve all substantive information, not invent. We need to use

• for any list of duties/requirements/benefits. Use

  for prose. We need to avoid boilerplate like EEO etc. There's none. We need to avoid duplication. Let's extract content. First, role overview/prose: "Provides senior expert level technical support for the most critical and complex projects. Troubleshoots, diagnoses, and resolves hardware or software issues for new and existing technologies and tools. Global Risk and Security (GR&S) at Vanguard enables business strategy, protects client and Vanguard interests (e.g., assets and data), and stewards a strong risk culture. Our teams leverage enterprise-wide insights, deep expertise, and trusted advice so that across Vanguard leaders and crew drive faster, stronger, risk-informed decisions. Within GR&S, the Enterprise Security and Fraud (ES&F) sub-division is responsible for the global protection of Vanguard crew, property, data, and client assets. We are the trusted advisors that protect the pride of Vanguard with state-of-the-art security and fraud capabilities. The Cloud Security Engineer will provide expert level system analysis, design, development, and implementation of Identity Solutions. Identifies, resolves, or escalates security and software opportunities, vulnerabilities, and defects." That's prose for About the role. Then responsibilities list after "In this role, you will:" includes many items. Let's extract each bullet: - Collaborate with cross functional teams to architect and implement authentication solutions using Ping Federate, SiteMinder, Auth0 or other similar tools. - Provide subject matter expertise in Identity and Access Management (IAM) domain, SAML, OIDC, OAuth, MFA and FIDO2. - Need to be proficient in JavaScript, Java, Groovy Script and Web API development and integration. - Require experience consuming, developing, integrating, and documenting REST API’s and its specifications. - Elevate code into the development, test, and production environments on schedule. - Provides follow up production support and submit change control requests and documents. - Provide subject matter expertise in software development methodology and development architecture standards. - Mentors and trains staff with less experience. - Resolves elevated issues and recommends enterprise-wide improvements. - Participate in design, code, and test inspections throughout the life cycle to identify and fix issues. - Explains technical considerations at related meetings, including those with internal clients. - Thoroughly understand client business functions and technology needs. - Has a broad and deep understanding of Vanguard's technologies, tools, and applications, including those that interface with business area and systems. - Is well versed on the latest technologies and tools supporting software development in the industry. - Thoroughly understand and complies with Information Technology and Information Security policies and procedures and verifies that deliverables meet requirements. - Ensure implementation solutions support architecture objectives (e.g., availability, scalability, performance, security, etc.), as appropriate. - Participate in special projects and performs other duties as assigned. That's a long list; we can put as

  • . Then "What it takes:" includes: - Minimum of eight years’ experience in Identity and Access Management preferably in Financial Services domain - Experience in JavaScript, Java, Groovy Script and Web API development and integration - Subject Matter Expert in IAM, SAML, OIDC, OAuth, MFA and FIDO2 - Undergraduate degree in a related field or the equivalent combination of training and experience. These are requirements/qualifications. Could split into Requirements (experience) and Qualifications (education). But we can combine. We also have "Special Factors This is a hybrid role with Tues, Wed, Thurs in the office and Mon, Fri is remote." That's schedule. Also "Special Factors Sponsorship Vanguard is not offering visa sponsorship for this position." Might be considered a note but not required heading; we could include as a short

    under maybe "About the role" or separate? Not needed for headings. Could include as a note but not required. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it." This is minor metadata (sponsorship). So we can include a short

    maybe under a generic section? But we have no heading for that. Could just include as a

    after schedule? Might be okay. We must not include boilerplate like EEO etc. Not present. We must not create sections with filler like "commensurate with experience". Not present. We must not include Benefits or Pay sections because not mentioned. Thus sections: About the role, Responsibilities, Requirements (or Qualifications), Skills maybe, Schedule. We could have Skills section for technical proficiencies: JavaScript, Java, Groovy Script, Web API, REST API, IAM, SAML, OIDC, OAuth, MFA, FIDO2, Ping Federate, SiteMinder, Auth0, etc. But those are already in responsibilities and requirements. Might be redundant. Better to keep Responsibilities and Requirements. We could have Qualifications for education. Let's decide: - About the role: prose overview. - Responsibilities:

    of duties. - Requirements:
    of experience requirements (8 years IAM preferably FS, experience in JS/Java/Groovy/Web API, SME in IAM etc.) - Qualifications:

    for undergraduate degree or equivalent. - Schedule:

    for hybrid schedule. - Sponsorship note: maybe

    under Schedule or separate? Could add as a short

    after schedule. We must not repeat content. Ensure we capture all. Let's craft. HTML fragment:

    About the role

    Provides senior expert level technical support for the most critical and complex projects. Troubleshoots, diagnoses, and resolves hardware or software issues for new and existing technologies and tools. Global Risk and Security (GR&S) at Vanguard enables business strategy, protects client and Vanguard interests (e.g., assets and data), and stewards a strong risk culture. Our teams leverage enterprise-wide insights, deep expertise, and trusted advice so that across Vanguard leaders and crew drive faster, stronger, risk-informed decisions. Within GR&S, the Enterprise Security and Fraud (ES&F) sub-division is responsible for the global protection of Vanguard crew, property, data, and client assets. We are the trusted advisors that protect the pride of Vanguard with state-of-the-art security and fraud capabilities. The Cloud Security Engineer will provide expert level system analysis, design, development, and implementation of Identity Solutions. Identifies, resolves, or escalates security and software opportunities, vulnerabilities, and defects.

    Responsibilities

    • Collaborate with cross functional teams to architect and implement authentication solutions using Ping Federate, SiteMinder, Auth0 or other similar tools.
    • Provide subject matter expertise in Identity and Access Management (IAM) domain, SAML, OIDC, OAuth, MFA and FIDO2.
    • Need to be proficient in JavaScript, Java, Groovy Script and Web API development and integration.
    • Require experience consuming, developing, integrating, and documenting REST API’s and its specifications.
    • Elevate code into the development, test, and production environments on schedule.
    • Provides follow up production support and submit change control requests and documents.
    • Provide subject matter expertise in software development methodology and development architecture standards.
    • Mentors and trains staff with less experience.
    • Resolves elevated issues and recommends enterprise-wide improvements.
    • Participate in design, code, and test inspections throughout the life cycle to identify and fix issues.
    • Explains technical considerations at related meetings, including those with internal clients.
    • Thoroughly understand client business functions and technology needs.
    • Has a broad and deep understanding of Vanguard's technologies, tools, and applications, including those that interface with business area and systems.
    • Is well versed on the latest technologies and tools supporting software development in the industry.
    • Thoroughly understand and complies with Information Technology and Information Security policies and procedures and verifies that deliverables meet requirements.
    • Ensure implementation solutions support architecture objectives (e.g., availability, scalability, performance, security, etc.), as appropriate.
    • Participate in special projects and performs other duties as assigned.

    Requirements

    • Minimum of eight years’ experience in Identity and Access Management preferably in Financial Services domain
    • Experience in JavaScript, Java, Groovy Script and Web API development and integration
    • Subject Matter Expert in IAM, SAML, OIDC, OAuth, MFA and FIDO2

    Qualifications

    Undergraduate degree in a related field or the equivalent combination of training and experience.

    Schedule

    This is a hybrid role with Tues, Wed, Thurs in the office and Mon, Fri is remote.

    Vanguard is not offering visa sponsorship for this position.

    Check: Did we miss any substantive info? The "About Vanguard" paragraph about mission etc. Could be considered "About the role"? But we already have About the role covering role description. The "About Vanguard" is more company overview; not required but could be included as part of About the role? The instruction: "Prefer a few substantive sections over many thin ones." Could add a short paragraph about Vanguard mission under About the role? But we already have a lot. Might be okay to omit as it's not directly about the role but still substantive. However the instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should include the About Vanguard content somewhere. Where? Could add another

    under About the role after the role description, or create a separate section like "About Vanguard" but not allowed heading.