Data Engineer at a New York data company from a cold email to the CTO

I'd been applying selectively, only four applications over those two months, because I didn't want to waste time on roles that weren't actually interesting. Most of my search was quiet and slow, and honestly a little discouraging. Then I came across a Substack post by the CTO of a New York data company about their decision to refactor their entire data pipeline around dbt and Snowflake. The post was technical, specific, and honest about the tradeoffs they'd made. It wasn't marketing. It read like someone who actually lived inside the problem, and I recognized a lot of the same pain points from my previous role. I spent a couple of evenings on a cold email. I didn't pitch myself generically. I referenced specific paragraphs from the post and linked a public GitHub repo I'd built for stream-to-batch reconciliation. The repo wasn't perfect, but it was real work: documented, tested, and directly relevant to what he'd described. I figured if he was the kind of engineer who wrote that post, he'd at least look at the code. Three days later he replied. No recruiter, no application portal, no automated acknowledgment. Just a direct response asking if I wanted to jump on a call that week. The process ended up being four rounds over about ↓