Ben Rogojan (Seattle Data Guy)

Founder & Lead Consultant, Seattle Data Guy · 1 appearance on the record.

computed by AI from the episodes · how this works → · full disclaimer →

engineerfounderauthorother@seattledataguy ↗LinkedIn ↗theseattledataguy.com ↗

Ben Rogojan is an independent consultant advising companies on cloud data infrastructure, data modeling, and modern data stack tooling, having previously worked as a data engineer at Facebook (Meta). Operating under the pseudonym "Seattle Data Guy," he produces widely read educational content, courses, and technical commentary across Substack and YouTube.

24statements → 12claims → 2claims resolved → 3.38/5average certainty → 2.12/5average debate potential → 4.3/5argument clarity · the sources →

2 supported 0 partly supported 0 contradicted 10 not checkable as stated how the 12 claims stand · each chip opens the sources

7 predictions · 5 assertions · 5 opinions · 7 insights · every statement was checked. The predictions and assertions are the 12 claims: statements the public record can support or contradict. 2 are resolved, and 10 name no date, number or outcome precise enough to check. Everything else (opinions, insights, what ifs, disclosures) can never be settled by the record, so it carries no assessment.

The record, in short

What the tape says about how Ben argues and how the claims held up. Everything they said, and everything said about them, is in the tabs below.

Their most notable supported claim

Assertion Supported
Riot Games deployed machine learning models using Apache Airflow
“One of the teams at Riot Games was like deploying their ML models and they were using Airflow.”
Ben Rogojan (Seattle Data Guy) Jan 23, 2025 ▶ 8:50 Understanding Data Engineering in 2025 | Ben Rogojan, Seattle Data Guy

Argument clarity: do they answer the question? how? →

4.3 / 5 directness 4.7 · coherence 4.4 · precision 4.2 · compression 3.6

redirected or did not address 1 of 16 assessed questions (6%). Watch them ▸

This is a score against a rubric. It is not a rank. Every host question → answer exchange is scored with names hidden on directness, coherence, precision and compression, 1–5 each, on meaning alone: disfluencies are ignored, and only raw unedited episodes count. This is the score that measures thought. Every scored exchange, scores shown → · The rubric and its checks →

How they sound: speaking style how? →

312 words/min while actually speaking · 32 um and uh per 1k words

Measured by listening to the audio itself: 11,142 words across 1 episode of raw-level tape, transcribed verbatim with every um and uh kept, each one attributed only where the alignment onto our timed stream is unambiguous. These are measurements of speaking style. We do not rank them: across this corpus, fluency and argument quality are nearly uncorrelated (ρ≈0.2), and smooth talking does not signal clear thinking. How it's measured →

Everything Ben Rogojan (Seattle Data Guy) said on the MAD Podcast that made the record, most notable first. Filter by type, assessment or year in the ledger →

