Enterprise data architecture & data warehousing
Design of the end-to-end data landscape: operational stores, landing and staging, central warehouse or lake, data marts, and consumption layers. Fluent in both Kimball and Inmon, on-premises and cloud.
- Enterprise and application data models; metadata-driven design
- Warehouse and lakehouse design on Snowflake, BigQuery, Redshift, Athena, Databricks, or SQL Server
- Massively parallel and multi-tenant architectures
- Availability modeling and capacity planning
Proof point: architected a 19-node, 2 TB massively parallel warehouse for 1,000+ users at about a quarter of the cost of a comparable state system.
Data engineering & pipelines
Reliable ingestion and transformation from every source your business runs on, with the operational discipline to keep it running: monitoring, data quality checks, change management, and archiving.
- ETL/ELT with Airflow, dbt, Fivetran, Airbyte, Glue, SSIS, or custom code
- Automated code generation for repetitive pipelines and legacy formats
- Multi-cloud consolidation: AWS, Azure, GCP, Oracle Cloud
- Pipeline performance, scheduling, and cost control
Proof point: consolidated usage data from four clouds, thirteen environments, and hundreds of customers into one data lake at Qubole.
Application database design & data-access layer
The database under your product determines how fast you can build, how well it performs, and how clean your analytics will be. We design it properly, with a database-centric, metadata-driven approach that keeps logic where it belongs.
- Logical and physical modeling; naming, integrity, and logic placement standards
- Multi-tenant designs with strict per-customer data isolation
- Data-access layer design (ADO.NET, ORMs, stored procedures)
- Vendor and platform selection: PostgreSQL, MySQL, SQL Server, Oracle, DB2, Aurora
Proof point: designed the multi-tenant database and data layer for Verint's workforce-forecasting product used by major banks.
Data migration, integration & MDM
Architecture and program leadership for moving data between systems and keeping it consistent afterward, whether the cause is a new platform, an acquisition, or a legacy retirement.
- Migration architecture, sequencing, and cut-over planning
- Master data management for customer, product, pricing, and asset domains
- Enterprise integration over bus or middleware architectures
- Post-acquisition consolidation of disparate systems and stacks
Proof point: led a 30-person team through Equinix's migration across tens of enterprise applications, including MDM and real-time integration.