Hey Sebastian, I’ve personally never hired for a GTM role, and I’m currently in my first GTM position, so take this with a grain of salt.
From what I’ve seen online and across job boards, though, technical skills alone usually aren’t enough if you want to get hired as a GTM Engineer.
I think it helps a lot if you can show that you’re able to take an ICP definition, segment the market, identify the right accounts and people, and actually reach them using tools like Clay. That probably gives you a better chance than only showcasing sophisticated workflows.
And if we’re talking about technical skills specifically, I think being able to connect Clay with systems like HubSpot, Salesforce, and other outbound or RevOps tools is very valuable.
Companies rarely use Clay in isolation. Showing that you understand integrations and can make Clay work as part of a larger GTM stack would, in my opinion, significantly improve your chances of getting hired.
Also, I’d recommend following Joe Rhew on LinkedIn. He posts a lot of useful content about the GTM job market and does a good job of showing that “GTM Engineer” is really an umbrella term.
There are different types of GTM Engineer roles, and each one has a slightly different focus and requires a different mix of skills.
I’d suggest checking out his content to understand those different categories. It can give you a better idea of what to learn next and what kinds of projects you should add to your portfolio to be more competitive in the job market.
Hope I helped!