Ashwin Muralidharan kept the work. He changed the title.

A founder changes his job title, and a company’s story briefly becomes a story about three letters. CEO gives way to CPO. The announcement fits on a screen. The responsibilities need rather more room. On October 6, 2026, Ashwin Muralidharan became General Medicine’s Chief Product Officer after serving as its founding CEO. He continued to lead product, engineering, design and operations. For a career profile, that continuing work is the interesting place to begin.

Executive titles are useful signposts. They tell us where to direct a question, whose name belongs on an announcement and who has which seat in the organization. They are less helpful as descriptions of a working day. Muralidharan’s new title arrives with a broad operating brief, inside a company he founded with Elliot Cohen and TJ Parker in 2023. The partnership continues; its division of responsibilities has changed.

His earlier professional record offers a way to read that change. Before the founding team and its financing announcements, there was an engineering education, a factory expansion project and work associated with Fluke’s innovation team. Before becoming a founder, there was an advisory role at Amazon. Put those chapters beside one another and the profile becomes less concerned with the prestige of an office than with the practical business of making things work.

A factory before a storefront

Muralidharan studied bioengineering at Washington State University from 2009 to 2013. He later completed Harvard Business School’s Credential of Readiness in 2015. The two entries bring engineering and business into the same educational record. Neither needs to be dressed up as a childhood prophecy. Education is preparation; what someone subsequently does with it supplies the more revealing detail.

From January to May 2014, he worked on the Boardman East Line 2 Expansion Project. Chris Laurion, whose operations team he supported, described his work on a segment of the production-facility startup. His duties included training materials, Lean and 5S methods, equipment-vendor coordination, reviews of engineering and construction work, and project tracking. These are concrete responsibilities, a useful corrective to the fog that can collect around the word leadership.

Consider the unromantic variety in that list. Training materials concern whether people understand a task. Vendor coordination concerns whether the required equipment or materials arrive. Project tracking concerns whether separate pieces of work remain in step. A production line has little interest in anyone’s eloquent intentions. It asks whether the next thing is ready when the previous thing is done. There is a certain editorial severity in a factory.

Nikola Mrvaljević, a colleague, described Muralidharan’s contribution to Fluke’s innovation team through market analysis and work concerning potential acquisition targets. It adds a commercial dimension to the engineering record. The subject shifts from how an operation works to how a market works. In a company, both questions matter: an elegant solution still needs a reason for someone to want it.

The Amazon connection

At Amazon, Muralidharan served as a Technical Advisor and Chief of Staff to a senior vice president. He worked on product strategy. It is a different professional setting from a factory project, but the job description again combines technical concerns with organizational ones. The record gives us a role and a scope, rather than a convenient story about one sudden revelation.

An advisory role also occupies an interesting position in a career. The person doing the work has to understand both a proposal and the organization expected to deliver it. A technical decision sits beside a business decision; a product plan sits beside competing demands on people and time. The title itself contains that dual responsibility. It joins the language of technology to the language of an executive office.

Amazon is also where the founding partnership’s professional histories overlap. Cohen and Parker had cofounded PillPack, which Amazon acquired in 2018. Muralidharan was their Amazon colleague. When the three cofounded General Medicine in 2023, the company brought together people with a shared employer in their past and different roles in their experience. Familiarity supplied context for the partnership. Building an independent company supplied a new set of responsibilities.

Muralidharan became founding CEO. The company’s nationwide launch followed in May 2025. There is a useful distinction between those dates: founding a business and presenting it broadly to customers are separate milestones. An organization needs time to turn an idea into arrangements, systems and an actual service. The interval is part of the story, even when it lacks the convenient drama of an announcement day.

The question inside the company

Muralidharan describes an internal mantra: default to “How might we?” instead of “We can’t.” It is modest enough to be useful. The question does not promise that every proposal will succeed. It leaves space to examine a difficulty before treating it as settled. As a piece of working language, it asks for a next step.

“How might we?”

Ashwin Muralidharan, describing an internal company mantra

The phrase also gives the reader something more concrete than a personality adjective. Calling a founder visionary tells us very little about what he says to colleagues. A question tells us rather more. It places attention on the possibility of doing the work and makes the obstacle available for discussion. Whether the answer is a new system, a changed process or a smaller experiment remains an operational matter.

There is a limit to what any mantra can accomplish. A phrase cannot coordinate a vendor, write training instructions or resolve a dependency by itself. The practical interest lies in what follows the question. Muralidharan’s earlier project work makes that distinction especially apt. An invitation to find a way still needs someone to arrange the details. The cheerful part of the sentence has to survive the less cheerful part of the task.

This is why the factory entry deserves its place beside the executive appointments. It provides a vocabulary of actual work: materials, reviews, coordination, tracking. The Fluke recommendation adds analysis. The Amazon role adds strategy. None of these entries proves a fixed personality or predicts the future. Together, they give a reader several specific ways to understand the kinds of responsibilities that appear across his career.

Three founders, a new division of work

The October 2026 change puts Parker in the CEO role and Cohen in the President role, with Muralidharan as Chief Product Officer. General Medicine’s announcement says Muralidharan decided that this structure was right for the company. The continuing product and operating responsibilities are explicit. That makes the transition more precise than a bare notice that one executive has replaced another.

For a reader accustomed to the tidy hierarchies of an organization chart, the breadth of the CPO brief is worth pausing over. Product, engineering, design and operations do different work. They also depend on one another. An idea has to be specified, built, made understandable and delivered. Giving those functions a common executive point of responsibility is an organizational choice with consequences for the daily work.

A founder’s relationship to his company can therefore continue through a change in title. The responsibilities, the founding partnership and the company’s stage of development give the transition its meaning. Muralidharan’s current chapter is anchored in an operating remit that remains substantial. Readers do not need to invent an emotional drama around the announcement to find it interesting. The documented arrangement is interesting on its own.

There is also a useful restraint in reading a career this way. Funding announcements make excellent punctuation marks, but punctuation cannot carry an entire paragraph. A professional story needs the verbs between the milestones. In Muralidharan’s case, the verbs include supporting, analyzing, advising, founding and leading. Each asks something different of a person. Each belongs to a specific setting rather than an all-purpose legend about entrepreneurship.

The practical thread is coordination. A factory project requires people and equipment to meet a schedule. Market analysis requires technical possibilities to meet commercial judgment. An executive advisory role requires proposals to meet organizational decisions. A product role requires several functions to meet at a usable result. These are different settings, and the comparison is a way of reading the career rather than a claim about his private motivations. What makes the connection useful is its attention to responsibilities. It keeps the person in the story without assigning him an invented inner monologue. The work supplies enough detail to make a title worth examining.

He is now based in San Francisco, at a company whose founding team has chosen a new division of executive work. The route here passes through an engineering degree and several kinds of practical responsibility. The next chapter will be written through the product and organization he continues to lead. For now, the most revealing detail in the new title is the work that accompanied it. Three letters changed. The operating brief takes a whole sentence.