Skip to main content

SERGIO SÁNCHEZ

v0.4 · Jan 17, 2026 · San Francisco Bay Area

Data Infrastructure Modernization

2022-2026Data EngineeringClient: TalkingPoints
70% cost reduction, near-real-time data freshness

Built from scratch (-ish). Hevo → (a few other things 😬) → Fivetran, Medallion architecture with dbt, CI/CD on GitLab, 70% Snowflake cost reduction.

Technology Stack

SnowflakedbtFivetranGitLab CI/CDMongoDBAWS S3Python

Links

Frequently Asked Questions

What made the Fivetran migration worth the effort?

The old ETL was a maintenance burden that required deep tribal knowledge to debug. When it failed, we had to dig through custom code to understand why. With Fivetran, failures are visible, documented, and usually self-recovering. The time we saved on maintenance went into building things that matter.

How do you approach Snowflake cost optimization without breaking things?

Start with usage patterns, not query plans. Talk to stakeholders about when they actually need fresh data—often the answer is 'not as frequently as we're providing it.' Then work backward to the cheapest architecture that meets real needs.

What would you do differently if starting over?

I'd push harder on stakeholder conversations earlier. We spent time optimizing queries that turned out to be unnecessary once we understood actual usage patterns. The technical work is the easy part—the people work is what determines success.