Principal Data Architect

Job Title: Principal Architect
Work Mode: Remote (EST or CST only)
Interview Type: Virtual

 
Job Description

The Principal Architect, Data architecture and Solution Engineering, will be responsible for developing and executing the data strategy at the business unit level that powers the most advanced end-to-end solution architecture from transactional Systems of record to AI driven business intelligence for highly complex and significant technology transformation initiatives in partnership with key business and IT stakeholders. 

Roles and Responsibilities 

·         Provide data technology leadership, oversight, and guidance to ensure that the solution adheres to PSS Architecture Guiding Principles and standards while maximizing reuse of technology assets.

·          In depth experience in performing Buy vs Build analysis based on the qualitative and quantitative analysis across the available options to provide a final recommendation based on the rationale

·         Play a key leadership role in architecture design reviews and identify gaps and recommend design changes. 

·         Actively lead and participate in the Architecture community to drive modernization opportunities for the advancement of PBM data technologies while keeping in mind the complexities of our technology landscape

·         Develop data architectures, guardrails and guidelines to instill a strong data discipline, providing leadership, coaching and guidance to Engineering and Product teams across the organization.  

·         Architect AI driven business intelligence powered by a Universal Semantic Layer delivering powerful predictive analytics and Natural Language queries

·         Advise and assist App development teams with technical roadblocks such as performance challenges within a solution in key strategic initiatives

1. Skills:
   
   Data Modeling
   Data Design
   AI
   Forward Thinking
   Excellent Comm skills
   Data Architecture for Transaction
   Architecture for Consumption
   Data platforms: No specific need - but candidates should have command over relational databases, No-SQL databases, graph databases, data lakes and lakehouse implementations.