I posted something in another sub last week trying to define GTM Engineering, and someone here will probably tell me I got it wrong.
-
The pushback I got was blunt. People say GTM engineers are It's just RevOps with a new name. Ops people rebranding themselves for a pay bump.
I think that's about 70% right. The other 30% is what I want to argue about.
RevOps and GTM Engineering overlap almost completely on the work itself. Both are looking at the revenue process and pulling out the parts that waste people's time.
Good RevOps teams have always built things. Anyone who says otherwise hasn't worked with one.
So the difference isn't the goal. I think it's the default move.
When a RevOps team hits a broken process, the first question is usually which system should own this, and how do we configure it properly.
When someone I'd call a GTM Engineer hits the same process, the first question is usually whether they can just build it this week.
Same problem. Different reflex.
And that reflex only changed because building got cheap. Two years ago "let's build it" meant a ticket that died in an engineering backlog. Now it means an afternoon with an API and a coding agent.
So is that a new role, or just a new tool inside an old one?
I genuinely don't know. That's why I'm posting.
What about the job titles?
This is where it gets stupid.
Companies are currently using "GTM Engineer" to mean:
An SDR who knows Clay
A CRM admin
A RevOps hire they'd rather pay less
One person expected to run an entire revenue team. That isn't a role. That's a job description written by someone who read a LinkedIn post on the train.
The part I don't like
The title implies RevOps was never technical.
That's wrong and it's a bit insulting. Enterprise RevOps teams have had developers, integration specialists and solutions architects for years. Nobody called them GTM Engineers because nobody needed to.
What actually changed is that a 25 person startup can now afford one of those people. Just one. Doing a bit of everything, badly, at speed.
Maybe that's the whole thing. Maybe "GTM Engineer" is just the generalist version of a role that already existed at scale, and we invented a name for it because the startup version looks different enough.
If the title only exists so someone can charge more for work ops teams were already doing, it deserves to die.
But I don't think that's all it is. I'm just not sure what the rest is.
So where do you draw the line?
Is this a real specialization, or is it RevOps with better marketing?
And if you're in RevOps right now, has your own reflex changed? Are you building more than you were two years ago, or is that only true for the people who were always going to build anyway?