Rajiv Ramaswami: The Quiet Force Behind One of Tech's Greatest Comebacks

In September 2020, Rajiv Ramaswami became CEO of Nutanix without having met most of the people he would now be leading. The pandemic had seen to that. The interviews, the negotiation, the handover from the founder: all of it had happened over video calls. The company he was inheriting was burning more than $200 million a year in cash, and had already raised a significant $750 million from Bain Capital. And Dheeraj Pandey, the founder who had built Nutanix from nothing into a publicly traded enterprise, was on his way out.

"I walked into a turnaround," Ramaswami recalled. "The company had strong technology, good products, and a strong reputation for innovation. But the business had stalled, and it needed to be taken to the next level."

What is striking, in retrospect, is that this did not appear to unsettle him especially. Not because the situation was not serious, but because Ramaswami had been here before. Over a career spanning IBM research laboratories, a dot-com collapse, and a gutted division at Cisco, he had developed a specific and unusual competence: the ability to do the unglamorous work after the excitement has left the room. He is not a founder. He is not a visionary in the sense the term is typically used in technology circles. He is something rarer and, in certain situations, considerably more useful - stable, strong, and grounded.

The Formation

Ramaswami grew up in India at a time when the paths available to a high-achieving student were narrower than they are today. His mother was a senior government officer, and the household took education seriously as a matter of course. "In the environment I grew up in," he explained, "education was one of the central pillars of family life. There was always a strong sense that academic discipline mattered, that doing well in studies mattered, and that education was the foundation for what came next in life."

He was not, he was at pains to clarify, one of those precocious children who dismantled household appliances for the pleasure of understanding how they worked. His gifts were more structural: he liked logic, systems, the feeling of grasping a principle rather than memorising a fact. Biology, with its dissection laboratories and its premium on rote retention, was never going to hold him. He moved towards physics, then towards engineering, less from passion than from the honest recognition that it was where his mind worked best.

In 1982, he gained admission to the Indian Institute of Technology Delhi. He chose electrical engineering over computer science, a choice he might not repeat today, but one that, by the second year of his undergraduate studies, led him to a pair of courses in communications and information theory that changed something in him.

"Those courses really fascinated me," he said with a certain warmth. "They opened up a whole way of thinking about how information moves, how communication happens, how systems are designed to carry signals. The field was intellectually beautiful in a way that appealed to me. It combined logic, mathematics, real-world applications, and systems thinking."

He graduated in 1986. The options for a young engineer in India at that time were limited: a government posting, a management degree, or graduate study abroad. He had been offered a job at Indian Telephone Industries and found it uninspiring. He had been admitted to the University of California, Berkeley, on a full fellowship. The decision, he noted, was straightforward.

The Research Years

Berkeley led to a PhD in optical communications, specifically fibre optics, which he completed in 1990. The timing was fortunate. Fibre optics was an emerging field in the late 1980s, and emerging fields carry a particular intellectual generosity. "If you enter a field when it is just beginning to expand in importance," Ramaswami observed, "there is often a tremendous amount of open space. There are many important questions to answer, many systems to build, and many ideas that have not yet become settled."

After Berkeley, he joined IBM's TJ Watson Research Centre, one of the storied American industrial laboratories of the twentieth century, where he spent the better part of nine years doing something that has become increasingly rare in the technology industry: actual research. He wrote papers, filed patents, and worked on the architecture of high-performance communication networks.

"A lot of the work was around how to architect and engineer very high-performance communication systems," he explained. "These were complex systems problems. You had to think not only about individual components, but about how the whole system would function reliably and efficiently."

The shift from researcher to builder came in 1994, when he led a small team that produced one of the first commercial fibre-optic systems in the industry. He described that moment as a turning point in how he thought about his work.

"Once you take an idea and turn it into an actual product, your mindset changes," he said. "The question is no longer only whether something is elegant or theoretically sound. Now you also have to think about whether it can be built, delivered, adopted, and used in the real world." That reorientation, from the beauty of a problem to the utility of its solution, has defined his approach ever since.

The Crash

