Data Architect

Posted yesterday

software technologyPhoenix (AZ)

Data Warehousing SpecialistsComputer Systems Design Services

SENIORITY

Lead

About the role

Data Modeler ArchitectThe Data Modeler Architect is responsible for strategic understanding and documenting of existing corporate data and related applications as well as the tactical design and integration of new foundational, highly-shared Health payer domain data.The Data Modeler Architect is responsible for creation and maintenance of artifacts related to information architecture including Architectural Diagrams, Data Flow Diagrams, and Conceptual, Logical and Physical Data and or Process Models.Assists in near/mid-term roadmap creation, to address gaps and move towards future state architecture to support growth, optimization and innovation.Creates visual representations of the people, places and things of interest to a business. Facilitates communication between business people and technical people. Documents the data concepts / data blueprint that must be communicated and agreed upon.Designs data interfaces between systems, and the infrastructure that will support common data operations. Creates a formal process for managing the flow of data and how it is processed across the Enterprise.RequiredWork Experience:3 years' experience in modeling including Conceptual, Logical, and Physical data and process modeling (Level 1)2 years end to end experience evolving data and process models from initiation to physical implementation (Level 1)2 years' experience in mapping data integration and data architecture (Level 1)5 years' experience in modeling including Conceptual, Logical, and Physical data and process modeling (Level 2)3 years end to end experience evolving data and process models from initiation to physical implementation (Level 2)3 years' experience in mapping data integration and data architecture (Level 2)Preferred Work Experience:7 years of experience modeling data to conceptual, logical and physical models (Level 1 and 2)5 years' experience in healthcare industry data (e.g. EDI, HL7/FHIR, Health and Pharmacy Claims, Service, and Enrollment transactions). (Level 1 and 2)5 years' experience in mapping data integration and data architecture (Level 1 and 2)4 years' experience Master Data Management (Level 2)Preferred Certifications: Technical Certifications in Microsoft SQL

Before you apply

Applying takes about a minute. These four things decide how fast it moves after that.

Your profile is current

It's what we read first. Occupations, seniority and locations matter more than a long history.

Two examples you can talk through

Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.

A number in mind

What you're on now and what would make you move. We negotiate better when we know both.

Your notice period

Employers plan around it, and it's the question that stalls offers most often.

Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.