Senior Principal Data Architect

Job description

Data Engineering Lead — Summary (From Meeting Transcript) 1. Purpose of the Role The Data Engineering Lead is the primary operational and communication bridge between the North America–based IPH data leadership and the India based TCoE (Tech Center of Excellence) team in Hyderabad. They ensure smooth delivery, alignment, and execution across geographies. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ 2. Key Responsibilities A. Communication & Coordination • Act as the conduit between US leadership and Hyderabad teams—ensuring clarity, translating expectations, and surfacing risks or issues early. • Provide dotted line mentorship and support to all engineers/analysts in the pods, especially during off hours or time zone gaps. B. Delivery Leadership / Scrum Ownership • Serve as a scrum master / delivery owner to guide the engineering and reporting pods • Ensure teams join daily standups, collaborate effectively, and integrate with the wider IPH data organization. C. Oversight Across Four Data Domains While not expected to be a deep expert in all, the lead must understand and guide work across: 1. Data Strategy & Planning 2. Data Governance 3. Infrastructure & Data Engineering 4. Analytics & Reporting D. Quality, Consistency & Governance • Monitor and ensure consistency of data definitions, modeling practices, and reporting outputs across brands as IPH centralizes data\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ 3. Technical Skill Expectations Core Technical Stack • Databricks (primary platform for new unified data engineering) • Snowflake (legacy skill helpful during migration • DBT (for transformation and governance metadata) • Azure Purview (planned governance/lineage tooling)