Principal Engineer - IAM
About the role
thenwith that content. Next: "In This Role, You Will Serve as a principal technical advisor for enterprise IAM, identity governance, privileged access, authentication, authorization, and cloud-native security initiatives.Define technical strategy, reference architectures, engineering standards, and reusable patterns for enterprise identity platforms.Lead the design and modernization of highly complex IAM and PAM platforms using Java, Spring Boot, microservices, APIs, Kubernetes, and cloud technologies.Design identity lifecycle, application onboarding, access governance, role-based access, least-privilege, segregation-of-duties, and access recertification capabilities.Develop secure integrations across IAM, IGA, PAM, cloud, application, and enterprise service-management platforms.Provide engineering leadership for privileged access solutions, including time-bound access, session provisioning, secrets management, auditing, and access monitoring.Establish fine-grained authorization patterns for applications, APIs, workload identities, AI agents, and machine-to-machine interactions.Evaluate and implement secure Generative AI capabilities, including AI agents, MCP servers, RAG solutions, identity propagation, and authorization controls.Establish observability, resiliency, testing, deployment, and production-support practices for security-critical identity platforms.Partner with senior leaders and stakeholders to define platform roadmaps, prioritize investments, and translate business and regulatory requirements into engineering solutions.Mentor engineers and technical leads while promoting software engineering, security, automation, and operational best practices.Evaluate emerging identity, security, cloud, and AI technologies and recommend innovations that strengthen security and improve engineering efficiency.Demonstrate proficiency in using AI-assisted development and analysis tools (e.g., GitHub Copilot and approved code-centric agents)Leverage AI to accelerate system design, coding, testing, analysis, and troubleshootingApply strong technical judgment when validating and integrating AI-assisted outputs into solutionsUnderstand and account for model limitations, security risks, and operational considerationsApply AI responsibly in development and production environmentsEnsure AI usage aligns with security, compliance, privacy, and ethical standards" These are responsibilities. Could be "Responsibilities". We'll list as
- each bullet.
But need to split into separate items. The text is a long run-on with periods. We'll split at each sentence that starts with a verb. Let's extract bullet points:
- Serve as a principal technical advisor for enterprise IAM, identity governance, privileged access, authentication, authorization, and cloud-native security initiatives.
- Define technical strategy, reference architectures, engineering standards, and reusable patterns for enterprise identity platforms.
- Lead the design and modernization of highly complex IAM and PAM platforms using Java, Spring Boot, microservices, APIs, Kubernetes, and cloud technologies.
- Design identity lifecycle, application onboarding, access governance, role-based access, least-privilege, segregation-of-duties, and access recertification capabilities.
- Develop secure integrations across IAM, IGA, PAM, cloud, application, and enterprise service-management platforms.
- Provide engineering leadership for privileged access solutions, including time-bound access, session provisioning, secrets management, auditing, and access monitoring.
- Establish fine-grained authorization patterns for applications, APIs, workload identities, AI agents, and machine-to-machine interactions.
- Evaluate and implement secure Generative AI capabilities, including AI agents, MCP servers, RAG solutions, identity propagation, and authorization controls.
- Establish observability, resiliency, testing, deployment, and production-support practices for security-critical identity platforms.
- Partner with senior leaders and stakeholders to define platform roadmaps, prioritize investments, and translate business and regulatory requirements into engineering solutions.
- Mentor engineers and technical leads while promoting software engineering, security, automation, and operational best practices.
- Evaluate emerging identity, security, cloud, and AI technologies and recommend innovations that strengthen security and improve engineering efficiency.
- Demonstrate proficiency in using AI-assisted development and analysis tools (e.g., GitHub Copilot and approved code-centric agents)
- Leverage AI to accelerate system design, coding, testing, analysis, and troubleshooting
- Apply strong technical judgment when validating and integrating AI-assisted outputs into solutions
- Understand and account for model limitations, security risks, and operational considerations
- Apply AI responsibly in development and production environments
- Ensure AI usage aligns with security, compliance, privacy, and ethical standards
That seems fine.
Next: "Required Qualifications: 7+ years of Engineering experience, or equivalent demonstrated through one or a combination of the following: work experience, training, military experience, education7+ years of Experience designing and engineering enterprise Identity and Access Management, Identity Governance and Administration, or Privileged Access Management platforms"
Note there is a typo: "education7+ years". We'll preserve as is? Probably we should keep the text exactly but maybe fix spacing? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep as given, but we could keep the weird concatenation? It's part of the posting. We'll keep it as is.
Then "Desired Qualifications:" list many items.
We need sections: Requirements, Qualifications, Skills. The posting has Required Qualifications and Desired Qualifications. Could combine into Qualifications section with subpoints? Or separate Required and Desired? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we have to decide which headings to use. We have content for Required Qualifications and Desired Qualifications. Could put under Qualifications heading, with sub-bullets marking required vs desired. Or we could split into Requirements and Qualifications. But we have both required and desired; maybe we treat Required Qualifications as Requirements, and Desired Qualifications as Qualifications. That seems logical: Requirements = mandatory, Qualifications = desired/preferred. We'll do that.
Thus:
Requirements
- 7+ years of Engineering experience, or equivalent demonstrated through one or a combination of the following: work experience, training, military experience, education
- 7+ years of Experience designing and engineering enterprise Identity and Access Management, Identity Governance and Administration, or Privileged Access Management platforms
Qualifications
with bullets. List: - Advanced development experience with Java, Spring Boot, Spring Security, REST APIs, microservices, and event-driven architectures. - Experience with IAM or PAM platforms such as Saviynt, Oracle Identity Manager, CyberArk, BeyondTrust, or comparable technologies. - Experience developing identity lifecycle, Joiner-Mover-Leaver, access recertification, role management, segregation-of-duties, and least-privilege solutions. - Experience designing privileged access capabilities, including session provisioning, credential management, access monitoring, audit controls, and time-bound access. - Experience modernizing enterprise platforms using Kubernetes, EKS, Docker, Helm, Terraform, GitOps, and cloud-native engineering patterns. - Experience developing CI/CD pipelines and automated delivery practices using GitHub Actions, Argo CD, Bamboo, Bitbucket, or similar technologies. - Knowledge of authentication, authorization, RBAC, policy-based access control, workload identity, secrets management, and fine-grained entitlement models. - Experience designing secure AI platforms involving Generative AI, AI agents, MCP servers, RAG, LLM integrations, or AI authorization controls. - Experience establishing enterprise reference architectures, engineering standards, design-review practices, and platform roadmaps. - Experience supporting security-critical platforms in regulated environments, including audit readiness, risk management, monitoring, and production support. - Strong executive communication, stakeholder management, technical leadership, and engineering mentorship skills. Now Skills section: The posting does not have a separate Skills section; many of the desired qualifications could be considered skills. But we already used Qualifications for desired. Could we also have Skills? The instruction: prefer a few substantive sections over many thin ones. If we already have Qualifications covering desired, we might not need separate Skills. However we have also responsibilities which include skills. But we can omit Skills if no specific content beyond what's already captured. The instruction: include a section ONLY when the posting has real, specific content for it. So we should not add Skills if not distinct. We'll skip Skills. Benefits: The posting includes a Benefits section with list: Health benefits, 401(k) Plan, Paid time off, Disability benefits, Life insurance, critical illness insurance, and accident insurance, Parental leave, Critical caregiving leave, Discounts and savings, Commuter benefits, Tuition reimbursement, Scholarships for dependent children, Adoption reimbursement. We'll put underBenefits
with- each. Pay: The posting includes salary range: "$191,000.00 - $305,000.00". Also mentions: "Salary range is determined by location of the job. May be considered for a discretionary bonus, Restricted Share Rights, or other long - term incentive awards. This role is NOT available for 100% remote work Pay Range Reflected is the base pay range offered for this position. Pay may vary depending on factors including but not limited to demonstrated examples of prior performance, skills, experience, or work location. Employees may also be eligible for incentive opportunities." We need to include Pay section only if posting actually states them. It does state base pay range. So we will include Pay. We should not include Schedule unless posting states schedule. It does not mention schedule (like full-time, hours). So we omit Schedule. Now we need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "Posting Statements: Job posting may come down early due to volume of applicants. Required location(s) listed above. Relocation assistance is not available for this position" etc. Also remove "Posting End Date: 22 Sep 2026". Also remove "We Value Equal Opportunity ..." etc. Also remove "Reference Number R-576449". Also remove "Locations: 150 E 42nd