ITTech Pulse Exclusive Interview with Douglas Gourlay, Chief Executive Officer and President of Qumulo

Douglas Gourlay, CEO and President of Qumulo, in an exclusive interview with ITTech Pulse, shares how enterprises can overcome infrastructure constraints, modernize data architectures, and unlock AI at scale through intelligent data management.

You’ve worn many hats: U.S. Army infantry officer, Cisco executive, Arista VP, and now CEO of Qumulo. What single inflection point in your career most shaped how you lead and make decisions under pressure today?

The Army. Everything after it has been a footnote on the same lesson. As a young infantry officer, you learn very fast that under real pressure you do not rise to the occasion. You sink to the level of your preparation. The romantic version of leadership, the calm genius making a brilliant call in the chaos, is mostly fiction. What actually carries you is the work you did before the pressure arrived: the training, the rehearsals, the relationships, the trust you built with the people next to you.

The second lesson was harder. You almost never get complete information, and waiting for it gets people hurt. In combat, that is literal. In business, it is your market, your team, your window of opportunity. I learned to make the call with roughly 70% confidence, commit fully, and own whatever came back. Most executives I have watched fail, did not fail on strategy. They failed on indecision dressed up as diligence. So the inflection point was not a single moment. It rewired how I think about preparation, speed, and accountability, and I have run every team since in the same way.

Read More: ITTech Pulse Exclusive Interview with Dean Valentine, CEO and Co-founder of ZeroPath

With 70+ patents across networking and systems technologies and leadership stints at Cisco, Arista, and now Qumulo, how do you identify which technical problems are truly worth solving versus those that just generate noise in the industry?

Two filters, and every idea goes through both. First, is the problem real at the level of physics or economics, or is it only real in a marketing deck? A lot of what this industry celebrates solves a vendor’s positioning problem, not a customer’s actual problem. Customers do not lie about their pain. They sometimes confuse the features they want versus what they need. So I do not ask what people want built. I ask what is costing them money, time, or sleep, and I trace it down to the underlying constraint.

Second, does solving it change a cost curve or remove a hard constraint? If a solution makes something ten percent better, that is a feature and the market will forget it. If it makes something ten times better, or removes a constraint people built their entire architecture around, that is worth a career. Patents are a byproduct of asking those questions honestly. They were never the goal. The noise in this business comes from smart people solving problems that do not matter, because the problems that do matter are hard and unglamorous. I would rather be unglamorous and right.

Qumulo’s expanded Microsoft collaboration positions Azure as an immediate escape valve for enterprises trapped in the Silicon Squeeze. How does Azure Native Qumulo help organizations move to the cloud without rearchitecting their existing applications?

Most enterprises do not have a cloud problem. They have an architecture problem, and they have been told those are the same thing. They are not. Migrations stall because the application expects a file system. It expects to open a file, lock it, and write to it the way it has for thirty years. Public cloud object storage does not behave that way, so the standard advice has been to rewrite the application. For thousands of applications that is a multi-year project with a real chance of failure, so people simply do not move.

Azure Native Qumulo removes the premise. It is a real, fully managed file system running natively in Azure that speaks the exact protocols the application already speaks. The application does not know it moved. You point it at the new location, and it runs. That is the whole trick, and it is not a small one. When DRAM and NVMe scarcity turns your hardware refresh into a boardroom fight, you need somewhere to put workloads now, not after an eighteen-month porting project. Azure becomes an immediate release valve because the thing standing between you and the cloud, the rewrite or refactoring, is gone.

SLURP and NeuralProtect address two very different pain points, migration speed and ransomware defense. Were these features born from customer distress signals, and which enterprise segment is driving demand for them most urgently right now?

Every feature we are proud of started as a customer signal, not a brainstorm in a conference room. SLURP came directly from watching migrations crawl. Customers had petabytes sitting on aging hardware, a clear destination, and no realistic way to move the data inside the window they had. Migration speed was the wall everyone hit, so we went after it as a physics problem: how fast can you actually move data once you stop accepting the old assumptions. NeuralProtect came from a darker place. Customers were getting hit by ransomware and discovering that their last line of defense, their data, was exactly what the attacker encrypted. They did not want another alert. They wanted the data itself to be defensible.   Finding out tomorrow you got owned yesterday may drive the valuations of backup companies, but it isn’t pragmatic for real-time businesses.

On who is pulling hardest right now, it is not close. The urgency is concentrated in regulated, data-heavy enterprises: healthcare, financial services, and the public sector. These are the organizations where downtime is measured in lives or lawsuits and where a single ransomware event is existential, not an IT ticket. They are the ones calling, and they are not asking about features. They are asking how fast we can get them protected and migrated. That tells you everything. These were never really feature requests. They were distress signals.

Read More: ITTech Pulse Exclusive Interview with Nicholas Janouskovec Global Cybersecurity Business Development Manager at Emerson

