Senior Okta IAM Engineer

We need to output HTML fragment with sections: About the role? Actually the posting includes "Who is Tenable?" and "What makes Tenable such a great place to work?" That's like company overview. Could be "About the role"? Not exactly. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include sections only when posting has real specific content. We need to extract substantive info: Role description, responsibilities, qualifications, maybe skills, benefits, pay. We must not repeat job title as heading. Job title is "Senior IAM Engineer". Not to be used as heading. We need to remove boilerplate: EEO, legal, etc. Also remove duplicated lines, navigation, cookie, application instructions. We need to preserve all substantive info. Let's parse the posting: - Intro: Who is Tenable? description. - What makes Tenable such a great place to work? description. - Applicants must be authorized to work for any employer in the U.S. without sponsorship. (This is a requirement; could go under Requirements or Qualifications.) - Your Role As a Senior IAM Engineer within our IAM and Corporate Applications team, you will lead the design, automated deployment, and administration of our Okta enterprise identity platform. Your core responsibilities include architecting, writing, and maintaining scalable Terraform modules to provision and manage Okta applications, groups, authentication policies, authorization rules, and admin role assignments. You will manage Okta Workforce Identity Cloud configurations such as SSO, MFA, Adaptive Authentication, Universal Directory, and Workflows. Additionally, you will automate user onboarding, offboarding, and role-based provisioning (SCIM, SAML, OIDC) across cloud infrastructure and enterprise software. You will enforce Least Privilege Access and Zero Trust policies, assist with compliance reporting (SOX, SOC2, ISO 27001), integrate Okta Terraform workflows into continuous deployment pipelines (GitHub/Jenkins CI/CD), and serve as a subject matter expert for complex identity integrations and incident escalations. - Your Opportunity Step in as the primary subject matter expert for all Okta-related initiatives across our enterprise environment. Leverage Terraform to manage Okta resources and configurations, driving scalable lifecycle management processes and seamless user access control across a secure environment. Assist with managing a broader suite of corporate applications, including Google Workspace, Slack, GitHub, and Atlassian Jira & Confluence. Play a key role in supporting the adoption and integration of emerging AI platforms related to corporate application infrastructure. - What You'll Need 8+ years of hands-on experience designing and managing Okta enterprise environments and IAM. 3+ years of production experience using Terraform to manage identity providers (specifically the Okta Terraform provider), custom modules, state management, and continuous deployment pipelines. To be considered for this role, you must have the ability to commute to our Columbia, MD office three days a week. Hybrid. Deep understanding of identity protocols including SAML 2.0, OAuth 2.0, OIDC, SCIM, and LDAP. Experience with scripting and automation using Python, Bash, or PowerShell, and interacting directly with Okta REST APIs. And Ideally Experience with Okta Workflows, Okta Identity Governance (OIG), or Privileged Access Management (PAM) integrations. Experience operating within multi-cloud environments (AWS, GCP, Azure). A proven track record in enterprise application onboarding automation and directory consolidation. - This is the base pay range for this position. Compensation for the role will depend on a number of factors, including the candidate's qualifications, skills, competencies, location and experience, and may fall outside of the range shown. Employees are also eligible for variable compensation in addition to base pay (commission for sales roles, bonus for non-sales roles), depending on company and individual performance. Tenable also offers a variety of comprehensive and competitive benefits which include: medical, dental, vision, disability and life insurance; 401(k) retirement savings with company match; an employee stock purchase plan; an employee referral program; flexible spending accounts; an Employee Assistance Program (EAP); education assistance; parental leave; paid time off (PTO); company-paid holidays; health and wellness events; and community programs. US Pay Range $114,500 - $152,500 USD Then repeated same paragraph about pay and benefits. We need sections: maybe "About the company" (but not in list). The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose appropriate ones. We have content about role responsibilities (Your Role, Your Opportunity). Could combine into Responsibilities. We have qualifications/experience (What You'll Need) -> could be Requirements or Qualifications. We have skills (maybe deep understanding of identity protocols, scripting, etc.) could be Skills. We have Benefits and Pay. We have schedule: hybrid, commute to Columbia MD office three days a week. That's schedule info. We also have company overview (Who is Tenable? What makes Tenable such a great place to work?) Could be "About the role"? Not exactly. Could be "About the company" but not in list. Maybe we can put that under "About the role"? The instruction says use headings e.g. About the role, Responsibilities... It doesn't forbid other headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings. But we could also include "About the company" if needed? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are examples; we could use others if appropriate, but better to stick to those. We have company overview; maybe we can put under "About the role"? Not ideal but could be considered description of role context. Or we could omit it? The instruction says preserve ALL substantive information; do not invent or summarize away detail. So we need to keep that info. Could put it under a heading like "About the role" even though it's about company. Or we could create a heading "About Tenable" but that's not in examples; risk of being considered not following instruction. Safer to use "About the role" and put company overview there. Alternatively, we could treat "Who is Tenable?" as part of responsibilities? No. Better: Use "About the role" for company overview and role context. Then "Responsibilities" for core duties. Then "Qualifications" for experience needed. Then "Skills" for specific technical skills. Then "Benefits" and "Pay". Then "Schedule" for hybrid. We must not repeat headings with filler. Ensure each heading has substantive content. Let's extract content: About the role (company overview): - Tenable® is the Exposure Management company. Over 40,000 organizations around the globe rely on Tenable to understand and reduce cyber risk. Our global employees support 65 percent of the Fortune 500, 50 percent of the Global 2000, and large government agencies. Come be part of our journey! What makes Tenable such a great place to work? Ask a member of our team and they’ll answer, “Our people!” We work together to build and innovate best-in-class cybersecurity solutions for our customers; all while creating a culture of belonging, respect, and excellence where we can be our best selves. When you’re part of our #OneTenable team, you can expect to partner with some of the most talented and passionate people in the industry, and have the support and resources you need to do work that truly matters. We deliver results that exceed expectations and we win together! Responsibilities: - Lead the design, automated deployment, and administration of our Okta enterprise identity platform. - Architect, write, and maintain scalable Terraform modules to provision and manage Okta applications, groups, authentication policies, authorization rules, and admin role assignments. - Manage Okta Workforce Identity Cloud configurations such as SSO, MFA, Adaptive Authentication, Universal Directory, and Workflows. - Automate user onboarding, offboarding, and role-based provisioning (SCIM, SAML, OIDC) across cloud infrastructure and enterprise software. - Enforce Least Privilege Access and Zero Trust policies. - Assist with compliance reporting (SOX, SOC2, ISO 27001). - Integrate Okta Terraform workflows into continuous deployment pipelines (GitHub/Jenkins CI/CD). - Serve as a subject matter expert for complex identity integrations and incident escalations. - Step in as the primary subject matter expert for all Okta-related initiatives across our enterprise environment. - Leverage Terraform to manage Okta resources and configurations, driving scalable lifecycle management processes and seamless user access control across a secure environment. - Assist with managing a broader suite of corporate applications, including Google Workspace, Slack, GitHub, and Atlassian Jira & Confluence. - Play a key role in supporting the adoption and integration of emerging AI platforms related to corporate application infrastructure. Qualifications (experience): - 8+ years of hands-on experience designing and managing Okta enterprise environments and IAM. - 3+ years of production experience using Terraform to manage identity providers (specifically the Okta Terraform provider), custom modules, state management, and continuous deployment pipelines. - Ability to commute to our Columbia, MD office three days a week (Hybrid). - Applicants must be authorized to work for any employer in the U.S. without sponsorship. (We are unable to provide sponsorship for work visas of any kind at the time of hire, or at any point during employment.) This includes, but is not limited to: F1-OPT, F1-CPT, H-1B, TN, J-1, etc. Skills: - Deep understanding of identity protocols including SAML 2.0, OAuth 2.0, OIDC, SCIM, and LDAP. - Experience with scripting and automation using Python, Bash, or PowerShell, and interacting directly with Okta REST APIs. - Experience with Okta Workflows, Okta Identity Governance (OIG), or Privileged Access Management (PAM) integrations. - Experience operating within multi-cloud environments (AWS, GCP, Azure). - Proven track record in enterprise application onboarding automation and directory consolidation. Benefits: - Medical, dental, vision, disability and life insurance. - 401(k) retirement savings with company match. - Employee stock purchase plan. - Employee referral program. - Flexible spending accounts. - Employee Assistance Program (EAP). - Education assistance. - Parental leave. - Paid time off (PTO). - Company-paid holidays. - Health and wellness events. - Community programs. Pay: - US Pay Range $114,500 - $152,500 USD. - Compensation for the role will depend on a number of factors, including the candidate's qualifications, skills, competencies, location and experience, and may fall outside of the range shown. - Employees are also eligible for variable compensation in addition to base pay (commission for sales roles, bonus for non-sales roles), depending on company and individual performance. Schedule: - Hybrid role requiring ability to commute to Columbia, MD office three days a week. We must ensure not to repeat content. Also ensure we removed duplicated lines like the repeated pay/benefits paragraph. Now produce HTML fragment with

headings and

• for lists,

  for prose. We need to decide which content is prose vs list. For responsibilities, qualifications, skills, benefits we can use lists. For About the role maybe prose paragraphs. Pay could be prose or list; we can use

  for prose. Schedule could be

  . Let's craft. Check for any boilerplate left: We removed EEO, legal, etc. Also removed duplicated lines like "This is the base pay