Data Warehouse Architect

Description

Job Responsibilities Develop conceptual and logical data models and meta data models Develop architecture for project that includes integration (ELT & ETL), logical data model, metadata architecture Collaborate with BI architects and developers to support design and development of Business Objects universes Interview business and technical personnel to understand requirements Document requirements Collaborate with ETL developers to develop Informatica mappings, transformations, and work flows Collaborate with database administrators to physical and the logical models Collaborate with QA personnel to design test plans and test scripts Requirements 35 years data warehouse architect Deep understanding of data modeling including subtype and supertype; Understanding of performance and other tradeoffs of different model types dimensional, star schema, snowflake schema; Understanding of the impact of Teradatas architecture and capabilities on logical and physical data models; Experience developing Teradata indexing strategies; Extensive experience conducting source system analysis and designing transformations; Assertive but not arrogant or pushy; Bachelors Degree or equivalent plus 7+ years of data warehouse and business intelligence architecture experience.; 3 years Informatica PowerCenter ETL & ELT development experience 4 years experience architecting ETL and ELT into Oracle 23 years architecting ETL and ELT into Teradata 12 years use of Informatica / Teradata Push Down technologies 5+ years data modeling using ERWin 35 yrs experience Metadata modeling Excellent oral communication skills, both upwardly (managers, directors, vice presidents) and downwardly (developers). Strong written communication skills Strong presentation skills Familiarity with at least one Teradata industry logical data model Communications LDM preferred Experience with SAS would be a plu Additional Job Info Teradata must have hands on Teradata experience (actually worked with the database as Teradata is very different from Oracle). Logical Modeling and Physical Modeling Normalization and Denormalization Subtype and Supertype Understanding of Erwin and Informatica Must be able to model Data Hirearchy & Dimensional Modeling Soft Skills (that are a must have) Need people that are able to work politically the team has 35 (each person will have 35 projects to work on simultaneously). Will work with the BSA and customer to define requirements. Must be able to speak intelligently about modeling and have the ability to communicate well both written and verbal as they will be looped in on a lot of conference call and email communication.