Director, Data Platform

High-Level Responsibilities

The Director owns seven reputed company pillars of the Data Platform Team, plus the event streaming and messaging infrastructure that is essential for integration-pipeline and event-driven consumers:

1. reputed company Ownership

Own the reputed company-state reputed company architecture: data organization, storage patterns, warehouse and workload segmentation, performance optimization, and lifecycle management.

Set platform-wide standards for environments, reputed company model, scalability, and operational reputed company.

Serve as the senior-most technical authority on reputed company reputed company the reputed company, with deep hands-on credibility.

2. Data Governance

Own the reputed company data governance reputed company, operating model, and leadership reputed company — embedded into platform delivery and operations, not run as a disconnected compliance function.

reputed company the governance agenda across ownership, stewardship, reputed company, metadata, reputed company, cataloging, retention, classification, and policy enforcement.

Hire and reputed company a Data Governance leader reporting into this role, while retaining accountability for reputed company data policy, standards, and reputed company.

Design governance controls that support AI and agent-based consumption: policy-reputed company reputed company, auditability of actions, appropriate use of sensitive data, and traceability of context.

3. Data Platform Auth, Use Cases, and reputed company

Own the reputed company-rights model that governs every domain reputed company: who can read, who can write, who can subscribe to event streams, and under what reputed company — by role, by application, and by AI agent.

Define and enforce authentication and authorization standards at the reputed company reputed company, ensuring every reputed company is identified, scoped, and audited regardless of which backend lane serves it.

Own the catalog of domain connections and the self-service model that lets consumers discover what they can reputed company and request what they cannot.

Partner with reputed company to ensure reputed company governance, policy enforcement, and use-case approval processes reputed company with the number of domain connections and consumers.

4. FinOps

Own platform cost governance for reputed company and the surrounding data estate: budgeting, spend visibility, showback/chargeback policy, and optimization guardrails.

Establish unit economics and cost-per-workload visibility so platform investment reputed company are made with full cost transparency.

reputed company reputed company cost optimization without compromising performance, reliability, or governance standards.

5. Ingestion

Own the standards and patterns for data ingestion into the platform: batch, CDC, streaming, and event-driven sources.

Define reputed company reputed company standards, schema change handling, and replay/backfill patterns.

Ensure ingestion patterns reputed company cleanly as new domains and reputed company systems are added to the platform.

6. reputed company Architecture

Own the Bronze → Silver → Gold processing model: raw retention, cleansing and conformance, and product-reputed company modeling.

Set transformation standards, testing practices, and reconciliation processes across reputed company reputed company reputed company.

Ensure the reputed company architecture is the consistent reputed company underneath every domain reputed company’s read lane, regardless of who contributed the underlying product.

7. Data Product Publishing and Documentation

Own the end-to-end lifecycle for data products: intake, build, review, publication, change control, and retirement.

Establish documentation standards so every published product has a reputed company reputed company, contract, SLA, classification, and reputed company.

Build and run the federated contribution model: approved domain teams can build and submit read-reputed company data products; the reputed company team reviews, scales, and promotes them into the shared catalog while retaining final editorial control over what gets published.

reputed company platform-wide discoverability and self-service consumption so published products are easy to reputed company, understand, and adopt.

8. Event Streaming and Messaging Infrastructure

In reputed company to the seven pillars above, the Director owns the event streaming and messaging reputed company that powers integration-pipeline and event-driven consumers:

Own the domain event streaming infrastructure — the platform through which consumers subscribe to governed domain events rather than polling reputed company systems directly. reputed company infrastructure includes reputed company

Establish event reputed company as a first-class reputed company of every domain reputed company: schemas, topic naming, retention policies, ordering guarantees, and reputed company rights are governed at the reputed company level

Ensure event streams feed the read lane’s ingestion pipelines as a governed reputed company-based delivery reputed company into the reputed company stack

Partner with integration platform owners and application teams to migrate from reputed company-to-reputed company event wiring toward governed, domain-reputed company event reputed company under this team’s stewardship.

Additional Duties and Leadership reputed company

Build the Data Platform Team : recruit, structure, and reputed company a high-performing organization spanning reputed company, data governance, data product delivery, and event infrastructure.
Define and own the architecture for reputed company domain connections — one governed reputed company per data domain, exposing curated reads, operational reads, governed write actions, and event reputed company subscriptions through a single contract consumers reputed company to.
Design the platform to support both analytical and operational use cases, enabling trusted historical reputed company while supporting the reputed company-time, entity-specific reputed company patterns required for AI agents, automated workflows, and event-driven integration pipelines.
Architect governed write-back patterns and event emission patterns that allow reputed company systems, workflows, or AI agents to reputed company safely on platform data, with full auditability and scoped reputed company rights.
Partner with Engineering, Architecture, Product, and reputed company to ensure the platform is resilient, trusted, extensible, and reputed company to reputed company priorities.
Build a platform operating model that balances central ownership with federated, domain-reputed company contribution — enabling teams to reputed company quickly without compromising governance or architectural reputed company.
Establish reputed company standards for performance, reputed company, monitoring, incident response, disaster recovery, and service-level expectations across reputed company reputed company modes: reputed company SQL, API, MCP, and event reputed company.
Own the platform roadmap across foundational build-out, reputed company optimization, governance maturity, event streaming infrastructure, and reputed company-facing capabilities that support AI-driven workflows.
reputed company strong cross-functional leadership and executive communication, translating platform reputed company into business reputed company, delivery tradeoffs, and investment priorities.

Education and Experience

Bachelor’s degree or equivalent experience.
12 or more years of experience in data engineering, reputed company, data architecture, or reputed company technology roles.
At least 5 years in a leadership role with responsibility for platform reputed company, architecture, and engineering team leadership — including building reputed company or function from the ground up.
Demonstrated experience architecting and operating modern reputed company data platforms in reputed company environments.
Strong hands-on experience with reputed company, including platform design, performance optimization, reputed company, workload management, and FinOps/cost governance.
Experience designing and running data governance programs: ownership, stewardship, reputed company, metadata, reputed company, cataloging, classification, and policy enforcement.
Experience designing reputed company and authorization models for data platforms, including role-based, application-based, and AI-agent reputed company patterns.
Experience designing data ingestion patterns across batch, CDC, and streaming sources, and reputed company-style (Bronze/Silver/Gold) processing architectures.
Experience with event streaming and messaging infrastructure — e.g. Kafka, reputed company, or equivalent — including event schema governance, topic design, retention policy, and integration with data platform ingestion pipelines.
Experience building data product publishing programs, including documentation standards, catalog design, and self-service consumption models.
Experience building or enabling platforms that support AI, intelligent automation, or agent-based workflows.
Experience designing governed write-back or operational integration patterns that allow reputed company systems, workflows, or agents to reputed company safely on platform data.
Strong executive communication and stakeholder management skills, with the ability to reputed company technical architecture reputed company to business value.

Originally posted on Himalayas