Security Engineer

Job Description

• Extensive hands-on experience in IAM data and configuration migration, particularly involving complex user assignments and request histories.
• Proficiency in rebuilding and verifying Joiner, Mover, and Leaver (JML) access workflows.
• Experience migrating role-based access metadata and system entitlements across hundreds of target applications.
• Strong capability in executing trial migration runs, performing data reconciliation, and remediating deprecated features.
• Ability to generate operational runbooks and conduct technical knowledge transfer sessions for internal IT operations teams.
• Experience and strong knowledge of Identity Governance and Identity Lifecycle Management
• Deep expertise in Identity and Access Management (IAM) systems, with direct experience configuring and upgrading Bravura Identity.
• Strong technical background in integrating and provisioning to Active Directory (AD) and Microsoft Exchange.

Job Responsibilities

The IAM Migration Engineer is responsible for the accurate, complete, and secure transfer of all data, settings, and configurations from the legacy Bravura Identity system to the new supported version. This role is critical for maintaining the integrity of historical data and ensuring the uninterrupted functionality of existing access provisioning processes (joiners, movers, leavers).

• Execute the full migration of user data for 559 users.
• Migrates and verifies 58 configured workflows
• Transfers roles and entitlements that govern access across 221 applications.
• Migrate the complete request history, ensuring that absolutely no data is lost.
• Participates in trial migration runs and data reconciliation to guarantee a flawless transition into the production environment.

Department/Project Description

The project focuses on transitioning the Bravura Identity management platform to a newly supported version for a leading banking and financial institution. The process includes standing up non-production environments for change rehearsals (including a rehearsed cutover with rollback capabilities) and executing a full data migration without altering the underlying architecture.