Big data at enterprise scale
Daily work with SQL and Python over Snowflake, AWS and Databricks — measurement, troubleshooting and custom reporting on datasets belonging to Fortune 500 accounts, not tutorial-sized samples.
Practice 04
Scattered exports turned into dashboards and scheduled reporting — with the metric definitions agreed before the first chart is drawn, and the queries handed over so anyone can check the work.
Scope agreed in writing before work begins.
The problem
The most expensive meeting in any company is the one that starts by arguing about whose number is right. It usually happens because nobody ever wrote down what the metric means — does a sale count when it is invoiced, when it is paid, or when it ships?
Tooling does not fix that. Definitions do. The dashboard is the last step, not the first, and it is only as trustworthy as the agreement underneath it.
Scope
Stated before you ask, so the first call is about your problem rather than about what we do or do not cover.
How it runs
Before any tooling: what each metric means, which source is authoritative, and who signs off when they disagree.
Pipelines that pull, clean and reconcile automatically, so the reconciliation stops being somebody's Friday.
One dashboard people open daily beats twelve nobody remembers. We start with the decisions you actually make each week.
Every number comes with the query that produced it. If we disappear tomorrow, your team can still audit and extend the work.
Track record
Daily work with SQL and Python over Snowflake, AWS and Databricks — measurement, troubleshooting and custom reporting on datasets belonging to Fortune 500 accounts, not tutorial-sized samples.
Campaign measurement work assessed against IAB and MRC standards, covering viewability, invalid traffic and suitability. When a metric has to survive external scrutiny, the definition matters more than the chart.
Certified in Databases for Data Scientists (University of Colorado Boulder) and Python (Pontificia Universidad Católica de Chile), on top of a Mechatronics engineering degree.
The team's data engineering builds the layer under the dashboard: orchestrated pipelines (Apache Airflow), a warehouse modelled with Snowflake and dbt, and the business intelligence on top — so the numbers stay reliable and refresh without someone rebuilding them by hand each week.
Questions
Whatever your team already has a licence for and knows how to use. If there is nothing in place, a lightweight web dashboard you own outright avoids adding a subscription to maintain.
No — that is part of the work. Messy data is the normal starting point, and the cleaning rules get documented so the mess does not silently come back.
Yes, within what the data can actually support. Where the sample or the collection method does not justify a conclusion, you will be told that instead of being handed a confident chart.
Automation is about removing manual work from a process you already understand. This practice is about making the numbers themselves trustworthy. They pair well, and the assessment tells you which one should come first.
Start here
Describe the problem in a few lines. You get a written reply with a first read on it, whether or not there is an engagement in it. The message is sent from this page — no email client, no third-party form service, no trackers.