Cloud Security Consultant

We need to output HTML fragment with sections: headings

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. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Also remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. We need to parse the posting. Key info: - Goal statement: "Our goal is to solve problems and deliver results for our clients. At Cloud and Things, you can be a part of transforming the public sector’s IT environment. Our team is on the forefront of helping to solve the government's most complex IT challenges. If you are seeking a role that offers the opportunity to work on rewarding projects, consider a career with Cloud and Things." - Exempt position note: "*This is an exempt position. Salary commensurate with experience*" This is a line we need to consider: It says salary commensurate with experience, which is not specific numeric. According to rules: never emit Pay/Schedule/Benefits sections unless posting actually states them. Also we should not include placeholder like "commensurate with experience". So we should not create a Pay section because it's not specific numeric. Also we should not include that line at all? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." However, "Salary commensurate with experience" is not substantive detail; it's vague. It might be considered boilerplate? It's not exactly boilerplate but it's a vague statement. The rule says: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. So we should not create a Pay section. Also we might omit that line entirely because it's not substantive? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The line "Salary commensurate with experience" is not substantive detail; it's vague. It might be considered filler. I'd lean to omit it. - Job Title line: "Job Title: Cloud Security Consultant" - we must not repeat job title as a heading. So we can maybe include it in a short

as metadata? The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So we can include Job Title in a short

maybe with location etc. But we should not repeat as heading. So we could have a

containing the job title, location, duration, W2 hourly rate, application deadline. However, we need to check if we should keep that info. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep location, duration, W2 hourly rate, application deadline. Those are substantive. The job title is also substantive but we cannot use as heading; we can include in a paragraph. - Overview: "We are seeking a Cloud Security Consultant who will support our NYS client. This role provides hands-on security design, engineering, and oversight for the PeopleSoft OCI architecture, ensuring the environment is hardened, compliant, monitored, and aligned with cybersecurity standards. The consultant will partner with Application Security, IAM, Network, Data Security, Cloud Engineering, DBA, and architecture teams to deliver a secure OCI landing zone and PeopleSoft deployment." - Duties: list bullet points. - Mandatory Qualifications: list. - Desirable Qualifications: list. - What We Offer: list. - Then there is a bunch of boilerplate about EEO, AI-assisted resume evaluation, privacy notice, etc. Those should be removed. We need to decide sections. We have: - About the role: could combine the introductory paragraph (goal statement) and overview? The "About the role" section could contain the description of the role, maybe the overview paragraph. The introductory goal statement could also be considered about the company. But we can put it under About the role. - Responsibilities: the Duties list. - Requirements: could be Mandatory Qualifications. - Qualifications: maybe Desirable Qualifications? But we already have Requirements for mandatory; Qualifications could be desirable or additional qualifications. However, the instruction says use headings for sections like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which to use. We have mandatory qualifications (4+ years OCI, 4+ years PeopleSoft, etc.) That's definitely requirements. We have desirable qualifications (PeopleSoft experience in enterprise cloud environments preferred, familiarity with PeopleSoft architecture preferred, Cloud security engineering experience with Azure and/or AWS as secondary cloud platforms). That could go under Qualifications or Skills. We have skills implied in mandatory and desirable: strong communication, cross-functional collaboration, ability to design etc., strong OCI experience with policies etc., experience with CSPM tools, etc. Those could go under Skills. We have What We Offer: that's Benefits. We have Pay: we have W2 Hourly Rate: $48-$55/hour. That's specific numeric. So we should include a Pay section with that info. Also we have Duration: 12 Months (with potential for extension). That could go under Schedule? Or maybe Schedule section for duration/shift? The instruction says Schedule section only if posting actually states them. It does state duration. So we can put Schedule: 12 Months (with potential for extension). Also location: 2 Broadway, New York, NY (Onsite). That could be part of About the role or maybe a separate section? There's no heading for location; we could include in a short paragraph with job title. Application Deadline: 9/21/2026. That's also metadata; could be in same short paragraph. We must not include application instructions (like "Ready to make a difference? We’re eager to connect...") That's more of a call to action; maybe we can keep as part of About the role? It's not boilerplate but it's a closing statement. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The line "Ready to make a difference? We’re eager to connect with qualified candidates committed to delivering results and fostering excellence within client projects." seems like application instruction / call to action. Might be considered application instructions. Safer to remove it. Also the line "Cloud and Things complies with all applicable federal, state, and local laws regarding recruitment and hiring. All qualified applicants are considered for employment without regard to ..." is EEO boilerplate; remove. AI-Assisted Resume Evaluation notice etc. Remove. Thus we keep: - Short paragraph with job title, location, duration, W2 hourly rate, application deadline. Possibly also note exempt? The exempt line we decided to omit because it's vague salary statement; but we have actual pay rate, so we can ignore the exempt line. - About the role: combine the introductory goal statement and overview? Let's think: The goal statement is about the company and mission. Could be part of About the role. The overview paragraph is more specific about the role. We'll put both in About the role as

