Custom ETL over inconsistent sources, analytical ClickHouse and Postgres tuned to the query, ingestion that reruns safely. Schema to dashboard, I own the plumbing.
6B+
rows in production ClickHouse
750+
matches ingested automatically
500ms
P90 analytical query latency
About me
I am Vansh Bordia, a data engineer who likes the boring parts: idempotent jobs, validated schemas, and a pipeline that can be rerun at 2am without anyone sweating. Half a terabyte of raw broadcast data became structured analytics because the ingestion was built to survive messy sources.
I care about the boring parts because they are what makes the numbers trustworthy downstream: reconciliation checks, retry and rate-limit logic, columnar storage tuned to the actual query pattern, and documentation so the next person can extend it.
Why me
I build the pipes, not just the queries: multi-source ETL that reconciles inconsistent schemas, analytical storage tuned to the query pattern, and ingestion that has not lost a row in production.
I build the pipes, not just the queries. Ingesting multi-source broadcast JSONL with inconsistent schemas, modelling it for analytical workloads, and keeping the pipeline idempotent so a rerun never corrupts a dashboard. 6B+ rows in production ClickHouse at sub-500ms P90.
6B+ rows in production ClickHouse at sub-500ms P90