Water utility
A city's water utility serves half a million people. It works not because of one genius at the top, but because three kinds of professionals keep it running — and they each do something different with the same water.
Water utility · the civil engineer
The civil engineer designs and architects the water infrastructure for the whole city. She makes sure that everything is properly connected and the joints don't leak. The civil engineer builds the connections from source to treatment plants to basins — and on to the consumers.
Data world · the data engineer
The data engineer has the same job, but in data. The reservoir becomes a database. The treatment plant becomes a transformation step. The pipe becomes a pipeline. A Data Engineer designs and builds the infrastructure that data flows through.
What this means
A Data Engineer builds and runs the plumbing of the data world — the databases that store data and the pipelines that move and clean it. When a dashboard loads slowly, or last night's refresh fails and Monday's report still shows Friday's numbers, that's theirs to fix.
Works with: databases, pipelines, cloud platforms, code. Delivers: reliable, well-structured data everyone else builds on.
Water utility · the analyst
The water analyst is interested in what's in the water — except the water. Are there poisonous heavy metals? Any malign bacteria? What's the temperature and acidity? This is important to comply with regulations, but it also helps to detect anything possibly leaking into the water.
Data world · the data analyst
Same routine, in data. The water becomes a data sample. The analysis of the water becomes an accuracy metric. The regulations become quality targets. A Data Analyst takes the data the Engineer orchestrates and examines it to turn it into answers and insights.
What this means
A Data Analyst can give business answers based on the data provided by the engineer. "Which region had the strongest quarter?" "Why did costs jump 12% in November?" — the analyst investigates and reports back in charts a non-specialist can act on. Their dashboards are usually the most visible thing the data team produces: it's what leadership actually reads.
Works with: SQL, spreadsheets, dashboards. Delivers: clear answers about what's happening right now.
Water utility · the hydrologist
The hydrologist's job is to make forecasts for the future. Rainfall, of course — but also predictions like: what happens to groundwater levels if consumption increases by 10% over the next five years? These forecasts help the whole city to act before it's too late.
Data world · the data scientist
Same job, different topics. The rainfall becomes sales. The groundwater level becomes brand awareness. The Data Scientist takes the long view and tells the rest of the business what's likely to happen.
What this means
Where the analyst describes what is happening, a Data Scientist asks why — and what happens next. They build predictive models: which customers will cancel next quarter, how revenue is affected by a change in prices. The work is experimental and can be wrong, but when it lands it lets the business act before events unfold instead of reacting after.
Works with: large datasets, statistics, machine learning. Delivers: predictions and patterns no report would reveal.
Together
None of them can do their job without the other two. The Engineer builds, the Analyst explains, the Scientist predicts. The arrows close into a continuous cycle — and that cycle is what turns raw information into a decision someone can act on.