By the late 1990s, optical networking had become one of the hottest sectors in technology. Ramaswami moved his family from the East Coast to Silicon Valley and joined a startup in the same space as employee number three. "You could feel that the industry was moving quickly," he recalled, "and there was a sense of possibility everywhere." In 2000, the company was acquired by Nortel, then one of the world's largest telecommunications companies, for around three billion dollars.

Then the bottom fell out. The telecom collapse of 2001 and 2002 was not a correction. It was an extinction event. Nortel, which had paid approximately $3 billion for the startup, shut down the division. Then, in time, Nortel itself ceased to exist. Ramaswami was laid off in 2002. He was, he noted, financially secure. He took six months off and spent the time with his small children. "In hindsight," he said, "I value that period a lot."

He did not narrate this episode as a defining wound. What it produced, he explained, was a permanent recalibration of how he thought about momentum and markets.

"When industries are booming, it is easy for everyone inside them to start believing the momentum is permanent," he said. "Then the crash came and exposed how fragile some of that really was. It taught me that markets can turn very quickly and that leadership has to be built for both upcycles and downcycles." That lesson, absorbed at some cost, stayed with him through everything that followed.

Learning to Run a Business

After a period of recruitment from Cisco, Ramaswami joined the company in 2003 to run a business unit that had once generated over a billion dollars in revenue but, by the time he arrived, had contracted to around two hundred million. The team was roughly two thousand people, assembled from several acquired companies that had never been properly integrated. Much of the original customer base had disappeared in the aftermath of the dot-com collapse.

"I walked into a situation where I had to restructure, consolidate, cut back where necessary, and then rebuild," he said. "It meant making hard calls. We had to lay off people, shut down products, simplify operations, and then go out and win new business. It was a trial by fire." He described the experience of making large-scale redundancies not as a strategic exercise but as something that demands a specific kind of moral seriousness. "Laying people off forces a kind of maturity on you," he added. "You have to become very clear about what is essential and what is not, and you have to be willing to live with those decisions."

The deeper lesson, though, came from a discomfort that arrived slightly later, as he moved into successive general manager roles in domains where he was no longer the most technically expert person in the room. "That triggered insecurity in me," he admitted. "I wondered whether I could really succeed if I was not the expert. I had this sense that perhaps I would not be able to do the job well because I did not know the area deeply enough."

What he came to understand instead was a different theory of leadership, one organised less around personal mastery and more around the capacity to create it in others. "I learned that I did not need to know everything," he said. "I needed to create a team that knew what it was doing, trust them, and then guide the business with judgment. Once that clicked, I became much more comfortable operating across different domains." It is a formulation he returned to often, and it had the quality of something tested rather than borrowed.

The Nutanix Transition

After Cisco, Ramaswami spent eight years at Broadcom and nearly five at VMware, where he served as chief operating officer. By the time the Nutanix opportunity arrived, he was not stepping into senior leadership for the first time. He had seen different company dynamics, managed large teams, and navigated the particular difficulties of operating inside organisations that were themselves in transition.

Nutanix was founded in 2009 by Dheeraj Pandey, whose engineering instincts had produced a genuinely important piece of infrastructure software: a hyperconverged platform that simplified the architecture of enterprise data centres. The company went public in 2016 and grew quickly. It had also, by the time Ramaswami arrived, accumulated the kinds of structural problems that fast growth without financial discipline tends to produce.

The business model needed to shift from selling hardware and perpetual software licences to a subscription model, which is one of the most difficult transitions a mature technology company can make. It requires accepting lower revenues today in exchange for more predictable revenues tomorrow, and it demands a level of organisational patience that is genuinely hard to sustain.

The founder-to-professional-CEO handover carried its own weight. Pandey was a charismatic and deeply respected figure inside the company. Ramaswami understood that his authority could not be built on that kind of personal mythology. It would have to come from somewhere else entirely.

His approach to the cultural question was deliberate. The company's existing values, expressed as humble, honest, hungry, with heart, he found genuinely compelling and left entirely intact.

