The Engineer Who Stays in the Plumbing
Most technology executives talk about transformation. Ashok Shivarudraiah writes the patents that make transformation possible. His LinkedIn handle is @ashivaru - economical, memorable, engineered. Like everything else he builds.
He describes himself, in exactly the right order, as "Dad, Hacker, and Entrepreneur." The order matters. In an industry that reverses those priorities without noticing, Ashok keeps the list honest.
After six years helping Salesforce build the infrastructure behind Data Cloud - the company's ambitious push to unify customer data at enterprise scale - he walked out with that rarest of exit lines: genuine warmth. "A one-of-a-kind company," he wrote, "that has managed to balance a competitive drive for innovations." Not a complaint dressed as a compliment. Just the truth, said plainly.
"After 6 years, I said goodbye to Salesforce - a one-of-a-kind company that has managed to balance a competitive drive for innovations."
- Ashok Shivarudraiah, LinkedInThe Oracle Years - Writing the Rules of the Road
Before Salesforce, there was Oracle - and before the cloud, there was the database driver. Ashok spent years at Oracle International Corp working on something unglamorous and load-bearing: JDBC, the Java layer that sits between your application and your database. The plumbing behind the plumbing.
In 2015, he co-invented a patent for compacting byte arrays in database clients - the kind of optimization that saves microseconds on millions of queries and adds up to something real. In 2016, he co-invented the architecture for accessing sharded databases through a topology cache at the driver layer. Distributed computing, solved at the connection level.
His third Oracle patent tackled parallel data transfer from JDBC to data warehouses in massively distributed database environments - partition-based, size-based, ROWID-based query splitting with predicate pushdown optimization. Written in the language of someone who has actually debugged this at 2 AM.
His co-inventors at Oracle included names like Douglas Surber and Jean De Lavarene - the kind of quiet, deeply technical team you don't read about in TechCrunch but whose work runs underneath every enterprise system you've ever used.
The Salesforce Chapter - From Drivers to Data Cloud
Salesforce in the late 2010s was betting enormous resources on Customer Data Platform technology - the idea that a company should have one unified, real-time picture of every customer across every channel. Ashok joined as Vice President of Engineering and immediately got to work on the infrastructure that would make that possible.
In 2021, he filed a patent for "Segment Activation on Related Entities" - the technology that lets marketing teams target customers across related entities in a multi-tenant system without creating a separate segment for every entity type. It sounds narrow. It is, in fact, the difference between a platform that scales and one that doesn't.
Two years later, another patent: "Declarative Entity Segmentation." A declarative interface for complex segment queries with nested Boolean logic across multi-tenant databases. Translation: the ability to ask complicated questions about your customer base without writing complicated code.
Both patents reflect Ashok's characteristic approach - find the constraint in the system, solve it at the infrastructure level, and let the people above you build faster on top of it.
Five Patents. Two Companies. One Thread.
The 90% Problem Nobody Talks About
Engineering turnover in Silicon Valley runs around 20-30% annually. The average VP of Engineering accepts this as climate. Ashok treats it as a design flaw. He has publicly cited a 90%+ retention rate on his teams - in an industry where that number isn't a boast, it's a rebuke to everyone else's management philosophy.
He has been building and leading teams for nearly three decades, across Financial, Telecom, Real Estate, Hospitality, Education, and Automotive sectors. The breadth is unusual. Most engineers go deep in one vertical; Ashok went wide and then led others who went deep. It's a different kind of expertise - the kind that can translate between industries, pattern-match across domains, and build teams that actually talk to each other.
His LinkedIn lists experience "ranging from Engineer to CEO." That arc - from writing JDBC drivers to leading engineering organizations to running startups - is the biography of someone who stayed curious long past the point where they could have coasted.
The Side of Ashok Tech Headlines Miss
While architecting multi-tenant data platforms, Ashok also built FeedAKid - an HTML5 mobile app for donating midday meals to school children in India. And FeedAChild, a jQuery Mobile app for micro-payments toward social causes. Neither went viral. Neither needed to. They exist on GitHub under his @ashivaru handle, sitting next to infrastructure automation scripts and distributed computing setups, with exactly the kind of quiet conviction that doesn't need an audience.
He has spoken on blockchain at conferences in San Francisco, Washington D.C., Singapore, Dubai, and multiple major cities in India. His technical profile includes Solidity - the language for Ethereum smart contracts. An Oracle database architect who also writes blockchain smart contracts is either very curious or very restless, and in Ashok's case the evidence suggests both.
"Dad, Hacker, and Entrepreneur." The order matters more than it looks.
- Ashok Shivarudraiah's self-descriptionVoice Agents and the Bet He's Making Now
After leaving Salesforce, Ashok turned toward enterprise voice agents - the next frontier in how businesses interact with their systems and customers through natural language. He appeared on at least one podcast discussing how a small engineering team balances speed and quality across multiple engineering dimensions when building in this space.
The choice makes a particular kind of sense. Enterprise voice agents require deep systems thinking (his specialty), multi-tenant architecture experience (his patent portfolio), and the ability to lead small teams through ambiguous territory (his demonstrated skill). He is not a dilettante arriving late to a trend. He is a systems engineer choosing which layer to build on next.
He is also a mentor at the Founder Institute, the world's largest pre-seed startup accelerator. The combination of investor-adjacent mentorship and hands-on building suggests someone in the middle of figuring out his next chapter rather than someone coasting on his last one. That inflection point tends to produce interesting things.
Stanford GSB gave him the business vocabulary. Oracle gave him the technical foundation. Salesforce gave him the platform-scale experience. What he builds next won't lack for raw materials.