On a business trip to the Netherlands, Haresh Kumbhani found himself thinking about Baruch Spinoza. Then he began thinking about databases. The transition might alarm a dinner companion hoping for an evening free of work. For an engineer, it has a certain elegance: a philosopher’s attention to context becomes a way of asking which technology belongs in which situation.
Kumbhani made that connection in his 2017 essay on cloud data management. It is a useful entrance to a career spent among enterprise software, networks and startups. Here is a founder who can take the scenic route through intellectual history and still arrive at a practical engineering decision. The philosopher gets an invitation; the business requirements retain the deciding vote.
Based in San Jose, California, Kumbhani is the founder and CEO of Zymr. His work combines running a product engineering business with technical architecture and mentoring. Across his public writing and teaching, a recurring concern emerges: how to make complicated ideas usable. The question applies equally well to a cloud platform and to a student wondering whether an idea might become a company.
A career with its sleeves rolled up
His education spans electronics, computer science and business: a bachelor’s degree in electronics from the Maharaja Sayajirao University of Baroda, a master’s in computer science from New York University and an MBA from Santa Clara University. It is a combination that puts circuits, software and commercial decisions in the same conversation. Each brings a different sort of awkward question to the table.
Kumbhani’s enterprise experience includes Cisco, Qualcomm and Novell. Earlier roles also took him through companies such as Cranite Systems and Code Green Networks. His career therefore reaches beyond the familiar startup photograph of a founder beside a whiteboard. It includes the work of developing and deploying software inside businesses where the product must function after the presentation ends.
At Zymr, his responsibilities include solution architecture and technology strategy. Those are revealing duties for a chief executive to retain: they keep the connection between a commercial promise and the system expected to fulfil it close at hand. A contract describes what the customer hopes to receive. Architecture must eventually explain how the thing will behave.
He works alongside a leadership group with its own engineering and entrepreneurial histories. Co-founder Ashok Desai now serves as a board advisor; Ashwin Kumbhani is COO. The relevant connection is the shared work of building Zymr, with different people covering technical choices, operations and business direction. A founder’s story becomes more interesting when the other chairs around the table are occupied.
The customer gets to choose the problem
Zymr dates its founding to 2012. By 2017, Kumbhani was discussing cloud development through a deceptively straightforward lens: start with the customer’s business challenge. Identify the use cases and the people who will use the product. Choose the technology after those requirements become clear. This gives engineering a destination before it acquires luggage.
One of his recurring ideas is vertical slicing. In broad terms, that means organising development around a useful capability that crosses the necessary parts of a system. The point is to bring the business purpose into the engineering conversation early. A beautifully constructed component can still be a very expensive answer to a question nobody asked.
His published advice also leaves room for trade-offs among cloud providers. The market and the customer’s direction matter when selecting a platform. Cost belongs in that discussion too, alongside security and implementation. It is a practical way to approach a field whose vocabulary can make ordinary purchasing decisions sound like constitutional crises.
He took the same subject into a June 2017 essay about making technology startups successful through vertical slicing. The title is technical; the underlying concern is recognisable to anyone who has commissioned work. How can the team make progress toward something useful while preserving the ability to learn? A founder needs an answer before the development bill becomes its own strategic problem.
- 01Business challengeWhat needs solving?
- 02People & use casesWho needs it to work?
- 03Technology choicesWhat will serve that purpose?
Spinoza would like a specification
The Netherlands anecdote supplies a more playful version of that business-first thinking. Kumbhani used Spinoza as a starting point for considering databases in context. The interesting choice was to give a technical essay a human opening. A business journey became an occasion for reflection; the reflection became a discussion of engineering judgement.
That suits the traveler and history enthusiast described in his professional biography. It also suggests why the anecdote sticks. A list of technologies becomes obsolete rather briskly. The image of an engineer letting a philosopher interrupt his thoughts survives the next product announcement. There is room for curiosity even in a subject that usually arrives accompanied by diagrams.
For the reader, the pleasure lies in the unexpected company. Databases rarely get invited into the history of ideas, though people have certainly been arguing about how to organise information for a very long time. Kumbhani’s detour gives the technical discussion a personality. It makes a decision about software feel like an act of judgement by a person.
A business plan that fits on one page
His connection to the University of Baroda continues through MSU Vision 2020, which lists him as a strategic advisor on its executive team. The initiative brings alumni experience back to students and the university. For Kumbhani, mentoring entrepreneurs sits alongside his commercial work, giving his experience another audience beyond clients and colleagues.
On December 12, 2020, he and Raj Joshi presented Incubator 101, introducing students to the programme and an entrepreneurial journey with guidance. On January 10, 2021, Kumbhani presented a 37-minute session on the Lean Business Model Canvas. The scale is appealing: a business can demand years of effort, but its initial logic should survive being written on one page.
The canvas session covered a nine-step approach to developing and revising a business strategy. Its event description put the relationship plainly: “Structure Follows Strategy.” There is considerable mercy in teaching that principle before a student has hired a team or accumulated software subscriptions. An early plan can be revised with a pen; an established organisation requires rather more negotiation.
The two sessions connect naturally with his advice to software clients. Before assembling the machinery, clarify the purpose. Before choosing an organisational structure, work through the strategy. A novice founder and an enterprise customer may have very different budgets, but each benefits from making assumptions visible while there is still time to change them.
“Structure Follows Strategy.”
From the description of Kumbhani’s 2021 business model session
The listed length of his Lean Business Model Canvas webinar. A small appointment with a large question: how will the business work?
Security has a habit of joining the meeting
Kumbhani’s technical interests have long included cybersecurity. In 2017, he was discussing the responsibility businesses retain for application-level security when using cloud services. Buying infrastructure does not settle every question about protecting the software and information placed upon it. The appealing simplicity of a purchase is followed by the less photogenic work of operating it.
He returned to the subject in an October 2024 article on AI and security testing. The piece considered automated vulnerability detection and the challenges accompanying AI-assisted testing. His author biography also described time spent mentoring developers in design thinking and agile development. The pairing is instructive: new tools still arrive in the hands of people who must learn to use them thoughtfully.
There is a particular kind of founder biography hidden in these subjects. It is made of requirements, testing, deployment and professional development. Those words seldom compete with a funding announcement for attention. Yet they describe what customers live with once the announcement has passed. Engineering careers acquire substance in the details that somebody must continue to mind.
From cloud products to accountable AI
Zymr announced a partnership with Databricks in October 2023, bringing data engineering, analytics and AI into a shared service offering. In June 2024, the company announced a Gold Stevie Award in the financial AI/ML category for work on a risk engine. These are company milestones, with the engineering team’s work at their centre, rather than personal trophies to add to a founder’s mantelpiece.
The direction continues in Kumbhani’s later writing. An August 2026 commentary on agentic AI emphasises ownership, access controls, orchestration and records of autonomous actions. The concerns are concrete: somebody must be accountable for a system, and the organisation must be able to understand what it has done. A convincing demonstration is only the beginning of that responsibility.
His banking commentary approaches AI through the quality and connection of the underlying data. The two subjects belong together. An organisation needs information it can use and systems it can supervise. Read across the years, the emphasis remains recognisable: decide what the business needs, then attend to the architecture and operating work that make it possible.
Kumbhani’s stated ambition for Zymr has included making Silicon Valley’s innovation practices more widely accessible. His student teaching gives that ambition an intimate scale: one early business model, one question about strategy, one chance to reconsider a plan. His enterprise work gives it a larger setting. Both ask experience to become useful to somebody else.
And somewhere in that working life there is still room for a Dutch philosopher. It is a welcome detail in a career crowded with technical nouns. Curiosity can take the long way round. When it returns to the meeting, however, there is a customer waiting, a student with a question, or a system that needs to work. Kumbhani’s story keeps coming back to that practical appointment.