Data architecture & data mesh
Lakehouse and domain-oriented platforms with governance built in.
- Monolith → 34 domain-owned GCP projects
- Shared policies for replication, quality, catalog, access
- 17-parameter source-quality rating with team alerts
Data & AI Solutions Architect · 14 years
Senior Solution Architect at Searce, a Google Cloud partner. Before that I led the data-platform function at Tokopedia and ran a 4.2 PB Hadoop platform at Airtel.
Where I've built and run data platforms
About
I'm a data and AI solutions architect with fourteen years in data. I started as an Oracle DBA keeping high-availability telecom databases running, then set up and ran a 4.2 PB Hadoop platform at Airtel.
At Tokopedia (GoTo Group) I led the data-platform function: eleven direct reports across five teams. We moved a monolithic platform to a domain data mesh of 34 domain-owned projects, made data quality visible to every team, and cut cloud spend 32–43% per team.
Today I'm a Senior Solution Architect at Searce, a Google Cloud partner, where I design data-platform modernisation and AI programmes for enterprises: discovery, migration strategy, lakehouse architecture and disaster recovery.
I also build AI systems hands-on to learn what actually holds up, such as agents behind human approval gates, blind evaluation harnesses and reproducible data platforms, and I write up what I learn as architecture notes.
Capabilities
Eight areas, each backed by work I've actually done.
Lakehouse and domain-oriented platforms with governance built in.
Moving estates to Google Cloud without stopping the business.
Batch and streaming pipelines that teams can actually operate.
Rules that are enforced, not just written down.
Cost treated as an architecture decision, not a monthly surprise.
AI that is governed, evaluated and cost-aware.
Teams that own their platforms, end to end.
From the first workshop to a statement of work.
How I work
Workshops and estate sizing: what the data has to do for the business, what exists today and what it costs.
Target architecture, migration waves, governance and recovery, with the trade-offs written down.
PoCs, parity checks and evaluations before anyone commits, so a design gets tested, not just believed.
Run what ships: cost attribution, quality ratings, access audits and clear ownership.
Selected work
Short engineering reports: the context, what I did, the architecture and what changed. Each one says how far the work got.
Led the move of a large e-commerce company's central data platform into 34 domain-owned cloud projects, with shared policies and a source-quality rating.
Ran a four-phase FinOps programme across five teams that cut cloud spend 32–43% per team, sustained by continuous cost monitoring.
Set up and ran a 4.2 PB Cloudera Hadoop platform end to end, with ETL, reporting and automation, plus two Cassandra clusters for Customer 360.
Experience
Seven roles across telecom, HR services, e-commerce and cloud consulting.
2025 — Present
Architecture and pre-sales for enterprise data-platform modernisation and AI programmes on Google Cloud: discovery, sizing, migration strategy, lakehouse design and cross-cloud disaster recovery.
2024 — 2025
Databricks architect on Azure. Designed complete, end-to-end data pipelines with Azure Data Factory and Databricks.
2019 — 2024
Lead Data Platform → Engineering Manager, Data Platform
Led the data-platform function: 11 direct reports across data engineering, data science, data analytics and two internal teams. Moved a monolithic platform to a domain data mesh (4 → 34 domain-owned GCP projects), ran a four-phase FinOps programme that cut cloud spend 32–43% per team, and built a 17-parameter data-quality rating with alerts by team and service.
2018 — 2019
Set up and ran a 4.2 PB Cloudera Hadoop platform end to end, with Ab Initio and NiFi ETL, billing and utilisation reporting, and Ansible and Grafana automation. Stood up two Cassandra clusters for Customer 360.
2016 — 2018
Database engineering and a Hadoop analytics warehouse for a global HR-services client; migrated data from SAP IQ to Hadoop.
2014 — 2016
L3 DBA for high-availability telecom platforms: 12 production RAC databases and 32 migrations for one operator, plus Data Guard and database builds for operators in Dubai and Malaysia.
2012 — 2014
Oracle and SQL Server administration and PL/SQL development for a banking CRM platform.
Technology timeline
When I used what, taken from the roles above.
Notes
Architecture notes: patterns I design with, and lessons from building data and AI systems.
Nov 2026 · 1 min read
The Model Context Protocol standardises how agents reach tools and data. Governance is still your job.
Nov 2026 · 1 min read
Partitioning, clustering, the on-demand vs Editions decision, and the query habits that decide most of the bill.
Nov 2026 · 1 min read
Getting operational changes into the warehouse in minutes: capture, ordering, merging and the cost traps.
Nov 2026 · 1 min read
Open table formats let several engines share one copy of data. What they give you, and the decisions that matter more than the format.
Nov 2026 · 1 min read
Retrieval-augmented generation works when retrieval is treated as a data problem: permissions, freshness and evaluation first.
Nov 2026 · 1 min read
One catalog for tables, files, models and permissions, and the decisions to make before teams start creating things.
Toolkit
Contact
I'm happy to talk architecture, modernisation or governed AI. Email is quickest.