elements. - Responsibilities:

Responsibilities

then

• each duty. - Requirements:

  Requirements

  then
  • each mandatory qualification. - Qualifications:

    Qualifications

    then
    • each desirable qualification. - Skills: maybe we can extract skills from mandatory and desirable that are not already captured? But we might avoid duplication. The instruction: Prefer a few substantive sections over many thin ones. We already have Requirements and Qualifications; maybe we can combine skills into Requirements or Qualifications. However, we have separate headings allowed; we could create Skills section for things like strong communication, cross-functional collaboration, ability to design etc. But many of those are already in mandatory qualifications list (they included "Strong communication and cross-functional collaboration skills." etc). So we could keep them under Requirements. To avoid thin sections, maybe we omit Skills section and just keep Requirements and Qualifications. - Benefits:

      Benefits

      then
      • each What We Offer item. - Pay:

        Pay

        then

        W2 Hourly Rate: $48-$55/hour

        - Schedule:

        Schedule

        then

        Duration: 12 Months (with potential for extension)

        We should also include location maybe in the short paragraph. Now check for any duplicated lines: The duties list includes some repeated concepts? We'll keep as is. Now ensure we don't include any boilerplate. Let's extract the exact text for each piece. Job Title line: "Job Title: Cloud Security Consultant" Location: "Location: 2 Broadway, New York, NY (Onsite)" Duration: "Duration: 12 Months (with potential for extension)" W2 Hourly Rate: "W2 Hourly Rate: $48-$55/hour" Application Deadline: "Application Deadline: 9/21/2026" We could combine into one paragraph: "

        Job Title: Cloud Security Consultant | Location: 2 Broadway, New York, NY (Onsite) | Duration: 12 Months (with potential for extension) | W2 Hourly Rate: $48-$55/hour | Application Deadline: 9/21/2026

        " But we must not repeat job title as a heading; it's fine in paragraph. Now About the role: The introductory paragraph: "Our goal is to solve problems and deliver results for our clients. At Cloud and Things, you can be a part of transforming the public sector’s IT environment. Our team is on the forefront of helping to solve the government's most complex IT challenges. If you are seeking a role that offers the opportunity to work on rewarding projects, consider a career with Cloud and Things." Then Overview: "We are seeking a Cloud Security Consultant who will support our NYS client. This role provides hands-on security design, engineering, and oversight for the PeopleSoft OCI architecture, ensuring the environment is hardened, compliant, monitored, and aligned with cybersecurity standards. The consultant will partner with Application Security, IAM, Network, Data Security, Cloud Engineering, DBA, and architecture teams to deliver a secure OCI landing zone and PeopleSoft deployment." We could combine into two

        under About the role. Now Responsibilities (Duties): List: - Provide hands-on cloud security design, engineering, and oversight for the PeopleSoft OCI architecture and secure OCI landing zone. - Design, implement, and oversee security controls to harden the environment and support compliance with cybersecurity standards. - Configure and assess OCI security capabilities, including policies, compartments, Security Zones, WAF, Load Balancing, Vault, Key Management, and network security controls. - Support application security, DevSecOps, API security, CSPM, logging, monitoring, cloud audit logs, event metrics, and SIEM integration for the PeopleSoft OCI environment. - Collaborate with Application Security, IAM, Network, Data Security, Cloud Engineering, DBA, and architecture teams to deliver and maintain a secure PeopleSoft OCI deployment. We'll output as

        • each. Now Requirements (Mandatory Qualifications): List: - 4+ years of Oracle Cloud Infrastructure (OCI) experience, including hands-on cloud security engineering. - 4+ years of PeopleSoft experience. - 4+ years of cybersecurity and security engineering experience. - Strong communication and cross-functional collaboration skills. - Ability to design, implement, and oversee security controls for a secure PeopleSoft OCI deployment. - Strong OCI experience with policies, compartments, Security Zones,