Do they think in systems, not tasks?
The job is not to do GTM work faster by hand. It’s to build the machine that does it. We want someone who, handed a recurring manual process, instinctively reaches for the version that runs itself. Someone who has built things that kept working after they walked away, and who measures their impact in leverage created, not hours logged.
Can they earn a developer’s trust?
Developer tools are different. Your users are technical, skeptical, and quick to spot inauthenticity. The plays that work for a business app fall flat here. We want someone who understands, in their bones, what it feels like to be a developer evaluating a product, and who builds GTM motions that respect that instead of spamming through it.
Are they a commercially oriented builder?
The best GTM engineers we’ve met are hybrids: they care about revenue and they can ship. Not a marketer who can’t build, not an engineer who doesn’t care whether the work moves the business. We want someone who lives in the middle and is genuinely good at both.
Do they value simplicity and pragmatism?
Simplicity is at the heart of all good systems, and GTM systems are no different. Don’t come here to build a Rube Goldberg machine of fifty chained automations. Come here because you want to get really good at achieving great things in the simplest possible way
Do they bring energy to the room?
Startups are hard. Building something from nothing is hard. Driving forward progress despite uncertainty is hard. Shitting on stuff is easy and just brings everyone else down. We have a high bar for quality but also a high bar for being constructive, positive, and excited about making things better. We’re meant to be having fun here.