Prediction Not checkable as stated
Rogojan: Apache Iceberg is becoming the de facto open table format standard
“Iceberg as the de facto, like if we're going to use an open, open table format, that's going to be likely the one people will, I assume, pick since everyone's now supporting it, right?”
Ben Rogojan (Seattle Data Guy) Jan 23, 2025 ▶ 39:14 Understanding Data Engineering in 2025 | Ben Rogojan, Seattle Data Guy
Prediction Not checkable as stated
Rogojan: SQL will remain essential as LLM raw data-dumping approaches fail
“The next one I said SQL isn't going anywhere, and I kind of said that for more than one reason. One, I feel like someone's going to tell us it's time to revamp data lake v one again, where we'll just dump everything in there and we'll let an LLM figure it out …”
Ben Rogojan (Seattle Data Guy) Jan 23, 2025 ▶ 51:39 Understanding Data Engineering in 2025 | Ben Rogojan, Seattle Data Guy
Insight
Ben Rogojan: Data teams bear primary responsibility for bridging business communication gaps
“I think in general, I found that if you're the data team, you're going to probably have to do a little more of the lift just because it's, Maybe a little easier for you to make that leap.”
Ben Rogojan (Seattle Data Guy) Jan 23, 2025 ▶ 27:51 Understanding Data Engineering in 2025 | Ben Rogojan, Seattle Data Guy
Prediction Not checkable as stated
Rogojan: Fully replacing data engineers with AI is still years away
“So I think we're a few years away from just like replacing data engineers, which has been the goal for what it feels like a decade or plus now.”
Ben Rogojan (Seattle Data Guy) Jan 23, 2025 ▶ 32:00 Understanding Data Engineering in 2025 | Ben Rogojan, Seattle Data Guy
Insight
Rogojan: Databricks and Snowflake are fighting for workflows, not contract lock-in
“It's really been a white fight for workflows versus a fight for like contracts. Cause in the past it was like, okay, you sign a ten million dollar contract for Teradata. You're kind of stuck with it, right? Like there's no choice now for the next three to five…”
Ben Rogojan (Seattle Data Guy) Jan 23, 2025 ▶ 41:45 Understanding Data Engineering in 2025 | Ben Rogojan, Seattle Data Guy
Opinion
Rogojan: Databricks is better suited for machine learning than data warehousing
“I think Databricks makes sense to me still more from an ML standpoint. I know they like the data warehousing side. I know they, that's where they're going to pitch themselves”
Ben Rogojan (Seattle Data Guy) Jan 23, 2025 ▶ 49:14 Understanding Data Engineering in 2025 | Ben Rogojan, Seattle Data Guy
Prediction Not checkable as stated
Ben Rogojan: Natural language-to-SQL AI will not take over anytime soon
“I don't think we're going to see that take over anytime soon, unless you have your data in such a well-formatted way that, like, yeah, of course it's easy to do.”
Ben Rogojan (Seattle Data Guy) Jan 23, 2025 ▶ 53:12 Understanding Data Engineering in 2025 | Ben Rogojan, Seattle Data Guy
Insight
Rogojan: Organizations repeat foundational data mistakes in every AI hype cycle
“People Kind of go through the same iterations. New people come to the space or possibly maybe it's more the business side get really excited by the prospect of what AI or data science or neural networks, whatever iteration we're in can do. And then we kind of …”
Ben Rogojan (Seattle Data Guy) Jan 23, 2025 ▶ 1:34 Understanding Data Engineering in 2025 | Ben Rogojan, Seattle Data Guy
Assertion Not checkable as stated
Ben Rogojan observed ML engineers at Facebook accessing data directly from warehouses
“Some companies do have maybe the ML engineers access data more directly from maybe the data warehouse, which was things I saw like at Facebook.”
Ben Rogojan (Seattle Data Guy) Jan 23, 2025 ▶ 8:29 Understanding Data Engineering in 2025 | Ben Rogojan, Seattle Data Guy
Insight
Ben Rogojan: Non-Big Tech data engineers must manage their own pipeline tooling
“At Facebook, you essentially have your internal airflow that a different team runs, and you can just push files to it and it picks up the data pipelines, you know, automatically. Whereas in most other companies, you might be the person that has to even manage,…”
Ben Rogojan (Seattle Data Guy) Jan 23, 2025 ▶ 13:55 Understanding Data Engineering in 2025 | Ben Rogojan, Seattle Data Guy
Insight
Rogojan: Understanding data flow takes longer than learning SQL syntax
“SQL you can learn quickly. What's going to take time is just getting a sense for how data Operates and flows and data sets in general.”
Ben Rogojan (Seattle Data Guy) Jan 23, 2025 ▶ 18:50 Understanding Data Engineering in 2025 | Ben Rogojan, Seattle Data Guy
Prediction Not checkable as stated
Rogojan: Enterprise migration away from Spark and Kafka will take years
“I think initially just picking up Kafka, Spark, those are still so heavily in use that even if they go out in the next three to five years, it's going to take time to migrate and things of that nature.”
Ben Rogojan (Seattle Data Guy) Jan 23, 2025 ▶ 22:06 Understanding Data Engineering in 2025 | Ben Rogojan, Seattle Data Guy
Insight
Ben Rogojan: API connections are usually the hardest part of data extraction
“Cause that's usually the big thing. It's like the API connection tends to be the one that is the hardest.”
Ben Rogojan (Seattle Data Guy) Jan 23, 2025 ▶ 33:38 Understanding Data Engineering in 2025 | Ben Rogojan, Seattle Data Guy
Opinion
Rogojan blames excessive VC funding for the bloated data engineering tool ecosystem
“I think the reason you see so many tools is like, I mean, VC funding was pretty high, so you can blame yourselves.”
Ben Rogojan (Seattle Data Guy) Jan 23, 2025 ▶ 36:33 Understanding Data Engineering in 2025 | Ben Rogojan, Seattle Data Guy
Opinion
Rogojan: Snowflake is difficult to beat for lean, resource-constrained data teams
“Snowflake makes it really easy, and I'd say BigQuery does too, but Snowflake makes it really easy. Like, if you do not have a ton of people to manage things, I think it's hard to go against it.”
Ben Rogojan (Seattle Data Guy) Jan 23, 2025 ▶ 49:01 Understanding Data Engineering in 2025 | Ben Rogojan, Seattle Data Guy
Prediction Not checkable as stated
Rogojan: Companies will keep chasing data holy grails like self-service analytics
“I think we'll continue chasing the same holy grails. I feel like we want to see new things, but I think We're still trying to figure out some things like self-service analytics or some of the other holy grails, like even being like data driven kind of feels li…”
Ben Rogojan (Seattle Data Guy) Jan 23, 2025 ▶ 55:07 Understanding Data Engineering in 2025 | Ben Rogojan, Seattle Data Guy
Insight
Rogojan: Data teams get trampled by fickle business demands without strong leaders
“If you don't have a strong data leader that can either push back or make sure that you're doing things in a way that makes sense you kind of can get trampled by the business side and what they need and their kind of fickle nature where it's like, okay, now we'…”
Ben Rogojan (Seattle Data Guy) Jan 23, 2025 ▶ 58:05 Understanding Data Engineering in 2025 | Ben Rogojan, Seattle Data Guy
Prediction Not checkable as stated
Rogojan predicts a rise in vertical-specific data solutions for domain data
“Yeah, I think we'll probably start seeing some vertical specific data solutions come out whether that's like tooling or maybe just one example I gave in, in my article was like Tuva Health, which is trying to make it easier to just standardize healthcare speci…”
Ben Rogojan (Seattle Data Guy) Jan 23, 2025 ▶ 58:31 Understanding Data Engineering in 2025 | Ben Rogojan, Seattle Data Guy
Assertion Supported
Riot Games deployed machine learning models using Apache Airflow
“One of the teams at Riot Games was like deploying their ML models and they were using Airflow.”
Ben Rogojan (Seattle Data Guy) Jan 23, 2025 ▶ 8:50 Understanding Data Engineering in 2025 | Ben Rogojan, Seattle Data Guy
Assertion Not checkable as stated
Ben Rogojan: Most data engineers transition laterally from analyst or developer roles
“I see a lot of people move laterally into data engineering, often from either data analyst or software engineer. Data analyst, because I think there's just the sheer quantity of data analytics jobs are More.”
Ben Rogojan (Seattle Data Guy) Jan 23, 2025 ▶ 15:47 Understanding Data Engineering in 2025 | Ben Rogojan, Seattle Data Guy
Opinion
Rogojan prefers AWS and GCP due to Azure usability issues
“I have my own qualms with Azure every time I use it. So I just like AWS and GCP slightly better.”
Ben Rogojan (Seattle Data Guy) Jan 23, 2025 ▶ 21:39 Understanding Data Engineering in 2025 | Ben Rogojan, Seattle Data Guy
Assertion Supported
Rogojan: Legacy data software like Informatica cost six to seven figures
“Before it's like, okay, you want Informatica, you know, let's talk six, seven figures in, in contract costs.”
Ben Rogojan (Seattle Data Guy) Jan 23, 2025 ▶ 35:33 Understanding Data Engineering in 2025 | Ben Rogojan, Seattle Data Guy
Opinion
Ben Rogojan is not a fan of Amazon Redshift
“Not a big Redshift fan.”
Ben Rogojan (Seattle Data Guy) Jan 23, 2025 ▶ 43:14 Understanding Data Engineering in 2025 | Ben Rogojan, Seattle Data Guy
Assertion Not checkable as stated
Ben Rogojan: Data type issues still routinely break data pipelines
“But to this day, people are still having like a data type issue break a pipeline that then causes everyone to have to kind of spend a little bit of time fixing them.”
Ben Rogojan (Seattle Data Guy) Jan 23, 2025 ▶ 12:49 Understanding Data Engineering in 2025 | Ben Rogojan, Seattle Data Guy

Appearances (1)

EpisodeDateSpeaking time
Understanding Data Engineering in 2025 | Ben Rogojan, Seattle Data Guy Jan 23, 2025 44m
Made with StarZero

Turn any episode into a week of clips.

This entire site, over 400 conversations transcribed, diarized, checked and made playable, runs on the StarZero media pipeline. Drop in your own episode and the podcast clipper finds the moments worth sharing, cuts them, captions them, and reframes them for every feed.