Are marketers engineers now?
I built an entire event registration and ticketing system for a user conference because the off-the-shelf tools were too opinionated. When you buy a tool, you buy into its process. When you build one, it fits yours.

Let's say you go to a dinner party and someone asks you what you do, and you say you are "in marketing."
Then, let's say they look at your laptop screen, and they see Claude Code. They see that you are building a pretty comprehensive internal application to make your marketing job a lot easier.
And then, let's say they look at your token spend, and they can see that you have not just built a comprehensive internal application, but you've built several.
And not only are these simple little applications, but they're simple little applications that massively progress the business.
Would you actually be an "engineer"?
Marketing engineering
I recently ran a user conference for my product, and most of the off-the-shelf event tools that were available to me were too opinionated. They had obtuse legacy APIs, they had complicated user interfaces, and they had a very specific way that they wanted you to run your event.
I ended up building an entire event registration and ticketing system on top of the Luma API, Notion workers, and Supabase edge functions and compute. The registration and ticketing system fed directly into our internal CRM and customer tracking systems. I built a sophisticated promo code system so that anybody in sales or customer success could request and disseminate promo codes to customers so that they could attend. I created a native iOS and Android app to track on-site arrivals by customers and see statistics about attendees. And I built a Slack integration so that sales and customer success could be notified whenever one of their customers showed up to the event and scanned their ticket in order to get in.
This was the kind of tool that enabled me to run a user conference to ensure that all of my internal stakeholders could engage with their customers and make sure that customers had minimal waiting time when arriving at the event and could quickly get inside and enjoy the event experience.
(On top of all this, I also drove the speakers, content, and messaging for the entire event, but that's another story.)
I did all these things because this was the easiest way for me to scale myself and ensure that I could focus the bulk of my efforts on my other day-to-day product marketing responsibilities.
When you buy a tool, you buy into its process. Oftentimes, you morph your internal needs to accommodate that external vendor's process.
If you're able to build a tool, you can construct it in a way that it extends and enhances your own processes.
Execution got cheap
In the past, you would almost never consider building over buying. But today, execution got really cheap, and building is actually quite inexpensive. You spend your time defining your requirements and your specifications up front, and then you manage your coding agent to build what you need. If you're able to work hand in hand with a security team that's willing to let you experiment and gives you a safe place to do it, you can build a great many things to support your business.
As far as saving time is concerned, you can onboard an agency, and then you'd have to give them the download on everything that you want done. You could bring on a freelancer, and they would have to get integrated with your systems. Or you can burn a bunch of tokens to build exactly what you want in the same amount of time.
The build-over-buy era has arrived.
Whither SaaS
Obviously, this brings up a number of concerns about SaaS products. If you've got a SaaS product, what should you do? Well, truth be told, at the center of my entire system is a properly priced SaaS product. The Luma API enabled me to plug into the Luma workflow and the Luma ticketing system, and I didn't have to build those things on my own. And Luma was very competitively priced (just a few hundred bucks), which made it very easy for me to build on.
If you're in the SaaS game, the big thing is to own a number of sophisticated workflows and then expose those workflows through APIs and MCP servers (so that others can build on top of it and agents can connect to it).
Even the tiny little SaaS products that I'm building on my own all have APIs and MCP servers.
Think about yourself as indispensable infrastructure instead of a self-contained, per-seat-licensed product. Codify your workflows and build reusable engines.
The downsides to marketers coding
While it's true that systems thinking is the core here, it's still probably necessary for marketers to be able to own their own destiny and code. If you're running an event and you want an event landing page, in the old days, you would need several weeks to get a designer and developer to build you your site. Today, that can be done in a fraction of the time.
Any number of marketing tasks that used to require external support and several days, if not weeks, of lead time, now can be done almost instantly.
The downsides are that marketers tend to build a bunch of vibe-coded apps, which then could end up becoming abandoned or could require support and maintenance long after the marketer leaves the company. And these are legitimate concerns, of course.
There's a need for balance between things that could legitimately improve the speed and outcomes of the business and things that are here today, gone tomorrow. (Incidentally, the aforementioned event tool is a throwaway tool.)
Understanding the difference is something every organization needs to come to grips with as the builder era progresses.
The marketing engineer
Around 2023, Clay started calling the people who build growth and sales systems "GTM engineers," and the phrase turned into a job title. Clay defines a GTM engineer as someone who "combines growth judgment with AI and automation to build revenue systems." According to State of AI Marketing, more than 400 GTM engineer jobs were posted this spring.
Profound, the AI search company, did the same thing for marketing. It introduced the marketing engineer at its Zero Click conference in San Francisco on April 8, 2026, along with a manifesto, a course, a certification, and a job board. Nick Lafferty, Profound's founding marketing engineer, wrote that there was no title for the job he wanted to do, so they made one up.
Profound's manifesto describes a marketing engineer as "a full-stack marketer with the skills of a builder." The role has two jobs. The first is to watch how marketing work actually gets done and build systems that handle the repetitive parts, with people still in the loop where judgment matters. The second is to find new ways of marketing and build the systems that run them. Profound separates this from marketing ops. Ops keeps the infrastructure running, and marketing engineering uses that infrastructure to invent new ways of marketing. Lafferty's version is shorter: a marketing engineer is "part-builder, part-marketer."
It's the same instinct behind the pi-shaped marketer, and it's why the lines between marketing roles are starting to blur.
Conclusion
The marketing discipline is in a period of rapid change, as is nearly every other profession. We don't know if the "marketing engineer" title will stick, but we do know that there is little downside for marketers, particularly developer marketers, to get closer to building.

Developer marketing expert with 30+ years at Sun Microsystems, Microsoft, AWS, Meta, Twitter, and Supabase. Author of Picks and Shovels, the Amazon #1 bestseller on developer marketing.
