Enterprise Solution Architect - Okta / KeyCloak

Job Description :

• Partner with business stakeholders to architect comprehensive insurance solutions across products, distribution channels, and customer service capabilities.
• Champion lean business case development focusing on measurable outcomes, Drive innovation through emerging technology adoption.
• Lead proof-of-concepts for new business capabilities, Influences : Technology Strategy, Solution Design, Architecture Standards.
• Demonstrates Thought leadership and mentor a team of solution architects and business analysts in insurance domain expertise.
• Create solution roadmaps aligned with business strategy, Partner with senior leadership, engineering teams, and product managers to make key architectural decisions, ensuring technical feasibility and scalability.
• Stay abreast of emerging business technology trends and evaluate their potential to impact our technology stack and overall architecture.
• You can act as a bridge between technology teams and business teams.
• Lead initiatives to integrate AI / GenAI technologies into existing systems for enhanced decision making, automation and customer experience
• Ensure adherence to standards, patterns, data privacy regulations, and best practices across all systems and platforms.
• Collaborate with enterprise architects to define standards and design patterns.
• Lead and / or contribute to the evaluation, selection, and implementation of enterprise technologies.
• Publish strategic roadmaps, white papers and engage peer architects in forming strategies for solving key business imperatives.
• Able to present and articulate strategic initiatives to executive leaders
• Collaborate with : Business Unit Leaders, Enterprise Architecture, Development Teams
• Participate in talent development and recruiting.
• Design patterns in microservices architecture and few practical questions.
• Scalability in event driven systems like Kafka.
• Cloud migration.
• Authentication, Authorization - Okta, KeyCloak.
• Strategy in choosing DB type, RDBMS vs No-sql.

You Have :

Preferred Qualification :

(ref : hirist.tech)