A champion of people trying to build things
On May 20, the technology world lost S. 'Soma' Somasegar at 59—a Microsoft veteran and Madrona Ventures investor whose career was built on a quiet but consequential conviction: that the strength of any platform rests in the hands of those who build upon it. He spent decades translating the needs of individual developers into the language of corporate strategy, and later carried that same philosophy into venture capital, where he mentored a generation of Pacific Northwest founders. His death invites reflection on what it means to lead not by accumulating power, but by distributing it.
- A rare bridge between corporate giants and grassroots developers has gone quiet at 59, leaving a gap that will be felt across multiple generations of technologists.
- Somasegar's death arrives precisely as the industry wrestles with the questions he spent his life answering—how large platforms should treat their developer communities, and what successful technologists owe those still climbing.
- Tributes from developers, founders, and peers describe not a man measured by market share, but one whose influence lived in the careers he shaped and the communities he refused to abandon.
- At Madrona Ventures, his role went far beyond writing checks—he sat in pitch meetings, offered strategic counsel, and helped founders navigate challenges that no term sheet could address.
- The open-source and developer-relations culture he helped build at Microsoft now stands as a living legacy, reshaping how the industry's largest players engage with the people actually writing the code.
Soma Somasegar, who spent decades at Microsoft shaping how one of the world's most powerful software companies related to the developers building on its platforms, died on May 20 at the age of 59. His passing marks the loss of someone whose influence was never easily captured by titles or org charts—a technologist who believed, with rare consistency, that a platform's true power resided in the ecosystem of people willing to build on it.
At Microsoft, Somasegar rose to lead developer platforms and tools during some of the company's most consequential transitions. He became known for advocating positions that weren't always natural for a company of that scale: that openness mattered, that developers deserved genuine representation in platform decisions, and that the future favored companies willing to listen. Colleagues described him as someone who could move fluidly between the concerns of individual programmers and the strategic demands of a multinational corporation—a rare fluency that made him indispensable during periods of significant change.
After Microsoft, he joined Madrona Ventures, where he became a defining presence in the Pacific Northwest startup ecosystem. His transition to venture capital felt less like a career pivot than a natural extension of his philosophy. He invested capital, yes, but what founders remembered most was his presence—the strategic advice, the introductions, the willingness to sit with a problem long after the pitch meeting had ended.
The remembrances that followed his death painted a portrait of someone whose legacy would be measured not in earnings or exits, but in the developers he empowered and the founders he helped believe in themselves. He died at a moment when the technology industry is actively debating the very questions he spent his career answering—and his absence will be felt most acutely in the silence where his answers used to be.
Soma Somasegar, the Microsoft executive who spent decades shaping how the world's largest software company engaged with the developers who built on its platforms, died on May 20 at 59. His death marks the loss of a figure whose influence extended far beyond any single company—a man who believed, with the kind of conviction that shapes industries, that the health of a technology ecosystem depended on listening to and empowering the people actually writing the code.
Somasegar's career at Microsoft spanned multiple eras of the company's evolution. He rose through the ranks leading developer platforms and tools, a role that positioned him at the center of some of the company's most consequential decisions about how to relate to the broader programming community. During his tenure, he became known for advocating positions that were not always obvious to a company of Microsoft's size and market dominance—that openness mattered, that developers deserved a voice in platform decisions, that the future belonged to companies willing to listen rather than simply dictate.
His work on developer relations and open-source initiatives helped reshape Microsoft's reputation in communities that had long viewed the company with skepticism. He understood that a platform's power was only as great as the ecosystem of creators willing to build on it, and he pushed the company toward policies and practices that reflected that reality. Colleagues and peers described him as someone who could translate between the needs of individual developers and the strategic imperatives of a multinational corporation—a rare skill that made him invaluable during periods of significant technological transition.
After leaving Microsoft, Somasegar moved into venture capital, joining Madrona Ventures, where he became a prominent investor and mentor in the Pacific Northwest technology ecosystem. The shift from corporate executive to venture capitalist was natural for someone with his background and philosophy. He brought the same commitment to developer communities and startup founders that had defined his Microsoft years, investing in companies and offering the kind of hands-on mentorship that comes from decades of experience navigating the technology industry's complexities.
At Madrona, he became known not just for capital deployment but for genuine engagement with the entrepreneurs he backed. He attended pitch meetings, offered strategic advice, made introductions, and helped founders think through problems that extended far beyond the immediate business question at hand. For many startup leaders in the region, Somasegar represented a particular kind of technology leader—one who had succeeded at the highest levels of corporate America but retained a genuine interest in the work of building something new.
The technology industry's response to his death reflected the breadth of his influence. Developers who had worked with his tools at Microsoft, entrepreneurs who had received his mentorship at Madrona, and peers across the industry shared tributes that painted a picture of someone whose impact was measured not in quarterly earnings or market share, but in the careers he had shaped and the communities he had strengthened. He was remembered as a champion—a word that appeared repeatedly in the remembrances—of people trying to build things, whether they worked inside a Fortune 500 company or were launching a startup from a coffee shop.
Somasegar's death comes at a moment when the technology industry is actively debating questions he spent his career thinking about: How should large platforms relate to their developer communities? What responsibility do successful technologists have to mentor the next generation? How do you build ecosystems that are both commercially viable and genuinely open to new voices? These are not abstract questions in the technology world, and Somasegar's career offered a sustained argument for why they matter. His legacy will likely be measured in the companies that were built by founders he mentored, the developers who were empowered by the platforms he championed, and the culture he helped establish—the idea that technology leadership means, fundamentally, serving the people who are actually doing the work.
Citas Notables
Remembered as a champion of developers and entrepreneurs across both his Microsoft and venture capital careers— Industry peers and colleagues
La Conversación del Hearth Otra perspectiva de la historia
What made Somasegar different from other Microsoft executives of his era?
He seemed to genuinely believe that Microsoft's power came from the developers building on top of it, not from the company's ability to dictate terms. That's not a radical idea now, but it was less obvious when he was rising through the ranks.
Did that philosophy create tension inside Microsoft?
Almost certainly. You don't push a company toward openness without encountering resistance from people who see that as giving away leverage. But he had the credibility and the track record to make those arguments stick.
Why move to venture capital?
It was a natural extension of what he already believed in. Instead of shaping one platform, he could help shape dozens of companies. The mentorship part was probably more important to him than the financial returns.
What do you think he would say about the current state of developer relations in tech?
Probably that there's still work to do. The conversation has shifted, but the underlying tension between platform control and developer autonomy hasn't disappeared. He'd likely be pushing companies to go further.
Did he have a particular philosophy about failure?
From what people said about him, he seemed to view failure as part of the process, not a disqualifying event. That matters when you're mentoring founders. It gives them permission to take real risks.