What a GTM engineer actually does (and how to hire a good one)
I get asked this a lot. Someone sees "GTM Engineer" on my profile and asks if that's a sales job, a marketing job, or a developer job.
It's a bit of all three. Here's the plain version.
What a GTM engineer is
GTM stands for go-to-market. A GTM engineer builds the system that finds your buyers and gets them into conversations with you.
Not one piece of it. The whole thing.
A marketer writes the copy. A salesperson runs the calls. An SDR sends the emails. A GTM engineer builds the machine that does the middle part, then keeps fixing it based on what comes back.
The "engineer" part matters. This job is closer to building software than writing ads. You are wiring tools together, moving data between them, and automating steps that used to be done by hand.
How the job actually works
Here's my week, more or less.
I pick who to target. Not "SaaS companies." Something tighter, like ops leads at freight brokers with 50 to 500 people who just posted a hiring ad. The tighter the definition, the better everything downstream works.
I build the list. Pull the companies, find the right people, get their emails, check the emails are real. Bad data kills a campaign before anyone reads a word.
I set up the sending. Separate domains, new inboxes, warm them up for a few weeks, cap how many go out per inbox per day. This part is boring and it is where most campaigns quietly die.
I write the emails. Usually four. Each one gives a different reason to reply. One offer per test, so I can actually tell what worked.
I handle the replies. Everything gets sorted the moment it lands. Interested ones hit Slack in seconds. The rest get filed without anyone looking at them.
I read the numbers and change one thing. This is the actual job. Not sending more email. Working out why the last batch did what it did.
I wrote more about that last part in the outbound numbers nobody shows you, if you want the detail on what I look at.
You can see my full six-stage setup on my process page.
Why companies hire one
Most teams have the pieces already. A CRM here, a sending tool there, someone's cousin who knows Clay a bit. What they don't have is one person who owns the whole path from "who should we talk to" to "meeting booked."
So things fall between the cracks. The list is good but the emails land in spam. The emails are great but the list is wrong. Replies come in and sit for four days.
A GTM engineer owns all of it, so there is nobody to blame but them. That's the point.
How to find a good one
I'll be straight with you here, including the parts that don't flatter people like me.
Ask what they've broken. Anyone can show you a nice Clay table. Ask about a campaign that flopped and what they did next. If they can't tell you exactly why it failed, they weren't really reading the data.
Ask who they'd say no to. A good one will tell you when outbound isn't the right move yet. If your offer isn't clear, no amount of email fixes that. Someone who says yes to everything is selling you activity, not results.
Check they know deliverability. Ask how they'd warm up a new domain, or what bounce rate they aim for. If they only talk about copy and lists, your emails are going to spam and nobody will notice for a month.
Make them explain their last build end to end. Not the tools. The order of decisions. Why that ICP, why that angle, what they'd change. Tool names are easy to memorise. The thinking isn't.
Skip the tool specialist. Being great at one tool is not the same as owning the system. Tools change. The system is the thing.
One last thing
If you're hiring for this, be honest about what you actually want. Someone to run a process you already have is a different hire from someone to build one from nothing. Those are not the same person, and asking for both at one salary is why a lot of these roles don't work out.
I'm Malik. I build and run cold outbound systems for B2B and SaaS teams, end to end. You can see the work I've done, connect with me on LinkedIn, or book a call if you want to talk through your setup.