Architect, Cybersecurity, Identity Security - Remote

We need to output HTML fragment with sections: About the role? The posting includes description: "Preference will be given to candidates residing in the Eastern or Central time zones." That's a note. Then description of role: "As an Identity Security Architect, you will design and govern enterprise identity and access management solutions..." That's about the role. Then "What you will do:" with Technical Responsibilities and Leadership & People Management Responsibilities. Then "Knowledge and Capabilities:" bullet? Actually it's a paragraph. Then "What You Need:" with Required Qualifications list. We need headings: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to include sections only if posting has real specific content. We have content for About the role (the description). Responsibilities (Technical Responsibilities and Leadership & People Management). Requirements/Qualifications (What You Need). Benefits (Health benefits, Financial benefits). Pay (Pay Ranges). Schedule? Not mentioned. So we omit Schedule. We must not repeat job title as heading. No Job ID. Remove boilerplate: "Preference will be given to candidates residing in the Eastern or Central time zones." That's substantive? It's a preference note; we can include maybe in About the role paragraph. Keep it. We must not include duplicated lines, cookie/navigation/legal/EEO etc. There's some text about Stryker etc. That's substantive about company; we can keep maybe in About the role or a separate "About the company"? Not in allowed headings list. Could fold into About the role paragraph. The instruction: "Prefer a few substantive sections over many thin ones." So we can have About the role, Responsibilities, Requirements, Benefits, Pay. We need to use

