Michele Pilgrim announced her arrival at Pulumi with the cheerful restraint of someone trying, and failing agreeably, to keep enthusiasm within corporate limits. She knew quickly that the company was the right fit, she wrote. Its founders were engineers who moved fast. Its culture reflected their instinct to help customers build. Then came the sentence that explained more than the appointment: her years around data platforms and infrastructure-heavy systems suddenly formed a satisfying whole.
The phrase is a neat summary of a career built around technology’s hidden floors. Pilgrim has worked across VMware, Alteryx, Delphix, DataStax, Sisense and Starburst. The logos change, as logos are paid to do. The underlying problem remains remarkably stable. These companies sell the machinery underneath other work: virtualization, analytics, test data, databases, lakehouses and now cloud infrastructure. Their products are important, intricate and largely invisible to anyone not responsible for keeping a system useful, governed and alive.
Marketing such products is an exercise in disciplined translation. Make the story too technical and it stays in the server room. Make it too airy and the engineers leave before the second slide. Pilgrim’s professional advantage begins with an uncommon pairing: a UCLA Bachelor of Science spanning electrical engineering and astrophysics. She chose marketing, but never wandered far from systems.
01 / A durable problemThe résumé beneath the interface
A career chronology can become a dull chain of job titles. Pilgrim’s makes more sense as a descent through layers of the enterprise stack. VMware helped make computing resources more flexible. Alteryx and Sisense worked on how people prepare, analyze and see data. Delphix and DataStax lived closer to the data itself. Starburst promised access across distributed stores without requiring every byte to move house. Pulumi lets developers define and manage cloud resources with familiar programming languages and software practices.
A career through the stack
The products differ. The recurring assignment is to make technically dense systems legible to the people who buy, build and operate them.
The line is not perfectly tidy, because no real career is. It is nevertheless coherent. Pilgrim has repeatedly chosen categories where a marketer must learn the mechanism before naming the benefit. That habit was visible by 2017, when she was among the VMware employees recognized on CRN’s Women of the Channel list. Channel work rewards a particular kind of clarity: the story has to survive being retold by partners, across markets, to customers with different constraints. A message that only its author can deliver is not a message. It is a monologue.
Her later roles extended that translation problem. At Delphix, she held a vice president of marketing title. At DataStax, her remit included growth marketing. Sisense put her close to analytics. By 2024, she was a public media contact at Starburst, and a later brand-and-website case study credited her as VP Marketing. The subject matter had moved from virtual machines toward distributed data, but the commercial work still depended on connecting complicated architecture to an urgent business decision.
“After spending years deep in data, data platforms and infrastructure-heavy systems, this feels like one of those moments where the pieces finally click.”Michele Pilgrim, on joining Pulumi
02 / The operator’s vocabularyGrowth is a shared noun
Pilgrim’s public comments tend to be brief, but they expose an operating philosophy. Responding to a diagram about ideal-customer progression, she offered a compact correction: “We call it Growth.” Then she specified the joint ownership, describing a tight partnership between Growth Marketing and revenue operations. The capital letter matters less than the connective tissue. She treats growth as something built between teams, not a departmental possession guarded by a dashboard.
That instinct appears again in how she writes about wins. During her time at Starburst, she celebrated a strong quarter by naming the sales development representatives, the enablement help and the technical support that contributed. The post did not hide the commercial goal. Pipeline was right there. Yet the people responsible did not dissolve into a percentage.
The celebration involved a Boston Harbor boat cruise and a Red Sox game. Pilgrim’s sign-off was wonderfully modest: “Bonus: I finally have a Boston Red Sox hat!” Corporate social media is rarely improved by more baseball caps, but it is frequently improved by a person noticing one. The anecdote also reveals her preferred scale. She can talk about enterprise AI and distributed data, then zoom all the way down to the souvenir that made a team day memorable.
This is not evidence of a grand personality theory. Public posts are edited windows. Still, the pattern is consistent enough to describe: technical fluency paired with visible credit for teams. At a company selling developer infrastructure, that combination is practical. Engineers tend to distrust theater. Communities tend to notice who receives credit. Enterprise buyers tend to ask whether the person telling the story understands what happens after the contract is signed.
03 / The Pulumi chapterWhen infrastructure learns a language
Pulumi’s central argument is unusually suited to Pilgrim’s background. The company treats infrastructure as software. Instead of confining cloud configuration to a specialized declarative format, its platform supports general-purpose languages including TypeScript, JavaScript, Python, Go, C# and Java. That choice promises more than syntactic comfort. It brings familiar software practices such as testing, reusable components, version control and continuous delivery into the work of provisioning cloud resources.
The audience is also a coalition. Developers want speed and expressive tools. Platform teams need consistency. Security leaders want policy and auditability. Finance teams care what the cloud costs. Leadership would prefer all of them to cooperate before the invoice or incident report arrives. Pulumi’s story has to hold those interests together without pretending they are identical.
Pilgrim explicitly noticed that connective ambition. In her announcement, she wrote that Pulumi’s use of general-purpose languages and AI tooling brings developers and platform engineers together. She also singled out Pulumi Neo, the company’s AI infrastructure agent. Her aspiration for the role was direct: help lead the company through its next stage of growth.
By 2026, her work was already visible around the edges of the builder community. After an AI engineering workshop, an AICamp organizer thanked Pilgrim and Pulumi colleagues for helping make the session practical, engaging and accessible to builders at different stages. It is a small public credit, but a telling one. Developer marketing earns trust through useful encounters. Accessibility here is not merely simpler language. It is the design of an experience in which newcomers can participate without making experts feel detained.
The marketer’s task is to reduce the distance between mechanism and meaning without reducing the mechanism.
04 / Precision at scaleThe category must travel intact
Pilgrim now occupies a role where every fashionable word arrives carrying luggage. Cloud. AI. Platform engineering. Governance. Developer experience. Each can become useful shorthand or decorative fog. Her career suggests she knows the difference because she has worked on the preceding layers. Data cannot power an application if it is inaccessible. Infrastructure cannot become repeatable if every deployment is a handcrafted event. A category story works when the dependencies line up.
There is also a pleasing fit between astrophysics and infrastructure marketing, even if one should resist turning education into destiny. Both deal in systems whose consequences are easier to observe than their full machinery. Both reward models that explain a great deal without claiming to explain everything. And both punish a loose relationship with scale.
The next stage at Pulumi will ask Pilgrim to make a sophisticated product clear across several constituencies while the role of AI in software work changes quickly. Her public record offers no manifesto for how she will do it. It offers something better: a sequence of related problems, tackled close to technical customers, and a vocabulary that repeatedly returns to partnership.
Her arrival also puts a marketer inside a company shaped by open-source habits. In that world, a claim can be tested in public. Code is inspected. Documentation is used under deadline. Community members compare the promise with the pull request. The brand therefore accumulates in thousands of practical encounters, many of which happen beyond a campaign’s reach. A CMO can frame the category and sharpen the invitation, but the product and its practitioners complete every sentence. Pilgrim’s record of staying close to infrastructure and distributing credit across teams suits that arrangement. It asks for authority without pageantry, and confidence that can survive contact with a terminal window.
That may be why the pieces clicked. Pulumi is not a departure from the career that preceded it. It is a compression of that career: engineering and narrative, data and infrastructure, developers and operators, product truth and company growth. The CMO’s task is to make the whole system visible. Pilgrim has been working her way toward that diagram for years.