What are the responsibilities and job description for the RBAC Analyst position at Avancer Corporation?
Job Details
Position: RBAC Analyst
Location: Alpharetta, GA (Hybrid)
Role Summary:
The RBAC (Role Based Access Controls) Analyst is responsible for partnering with business units to design, analyze, and implement role-based access controls aligned to job functions. This role serves as the primary liaison between the business and Identity & Access Management (IAM) teams to translate functional responsibilities into scalable, access models.
Key Responsibilities:
Business Engagement & Requirements Gathering
• Lead working sessions and meetings with Business Units to understand job functions, responsibilities, and access needs.
• Translate business processes and job activities into clearly defined access roles and entitlement groupings.
• Provide guidance to business stakeholders on RBAC concepts, role design best practices, and least privilege principles.
RBAC Analysis & Role Design
• Analyze existing roles, entitlements, and user access to identify gaps, overlaps, and opportunities for standardization.
• Design and refine business roles based on job function, including base roles, elevated roles, and exceptions.
• Support role lifecycle management including creation, modification, validation, and retirement.
• Maintain RBAC documentation, role definitions, and decision records for auditability and sustainability.
Continuous Improvement & Collaboration
• Identify opportunities to improve RBAC processes, tooling, and scalability.
Required Experience & Qualifications:
• 3–5 years of experience in Identity & Access Management (IAM), with direct experience in Role-Based Access Control (RBAC).
• Demonstrated experience conducting business-facing workshops or meetings to gather requirements and validate role designs.
• Strong analytical skills with the ability to interpret job functions, business processes, and access data.
• Experience designing roles aligned to least privilege and compliance requirements.
• Ability to document role definitions, access mappings, and governance decisions clearly.
• Strong communication skills with the ability to explain technical access concepts to non-technical stakeholders.
Thanks,