• for any list of duties/requirements/benefits. So for responsibilities we need list. For qualifications list. For benefits list. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep all details from the posting. Let's extract content. Preference note: "Preference will be given to candidates residing in the Eastern or Central time zones." Role description: "As an Identity Security Architect, you will design and govern enterprise identity and access management solutions that protect organizational assets while enabling secure access to business systems and applications. You will serve as the technical authority for identity security and partner with cybersecurity, infrastructure, cloud, application, enterprise architecture, security operations, and business teams across on-premises and cloud environments." Then "What you will do:" then subheadings: Technical Responsibilities: list items. Technical Responsibilities list: - Design and maintain enterprise identity security architecture, standards, and reference designs. - Develop identity strategies that support Zero Trust Architecture and enterprise digital transformation. - Architect authentication, authorization, federation, single sign-on (SSO), multi-factor authentication (MFA), and identity lifecycle management solutions. - Lead architecture reviews for IAM projects, cloud implementations, and business applications. - Design and govern Privileged Access Management (PAM) solutions and privileged identity controls. - Integrate identity security controls with Infrastructure, Cloud Engineering, Enterprise Architecture, Application Development, and Security Operations teams. - Develop identity governance processes for role-based access control (RBAC), least privilege, segregation of duties (SoD), and access certification. - Conduct identity threat modeling, architecture risk assessments, and security design reviews. - Evaluate emerging identity technologies and recommend architectural improvements. - Support compliance with NIST CSF, ISO 27001, HIPAA, SOX, FDA Cybersecurity Guidance, and applicable regulatory requirements. - Develop architecture documentation, technical standards, implementation guidance, and operating procedures. Leadership & People Management Responsibilities: - Provide technical leadership and mentorship to engineering teams implementing identity security capabilities. Knowledge and Capabilities: - Analyze complex identity security challenges and translate findings into practical architecture decisions. - Design enterprise identity architectures that connect security requirements, business needs, and technology capabilities. - Communicate identity architecture standards, risks, and implementation guidance to technical and business partners. What You Need: Required Qualifications - Bachelor's degree in Computer Science, Information Systems, Cybersecurity, Engineering, or a related discipline. - Minimum 8 years of experience in cybersecurity or identity management. - Minimum 3 years of experience designing enterprise IAM architectures. - Experience implementing SSO, MFA, PAM, Identity Governance and Administration (IGA), and directory services. - Experience with Microsoft Entra ID, Active Directory, Okta, Ping Identity, SailPoint, CyberArk, Delinea, or similar technologies, including cloud identity security across Azure, AWS, or Google Cloud. Posted Date: 09/14/2026 (metadata, we can drop or fold into short p). "This role will be posted for a minimum of 3 days." Also metadata; we can drop. United States of America (location). Pay Ranges: list of ranges with codes. We need to include Pay section only if posting actually states them. Yes, they have Pay Ranges. We need to preserve all substantive information; we should include the pay ranges as listed. Should we include them as a list? Probably a
  • each range. Health benefits include: list. Financial benefits include: list. Company description: "Stryker offers innovative products and services in MedSurg, Neurotechnology, Orthopaedics and Spine that help improve patient and healthcare outcomes. Alongside its customers around the world, Stryker impacts more than 150 million patients annually." plus vaccination note: "Depending on customer requirements employees and new hires in sales and field roles that require access to customer accounts as a function of the job may be required to obtain various vaccinations as an essential function of their role." That's substantive; we can include maybe in About the role or a separate "About the company" but not in allowed headings. Could fold into About the role paragraph. We must not include boilerplate like EEO etc. There's none. Now construct HTML. We'll start with

    for preference note and role description combined? Could separate. Section About the role:

    About the role

    then

    Preference will be given to candidates residing in the Eastern or Central time zones. As an Identity Security Architect, you will design and govern enterprise identity and access management solutions that protect organizational assets while enabling secure access to business systems and applications. You will serve as the technical authority for identity security and partner with cybersecurity, infrastructure, cloud, application, enterprise architecture, security operations, and business teams across on-premises and cloud environments. Stryker offers innovative products and services in MedSurg, Neurotechnology, Orthopaedics and Spine that help improve patient and healthcare outcomes. Alongside its customers around the world, Stryker impacts more than 150 million patients annually. Depending on customer requirements employees and new hires in sales and field roles that require access to customer accounts as a function of the job may be required to obtain various vaccinations as an essential function of their role.

    Then Responsibilities:

    Responsibilities

    then maybe split into Technical Responsibilities and Leadership & People Management as subheadings? But only allowed headings are those listed; we could still use

    for subheadings? The instruction: use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but better to stick to those. Could combine Technical and Leadership into one list? But we need to preserve detail; we could have two

    subheadings inside Responsibilities? Might be okay but risk of extra headings not in list. Safer: keep Responsibilities as one section with two

    lists, each preceded by a

    describing the category (Technical Responsibilities, Leadership & People Management Responsibilities). That's fine. Thus:

    Responsibilities

    Technical Responsibilities:

    • ... each item

    Leadership & People Management Responsibilities:

    • ... item
    Then Knowledge and Capabilities: Could be part of Requirements? Actually it's under "Knowledge and Capabilities". Could be included in Requirements or Qualifications? The allowed headings include Requirements, Qualifications, Skills. Knowledge and Capabilities could go under Requirements or Skills. Since we have Qualifications heading for required qualifications, we could put Knowledge and Capabilities under Skills? But better to put under Requirements as they are capabilities. Let's create a section

    Requirements

    and include Knowledge and Capabilities list plus maybe also Required Qualifications? But we also have Qualifications heading. To avoid duplication, we could have Requirements for knowledge/capabilities, and Qualifications for formal qualifications. That seems reasonable. Thus:

    Requirements

    Knowledge and Capabilities:

    • ... three items
    Then

    Qualifications

    Required Qualifications:

    • ... five items
    Then Benefits:

    Benefits

    with two lists: Health benefits and Financial benefits. Could separate with

    headings. Pay:

    Pay

    with list of ranges. We must not include Schedule. Now ensure we preserve all substantive information: we included preference note, role description, company description, vaccination note, responsibilities (technical and leadership), knowledge and capabilities, qualifications, benefits (health and financial), pay ranges. Check we didn't miss any: The "Posted Date: 09/14/2026" and "This role will be posted for a minimum of 3 days." and "United States of America" we omitted. Are those substantive? They are minor metadata; instruction says fold minor metadata into a short

    or drop it. We could include a short

    at top maybe: "Posted 09/14/2026; role open for minimum 3 days; United States." But we already have location implied. Might be okay to drop. But to preserve ALL substantive information, we should include them. However they said "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it." So we can include a short

    with that info. Let's add a

    before About the role: "Posted 09/14/2026. This role will be posted for a minimum of 3 days. United States of America." That's minor metadata. Now ensure we didn't include any boilerplate like cookie/navigation/legal/EEO etc. None. Now produce HTML fragment. Let's craft. Be careful to escape any HTML special characters? Not needed. We'll output:

    Posted 09/14/2026. This role will be posted for a minimum of 3 days. United States of America.

    About the role

    Preference will be given to candidates residing in the Eastern or Central time zones. As an Identity Security Architect, you will design and govern enterprise identity and access management solutions that protect organizational assets while enabling secure access to business systems and applications. You will serve as the technical authority for identity security and partner with cybersecurity, infrastructure, cloud, application, enterprise architecture, security operations, and business teams across on-premises and cloud environments. Stryker offers innovative products and services in MedSurg, Neurotechnology, Orthopaedics and Spine that help improve patient and healthcare outcomes. Alongside its customers around the world, Stryker impacts more than 150 million patients annually. Depending on customer requirements employees and new hires in sales and field roles that require access to customer accounts as a function of the job may be required to obtain various vaccinations as an essential function of their role.

    Responsibilities

    Technical Responsibilities:

    • Design and maintain enterprise identity security architecture, standards, and reference designs