Enterprises are drowning in unstructured data but starving for AI-ready pipelines. How does Qumulo’s zero-copy architecture natively connecting to Microsoft Foundry and Fabric change the economics of AI inference workloads at enterprise scale?

The quiet truth about enterprise AI is that most of the cost and most of the delay are not in the model. They are in the plumbing. Before you ever run inference, you copy data out of where it lives, transform it, land it in some AI-specific store, and keep that copy in sync. You pay for the duplicate storage, you pay for the movement, and you pay in time, which is the expensive one. Every copy is also a new security and governance surface you now have to defend. People badly underestimate how much of their AI budget is just data logistics.

Zero-copy attacks that directly. When the data Qumulo holds connects natively to Microsoft Foundry and Fabric, the AI services operate on the data where it already lives. You are not making a second copy to feed the model. You are not building and babysitting a pipeline whose only job is to shuttle bytes from one place to another. Strip that out and the economics of inference change at the structural level, not at the margin. You shrink the storage footprint, you remove the movement cost, and you collapse the time from data to insight. At small scale this is a nice efficiency. At enterprise scale, where unstructured data is measured in tens to hundreds of petabytes, it is the difference between AI as a science project and AI you can actually afford to run in production.

Global DRAM and NVMe scarcity has turned hardware procurement into a boardroom crisis. Beyond cloud bursting, what architectural principles should enterprise IT leaders adopt today to build storage resilience for a permanently constrained supply chain environment?

Start by accepting the premise, because most IT leaders have not. This shortage is not a spike that will pass. Treat constrained, expensive, and unpredictable supply as the permanent operating condition and design for it. Once you do, a few principles fall out.

First, decouple your software from any specific piece of hardware. If your storage only runs well on one vendor’s drives or one generation of memory, the supply chain owns your roadmap. The architecture should run on whatever silicon you can actually buy this quarter and let you mix generations without a forklift. Second, attack efficiency before you attack capacity. Most enterprises bought performance tiers and headroom they never use, because over-provisioning was cheap. It is not cheap anymore. Getting twice the useful work out of hardware you already own is now a better investment than buying more. Third, treat portability as a first-class property, not a fire escape. A workload should be able to live on premises, in the cloud, or both, and move based on where capacity and economics make sense that month. Cloud Bridging is the tactical version of this. The strategic version is designing so that no single supply source can hold your business hostage. The companies that come through this in good shape will be the ones that stopped treating hardware as a fixed input and started treating it as a variable to engineer around.

As agentic AI matures and data volumes scale exponentially in the second half of 2026, where do you see the biggest convergence happening between enterprise file storage, cloud infrastructure, and real-time AI workloads in the next six months?

The boundary between where data sits and where AI runs will keep dissolving faster than people expect. For decades, storage was a passive bucket. You put data in, you took data out, and the intelligence lived somewhere else. That model is ending. Agentic AI does not want a nightly export of stale data. It wants live, governed access to real enterprise data as it changes, and it wants it now, not after a pipeline catches up. So the storage layer has to become an active participant in the AI workload, not a warehouse the AI occasionally visits.

The specific convergence I would watch over the next six months is the collapse of the gap between the system of record and the system of intelligence. Data gravity wins. It is far cheaper to bring compute to the data than to keep moving petabytes to the compute, so the cloud, the file system, and the inference engine are being forced onto the same operational plane, with governance and security built into that plane rather than bolted on afterward. Whoever makes enterprise data instantly and safely usable by AI, wherever it lives, on premises or across clouds, without copying it around, owns the next phase. Six months is not long, but the direction is already set. The people still pretending storage and AI are separate categories are going to be surprised.

For engineers and IT professionals building careers in enterprise storage, cloud-native infrastructure, or data management today, what’s the one hard-won mindset shift, not a skill or tool, that separates those who lead from those who just execute?

Stop trusting the question you were handed. The single shift that separates the people who lead from the people who execute is the move from optimizing the answer to interrogating the problem. An executor takes the ticket, the spec, the requirement, and does an excellent job delivering exactly what was asked. A leader stops and asks whether the thing being asked for is the right thing at all and is willing to be the person in the room who says the requirement is wrong.

That is uncomfortable, which is why most people avoid it. It is safer to deliver what you were told. But almost every meaningful technical decision I have seen, the ones that actually moved a company, came from someone who refused to accept the premise and traced the problem back to first principles. The skills will change every few years. The tools you are proud of today will be obsolete soon enough. What does not go obsolete is the habit of owning the outcome instead of the task and caring more about whether the problem is worth solving than about whether your piece of it was technically clean. Learn that early and you will lead. Skip it and you will spend a career being very good at building the wrong thing.

Thank you, Douglas, for taking the time to share your insights with us.

Write to us [⁠wasim.a@demandmediaagency.com] to learn more about our exclusive editorial packages and programmes.