Clay Calls It GTM Engineering. Profound Calls It Marketing Engineering.

Clay’s September 3 profile of Osman Sheikhnureldin presents a head of GTM Engineering at the company that says it turned the phrase into a job title. Five months earlier, Profound used its Zero Click San Francisco event to launch Marketing Engineer. It paired the title with a course, certification, job board, and its own open role.

The two companies are selling nearly the same raw material: a marketer who can use data, automation, and agents to build systems instead of completing every task by hand. They are selling it to different boxes on an org chart.

Clay places the work in go-to-market. Its definition is a person who combines growth judgment with AI and automation to build revenue systems. The company says more than 400 GTM Engineer jobs were posted in the spring, with a $160,000 median salary according to Pave. It also says 7 bootcamps, including its own cohort program, teach the work.

Profound places the work inside marketing. Its Marketing Engineer manifesto separates the role from marketing operations: Ops keeps the infrastructure running, it says, while marketing engineering uses that infrastructure to create new marketing systems. The company’s own listing asks a Marketing Engineer to build agents, data infrastructure, publishing and distribution connections, and reporting systems. The posted base range is $135,000 to $200,000.

That title choice looks cosmetic until someone has to approve the hire.

We covered the wider marketing-engineer argument last week: the valuable work is moving beyond filling a campaign queue and into building the machinery that improves it. The new question is where that person belongs. Put them in revenue and their scorecard starts with lead quality, account signals, routing, and pipeline. Put them in marketing and it starts with customer insight, campaign learning, content distribution, and measurement. The underlying skills overlap. The authority and success criteria don’t.

The job is real. The boundary is still being written.

Clay’s current example is Sheikhnureldin. The company describes his earlier work at Rippling as building self-serve tooling and experimentation for growth, including an outbound machine that sent more than 200,000 cold emails a week. At Clay, the job begins with the constraint slowing growth, then uses automation and better data to remove it.

Profound’s description runs the same play from the marketing side. Its role owns agents for content drafting, social engagement, lead follow-up, sentiment monitoring, campaign reporting, and the systems connecting performance, AI citation tracking, attribution, and pipeline impact. The listing defines a systems role attached to marketing outcomes, not a conventional content role.

The public career stories make the appeal clear. Petra Hajal, now founder of RevenueHoop, describes the upside in Clay’s Series C announcement:

“Discovering Clay changed the trajectory of my career. I made an impact on my company, Oyster, got promoted, and started thinking bigger, building faster, and finally betting on myself.”

Umar Farooq Adam, GTM Program Manager at Hitachi, describes a similar internal path. It matches the knowledge-engineer work happening inside marketing teams, where the job is often maintaining the inputs and automation that turn scattered knowledge into usable work:

“Implementing Clay at Hitachi changed my career. What started as a personal project rolled to my entire team, fueled my promotions, and earned me company-wide recognition.”

Those are customer stories, not an independent measure of the category. Both vendors also profit when the category expands. Clay sells the platform and training around GTM Engineering. Profound sells a platform, course, certification, and job board around Marketing Engineering. Their enthusiasm is a product strategy as well as a labor-market observation.

That doesn’t make the job imaginary. It means a hiring manager shouldn’t borrow either vendor’s title before deciding what problem the person will own.

Start with the system, not the title.

For a 5-to-30 person company, a dedicated hire is rarely the first move. The first move is to name one recurring decision that is currently assembled by hand. It might be which accounts deserve attention this week, which customer objection is becoming a pattern, or which campaign result should change next month’s plan.

Then write the job around the system that makes that decision better. What inputs does it need? Who checks the output before money or a customer is involved? Which outcome proves it worked? A GTM Engineer should have a crisp answer about revenue work. A Marketing Engineer should have one about marketing work. If neither answer exists, the role is a title looking for a budget.

The job-title fight will continue because it gives both vendors a category to own. Small teams don’t need to take a side. They need a person, or an existing marketer with room to grow, who can turn one pile of scattered work into a system the rest of the company can inspect and use.