Founding GTM Engineer

Platoapp · Berlinjunior

In short

▸Ingeniero GTM fundador que construye desde cero el motor de revenue de Plato.
▸Day-to-day: mejora de datos en HubSpot, automatización de procesos, IA en workflows y forecasting confiable.
▸Destacado: eres el primer GTM Engineer, tienes libertad para definir lo que se construye y ver impacto real en 90 días.

In ~1 minute you get: who interviews you, the likely questions answered from your CV, and your CV tailored to this job. Free, no card.

🎧Land the interview? Bring the copilot. Our free extension listens to the live interview and flashes 3-4-word anchors from your resume and prep — glance, connect, talk. Get the extension →

What they ask for

✓Experiencia práctica arquitectando HubSpot desde cero (objetos, propiedades, estructura de datos)
✓Experiencia en herramientas de outbound/enriquecimiento (ej. Clay)
✓Construcción de workflows con IA/LLMs en entornos productivos
✓Rigor en datos: análisis de funnel, detección de datos corruptos, medición de impacto
✓Pensamiento sistémico y secuencial, no centrado en tickets
✓Capacidad de defender decisiones bajo presión

Don't tick every box? That's normal — your free dossier shows your gaps and how to cover them in the interview.

HubSpotGrainClaySales NavigatorAI/LLMsprompt designagentsenrichment waterfallsorchestrationforecasting

Who should you write to at Platoapp?

Your free dossier identifies the people who'd interview you — their background, what they value, and how to reach out so you stand out before applying.

Your responsibilities We're looking for Plato's first GTM Engineer: the person who brings RevOps to Plato as a discipline and builds our revenue engine as a product, not a ticket queue. Pipeline, conversion, and revenue per headcount are your metrics. You're inheriting real infrastructure - HubSpot as our source of truth, a custom-built deal-scoring app, call intelligence via Grain, and company-wide AI access - but the layers underneath are still unbuilt: clean data, automated process, real forecasting rigor, AI-driven workflows. That's the job. This is a team-of-one role that's essentially a sandbox: a direct line to the founders, a mandate to change how we work, and no playbook telling you what to build first. If you want to build the infrastructure behind a revenue engine from the ground up and see your own builds move real numbers, let's talk. g. Clay or similar) You've built with AI/LLMs - prompt design, agents, or AI-powered workflows - in real production work Strong data rigor: you can read a funnel, spot where the data is dirty, and quantify the impact of a fix before you build it You think in systems and sequencing, not tickets - and can defend your reasoning under real pushback Nice-to-haves: Experience as an early GTM-Ops/RevOps hire at another startup Familiarity with our stack or similar: Grain, Sales Navigator-style outbound tooling Comfort with unit economics (CAC, ACV, payback) Experience with mid-market, multi-stakeholder B2B deal cycles Why us? You'd be Plato's first-ever GTM Engineer - not inheriting someone else's system, but building the one that doesn't exist yet, and introducing RevOps as a discipline at a company that's never had one. A direct line to the founders, real budget for tooling, and a mandate to change how the revenue team works, from day one. This is an individual contributor role today - you'll be doing the building yourself, not managing a team. If this function grows as Plato scales, you'd be the one shaping what it becomes, not stepping into a structure someone else already defined. Because the function touches everything - data, process, automation, AI - you won't be boxed into one lane. If you want to see your own build move a real number within your first 90 days, this is that role.

Don't apply unprepared

We research who's interviewing you, tailor your CV and rehearse you live — first one free.