Code Story episode
S7 E4: Building in a Crisis: Launching a Zero-Access Data Observability Engine with Yuliia Tkachova, Co-Founder & CEO of Masthead Data
Sep 13, 2022 · Season 7 · Episode 4 · 22 min
No code solution, for catching data errors
Yuliia Tkachova grew up in the Ukraine, but lives in Canada now. She has a family with 2 kids, and a masters in statistics. And, she acknowledges that the war with Russia has been difficult to deal with, thinking of her friends and family back home. On the lighter side, she notes that she loves Depeche Mode and Red Hot Chili Peppers, whom she has seen many times in concert. She recalls the 2010 concert in Kyiv with Depeche Mode was a moment that she cherishes.
As a data product manager, Yuliia was called out, even during the early days of her job, that her customers were going to churn - due to some erroneous data downstream. After fixing this problem, she saw the landscape of data quality issues that were likely to occur with her customers, and wanted to do something about it.
This is the creation story of Masthead Data.
Sponsors
AirbyteDopplerHost.ioIPInfomablLinks
Website: https://mastheadata.com/LinkedIn: https://www.linkedin.com/in/yuliia-tkachova/
Checkout our episode stacks on Stacklist! https://stacks.codestory.co/
Advertising Inquiries: https://redcircle.com/brands
Privacy & Opt-Out: https://redcircle.com/privacy
More episodes
Keep listening
Topics
Explore related conversations
Technical due diligence checklist for startups
A technical due diligence checklist for founders and investors: what reviewers examine across architecture, security, team and process, and how to prepare before a raise.
Fractional CTO vs full-time CTO: which does your startup need?
A practical comparison of a fractional CTO and a full-time CTO: cost, scope, when each makes sense, and the questions to ask before you hire either one.
CTO vs VP of Engineering: how the two roles actually differ
CTO vs VP of Engineering explained: who owns architecture, who owns delivery, when to split the roles, and how to avoid the overlap that breaks engineering teams.