Michael Darmousseh has a peculiar definition of pride. It is not the launch party, the swelling user graph, or the clever architecture diagram. It is the day a piece of software he wrote can be switched off. “Nothing makes me more proud than retiring software that I built,” he wrote publicly. “Keeping software up to date and retiring old projects is a key part of building living software.” For an engineer who co-founded a company valued in the private markets at more than a billion dollars, this is an admirably unsentimental attachment to his own output. Code, in this view, is not a marble bust. It is more like scaffolding: indispensable until the building can stand without it.
That remark also provides the cleanest way into a career spent removing friction from processes that most people would rather not contemplate. Darmousseh worked on software for organizing personal records, then on electronic agreements, then on product and shipping protection. Estate administration, contracts, warranties, claims: each is a little kingdom of forms, handoffs and consequences. His specialty has been to make the kingdom behave like a system.
The operational education
Before the API, there was the counter
The polished founder biography generally begins at the university laboratory or in a borrowed garage. Darmousseh’s public work history begins more usefully at FedEx Office. He spent time as a production operator and later as a lead project coordinator. The titles are not glamorous. They are, however, an education in queues. A job arrives, materials and people must line up, and a promise has to survive contact with the clock.
At California State University, Stanislaus, from 2005 to 2009, he double-majored in mathematics and computer science. His honors thesis focused on artificial intelligence, well before every software biography acquired an AI paragraph. He participated in the Honors and McNair Scholar programs and the Hunger Network Club. The combination is revealing without requiring mythology: abstract training, applied curiosity and an interest in people beyond the machine.
By 2012 he was writing software at Milyoni, including Ruby on Rails and Node. The old developer fossil record survives in a 2010 Stack Overflow question about a Ruby, Mongrel and ODBC connection reset. It is an ordinary debugging question, which is precisely its charm. Long before “distinguished engineer” appeared beside his name, there was a stubborn connection and a person asking why it would not stay put.
The paperwork years
A small acquisition, a durable apprenticeship
In 2014, Darmousseh joined Estate Assist as lead software developer. The service was designed to organize financial, digital and personal information, a category where technical convenience sits beside the heavier requirement of trust. DocuSign acquired the company in September 2015. Darmousseh moved with it, first as an engineering manager and then as a senior software engineering manager, staying until early 2019.
That sequence matters. Estate Assist was small enough for the software to feel close to the problem. DocuSign was large enough for teams, reliability and institutional process to become part of the engineering brief. Former colleagues describe Darmousseh as an empowering manager, technically engaged but not given to hovering. One called him a mentor and motivator; another praised his ability to push teams toward performance while remaining people-oriented. Praise on professional profiles is a naturally sweetened genre, but the details repeat: responsibility, conversation, mentorship, scale.
“Nothing makes me more proud than retiring software that I built.”Michael Darmousseh on living software
The line sounds almost comic in a trade that treats creation as the only respectable verb. Yet retirement is one of the clearest tests of good engineering leadership. A system can be replaced only if its boundaries are understood. A team can remove it only if dependencies are visible. The funeral of old code is usually organized by good documentation, steady migration and an absence of ego. Living software needs a custodian who is willing to prune.
- Mathematics and computer science at Stanislaus State, alongside work at FedEx Office.
- Ruby, Rails and Node development at Milyoni.
- Lead software developer at Estate Assist.
- Engineering management at DocuSign after the Estate Assist acquisition.
- Co-founder and engineering leader at Extend, now distinguished engineer.
Making protection programmable
The warranty was hiding an interface problem
In February 2019, Darmousseh started Extend with Woodrow Levin, Joe Moss and Rohan Shah. Their chosen terrain was extended warranties, a business that had mastered fine print without mastering affection. The founding premise was that merchants should be able to offer protection without sending shoppers into a disconnected, creaking experience. The technical answer was API-first: make plans, purchases and claims part of the merchant’s own flow.
The engineering choices were early declarations of temperament. Extend adopted serverless architecture and infrastructure as code from day one. Teams used Postman collections to test whether merchant services worked with the platform’s integrations. Scripts ran sequences of calls. Tokens could be generated automatically. The same collections moved through stages of development and, unusually, were shared with customers. “We have so much confidence in our Postman Collections that we share them with our customers,” Darmousseh said.
The quiet machinery behind a protection offer
That chain later acquired the formal grammar of a patent. Darmousseh is a named co-inventor, with Levin, Shah and Moss, on a system for mapping product catalogs across distributed systems, choosing protection offers, responding to transactions and managing what follows. Patent prose can make a shopping cart sound like a moon landing. Underneath the clauses is a straightforward achievement: the founders described the connective tissue that lets a merchant’s catalog, a customer’s choice and a service action remain part of one system.
Nineteen months after launch, Extend announced a $40 million Series B and hundreds of merchant partners. Its products expanded beyond warranties into shipping protection and, later, broader post-purchase operations. Darmousseh argued that these tools could help independent merchants offer some of the convenience associated with Amazon: choices at checkout, easier protection and a cleaner resolution when something went wrong. This was not merely a sales argument. It was the architectural one, translated into retail language. Give the smaller merchant capabilities that can be integrated rather than an empire that must be recreated.
The title after the title
A founder returns to the workbench
Many technical founders drift toward a calendar composed entirely of meetings. Darmousseh’s current title at Extend is founder and distinguished engineer, a pairing that preserves origin while emphasizing craft. His public bio is even plainer: “MCP author. I build AI tools and agents for engineers.” The undergraduate interest in artificial intelligence has come back around, now tempered by years of building systems that have to survive customers, colleagues and Mondays.
His GitHub profile, under the name “turlockmike,” is less a showroom than a busy bench. There is Hataraku, an autonomous coding agent and SDK; a chess server for the Model Context Protocol; Murl, a curl-like command-line program for MCP; Infer, a pipe-friendly agent harness; and a database for cards from the Star Wars Unlimited game. The subjects wander. The interface instinct does not. Each project gives another system a defined way to ask for something and receive a useful response.
Chess is a particularly fitting test. It offers strict rules, a huge possibility space and an immediate penalty for bluffing. Random generation, another of his MCP projects, is the comic opposite: a disciplined interface built around uncertainty. Between them sits the contemporary agent problem. A model may speak fluently, but tools still need contracts. Inputs must be legible. Outputs must be handled. Errors must be less theatrical than the demonstrations.
The projects also make his career’s geography feel less important than it once might have. Extend is headquartered in San Francisco; Darmousseh is based in Rockwall, Texas; his GitHub handle still nods toward Turlock, the California city of his university years. The work travels as interfaces and repositories. This distributed life suits the architecture he favors. Services own bounded jobs. Teams share a contract. The whole remains coherent without every part occupying the same room. Even his biography has become, in the nicest sense, serverless.
The unusual builder is not loyal to the artifact. He is loyal to the useful next state.
Darmousseh’s career offers no theatrical origin scene, and benefits from the omission. It is a sequence of increasingly consequential handoffs: a print job, a database connection, a sensitive record, an electronic agreement, a merchant catalog, a protection offer, a claim, an agent calling a tool. The work is to shorten the distance between an event and what should happen next.
There is also a quiet rebuke here to the cult of permanence in technology. The software industry loves to say it is building the future, as though the future ought to keep every dependency. Darmousseh’s “living software” suggests a more domestic responsibility. Keep the place habitable. Replace what no longer serves. Invite other people to understand the plumbing. When the old structure has done its work, thank it by turning it off.
That may be the real continuity between warranties and agents. Both promise confidence about what happens after the exciting moment. A purchase is easy; the claim tests the system. A model demo is easy; the tool call tests the system. Darmousseh has made a career in that after-space, where promises become operations. It is less glamorous than launch day, and far more difficult to fake.