sebastian.mace

Hey everyone, I had another question for those currently working as GTM Engineers. I’m trying to get a realistic sense of how far I am from being competitive for my first GTM Engineer role. I already have hands on experience with things like API integrations, webhooks, JSON, Make, CRM systems, and building and maintaining production automations, and I’m currently going deeper into Clay and building out a GTM focused portfolio. Would anyone be willing to take a look at my resume and background and give me a rough assessment of the gaps I’d still need to close? I’d especially be curious about timeline. For example, if I can dedicate around X hours per week to learning and building projects, would you estimate I’m a few months away from being competitive, 6 or more months away, etc.? I know there’s no exact answer, but even a rough estimate from someone who hires or works alongside GTM Engineers would be really helpful. Happy to share my resume privately.

Hey everyone, I’m get some opinions from people working as GTM Engineers. I’m currently building out a GTM portfolio and learning Clay pretty deeply. Do you think it’s important for portfolio projects to show full integrations between Clay and systems like HubSpot/Salesforce, outbound tools, etc., or are strong projects built primarily inside Clay enough to demonstrate the skills employers are looking for? Some of the integration functionality requires a higher Clay plan, so I’m trying to figure out whether paying for that is actually necessary for a portfolio or if I’d be better off focusing on more sophisticated Clay workflows, enrichment, scoring, research, and automation logic. Would love to hear what you’d expect to see from someone trying to land their first GTM Engineer role. Thanks!

Hello Sayli G., I’m still waiting to receive a decision. Thanks!