Read Maloney Learned to Sell the Cloud. Now He’s Betting the Dashboard Is Finished

Read Maloney has spent much of his working life making strange new machinery sound sensible. First came the literal machinery: a mechanical engineering degree from Duke, followed by statistical analysis at Honeywell. Then came institutions, including the United States Marine Corps, where he served as a captain and completed two tours in Iraq as a platoon commander. Finally came the invisible machinery that modern companies rent by the hour: cloud computing, machine learning, data lakehouses, and now AI agents. His title is chief marketing officer. His recurring subject is friction.

At Dremio, where Maloney became CMO in September 2022, friction has many aliases. It is the analyst waiting for an engineer. It is the pipeline nobody remembers building. It is the second copy of a dataset made to rescue the first copy from poor performance. It is the dashboard whose key metric carries one definition in finance and another in sales. Dremio sells a data lakehouse platform, but Maloney’s public argument is easier to understand than the category name: businesses should reach trustworthy answers without dragging their data through a Rube Goldberg machine.

This is a marketer’s proposition delivered with an engineer’s dislike of unnecessary parts. It is also the thread that connects a career moving through AWS, Oracle, H2O.ai, and Dremio. Each stop put Maloney near a technology that needed translation before it could become ordinary. Cloud infrastructure once sounded reckless. Enterprise machine learning sounded occult. A table format called Apache Iceberg still sounds, to the uninitiated, like a maritime hazard. Maloney’s job has been to explain why any of it matters before the jargon eats the room.

An engineer learns the category business

Maloney graduated from Duke in 2003 with a B.S.E. in mechanical engineering. He became a Marine captain, led platoons during two deployments to Iraq, and was near Fallujah by November 2004. Years later, when he returned to civilian work, Honeywell gave him a bridge back to his technical training through data analysis and advanced statistics.

Then came business school. From 2008 to 2010, he studied at the University of Washington’s Foster School of Business, concentrating in marketing. The pairing looks unusually neat in retrospect: engineering supplied a way to take systems apart, while marketing supplied a way to make other people care when he put them back together.

AWS hired him as a product marketer in 2010. The timing matters. Amazon had launched its first foundational web services only a few years earlier, and “the cloud” was still a concept that buyers could reasonably mistrust. Maloney later built the company’s digital marketing team. At Oracle, he led North American marketing for cloud infrastructure and product marketing for cloud data warehousing and data science. At H2O.ai, beginning in 2020, he served as senior vice president of marketing and led the function for a company selling enterprise machine learning.

This was not a career of hopping between unrelated acronyms. It followed computing’s center of gravity: from renting infrastructure, to organizing vast stores of data, to training models on that data, to asking agents to reason over it. Maloney kept turning up where the technical possibility was a few persuasive explanations ahead of widespread comfort.

“The increased complexity and costs are taking engineers away from the more important things.”Read Maloney on the burden of data operations

The plumbing is the plot

Watch Maloney in a technical webinar and a pattern appears. He starts with an organizational complaint, not a feature. The business wants faster access. The central data team wants security and governance. Analysts need a new dataset, so a ticket begins its little pilgrimage through engineering. Meanwhile, warehouses, extracts, transformation jobs, and materialized copies accumulate like extension cords behind a television.

His favorite villain is not a rival logo. It is delay. He uses “mean time to insight,” a phrase with the antiseptic charm of an airport sign, to describe the distance between having a question and receiving an answer. Dremio’s pitch is that companies can query data closer to where it lives, expose it through a shared semantic layer, and avoid some of the copying and pipeline work that makes every change cascade through the system.

There is a humane point buried in the architecture. Maloney has said that complexity keeps engineers from higher-value work and leaves them “shoveling data all day long.” The phrase works because it makes digital labor physical. One can almost see the wheelbarrow. His story about better architecture is ultimately a story about what skilled people should not have to spend Tuesday afternoon fixing.

He does not always speak like a white paper. At an AWS re:Invent gathering, interviewer Ravit Jain asked Maloney how he pronounced “data.” Dremio later revived the clip, and the comments settled on a durable standard: if the pronunciation was good enough for Lieutenant Commander Data in Star Trek, it was good enough for them. Maloney’s 2026 essay “The Dashboard is Dead” ends with a section titled “Aiiiiiiight” and the line, “Good luck, you won’t need it.” Enterprise software can survive a joke. It may even benefit from one.

Why openness became a business argument

Maloney’s most consistent technical allegiance is to open architecture, particularly Apache Iceberg, the table format that lets different systems work with the same underlying data. Formats rarely inspire affection outside their committees. Iceberg matters because it is a defense against lock-in: a company can keep data in an open form and choose among compatible engines and tools rather than accepting one vendor’s entire menu forever.

When competing platforms began rallying around Iceberg, Maloney called it “go time” for the community. By 2026, he was declaring that Iceberg had won the table-format contest and turning to the next problem: the operational “management tax” of keeping an open lakehouse fast and healthy. Victory, in enterprise infrastructure, merely earns you a more interesting queue of chores.

After the dashboard

In April 2026, Maloney published his bluntest thesis: “The Dashboard is Dead.” The provocation was based on Dremio’s own use of AI agents to explore company data. A dashboard answers the questions its designer predicted. An agent can accept a fresh question, generate the query, return an answer, and take a follow-up. The interface shifts from a set of gauges to something closer to a conversation.

Maloney’s longer record adds the necessary caution. In discussions of generative AI, he repeatedly returns to data quality, governance, provenance, and the places where a human belongs in the loop. He saw machine-learning models at H2O.ai fail to reach production because teams built without first securing the business requirement. The fashionable model was not the missing ingredient. Context was.

This makes his dashboard obituary less reckless than its title. The bet is not that a chatbot sprinkled over bad data will rescue the enterprise. It is that agents become useful when the foundation is open, governed, current, and semantically coherent. If finance and sales disagree about the definition of revenue, a fluent AI will only make the disagreement faster.

“Data quality becomes an even bigger focal point.”Read Maloney on AI and the lakehouse

A bigger roof for the lakehouse

The corporate setting changed in July 2026, when SAP completed its acquisition of Dremio. The deal brought Dremio’s open, Iceberg-native platform into the orbit of SAP Business Data Cloud, where the ambition is to combine SAP and non-SAP information for analytics and AI without demanding another round of data movement and conversion.

For Maloney, it is an unusually tidy convergence of the themes he has spent years explaining: enterprise data, open formats, shared business context, and agents. It also creates the classic acquired-company challenge. A message built around openness must stay credible inside a much larger software institution. The standard cannot merely be open in the brochure. Customers will measure it by interoperability, control, and the freedom to keep using tools SAP did not invent.

Maloney’s career offers no evidence that he intends to become quieter. His writing in 2026 grew more direct, not less. Dashboards were declared dead. Iceberg was declared victorious. Beneath the declarations, though, the operating philosophy remained practical: own the data, reduce the plumbing, define the metrics, keep judgment where it belongs, and let more people ask useful questions.

The cloud became normal partly because its evangelists learned to stop describing servers and start describing what a company could do without buying them. Agentic analytics will face the same test. Maloney has arrived once again at a technical threshold, translating between the people building the machinery and the people who simply want Tuesday’s answer before Friday. The dashboard may not vanish on schedule. But it has, at last, acquired an articulate undertaker.