"I embraced it fully, and to this day we have not changed it," he said. "There was no need to." What needed to change, he concluded, was not what the company believed but how it operated day to day. "A founder-led culture can result in many parts of the company moving in different directions at once," he explained. "Different product leaders push their own priorities. Functions optimise for themselves. A lot gets tried at the same time. That may be manageable at an earlier stage. Once a company is public and needs to scale with discipline, that model becomes much harder to sustain."

The intervention he described was less dramatic than most turnaround narratives are. There were no theatrical restructurings, no all-hands speeches designed to signal a new era. What he introduced was alignment: clear company-level priorities, a consistent set of bets, and the operational discipline to pursue them. "What was encouraging," he recalled, "was that the organisation welcomed this. There was no major resistance. In fact, people felt the need for it. They knew the company had strong foundations but had lost some focus."

Nutanix returned to profitability on a non-GAAP basis in fiscal year 2023. The company's annual recurring revenue has grown consistently. Ramaswami did not allow himself to be particularly congratulatory about any of this.

The Intelligence Question

When the conversation turned to artificial intelligence, Ramaswami became slightly more animated than his usual deliberate cadence. He had a framework he believed in, and he laid it out with the systematic clarity of someone who had spent time getting it straight in his own mind.

"AI is one of the most important disruptive forces in technology today," he said, "and I think companies have to embrace it. If you do not embrace it, you are putting yourself at a competitive disadvantage. I also do not think fear is the right response. The right response is active engagement, disciplined experimentation, and figuring out how it changes your business, your products, and your internal operations."

He organised his thinking into three categories: AI on Nutanix, AI at Nutanix, and AI in Nutanix. The first referred to the external business opportunity created by a new class of AI applications that enterprises would need infrastructure to run. The second was about using AI internally to improve how the company itself operated. The third was about embedding AI capabilities into Nutanix's products to make them more useful to customers.

On the internal question, he was notably concrete. "In engineering, coding tools have already changed how our teams work," he said. "I would estimate that we have already gotten something like twenty per cent more productivity from our existing engineering base, and I expect that to improve further over time."

Customer support was another area where he pointed to measurable improvements already visible, with faster case triage and reduced time to resolution. He was equally candid about where the work remained incomplete. "I believe AI can dramatically improve productivity in go-to-market, sales, and marketing as well," he added. "That is an area where we want to do more." The phrasing was deliberate. Ramaswami did not claim ground he had not yet taken.

What he looks for

There is a version of Rajiv Ramaswami that is easy to underestimate. He does not trade in the language of disruption. He does not speak in the sweeping register that technology culture tends to reward. He is precise where others are expansive, and he qualifies his statements in ways that can, in a culture that prizes conviction, read as a kind of diffidence.

It is not diffidence. It is something closer to the habit of a man who has watched enough cycles of excess and correction to be permanently sceptical of certainty. When he talked about what he looked for in the people he hired, the qualities he named were not brilliance or boldness. They were hunger and integrity.

"I like people who are driven, people who want to do more, people who work hard and have ambition and energy," he said. "Raw drive is often what separates people who simply do a job from people who can grow into something much bigger." And then, with equal weight: "Integrity matters enormously. There is no substitute for ethics. People have to operate with honesty, with sound values, and with a sense of responsibility."

The advice he offered to leaders in technology had the quality of something distilled over a long time from repeated experience. It was not fashionable advice. It did not promise leverage, velocity, or the kind of asymmetric returns that technology culture treats as the only interesting outcome.

"The biggest advice is that you cannot rest," he said. "Technology changes constantly. Markets shift. Competitive dynamics shift. New platforms emerge. Customer expectations evolve. What worked a few years ago may not work now, and what works now may not work a few years from today." He considered this for a moment. "If you stop moving, you do not remain where you are. You effectively fall behind."

He said this without urgency. It was, for him, simply a description of conditions: the terrain that exists and must be navigated, without the comfort of wishing it were otherwise. The competition was continuing. New platforms were emerging. Rajiv Ramaswami was not particularly worried. He had been here before, in one form or another, and he knew what the work required. He kept moving.