Job Description: Data Model Architect

We are seeking a Data Model Architect to lead the design of scalable, future‑ready data models across our enterprise data platform. This role combines deep technical expertise with strong conceptual modeling skills to ensure data is organized, governed, and optimized for analytics, operations, and product use cases.

What You’ll Do

• Define and evolve enterprise‑wide conceptual, logical, and physical data models across domains.
• Lead data modeling for data lakes, lakehouse architectures, warehouses, and operational data stores.
• Establish data standards, taxonomies, ontologies, and naming conventions for cross‑team consistency.
• Partner with data engineering teams to design schema evolution, partitioning, SCD strategies, and optimization for performance and cost.
• Work closely with architects to align data models with domain-driven design (DDD) and data product principles.
• Collaborate with product, engineering, and analytics teams to translate business requirements into high‑quality data models.
• Review pipelines, schemas, and data contracts to ensure adherence to governance, quality, lineage, and security standards.
• Evaluate and introduce best practices for metadata management, master data, reference data, and semantic layers.
• Document models using industry‑standard tooling and communicate data structures clearly to stakeholders.

What You Bring

• 9+ years of experience in data architecture, data modeling, or data engineering.
• Strong expertise in conceptual/logical/physical modeling, dimensional modeling, and data vault.
• Experience designing models for modern stacks—Data Lakehouse (Iceberg/Delta/Hudi), MPP warehouses (Snowflake/BigQuery/Redshift), and OLTP systems (Postgres/MySQL).
• Hands‑on experience with ER/Studio, ERWin, dbt, Lucidchart, or similar modeling tools.
• Solid understanding of data governance, lineage, DQ, metadata management, and MDM.
• Ability to collaborate with cross‑functional teams and communicate complex data concepts simply and clearly.
• Familiarity with domain‑driven design and semantic modeling is a strong plus.

We Prefer

• Experience designing data models for API-driven ecosystems, event-driven architectures, and streaming pipelines.
• Knowledge of industry data standards (Aviation, Retail. Energy etc).
• Exposure to graph modeling, ontology design, or knowledge graph concepts.
• Working knowledge of modern data catalogs (DataHub, OpenMetadata, Collibra).

Architectural Knowledge

• Strong knowledge of:
  • Event-driven architecture
  • CDC patterns
  • Lakehouse vs Data Warehouse principles
  • Semantic layers and API-based data access
  • Multi-zone data modeling (bronze/silver/gold)
  • High-performance partitioning & file layout design
  • Streaming vs micro-batching vs ELT