IAM Security Engineer

We need to output HTML fragment with sections for headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections that have real specific content. The posting includes a lot of content: Position concept, primary duties, supervision, relationships, qualifications (education, licenses/certifications, experience, knowledge/skills/abilities). No explicit Benefits, Pay, Schedule given (except shift: 8 Hr. X 5 Days). That's schedule info. So we can include Schedule section with that. Benefits not mentioned. Pay not mentioned. So we can omit Benefits and Pay. We need headings: About the role (maybe position concept), Responsibilities (primary duties), Requirements (maybe experience required?), Qualifications (education, certifications), Skills (knowledge/skills/abilities). Also maybe "Shift" as Schedule. We must not repeat job title as heading. The title is IAM Security Engineer (but also IAM Security Technologist Progression etc). We'll not use it. We need to preserve all substantive info, not invent. Remove boilerplate like EEO etc. There's none. We need to format using

for section headings. Use

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

  for prose. We need to decide what goes where. About the role: Could combine position concept paragraphs for both Associate and Technologist? The posting includes two position concepts: IAM Security Technologist Associate and IAM Security Technologist. Might combine into a general description. We'll include both as prose. Responsibilities: list of primary duties and responsibilities (both associate and technologist). We'll combine them into a list. Requirements: maybe experience required? Could be separate but we have Qualifications covering education, certifications, experience. The instruction says use sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content. We could treat Requirements as experience required (years). Qualifications as education and certifications. Skills as knowledge/skills/abilities. Let's extract: Experience Required: - Associate: At least one (1) year of experience in IAM or related security engineering experience. Preferred: Two (2) or more years. - Technologist: 3 years of experience in IAM or (cut off). The text ends abruptly: "3 years of experience in IAM or". Probably means 3 years experience. We'll capture that as "3 years of experience in IAM or related security engineering experience." We'll note it's required. Thus Requirements section: list experience requirements. Qualifications: Education Required: Bachelor’s Degree in Computer Science, Information Systems or other technology-related field from an accredited college or university. An associate’s degree with an additional 2 years of required experience may be considered in lieu of a bachelor’s degree. A high school diploma and an additional 4 years of required experience may be considered in lieu of a bachelor’s degree. Preferred: None for Associate; for Technologist Preferred: Master’s Degree... Licenses/Certifications Required: None for Associate; Preferred: CISSP, CISM, CIAM, ITIL, Sabiynt, CyberArk, Microsoft Identity/Entra, or other relevant IAM/security certifications. For Technologist: Licenses/Certifications Required: Will require at least one certification in one of the following: CISSP, CISM, CIAM, ITIL, Sabiynt, CyberArk, Microsoft Identity/Entra, or other relevant IAM/security certifications. Preferred: None. We'll combine. Skills: Knowledge/Skills/Abilities (KSA) list. We'll output as

  • for each bullet. Schedule: Shift: 8 Hr. X 5 Days. Now produce HTML. We must not include markdown fences. Just raw HTML. Let's craft.

    About the role

    ... combine position concept paragraphs.

    We need to include both associate and technologist concepts? Might be redundant but we can summarize: The role supports IAM systems, ensures procedures, assists development, etc. We'll write a concise paragraph using info from both. But must preserve ALL substantive information; cannot summarize away detail. However we can combine but must not lose detail. Might be okay to include both concepts as separate paragraphs. We'll do:

    The IAM Security Technologist Associate is responsible for supporting the company’s information security systems, ensuring that all procedures are followed on a daily, weekly, and monthly basis. Supports all systems used to secure the enterprise information technology assets, the scope includes all network infrastructure, operating systems, and web server platforms throughout TECO Energy and its subsidiaries. Assists with the development and enhancing of IAM systems including SSO, authentication, and access controls ensuring confidentiality, integrity, and availability of IAM systems and data. Provides IAM Security support for the TECO environment primarily focusing IT corporate applications and OT/NERC applications. Responsible for adhering to established policies, following best practices, developing and possessing a solid understanding of exploits and vulnerabilities, resolving issues by following the appropriate escalation procedures. Supports the enforcement of corporate, regulatory, and risk management policies and assists in developing, maintaining, and publishing corporate IAM security standards, procedures, and guidelines for enterprise computing platforms. Position will be responsible for collaborating with multiple business units across multiple Emera affiliates.

    Then another paragraph for Technologist concept. We'll do that. Responsibilities: list primary duties. We'll combine both sets (they are similar). We'll produce a
    with each duty as
    • . Use the text from "Primary Duties And Responsibilities" for both associate and technologist (they are largely same). We'll include each bullet. Let's extract bullets from associate: - Assist in Developing and maintaining a roadmap for Identity and Access Management (IAM) including Governance and Administration (IGA), Privileged Access Management (PAM), authentication, SSO, directory services, and access governance. - Collaborate closely with teams including Cyber Security, Human Resources, Technology, Architecture and Lines of Business (LoBs) to create efficient and user-friendly IAM solutions. - Assist in designing, implementing, and maintaining access governance processes, including Joiner/Mover/Leaver workflows, access requests, RBAC, access certifications/reviews, application onboarding, and least-privilege controls. - Support enterprise IGA capabilities, including Saviynt, and integrations with business applications and directories. - Support Privileged Access Management (PAM) capabilities, including privileged account onboarding, credential management, access controls, and privileged access remediation with emphasis on platforms such as CyberArk. - Assist with the deploymen, management and enhancement of SSO and authentication solutions, including integrations with enterprise applications, Microsoft Entra ID/Active Directory, and other identity platforms to provide secure and seamless authentication. - Assist with the implementation and management of authentication and access control mechanisms, including multi-factor authentication, conditional access, and identity security controls. - Assist with the monitoring, troubleshooting and response to identity and access-related incidents and technical issues. - Support remediation of unauthorized access, excessive privileges, identity lifecycle failures, and other IAMN control issues. - Effectively collaborate with both technical and non-technical business owners, application teams, implementation partners, and managed service providers. - Identify opportunities to improve IAM automation, integraions, processes and toolsets, and provide hands-on technical support for activities outside standard managed service scope. Technologist duties similar but with slightly different verbs: Support the development and maintenance of a strategic roadmap..., Support the design, implementation and maintenance..., Support enterprise IGA..., Support Privileged Access Management..., Deploy, manage, and enhance SSO..., Support the implementation and management..., Monitor, troubleshoot, and respond..., Support remediation..., Effectively collaborate..., Identify opportunities... We could combine but risk duplication. However we must preserve all substantive info; duplication is okay but we might just include one set as it's essentially same. To be safe, we could include both sets but that would be repetitive. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplication is not inventing or summarizing away; it's preserving. So we could include both sets, but that would be lengthy but okay. But we might just include one set because they are substantively same; but that could be considered summarizing away detail (omitting some verbs). Safer to include both sets, maybe merge by using the more detailed version (technologist) which includes "Support the development and maintenance of a strategic roadmap" vs "Assist in Developing and maintaining a roadmap". Slight difference. We'll include both sets as separate lists? Could cause confusion. I'll include a single list that captures the essence, but note that we might lose nuance. However the instruction says not to summarize away detail; but combining similar points might be considered summarizing. I'd rather include both sets as separate
      under Responsibilities? Could have two lists: one for Associate responsibilities, one for Technologist responsibilities. That preserves detail. Thus:

      Responsibilities

      Associate

      but we cannot use h4; only h3 for section headings. We cannot add extra headings besides the allowed ones? The instruction says use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but to be safe we stick to only those headings. We could embed the associate/technologist distinction inside the list items by noting "Assist..." vs "Support..." but that may lose nuance. Given the risk, I'll produce a single responsibilities list that includes both sets of verbs by using "Assist/Support" etc. But that may be considered summarizing. Alternative: Keep the responsibilities as prose paragraph, not list. The instruction says use

      • for any list of duties/requirements/benefits. If we put them in prose, we violate that rule. So we must use list for duties. Thus we need to list duties. We'll combine the two sets but keep both variations by using "Assist/Support" etc. Eg: "Assist in developing and maintaining a roadmap for IAM... / Support the development and maintenance of a strategic roadmap for IAM..." That's still summarizing but we keep both phrases. We could separate each duty into two lines: one for associate, one for technologist. That preserves both. Thus each
      • could contain two sentences: one starting with "Assist..." and another "Support...". That preserves detail. Let's do that. Now Requirements: experience required. We'll list: - Associate: At least one (1) year of experience in IAM or related security engineering experience. Preferred: Two (2) or more years. - Technologist: 3 years of experience in IAM or related security engineering experience. We'll put as
        . Qualifications: education and certifications. We'll list education required for both (same). Preferred: Master’s for Technologist. Certifications: Associate: Preferred: CISSP, CISM, CIAM, ITIL, Sabiynt, CyberArk, Microsoft Identity/Entra, or other relevant IAM/security certifications. Technologist: Required: Will require at least one certification in one of the following: CISSP, CISM, CIAM, ITIL, Sabiynt, CyberArk, Microsoft Identity/Entra, or other relevant IAM/security certifications. Preferred: None. We'll list. Skills: Knowledge/Skills/Abilities (KSA) list. We'll extract the KSA bullet points from the posting (under Knowledge/Skills/Abilities (KSA) for Associate and also for Technologist? The Technologist section didn't repeat KSA but likely same. We'll include the list as given. List items: - Understanding of Identity and Access Management concepts, including RBAC, least privilege, entitlement management, and access controls. - Knowledge of identity lifecycle management, including Joiner/Mover/Leaver processes, onboarding, offboarding, access changes, and automated provisioning/deprovisioning. - Knowledge of